Free GEO Checker: Test Your Site's AI Search Readiness

What is a GEO checker?

A GEO checker tests how ready a website is for generative engine optimization, meaning whether AI answer engines such as ChatGPT, Claude, Perplexity and Google AI features can access, read and cite your content.

AI tools can only quote what they can fetch and understand. A page blocked in robots.txt, hidden behind a firewall, or built so the text only appears after JavaScript runs may never reach an answer. This tool checks those basics from the outside and shows you what is in the way.

What this GEO checker tests

How the GEO score is calculated

The GEO score is a weighted checklist of signals you can test from outside a site. A passed check earns its full points, a check marked "Improve" earns half, a failed check earns none, and informational checks are not scored. The score is points earned divided by points possible, as a percentage. Every check below is what the tool runs today.

The weights are my own judgment. They put the most points on whether AI crawlers can reach and read the page, because a page that cannot be fetched cannot be quoted. The content checks are rules of thumb, not confirmed ranking or citation factors. A high score means the readable signals are in place. It does not mean an AI tool will cite the page. In whole-site mode, the page-level checks run on pages from your sitemap and the results are combined into one score.

One caution. Google's guide to generative AI features says that, for Google Search, optimizing for generative AI is still SEO, and that structured data is not required for it. This tool tests readiness for AI tools in general, so some checks, such as structured data and question headings, are good practice rather than requirements. Treat the score as a readiness checklist, not a promise of citations.

AI crawlers and robots.txt: the 15 bots this tool tests

The tool reads your robots.txt and tells you whether each bot below is allowed for the page or site you enter. It uses the longest matching rule, handles wildcards and the $ end marker, and falls back to the rules for * when a bot has no group of its own. The "Purpose" column follows how each vendor describes the bot.

Bot names and behavior change, so check the vendors' own documentation: OpenAI, Anthropic, Perplexity and Google. The list above matches what the tool tests today.

Search and user bots vs training bots

Vendors split their crawlers by purpose. Search bots find pages so they can appear in AI answers. User bots fetch a page when a person asks the assistant about it. Training bots collect content to train models. OpenAI says each of its robots.txt settings is independent, so a site can allow OAI-SearchBot and still disallow GPTBot. Blocking the search and user bots can remove you from AI answers, which is why the tool scores those two groups and treats training bots as information only.

User bots are a special case. OpenAI says robots.txt rules may not apply to ChatGPT-User because users start those requests, and Perplexity describes Perplexity-User as generally not bound by robots.txt for the same reason. Anthropic says its three bots, including Claude-User, honor robots.txt. The tool reports what your robots.txt says for every bot either way.

Example robots.txt

This allows the search and user bots and blocks the training bots. Remove the last block if you are happy to be used for training:

User-agent: OAI-SearchBot
User-agent: ChatGPT-User
User-agent: Claude-SearchBot
User-agent: Claude-User
User-agent: PerplexityBot
User-agent: Perplexity-User
Allow: /

User-agent: GPTBot
User-agent: ClaudeBot
User-agent: CCBot
Disallow: /

Sitemap: https://www.example.com/sitemap.xml

The Fix files section of your report writes a version of this for your own site, including the training policy you pick.

How to check your site for AI search readiness

1. Enter a URL. Use Single page for one page or Whole site to read the pages in your sitemap.
2. Read the score and the Fix first list. Each item shows how many points it is worth.
3. Check the bot table to see which AI crawlers your robots.txt allows.
4. Open What an AI crawler sees. If your key content is missing, it is likely loaded by JavaScript.
5. Copy the fix files, publish them, then run the check again.

llms.txt: what it is and whether you need one

An llms.txt file is a Markdown file at the root of a site, proposed to give AI tools a short, clean guide to the site's key pages. The format is an H1 title, a one-line summary in a blockquote, and sections of links. It is a proposal, not a standard that search engines or AI providers have adopted.

This tool reports whether you have one, whether it has an H1 title and whether it contains Markdown links, and it can write a starter file from your sitemap. It gives llms.txt no points. Google's guide to generative AI features says site owners do not need llms.txt or other AI-specific files to appear in Google's generative AI search, and that Google may crawl such files without treating them in any special way. Other AI tools may treat the file differently, so check their documentation. If you add one, treat it as optional. Crawler access, readable HTML and clear content come first.

A minimal file looks like this:

# Example Company

