How to audit a site for AEO and GEO
The full AEO and GEO audit loop: access, extraction, answer-readiness, citability and entity, then measurement. By hand, at scale, and re-crawled to prove it.
14 posts
The full AEO and GEO audit loop: access, extraction, answer-readiness, citability and entity, then measurement. By hand, at scale, and re-crawled to prove it.
Main-content extraction keeps one block of your page and drops the rest. How to measure what survives, by hand and across a site, and the markup that helps.
What GEOBee's three lenses score, why the results are local and re-runnable, and what it does not measure: citations, prompt visibility, or rankings.
The rich result that justified most FAQ blocks is gone. What still earns one, the test for whether a question belongs in the body, and what filler costs.
Real markup is only half of it. What flattening does to a table lifted out of your page, and the four fixes that keep one readable on its own.
A page is retrieved in pieces of a few hundred words. What splitting does to ordinary prose, and the three edits that make a section survive it.
The five faults that keep a good page out of AI answers — each with a by-hand check, a way to run it across a site with or without a terminal, and the fix.
When to phrase a heading as a question, when a keyword label is still the right call, and how to check every heading on a site in one pass.
An element-by-element inventory of what AI crawlers keep, discard, and only conditionally read — plus the parts you can exclude on purpose.
What happens to a page between fetch and answer, the eight signals answer-readiness turns on, and how to check every one of them by hand and at scale.
Three acronyms, one page. Here is what answer engines and generative search changed about optimization, and what they did not.
The highest-weighted answer-readiness signal is a passage that answers its own heading in one breath. What it is, how to write one, how to check it.