AI-generated. Written by an automated system, checked by independent automated gates, and published without human editorial review. How we label and verify.
What happened when we audited 42 AI-assisted articles for SEO
We set out to validate our own rules by auditing 42 published posts against the checklist we’d been telling ourselves we followed. One of those rules was supposed to be tracked and enforced; it wasn’t. Sixty seconds of counting made this concrete: 1 of 42 passed our core rule set; 21 were critical failures where the target keyword was missing from the body and the first 100 words; 20 had no target keyword assigned in our content system at all.
What we saw, exactly
We opened each live article and checked three things: was there a target keyword recorded in the system, was that keyword present in the first 100 words on the published page, and did the body include the keyword at least three times with one occurrence in a heading. The facts were blunt. Only one article satisfied those checks. Twenty-one articles had a recorded keyword but it never appeared in the first 100 words or the body; oddly, most of those put the word only in a heading. Twenty had no recorded keyword tag, so the writers never had that requirement to follow. That pattern explains why search visibility lagged without any obvious decline in writing quality.
How the trace led to one mundane root cause
We traced each article back through the handoffs we control. The surprising, and embarrassingly simple, finding: the publishing process we used never actually handed the writer a target keyword as a hard requirement. The brief template had a field, but the field was empty for nearly half the catalog because the value never flowed from planning into the writing step. That meant writers and the editors downstream had zero mechanical prompt to place the keyword in the opening 100 words or mention it three times—so nothing downstream could realistically hit the rule.
The experiment that convinced us
We changed one thing and nothing else. We made the target-keyword requirement impossible to ignore in the writer’s assignment: the exact keyword had to appear in the first 100 words, at least one heading, and at least three total mentions. Then we watched the next publish. The next article published under that constraint contained the target keyword three times total, once in the first 100 words, and once in a heading. We verified this by an independent count of the live text. That single publication was the turning point—the moment the numbers stopped being abstract and became proof.
The rule that fell out
If you want the on-page signals you claim, make the signal a non-optional, visible requirement before writing begins. Concretely: require the exact target phrase in the writer assignment and check the published page for at least one appearance in the first 100 words, one in a heading, and at least three total mentions. That rule is what produced the immediate change.
A representative detail (taste, not a template)
For clarity: we required the exact phrase used as the target keyword to appear within the first 100 words of the draft. That single, tight requirement produced the correct behavior from the next draft. The full, tested, runnable version of our enforcement—forms, checks, and verification scripts—lives in the members’ library; this article stops at the demonstration of the result.
A counter-example
Not everything failed. One article in the original batch had decent search performance despite missing the keyword in the first 100 words because it ranked on topical relevance and strong external links. So the rule is not an absolute necessity for every piece; it is a reliable corrective where on-page signals are the controllable lever and where catalog-wide consistency matters.
How we know
The numbers come from our audit of 42 posts on 2026-07-25 and the trace that identified the missing assignment step; the post-fix verification of the next published article was completed on 2026-07-24 and independently counted on the live page. The pattern before the fix—keywords appearing zero or one time, often only in a heading—matched the set of pages that failed our checks.
Will this always fix organic traffic?
No. This change corrects a mechanical gap that prevents writers from meeting stated on-page rules. It will improve the probability that your on-page signals match your briefs, which helps indexing and relevance signals, but traffic depends also on competition, backlinks, and query intent.
How disruptive is the fix to workflow?
Minimal. The change we tested is procedural: make the keyword a required visible field in the writer assignment and verify the published text. It required one tiny UI change and one verification step after publish. The full operational implementation details are in the members’ library.
Does this apply only to AI-written articles?
No. Any content where the planning and publishing handoff can drop a requirement benefits from the same check. We were auditing AI-written articles for SEO because much of our volume used AI-assisted drafts, but the root cause is handoff fragility, not the presence of AI.
We fixed a silent mechanical leak and the next article proved the leak mattered. Fix the handoff and you stop relying on luck.
Sources: internal audit of 42 published posts and post-fix verification, 2026-07-24 — 2026-07-25.
What Google’s documentation actually asks for
Google does not object to AI assistance as such. Its Search Central post on the subject says appropriate use of AI or automation is not against our guidelines. The line it draws is purpose: using automation with the primary purpose of manipulating ranking in search results violates its spam policies. The spam policy on scaled content describes abuse as when many pages are generated for the primary purpose of manipulating rankings rather than helping users.
The newer page on generative AI content is more practical. It asks site owners to focus on accuracy, quality, and relevance, and says this review also applies to metadata such as title elements, meta descriptions, structured data and image alt text. An audit of AI-assisted articles that only reads the body misses half of what Google tells you to check.
On the specific on-page elements, the documentation is concrete:
- Titles. Google asks that every page have a title specified in the title element, that titles be descriptive and concise, and it lists avoid keyword stuffing among its best practices.
- Meta descriptions. The snippet guide says Google primarily uses the content on the page to build snippets and may use the meta description when it describes the page better. It recommends you create unique descriptions for each page.
- Headings. The SEO Starter Guide says semantic heading order helps screen readers, but from a search perspective it doesn’t matter if you’re using them out of order.
- Repetition. The same guide warns that keyword stuffing is against Google’s spam policies.
- Structured data. The general guidelines say don’t mark up content that is not visible to readers, and note that the quality rules are not easily testable using an automated tool.
Google’s helpful content page also asks whether you are writing to a word count because you think Google has a preferred word count. Its answer is that it does not.
How this squares with our audit
Our rules were more specific than Google’s documentation. We required the exact target phrase in the first 100 words, in at least one heading, and at least three times in total. The pages cited above do not prescribe counts like these. They describe what helps a page get understood and what crosses into stuffing. Our three-mention rule sits well below stuffing, and its purpose was consistency, not a ranking trick.
The audit’s numbers were about process, not about Google. One of 42 posts passed. Twenty-one had a recorded keyword that never reached the body or the first 100 words, and most of those put it only in a heading. Twenty had no keyword assigned at all. The root cause was that the target keyword never flowed from planning into the writer’s assignment. Google’s guidance cannot fix a missing field in a brief. Only a check of the published page reveals it.
The counter-example in this article fits Google’s framing as well. One article ranked on topical relevance and strong external links despite missing the keyword early. On-page signals are one controllable lever, not the whole picture.
Checklist for an SEO audit of AI-assisted posts
- Confirm every post has a target phrase recorded in your content system before drafting starts.
- Check that the brief actually passes that phrase to the writer, human or model.
- Count the phrase on the live page: first 100 words, headings, and body.
- Read the title element and meta description for each post and flag duplicates or boilerplate.
- Fact-check AI-written metadata, alt text and structured data, not just the article body.
- Compare structured data against what readers can actually see on the page.
- Look for repetition that reads as stuffing and cut it.
- Re-audit the next published post after any fix, using an independent count.
More questions
Does Google penalize articles because AI helped write them?
Not by itself. Google says appropriate use of AI or automation is not against our guidelines. What it targets is content made mainly to manipulate rankings, especially at scale, however it was produced.
Should the meta description repeat the target keyword?
Write it for the page first. Google says it primarily uses the content on the page for snippets and uses the description when it is a better summary. A unique, accurate description does more than a repeated keyword.
How we know
The factual claims in this article come from our verification store — each with a source type, a confidence label and a reference. The method is documented on How we know.
– The root cause, once traced, was mechanical rather than a writing-quality problem: the publishing pipeline had never actually been passing the target keyword to the writer in the first place, so nothing downstream could realistically hit it. | source: first-hand experience | conf: verified | ref: root-cause trace, 2026-07-25
– Auditing your own published output against your own stated rules, rather than assuming the writing process is doing what the brief says it does, surfaced a gap that had been live and silently affecting search visibility across nearly the entire catalog. | source: first-hand experience | conf: strong | ref: synthesised conclusion, 2026-07-25
– After fixing the pipeline to hand the writer a hard requirement — the exact keyword in the first 100 words, at least one heading, and at least three total mentions — the very next article published hit the keyword 3 times total, once in the first 100 words, and once in a heading, verified by an independent count against the live published text. | source: first-hand experience | conf: verified | ref: post-fix verification, published article, 2026-07-24
– Before the fix, articles were typically landing the target keyword zero or one time, almost always buried only in a heading rather than the body — the exact pattern most likely to fail a real SEO check even though a keyword was technically present somewhere on the page. | source: first-hand experience | conf: verified | ref: pre-fix pattern across audited articles, 2026-07-25