> Example Company sells bike lights and publishes guides on night riding.

## Key pages

- [Bike lights](https://www.example.com/lights): Our range with prices
- [Night riding guide](https://www.example.com/guide): How to ride safely after dark

GEO, SEO, AEO and LLMO: what the terms mean

People use these terms for overlapping ideas, and there is no official definition for any of them. This is how I use them on this page.

• SEO is making pages findable and rankable in search results such as Google's.
• GEO (generative engine optimization) is making pages easy for AI answer tools, such as ChatGPT, Claude, Perplexity and Google's AI features, to reach, read and quote.
• AEO (answer engine optimization) is making pages likely to be used as a direct answer, in featured snippets, voice answers and AI summaries.
• LLMO (large language model optimization) is another name some people use for the same goal as GEO.

Good SEO and good GEO overlap heavily. Google's own guide says that, from Google Search's perspective, optimizing for generative AI search is optimizing for the search experience, and thus still SEO. A page that cannot be crawled, loads no text without JavaScript, or says nothing clear will do badly in both. This tool tests the shared basics and a few signals aimed at AI tools, such as crawler access and answer-first writing.

What makes a page quotable by AI tools

Nobody outside the AI companies can say exactly how an AI tool picks what to quote. The content checks in this tool are rules of thumb that make a page easy to read, summarize and verify:

• Answer first. The paragraph after the H1 states the answer in roughly 15 to 100 words, then the page expands.
• Question headings. H2 and H3 headings phrased as the questions people ask, with a direct answer under each.
• Structure. Lists for steps and options, tables for comparisons, so facts can be pulled out cleanly.
• Specifics. Real figures, dates and measurements, where they are true.
• Sources. Links to primary sources for the claims you make.
• Clear authorship. A named author or publisher, linked About, Contact and Privacy pages, and a visible last-updated date.

Use the "What an AI crawler sees" and "Quotable passages" sections of your report to check these on a real page.

Common GEO problems and how to fix them

The page is empty without JavaScript

The tool counts the words in the HTML your server sends. If a page has under 50 words there, or under 120 words and looks script-built, the check fails. The fix is to render the main content on the server, with server-side rendering, static generation or pre-rendering, so the text exists before any script runs. A December 2024 study by Vercel and MERJ found that crawlers from OpenAI and Anthropic fetch JavaScript files but do not execute them. Crawler behavior can change, so check the vendors' current documentation.

A robots.txt rule blocks a search or user bot

Find the Disallow rule that names the bot, or a blanket rule under User-agent: *, and add an Allow group for the bots you want. Re-run the check and confirm the bot shows as allowed.

The firewall refuses bot user agents

The tool sends requests carrying GPTBot, ClaudeBot and PerplexityBot tokens and warns if it gets a refusal. It is only a warning, because real bots use published IP ranges that firewalls often treat differently. Check your CDN, security plugin or host rules and allow verified bots by IP or by the provider's bot verification feature.

No Organization or Person entity

Add Organization or Person schema with a name and URL, and list your official profiles in sameAs, such as LinkedIn and other pages that are really yours. Build it with the Schema Markup Generator and check it in the Schema Markup Validator.

No dates or old dates

Show a visible last-updated date and mark it up with dateModified. Update it only when you change the content in a real way.

Weak sitemap

Publish an XML sitemap, point to it from robots.txt, and keep accurate lastmod dates. The Technical SEO Auditor can check your sitemap URLs for redirects, noindex and errors.

Which tool to use for which AI search job

This GEO checker tests whether your site is ready to be found and read by AI tools. It does not measure whether those tools mention you. Pick by the job.

What this GEO checker does not do

• It does not ask ChatGPT, Claude, Perplexity or Google whether they cite you. It checks readiness signals only.
• It reads the HTML your server sends and does not run JavaScript.
• Single-page checks are limited to 30 per 10 minutes per connection. Whole-site checks have their own limit of 3,000 pages an hour per connection.
• The firewall test uses bot names in the user agent. Real bots come from verified IP ranges, so a refusal is a warning, not proof.
• Response time is measured from this server, not from the AI companies' servers.
• Content checks, the quotable passage ratings and the score weights are rules of thumb.
• Pages behind a login cannot be checked.

GEO checker FAQ

Built by Vansh Bohra, an SEO specialist in Ahmedabad, India. Last updated October 2026.