The only free check for whether your site is ready for AI agents and answer engines (ChatGPT, Perplexity, Claude). It scans two things at once: the emerging agent-discovery standards — well-known files, robots AI rules, DNS-AID, Markdown negotiation, MCP / OAuth / Skills / commerce discovery and Link headers — and AI-search content readiness — the raw-HTML-vs-JS-rendered gap, llms.txt, answer-first / Q&A structure, extractable-proof signals, E-E-A-T and deprecation-aware schema.
Slower endpoint. This check makes many discovery probes (well-known files, robots, DoH lookups, MCP/OAuth/commerce endpoints) plus a full JavaScript render to measure the raw-vs-rendered gap. Expect it to take noticeably longer than the other tools — allow up to ~30s and set your client timeout accordingly.
Query parameters
Name
Type
Description
urlrequired
string
The URL to scan for AI & agent readiness.
key
string
Your API key. Optional in the query string — you can also send it as the X-API-Key request header.
/.well-known/security.txt is present (a contact for security reports).
aiSearchReadiness
Readiness for AI answer engines — whether crawlers like GPTBot and PerplexityBot can actually see, extract and trust your content.
renderGap
Field
Type
Description
checked
boolean
Whether the raw-vs-rendered comparison ran.
rawWordCount / renderedWordCount
integer
Words in the raw HTML vs. after a full JavaScript render.
rawLinks / renderedLinks
integer
Anchor links before vs. after JS.
rawJsonLd / renderedJsonLd
integer
JSON-LD <script> blocks before vs. after JS.
contentHiddenFromAiCrawlers
boolean
The key signal.true means most of your content only appears after JavaScript runs — so AI crawlers like GPTBot and PerplexityBot, which do not execute JavaScript, can't see it. Server-render or pre-render to fix.
llmsTxt
Field
Type
Description
present
boolean
A /llms.txt file was found. When present, the report also includes isMarkdown, linkCount and looksLikeSitemapDump (a quality warning for over-long, undifferentiated link lists).
answerEngine
Field
Type
Description
questionHeadings
integer
H2/H3 headings phrased as questions (how / what / why… or ending in "?").
hasQAStructure
boolean
true when there are ≥3 question-style headings — a strong answer-first signal.
tables / orderedLists
integer
Counts of <table> and <ol> — structures answer engines lift easily.
semanticLandmarks
object
Presence/count of main, article and section landmarks that help parsers find the primary content.
proofSignals
Extractable, citable evidence that makes a page worth quoting.
Field
Type
Description
statistics
integer
Percentages and magnitudes (e.g. "42%", "3 million").
numbers
integer
Numeric tokens overall (years, prices, figures).
quotes
integer
Block quotes and inline quoted statements.
authorityCitations
integer
Outbound links to authoritative sources (.gov, .edu, Wikipedia, WHO, NIH…).
That author is a Person (stronger than an Organization byline).
datePublished / dateModified
boolean
Publication / last-updated dates present in schema.
aboutPage / contactPage / privacyPage
boolean
Links to About, Contact and Privacy pages — basic trust pages.
schemaDeprecation
Field
Type
Description
faqPageSchema
boolean
FAQPage JSON-LD is present.
faqRichResultsDeprecated
string
A note (when FAQ schema is present) that FAQ rich results were removed by Google in May 2026 — the markup no longer yields a Google rich result but still helps AI answer engines parse your Q&A, so it is worth keeping.
howToSchema
boolean
HowTo JSON-LD is present (its Google rich results were deprecated in 2023).
detectedTypes
string[]
All distinct schema @type values found on the page.
For raw response speed see Page timing; for full rendered performance use Lighthouse. See Errors for status codes.
We use cookies to enhance your browsing experience, serve personalised ads or content, and analyse our traffic. By clicking “Accept All”, you consent to our use of cookies.