Crawl, fix, re-crawl: proving a change moved something
A baseline crawl, a dated change log, a like-for-like re-crawl and a diff: how to prove a fix landed, and how to keep readiness deltas apart from traffic.
auditing
9 posts
The AEO audit, end to end, on a sample site
One AEO and GEO audit walked from scope to re-crawl on a fictional 20-URL site: what to check first, how to triage findings, and how to prove a fix landed.
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.
Boilerplate ratio: how nav and footers shrink your page
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.
Prioritizing AEO fixes: severity × page value
A reproducible way to order AEO and GEO fixes: rate severity, page value, and effort in a spreadsheet, rank the list, then re-crawl to prove each fix landed.
Status codes, redirects, and canonical drift on AI surfaces
How redirect chains, soft 404s, 4xx and 5xx responses, and conflicting canonicals decide which URL gets fetched, indexed, and attributed — and how to check.
What makes a page citable: stats, sources, quotable blocks
What the GEO research paper tested, what it found, and where it stops — then how to write citable sentences and count them across a site.
Five checks for a page that ranks but never gets cited
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.
How to check whether AI crawlers can actually reach you
Reading robots.txt tells you what you intended. Six checks that tell you what actually happens when an AI crawler requests one of your pages.