Performance · 2 min read · 21 October 2026

An SEO audit that refuses to grade myths

Plenty of SEO reports score things Google has said it ignores. This engine keeps a list of checks it will never build, cites a source for every rule it does run, and won't show a score without its coverage.

A cartoon robot referee holding up a red card at three balloons marked with a percent sign, a ruler and a shield, next to a checklist on a bench
145
rules implemented, each with fixture tests
8
myths the engine refuses to score
117
rules that still run without a browser

01 · The problem with most audits

A red warning feels like a fact, even when it isn't.

Plenty of SEO tools flag keyword density, a "domain authority" number or a title that's a few characters too long. A client sees red and asks for a fix. Developers spend a sprint on something that was never a ranking signal, and the real problems wait.

02 · Anti-rules: checks we will never build

The rule catalogue has a section of things to reject.

Each one is either disproven or widely misunderstood, and shipping it would damage the tool's credibility:

  • keyword density
  • third-party "domain authority" style scores presented as a Google signal
  • the meta keywords tag
  • title or description length as a ranking factor (it's a truncation warning, nothing more)
  • word count as a ranking factor
  • AMP as a ranking factor
  • llms.txt as a visibility factor (detect it, never score it)
  • a Lighthouse SEO score treated as a ranking

03 · Every rule cites a source

If a finding can't be defended, it doesn't ship.

Every rule in the catalogue lists its method, threshold, severity, data source and citation. When someone asks "says who?", the report answers. That turns an argument about opinions into a conversation about evidence.

04 · A score needs its coverage

A number without context is a guess.

The dashboard won't show a score on its own. It shows a band (excellent, good, fair, poor) and how much of the site the measurement actually covered. 117 of the 145 rules run on raw HTML. The other 28 need a rendered page or Lighthouse. If those didn't run, the report says so instead of pretending.

05 · Tested against sites built to fail

Each rule must prove it can pass, fail and stay out of the way.

There's a small set of deployed fixture sites with defects planted on purpose. Every rule needs a fixture for pass, fail and not applicable. A test also stops the three pillars (technical, relevance, authority) from importing each other, so a change in one can't quietly move another's score.

06 · AI interprets, it doesn't decide

The model is a reading aid, not a source of truth.

The AI layer is opt-in. It reviews meaning-level questions, like whether two pages compete for the same query. Every answer must point to evidence spans that are validated against the page. It never invents target queries, rankings or competitor facts. The cost of every run is logged, and each run has a ceiling.

07 · A confession about llms.txt

This site ships one.

My portfolio has an llms.txt, for developer tools and AI assistants that read it. It isn't there for rankings. My engine would report that it exists, and give it zero points. That's exactly the point.

Next storyLog first, email second