Outrings
AI agents and automation

Why is AI-generated SEO advice usually wrong?

Four reasons an assistant gives you outdated, generic or inapplicable SEO advice — and the one change that fixes most of it.

4 min read
Short answer

Because SEO advice ages badly, the training corpus is dominated by low-quality repetition, the model cannot see your site, and it has no way to know which of the twenty things it could suggest matters for you. Give it a real measurement of your site and most of the problem disappears — the model is a good analyst and a poor instrument.

Reason one: the corpus is mostly noise

SEO is one of the most heavily written-about topics online, and the great majority of that writing is content marketing repeating the same twelve tips. A model trained on the open web has read that material thousands of times and genuinely novel technical guidance perhaps once. The statistical centre of "SEO advice" is therefore the listicle, and that is what you get by default.

This is why the advice feels familiar. You are receiving the average of everything ever written on the subject, which is a reasonable starting point and never a diagnosis.

Reason two: it ages badly and the model cannot tell

Practices that were correct at some point remain in the corpus permanently, and nothing marks them as expired.

  • Keyword density targets. A number to hit was never real and has been actively counterproductive for over a decade. Still confidently quoted.
  • The meta keywords tag. Ignored by every major engine for many years. Still suggested.
  • Exact-match anchor text everywhere. Now a spam signal.
  • Submit your site to search engines. Replaced by sitemaps and ordinary crawling.
  • Word-count minimums. A correlation mistaken for a rule; padding a page to reach a number makes it worse.

Reason three: it cannot see your site

This is the largest factor and the easiest to fix. Asked what to improve, a model with no observation of your site suggests the things most sites need. If your titles are already good and your problem is that your entire content renders client-side and no crawler can read it, you will get advice about titles.

Worse, the advice will be correct in general, which makes it hard to reject. You will spend a weekend improving something that was not the constraint.

Reason four: no sense of proportion

Even given a list of real problems, a model with no effort or impact data will present them flatly. Twenty suggestions, all phrased as important. The one that would move the needle sits between two cosmetic ones. Prioritisation requires knowing both what a fix costs and what it recovers, and neither is inferable from the description of a problem.

The pattern across all four: models are strong at explaining, comparing and prioritising when given facts, and weak at supplying the facts. Used as an analyst, an assistant is genuinely useful. Used as an instrument, it produces the average of the internet.

The fix, in one step

Measure the site, then hand the measurement to the model.

  1. Run a real audit and take the structured result — findings, evidence, effort, and what was not covered.
  2. Paste it into the conversation, or connect a measurement tool so the assistant fetches it itself.
  3. Ask the question you actually have: what should I do first, and why does it matter for this site?
  4. Make one change.
  5. Re-measure and confirm the specific finding cleared before moving on.

The difference in answer quality is not subtle. The model stops generating plausible advice and starts reasoning about your evidence, which is the task it is genuinely good at.

What our audit reports about this

Every item below is measured directly, not inferred. Run it against your own site and the result names the exact rule or header responsible.

  • What is measurably wrong with your SEO right now — titles, descriptions, canonicals, headings, indexability — with the observed value for each.
  • Whether your content is present in the raw HTML or added by JavaScript, which is frequently the real constraint and is invisible in a browser.
  • An effort estimate and a projected point gain per finding, so advice can be ordered by payoff rather than by how alarming it sounds.
  • A Markdown report written to be pasted into an assistant, so the model reasons over evidence instead of filling gaps.

For agents and scripts, the same measurement is at /api/v1/seo?url=yoursite.com — see the API documentation.

Related questions

Is any AI SEO advice worth following?

Yes — advice grounded in a measurement of your site is often excellent, because interpreting findings and explaining trade-offs is what models do well. It is the ungrounded half that fails, and that half is easy to identify: it never names anything specific to you.

How do I tell generic advice from real advice?

Real advice names an observation. "Your canonical on /pricing points at /pricing/ which 301s back, so the signal is circular" could be wrong and can be checked. "Make sure your canonical tags are correct" cannot be either.

Should I ask the model to search the web first?

It helps for current best practice and does nothing for your specific site, because search results are articles about SEO rather than measurements of your configuration. It improves the general half of the answer and leaves the specific half exactly as it was.

What is the single most useful thing to give a model?

The list of what is currently failing, with the observed value attached, plus what was not checked. That combination lets it prioritise honestly and tell you where its advice does not reach.

Read next

All 100 guides · How every check works · API for agents