Free — no login
AI Search Readiness Checker
Tool details
A 12-point check for Generative Engine Optimization (GEO) and Answer Engine Optimization (AEO): the technical and on-page signals that help AI answer engines such as ChatGPT, Perplexity, Claude and Gemini read your page.
Looking for a maturity score for your marketing operation instead? Try the Marketing Automation Readiness Assessment.
Want help closing your GEO/AEO gaps?
We harden structured data, crawlability, llms.txt and answer-ready content to make your pages easier for AI answer engines to read.
Frequently asked questions
It fetches the page you enter plus /llms.txt, /robots.txt and /sitemap.xml at the site root, then runs 12 checks: llms.txt, robots.txt, XML sitemap, meta description, page title, a single H1, JSON-LD structured data, FAQ or Q&A content, Open Graph tags, canonical URL, author and publish-date signals, and content depth.
Each check has a weight, and the weights add up to 100. A pass earns the full weight, a warning earns half, and a fail earns nothing; the score is the share of weight earned. The heaviest checks are llms.txt (15), JSON-LD (12), the XML sitemap (10) and FAQ content (10).
No. The checker looks at technical and on-page signals in one page’s HTML and three root files. It does not query any AI engine or measure real citations, so treat the score as a list of gaps to close, not a prediction.
They answer different questions. The Marketing Automation Readiness Assessment is a 10-question self-assessment of your marketing operation (workflows, CRM, data, integrations and ownership). The AI Search Readiness Checker is an automated technical check of a web page for AI answer engines. Use the assessment to plan automation and this checker to audit a page.
Not yet. The robots.txt check only confirms the file exists; it does not parse rules for crawlers such as GPTBot or ClaudeBot. To draft those rules and an llms.txt file, use the llms.txt + robots-for-AI generator.
The checker reads the HTML returned by a plain server request, so content added later by client-side JavaScript is not seen. It checks only the exact URL you enter, and slow responses can time out (12 seconds for the page, 6 seconds for each root file).