Skip to main content
cd ../notes (back to all notes)
category
"Content Systems"
read
8 min
date

Do AI Content Detectors Matter for SEO?

Google's guidance on AI content asks about accuracy, value and purpose. Here is what to review in an AI-assisted draft instead of a detector score.

Does Google use AI detection scores to rank content?

Google’s published guidance gives no sign that it does. Google’s guidance on AI-assisted content is about accuracy, value and purpose, and none of Google’s pages on AI-generated content, generative AI content, helpful content or spam policies asks for a detector score, a percentage of human writing or any test of whether a tool wrote the words.

So a detector score answers a question Google’s guidance doesn’t ask. If you run every draft through a detector and rewrite until the number drops, you spend your review time on something Google’s guidance never mentions.

Google’s position has been public since its 2023 post on AI-generated content, which says appropriate use of AI or automation is not against its guidelines. Google says AI can help people create useful content. AI-assisted work is held to Google’s spam policies like any other content.

Google does draw a line, and it is about purpose and value. Google says using automation, including AI, to generate content with the primary purpose of manipulating search rankings violates its spam policies. Its 2024 announcement says the scaled content policy applies whether content is produced through automation, human effort or a mix of both. What matters is whether the page was made to help people and whether it adds value for them.

Two questions get blended together when you lean on a detector:

  1. Who typed the words? A detector tries to estimate this. Google’s guidance asks about the second question instead.
  2. Is the page accurate, useful and made for readers? This is what Google’s guidance asks about, and a detector score is a different measurement.

If you’re building a small content system with AI in it, the review step should answer the second question. My post on a simple content engine for a tiny team covers where AI fits in the weekly flow. This post is about the review gate before anything goes live.

What does Google’s spam policy say about AI content?

Google’s spam policy targets scaled content abuse: many pages generated mainly to manipulate search rankings rather than help users, no matter how they were created. Google’s 2024 announcement of the policy says it covers automation, human effort or a mix of both.

Google’s spam policies define scaled content abuse as many pages generated for the primary purpose of manipulating search rankings and not helping users, typically large amounts of unoriginal content that provides little or no value. One of the listed examples is using generative AI tools, or similar tools, to generate many pages without adding value for users.

For a small business, the risk sits in patterns like these:

  • Publishing dozens of near-identical pages, such as one page per town with the same text and a new place name.
  • Turning out posts on every keyword a tool suggests, whether or not your business has anything to say about it.
  • Publishing drafts without reading them, because the output looked finished.
  • Stitching together paragraphs from other sites without adding anything of your own.

Before you publish a set of similar pages, ask three questions about each one. Would it still help someone if it were the only page you published? Does it include facts that belong to that page’s subject and no other? Would a customer miss it if it disappeared? If the answer to any of them is no, merge it into a stronger page or leave it unpublished.

Each of the patterns in that list is a question of purpose and value, which is what the policy describes. A detector score measures something else, so passing or failing one doesn’t settle whether a page fits the policy.

Google says it uses automated systems to find spam, however the spam is produced. Making each page sound more human doesn’t change what the policy describes, which is many pages made mainly for rankings. The practical fix is to publish fewer pages that each earn their place.

What should you check before publishing an AI draft?

Check what Google’s guidance asks about: accuracy, added value, a clear purpose and honest authorship. A short checklist covers it.

The questions below are adapted from Google’s guidance on helpful content and on generative AI. They work as a review gate for any draft, whoever or whatever wrote the first version:

Question to askWhat to look for in the draft
Is every fact accurate?Names, numbers, dates, prices and process steps you can confirm from a source or your own records
Does it add something new?Your own examples, decisions, process or data, not a rewording of the top search results
Does it describe the topic fully?The answer a customer needs to act, including limits and what it depends on
Would you send it to a customer?A page you’d share with someone who asked this exact question
Is it made for a real audience?People who would find it useful if they came to your site directly

The first row matters most for AI drafts. Google’s guidance asks for accuracy in AI-assisted content. Check the small details hardest: a setting that moved, a form name that changed, a rule stated more broadly than it applies. Those are the details a customer acts on, so confirm each one against a current source.

The second row is where your business shows up. Google’s guidance warns against pages that add little or no value for users. Add what only your business knows: how you price a job, which questions customers ask on the first call, what you have learned from doing the work. That knowledge makes a post useful to the person reading it, and it is the part a generic draft can’t supply.

Write the review gate down and give it one owner. Here is a simple version for a small team:

  1. Write the brief before the draft. Name the customer question, the answer you want to give and the sources or records the facts should come from. Give the brief to whoever drafts, person or tool.
  2. Mark every fact during review. Highlight each name, number, date and instruction in the draft, then check each one against its source. Anything you can’t confirm comes out.
  3. Add one thing only you could add. A real example, a decision rule you use, a price range you stand behind. If you can’t think of one, ask whether the post needs to exist.
  4. Read it as the customer. Does the first paragraph answer the question? Would you send this page to someone who asked? If not, rewrite before it goes live.
  5. Record who approved it. One name and a date, kept with the post, so that when a fact changes you know who owns the page and when it was last confirmed. That person is the byline, or the reviewer named on the page.

Put this checklist into the brief your AI tool works from and into the approval step. My weekly newsletter system post shows one way to set up an approval lane so drafts don’t go out unchecked.

When should you tell readers AI helped write a post?

Tell them when a reader would reasonably wonder how the content was made. Google’s guidance recommends AI or automation disclosures for content where someone might ask “How was this created?” and suggests adding them when readers would reasonably expect them.

Google frames this as part of three questions to ask about content: Who created it, How it was created and Why. For most small-business posts, the answers can be short.

  • Who. Google encourages accurate bylines where readers might expect one. Put the real person who wrote or reviewed the post on it. Don’t invent an author to make a page look more expert.
  • How. If AI drafted a large part of the post, a sentence explaining how it was used, and who checked it, answers the question before a reader has to ask. For example: “This post was drafted with an AI writing tool from my notes, then fact-checked and edited by me.”
  • Why. The answer should be that the post exists to help a customer or prospect, not mainly to attract search visits.

The Why question is the one I’d use as a final filter. Before publishing, ask whether you would still want this page if search engines didn’t exist. If a customer could read it and make a better decision about working with you, keep it. If it only exists because a keyword tool said so, cut it or fold it into a page that already helps someone.

If you want your pages to show up in AI answers as well, the work is on the pages themselves. My post on why AI search skips local service businesses covers what answer engines need to see, and the guide to blocking Google AI training without leaving AI Overviews covers the crawler settings.

Frequently asked questions

What happens to a site that breaks Google’s spam policies?

Google says sites that violate its spam policies may rank lower in results or not appear in results at all. That applies to scaled content abuse along with its other spam policies.

Do Google’s search quality raters decide where my pages rank?

No. Google says rater data is not used directly in its ranking algorithms. Raters help Google check whether its systems are working, and Google suggests reading their guidelines as a way to assess your own content.

Do health or money topics need extra care when AI helps write them?

Yes. Google says its systems put more weight on reliability for topics that can affect people’s health or finances, however the content is produced. Have someone qualified check those posts before they go live.

Do AI Overviews need a different kind of content?

No. Google says there are no additional requirements to appear in AI Overviews or AI Mode. The same Search technical requirements and people-first content guidance apply to its AI formats and to regular results.

Start a conversation

What could work better?

I look at what is breaking, what you already use, and what your team will realistically adopt.

Let’s talk