GEO Audit
What It Measures
GEO stands for Generative Engine Optimization, and this audit answers one question: when an AI engine fetches your site, what can it actually use? It checks three layers — whether your pages serve readable text at all, whether your structured data tells machines who you are, and which of the entity signals AI engines look for are present or missing.
Why This Is Its Own Audit
AI crawlers are not browsers. Most do not run JavaScript, so a site that looks perfect in Chrome can serve an AI engine a blank page. Ranking in Google and being usable in AI answers are related but different problems: the SEO Audit covers how one page competes in Google, the Visibility Audit tells you whether AI engines actually name you today, and this audit tells you whether they even have the raw material to.
Running It
1. Open Tools → GEO Audit. 2. Pick a project — the domain fills in — or paste any URL. 3. Click Audit. Results return with a score and a breakdown per area.
Reading The Results
Each area lists what passed, what is missing, and what to change. Fix crawlability findings first: schema on a page an AI cannot read is schema nobody sees. Treat the score as a progress marker for one site over time — this month against last month means something; one site against a different site rarely does.
What To Do With The Findings
Press "Close these gaps" to carry the site into the Evidence Engine, which builds and publishes the missing pieces and then re-checks them on the following cycles. Schema gaps can also be closed directly through Entity Stack, which generates the Organization markup for your site.
Our own site once failed this audit — a JavaScript app serving zero readable words to anything that didn't run scripts. Browsers showed a finished site; AI crawlers saw an empty one. If your readable word count is near zero, fix that before anything else on the list.