Agent readiness check
Paste one public page URL to run RankEcho's 0-100 heuristic across detected structured data, crawl signals, initial HTML, a sitemap declaration in robots.txt, and llms.txt. The score is not defined by an AI provider and does not certify indexing, retrieval, ranking, impressions, or citations.
Read each dimension as a diagnostic signal. A missing signal can justify inspection; its presence is not an eligibility requirement or outcome predictor. llms.txt is an optional proposal, and Google says it ignores the file for Search and AI features.
Auxiliary-fetch limitation. This check does not display the status of its auxiliary robots.txt request. If that request fails, the crawl-access score may be overstated because no usable policy was returned. Confirm robots.txt with the policy checker; if its robotsStatus is 0 or 500-599, ignore both tools' allowance and readiness labels until the fetch succeeds.
Free and anonymous. Rate-limited to 20 checks per hour per IP. We fetch the page, /robots.txt, and /llms.txt.
Full heuristic report (JSON)
This single check uses one target-page response plus auxiliary /robots.txt and /llms.txt requests. It cannot observe every crawler, renderer, index, query, or answer surface. Verify any flagged condition with provider documentation and direct evidence before changing production.
Next: parse sitewide policy with the robots.txt policy heuristic, or use the free audit for bounded answer observations.
What does the agent-readiness score measure?
It is RankEcho's composite of signals detected during one check. The check fetches the target page, /robots.txt, and /llms.txt; it looks for structured-data presence, robots and page signals, initial-response text, a sitemap declaration in robots.txt, and llms.txt presence. It does not fetch or validate a sitemap, reproduce every provider's rendering stack, or decide whether the provider will index or select the page.
A composite is useful for triage only when its components remain visible. Inspect the individual findings and the raw JSON report rather than treating 0-100 as an industry standard.
Does structured data make a page eligible for AI features?
Not by itself. Accurate markup can expose visible facts in a machine-readable form, but Google says AI Overviews and AI Mode have no additional technical requirements or special AI schema. Normal Search eligibility applies, and eligibility still does not guarantee appearance.
Does server-rendered HTML guarantee AI access?
No. Useful text in the initial response improves compatibility with clients that do not execute the site's JavaScript, but provider behavior differs. A crawler may render, use an index, encounter a different edge response, or decline the page for another reason. The score does not authenticate the requester or observe provider selection.
Free audits check Perplexity and Gemini once per prompt. Paid and trialing accounts add ChatGPT, Claude, and Google AI Overviews when configured for the account, for up to 5 engines. A later answer observation is still not proof that one readiness signal caused the result.
What is llms.txt in this score?
It is an optional signal for the presence of a community-proposed Markdown index. The llms.txt project calls it a proposal, while Google says it ignores llms.txt for Search and its AI features. Presence should not be interpreted as ranking, indexing, or citation readiness.
What this check does not do
It does not verify a genuine AI crawler, inspect your CDN or WAF account, expose the auxiliary robots.txt status, test every target URL, establish Search Console or Bing index state, sample an AI answer, or predict traffic. The file checks and recommendations are RankEcho's current heuristic, not an engine requirement.
Primary sources reviewed
Checked 2026-09-01: Google AI features, the llms.txt proposal, Google's llms.txt guidance, RFC 9309, and Google crawler verification.
Frequently asked questions
Does a high readiness score guarantee citations?
No. It is a RankEcho heuristic from detected page signals. Provider crawling, indexing, retrieval, source selection, query demand, and answer variation are separate.
Is llms.txt a ranking factor?
Google says it ignores llms.txt for Search and its AI features. The community proposal describes an optional content index; it does not establish a ranking signal.
Does missing schema make a page ineligible?
No universal AI-eligibility rule says that. Add accurate schema when it serves a supported consumer, and do not infer citation impact from presence alone.
Can this check see Cloudflare or WAF blocks?
It observes the responses its own requests receive, but it cannot inspect account rules, verify a provider crawler, or prove what that provider received. Use edge and origin logs.
How is this different from the crawler policy check?
The crawler check parses /robots.txt with a built-in model. This page heuristic also inspects one URL and optional discovery files. Neither certifies provider access or outcomes.
Explore the other free checks:
Turn the diagnosis into a shipped change: use the RankEcho Resources library for Find, Fix, and Prove playbooks, checklists, and templates.