GEO Audit

Assess your website’s readiness for AI-generated answers through 4 complementary scores.

The GEO Audit evaluates each URL across four independent dimensions:

• whether AI agents can reach the page,
• whether they can parse its structure,
• whether the content itself is easy to process,
• and whether the page exposes the integration signals modern AI agents look for.

Each dimension produces a score from 0 to 100. Run the audit on a set of URLs, then filter by score to identify the pages that need attention first.

The four scores

Crawlability

Measures whether AI agents are technically allowed to access the page.

The audit checks robots.txt for each major AI crawler (GPTBot, ClaudeBot, Gemini Agent, PerplexityBot and others), verifies your llm.txt configuration, validates your sitemap, and checks for Link headers and Content Signals. It also records page response time, since slow responses can cause crawlers to time out. AI bot rules support wildcard handling — a single restrictive rule can block multiple agents at once.

A low score means some or all AI agents may be blocked from reading the page entirely — regardless of how well-structured the content is.

Score	What it means
85–100	All major AI agents can access the page.
60–84	Some agents are restricted or the page is slow to respond.
0–59	Significant access issues — content likely invisible to multiple AI agents.

Semantic

Measures how well the page is structured for AI parsing.

AI systems don’t read pages the way humans do. They rely on HTML structure — headings, paragraphs, lists, tables — to understand what a page is about and how to extract information. A page that looks well-designed in a browser may have very little structure in its underlying HTML.

The Semantic score evaluates the presence and quality of these structural elements, adjusted for the type of page being audited. A product page is expected to have a clear title and feature lists; a FAQ page is expected to have a Q&A structure. The score reflects whether the page meets those expectations.

The audit also checks Markdown negotiation — whether the server can return content in Markdown format when an AI agent requests it via the Accept header. Markdown is increasingly preferred by AI agents for cleaner text extraction.

It also checks for Schema.org JSON-LD structured data. Richer schema types (FAQPage, Product, HowTo, Article) are strong signals; generic types (WebPage, WebSite) are weak signals; no schema is a fail.

The detected page type is shown as a badge next to the score. If the detection is incorrect, you can override it manually.

Score	What it means
85–100	Well-structured — AI agents can parse and extract content reliably.
65–84	Acceptable structure — some improvements available.
40–64	Structural gaps that may reduce how accurately AI agents interpret the page.
0–39	Poor structure — content may be misread or ignored.

Readability

Measures whether the content is easy for an AI system to process and summarise.

The score looks at the language itself: sentence length, vocabulary complexity, reading grade level, and sentence structure. It also checks whether images have descriptive alt text — AI agents cannot interpret images without it.

Content that is dense, highly technical, or relies on complex sentence constructions may be hard to summarise or cite, even if it is perfectly accessible and well-structured.

Score	What it means
65–100	Clear, accessible content — easy for AI as human to process and summarise.
40–64	Acceptable — some complexity may reduce summarisation accuracy.
0–39	Dense or complex content — AI agents may struggle to extract key information.

Discovery

Measures whether the page or domain exposes the integration signals that AI agents and agentic frameworks look for.

This score goes beyond content accessibility. It checks whether your site publishes the machine-readable endpoints, authentication protocols, and agent capability declarations that allow AI systems to interact with it programmatically — not just read it.

Discovery data is sourced from Is It Agent Ready?, a free tool by Cloudflare that scans your site against multiple emerging agentic standards to measure AI agent readiness.

The audit checks two groups of signals:

Bot Access Control

• Web Bot Auth signing — whether the domain supports authenticated bot access using the Web Bot Auth protocol

API, Auth, MCP & Skills

• API catalog (RFC 9727)
• OAuth/OIDC discovery
• OAuth Protected Resource metadata
• MCP Server Card
• Agent Skills index
• WebMCP

Each check returns pass, fail, or neutral. Neutral checks (where the standard is not applicable to the page type) contribute a partial score rather than counting as failures.

Score	What it means
75–100	Strong agent integration signals — the site is well-prepared for agentic use.
40–64	Partial readiness — some integration protocols are missing.
0–39	Limited agent integration — the site is not yet discoverable by most agent frameworks.

AI Recommendations

Each audit includes an AI Recommendations panel that synthesises the four scores into a plain-English summary and a prioritised action list.

The summary tells you how the page performs overall and where the most impactful opportunity lies. The recommendations below it are specific and ordered by impact — so if you can only fix one thing, you fix the right one first.

Reading the results

Each URL shows all four scores side by side. You can sort and filter by any score to prioritise fixes. The panel below each score lists the specific issues found and what to do about them — most actionable first.

A page can score well on Crawlability but poorly on Semantic, Readability or Discovery. All four matter for AI citation: the agent needs to be able to reach the page, understand its structure, and process its content, and ideally interact with your site through standard protocols.

Common patterns

High Crawlability, low Semantic

The page is accessible but poorly structured. Common on pages built with heavy client-side rendering, where visible content is generated by JavaScript and absent from the raw HTML. Improving server-side rendering or adding structured HTML markup typically resolves this.

High Semantic, low Readability

The page has good structure but the content is difficult to process — common on legal, medical or highly technical pages. Add a plain-language summary or break long sentences into shorter ones.

Low Crawlability across all pages

Usually caused by an overly restrictive robots.txt that blocks AI crawlers as a group. Review your bot access policy and explicitly permit the agents you want to allow.
Note that wildcard rules can unintentionally block multiple crawlers at once.

Low Discovery score

The site has not yet published agent integration standards. Start with the MCP Server Card and OAuth/OIDC discovery endpoints — these unlock the highest point value in the Discovery scoring matrix.

What’s next

Asset Evaluation

Score creative assets against brand attributes.

Search Visibility

Track domain and brand presence across engines.