The SEO Audit That Approved a Page With No Headline, and How We Caught It

AI-generated. Written by an automated system, checked by independent automated gates, and published without human editorial review. How we label and verify.

The moment our SEO preflight audit broke

We built an automated auditor that must decide: block or pass, before a page goes live.

We thought the checklist and a single score would be enough.

It wasn’t.

In one run an approving reviewer marked the skill with top marks on form. The score was high. The verdict was pass.

Then the mandatory third checker ran and flagged twenty logic errors. Twenty. More than any other skill in that batch.

What we tried and what changed

Start with what the writer saw. They never saw the original sources. They saw a short brief distilled from three external search-advice texts and our house rules. That made word-for-word copying impossible by design.

We also required receipts: every check had to ship with evidence and a stated weight, and the system would publish a checksum so anyone could recompute the verdict from the article alone. That was in from the start.

Before version 1.1 the auditor re-used its own earlier measurements. It accepted the evidence that had been attached without replaying the measurement against the raw input. That mattered.

Here’s the concrete failure. An article reached an 80 percent score and passed. But it had no main heading and the target keyword did not appear in the opening. The checklist should have blocked that. It didn’t because there was no critical gate — the threshold alone allowed the pass.

That was the turning point. The third checker didn’t just annotate; they re-ran checks against the raw input and found twenty logic errors the approver missed. Every one could be traced to either a mis-measured field or a missing hard stop.

We made two concrete changes the same day. First: every verdict now re-measures its own evidence directly from the raw input. Every quoted field must match character for character. One mismatch kills the run; there’s no rescue by score. Second: we added a critical gate so that certain failures block publication regardless of the percentage score.

After those edits the same checklist could no longer be tricked into approving a page missing its main heading or lacking the keyword at the top. The audit now ships with a full receipts table plus the checksum described so a stranger can recompute every check from the article alone. And version 1.1 closed all twenty logic errors on the same day it found them.

Why that worked

We learned a simple fact: measured evidence that isn’t replayed is untrustworthy. If you accept supplied measurements, you inherit prior mistakes. Replaying measurements against the raw input exposed mismatches we otherwise missed.

Second fact: a single aggregate score hides critical failure modes. An article can hit a high percentage yet fail a vital requirement. A critical gate makes that failure visible and non-negotiable.

Third fact: transparency plus recomputability deters sloppy evidence. When every check must come with traceable evidence and an exact checksum anyone can rebuild, reviewers tighten up. The receipts are not theater; they are an accountability mechanism.

A counter-example we saw

Not everything broke before the fix. Some skills in the same batch had sensible checks and genuine metrics, and the third checker found few or no problems. The failure was not universal. It clustered where we depended on supplied measurements and had no hard stop for essential requirements.

How we know

We can point to the audit records. The writer’s input was the distilled brief, verified. The pre-1.1 runs show approvals with high scores but missing headings and missing opening keywords. The third checker’s report lists twenty discrete logic errors; every one maps to a specific check and raw-input mismatch. Version 1.1 edits close those items and add the critical gate. The receipts and checksum format are recorded so an independent party can recompute the result from the published article alone.

Questions we got

Why force character-for-character matching?

Because fuzzy acceptance hides mistakes. We tried loose matching and it let small but consequential divergences slip through; exact matching exposed them immediately.

Does a critical gate reject too many useful pages?

It can, if mis-specified. That’s why the gate is reserved for essential on-page requirements only — headings, required disclosures, core metadata. Non-essential items remain in the scored checklist.

Can the receipts be faked?

Not easily. The receipts plus a stated checksum construction let anyone recompute the checks from the article alone; that recomputability is the deterrent. If a receipt doesn’t rebuild, the checksum fails and the evidence collapses.

The runnable skill file lives in the members’ library.

Rule: always re-measure your own evidence and block on essential failures before you count percentages. That rule is now built into every SEO preflight audit we run.

Sources: production audit records and the version 1.1 skill file updates from our content pipeline.

What Google Search Central and Lighthouse documentation says

Google’s own guidance on titles starts with presence. Its page on title links tells site owners to make sure every page on your site has a title specified in the <title> element, and to keep those titles descriptive and concise. It also says that generating title links in results is completely automated, drawing on several sources: the title element, the main visible title, and heading elements, such as <h1>. A page with no clear title and no main heading leaves Google less to work with.

On heading structure, Google is more relaxed than many audit tools. The SEO Starter Guide says semantic heading order helps people who use screen readers, but that from a Google Search perspective it doesn’t matter if you’re using them out of order. Correct order is an accessibility and clarity concern first.

Snippets follow a similar pattern. Google says it primarily uses the content on the page to build the snippet shown in results, and may use the meta description when it describes the page better than the on-page text. Writing a good description is still worth doing; it just is not a guaranteed display.

Crawlability is where a mistake can quietly remove a page. Google’s robots.txt introduction explains that the file manages crawler access and is not a mechanism for keeping a web page out of Google. To keep a page out of Google, the same page says to block indexing with noindex or password-protect it. Confusing the two is an easy way to get the opposite of what you intended.

Lighthouse turns some of these points into automated checks. Its SEO audits include a check that fails when page is blocked from indexing, and a meta description audit that fails when the element is missing or empty. That audit is explicit about its limits: Lighthouse does not evaluate the quality of your description. It checks that something is there.

How the documentation relates to our audit failures

The documentation draws a line our version 1.0 auditor blurred. Some requirements are presence checks: a title, a main heading, core metadata, a page that can be indexed. Others are quality judgments that belong on a sliding scale. Lighthouse keeps the two apart by making presence a pass/fail result. Our 80 percent threshold mixed them together, which is how an article with no main heading and no keyword in its opening could still pass.

The critical gate we added in version 1.1 restores that line. Essential on-page items (headings, required disclosures, core metadata) now block publication no matter what the score says. Everything else stays in the scored checklist.

The documentation also keeps us honest about what the gate is for. Google’s guide says heading order does not matter to Search, and the Google pages cited here do not make a keyword in the opening a Search requirement. Our hard stop on a missing main heading and on the opening keyword is a house standard. It protects readers, accessibility and consistency. We do not present it as a Google rule.

Our replay rule goes one step further than a typical presence check. Lighthouse confirms an element exists. Our auditor re-measures every quoted field from the raw input, character for character, because the twenty logic errors the third checker found traced back to mis-measured fields or missing hard stops. A check that trusts an earlier measurement inherits that measurement’s mistakes.

A preflight checklist you can adapt

1. Confirm the page has a non-empty title element and a single clear main heading.
2. Confirm the page is indexable: no stray noindex, and no reliance on robots.txt to hide it.
3. Confirm a meta description exists and is not empty, then judge its quality separately.
4. Decide which items are hard stops. Keep that list short and limited to essentials.
5. Score everything else, and never let the score override a hard stop.
6. Re-measure every piece of evidence from the raw page instead of accepting stored values.
7. Publish the evidence and weights with the verdict so someone else can recompute it.

More questions

Will a missing H1 hurt rankings?

Google does not say so in the guidance cited here. It lists heading elements among the sources it can use for title links, and says heading order does not matter to Search. We still block a page without a main heading, because readers and screen-reader users rely on it and because it is a cheap, objective check. That is our standard, not a ranking claim.

Is passing the Lighthouse SEO audits enough to publish?

No. Lighthouse checks presence and basic crawlability. Its own documentation says the meta description audit does not judge quality. A useful SEO preflight audit adds what Lighthouse cannot see: whether the evidence was measured from the real page, and whether the essentials passed on their own merit rather than being carried by a high score.