An article goes out under a client's name with an invented statistic and an internal link to a page that doesn't exist. The client's marketing manager finds both in ten minutes, and the damage costs more than the article was ever worth, because now every future deliverable gets read with suspicion. Between draft and client there has to be a gate: a fixed set of checks with a pass or a fail, run on every article, every time.
A gate is a check anyone can run
An editor's taste doesn't scale to the volume a content retainer demands, and taste varies by editor, by article, and by how tired the editor is. A gate is different: it's binary, it's written down, and it gives the same answer whoever runs it. "Does every number have a source the reader could open" is a gate. "Is this good" is an opinion.
Gates don't replace editorial judgement. They protect it. When the mechanical checks are done by checklist, the editor's attention goes to the argument, the angle and the client's voice, which are the things only a human can judge.
Three gates cover what actually goes wrong: facts, intent and structure, and links and metadata.
Gate one: every claim survives a source check
AI drafts invent statistics, studies and quotes, and tired human writers do the same by half-remembering. The gate is strict because the failure is expensive: a number appears in the article only with a named source the reader could click, and a claim with no source either becomes qualitative or comes out. A study mentioned by name gets found before it gets published, because citing research that doesn't exist is the single fastest way to embarrass a client. Generators that attach citations make this faster to check, never unnecessary.
Client facts get the same treatment. Prices, service areas, guarantees, product names and anything phrased as a promise get checked against the client's actual business. The client knows their own offer better than you do, so they will catch what you don't, and an invented claim under their name reads to them as carelessness with their reputation.
Gate two: the page matches the search it targets
Open the target query and look at what ranks. If the query wants a how-to and the draft is a sales page, no amount of polish fixes it, and this is the most common way a well-written article fails. The draft should answer the searcher's question within the first screen, then earn the rest of the reader's time. Keyword strategy per client covers how the target got chosen; the gate checks the draft actually serves it.
Structure is the measurable half of this gate: one H1, headings that follow a hierarchy, paragraphs short enough to scan, enough substance for the page type. A deterministic content scorer is the right instrument here, because it measures form the same way every time, so the same page always gets the same score and two scores are comparable. What a scorer cannot do is tell you whether the claims are true or the advice is any good. It measures form, not correctness, which is exactly why gate one stays human.
Gate three: links, images and metadata resolve
Internal links point at pages that exist on the client's site. This needs saying because generators asked to add internal links will invent plausible-looking paths unless they're given real targets, and a human skimming a draft won't spot the difference. Click every one.
External links go to primary sources, resolve without errors, and never point at the client's competitors. Images carry alt text and are actually licensed. The title and meta description read correctly at SERP length, and they're unique against the client's other pages, because two pages with the same title compete with each other before they compete with anyone else. The free SERP snippet preview shows the title and description as Google would display them, which settles the length question in seconds.
Fail closed, and keep the record
When a gate fails, the article goes back a stage. It never goes forward with a note attached, because a note is a way of publishing a known defect. This feels slow the first month and stops feeling slow the first time a gate catches a fabricated statistic on a page the client planned to run ads to.
Keep a simple record of which gate failed per article. The pattern is the payoff: if most articles fail the intent gate, the briefs are weak, and if most fail the link gate, the drafting setup isn't getting real link targets. A gate that fails often is telling you where the pipeline leaks, which is cheaper to learn from a checklist than from a client.
What to take away
- A gate is a binary, written-down check that gives the same answer whoever runs it, which is what lets quality survive volume.
- Every number needs a source the reader could open, and client facts get verified against the client's real business before anything ships.
- A scorer measures form and does it consistently, so use it for structure, and keep the truth of claims as a human check.
- Fail closed: an article that fails a gate goes back a stage, and the record of which gates fail tells you where the pipeline leaks.
Next
Once an article clears the gates, it still has to reach the client's site intact. Publishing to a client's CMS covers access, clean publishing and proving the page is live.