GEO Optimization Suite

The GEO Optimization Suite is a collection of 10 tools designed to help you optimize your website for AI search engines. Each tool analyzes a different aspect of your site's AI readiness.

With the GEO Optimization Suite, you can:

• Score how ready your whole domain is for AI agents, across discovery files, content formats, access rules and agent interfaces
• Generate and validate your llms.txt and robots.txt so AI crawlers can find and use your content
• Check whether AI bots can actually crawl and render your key pages
• Audit your schema markup and content structure for AI readiness
• Fix the technical gaps that stop AI models from citing your site

You switch between the tools using the tab navigation at the top of the GEO Optimization page. Each tab below covers one analysis type.

Agent Readiness Report

Scores your domain across the four dimensions that decide whether an AI agent can find, read, and act on your site. It runs about twenty read-only requests against your site root, so it finishes in under a minute and never crawls your pages.

• Discovery: robots.txt, XML sitemap, llms.txt and llms-full.txt, HTTP Link headers.
• Machine-readable content: markdown content negotiation (an Accept: text/markdown request), a markdown URL variant, JSON-LD, and feed autodiscovery.
• Access and permissions: per-crawler robots.txt rules, the Content Signals directive, and a live fetch sent with a real crawler user agent. We also look for a Web Bot Auth directory, but only report it, never score it: that file is published by crawler operators to advertise their signing keys, so a normal website has no reason to serve one.
• Agent interfaces: MCP server card, agent skills index, API catalog, OpenAPI document, OAuth discovery, A2A agent card, and the Agentic Resource Discovery catalog.

A fifth group, agent commerce (x402, Agentic Commerce Protocol, Universal Commerce Protocol, AP2), is probed and listed but deliberately left out of the score, because those standards are still moving.

Two things worth knowing when you read the report:

• The live crawler check tests the user agent, not the IP. We send a real crawler user agent from our own network. A block means the user agent string was refused. A site that verifies crawlers by IP range or request signature may still block us while allowing the real crawler, so treat a failure as a prompt to look at your edge rules rather than proof of a misconfiguration.
• A low interfaces score is normal today. MCP server cards and API catalogs are new, and most sites publish none of them. The dimension is weighted so the basics still carry your score.
• The MCP server card is not a well-known file. We look for it through your Agentic Resource Discovery catalog at /.well-known/ai-catalog.json, which is where the specification says a card should be advertised. Several guides tell you to publish it at /.well-known/mcp/server-card.json instead; the specification rules that location out. If we find a card there we flag it so you can move it, rather than passing you for it.

Inside the dashboard the report adds a Declared vs observed panel that a public report cannot show: it puts what your robots.txt declares next to what your edge actually did to real agents over the last 30 days, using your Agent Analytics data. It flags two mismatches: a crawler you block that keeps crawling anyway, and a crawler you allow whose requests mostly come back as errors.

The same check is available to anyone without an account as the free Agent Readiness Checker.

Quick AI Visibility Report

Generates an on-demand visibility report for any domain, showing how it appears across AI models. It is a one-off snapshot, not the weekly tracking your project prompts give you, which is why it is called "quick".

The same report is available to anyone without an account as the Free AI Visibility Report. Inside the dashboard it is called the Quick AI Visibility Report, runs against the project you have open, and can be exported to PDF.

llms.txt Generator

Creates an llms.txt file for your website, a markdown document that helps AI models understand your site's official content efficiently.

robots.txt Checker

Analyzes your robots.txt file to check whether AI crawlers (GPTBot, ClaudeBot, GoogleOther, etc.) are allowed or blocked.

GEO Crawlability Checker

Compares static HTML vs JavaScript-rendered content to identify what AI crawlers can actually see on your pages.

Cookie consent banners are excluded from this comparison automatically. Consent platforms like Cookiebot or OneTrust inject their banner and cookie declaration with JavaScript, which can add thousands of words of boilerplate to the rendered page and would otherwise make the content parity score look much worse than it really is. When a consent banner is detected, the report shows a note with the number of words excluded.

What the report sections are called

The report is organized around a static fetch versus a full browser render, but the sections on screen are named after what they compare, not after the two fetches:

• How AI Engines See This Page: a verdict per engine (sees full content, partial content, little or nothing, or indexed with snippets blocked). Only Google's renderer executes JavaScript.
• Content Comparison: Static Words (what AI bots see), Rendered Words (what browsers see), and Content Parity, the share of your content visible to AI bots.
• Meta Tags Comparison and Structured Data (JSON-LD): two columns, Static (GPTBot) and Rendered (Browser), so you can see which tags and schemas only exist after JavaScript runs.
• Indexing & AI Directives, Initial HTML Response Size, Links, Images, Technical Details and Recommendations.

How to tell whether a firewall is blocking the crawl

If your site sits behind Cloudflare or another bot protection and you want to confirm whether it is blocking us, look for the amber "Anti-bot protection detected" banner. That banner is the signal: it appears when the fetch came back with a challenge page instead of your real content. When it is absent and the Static Words count reflects your real page, the fetch got through.

The GEO Crawlability Score is not a "percentage blocked" number. A score of 80% does not mean 20% of your site is blocked. The score also drops for content that only appears after JavaScript, missing or mismatched meta tags, links, and schema. Read the findings under the score to see which check is failing.

To validate a firewall change your IT team made:

1. Open Project Settings and turn on Crawler Identification, so our crawlers announce themselves as LLMPulseBot/1.0.
2. Ask your IT team to allowlist that exact User-Agent (allowlisting only GPTBot is not enough, because the rendering step uses a headless browser).
3. Run the Crawlability report again on the same URL and compare it with the previous one: the anti-bot banner should be gone and Static Words should match your real content.

Schema & Structured Data Analyzer

Checks your structured data markup for AI optimization, validates schema.org types, product data, and FAQ markup.

Content Readiness Checker

Analyzes whether your content is structured and formatted in a way that AI models can easily cite.

Discoverability & Authority Report

Evaluates your domain's authority signals and discoverability across AI search platforms.

Site Structure Report

Analyzes your internal linking structure and site architecture for AI crawlability.

ChatGPT Shopping Feed Checker

Validates your product feed for ChatGPT Shopping compatibility.

How to use it

1. Navigate to GEO Optimization in the sidebar (under Optimization)
2. Select a tool from the tab navigation
3. Enter a URL or domain to analyze
4. Review the generated report with scores and recommendations
5. Reports can be shared via unique public URLs

Tips & notes

• Most GEO tools are available on all plans with rate limits (1-2 reports/day for free users, unlimited for paying customers)
• Reports include actionable recommendations specific to each tool
• Results are emailed to you and accessible via shareable links
• Some tools (like Crawlability) use headless browser rendering and may take 30-60 seconds
• If a site behind strict bot protection returns inaccurate reports, open Project Settings and turn on Crawler Identification. Our GEO and crawlability crawlers will then fetch that project's site with a fixed, self-identifying User-Agent that your team can allowlist in your firewall or bot protection (for example Cloudflare), so reports reflect your real content instead of a challenge page. The toggle is off by default