Static pre-check · Fri, 07 Aug 2026 06:51:08 GMT
algolia.com
AI agents struggle to discover, access, and parse the site due to missing robots.txt, sitemap.xml, and llms.txt files, with no agent-specific response handling.
Watch a real agent use your site →
A live Claude Code run against algolia.com, streamed step by step.
Test this with real agents →
An audit: measured success rates from repeated real agent runs, with confidence intervals and downloadable evidence.
Discovery 11.8/22.2
robots.txt existsdetailsFAIL
robots.txt not served (HTTP 403)
Fix: Serve a /robots.txt. Without it, agent crawlers have to guess what they may fetch.
sitemap.xml exists and parsesdetailsFAIL
sitemap.xml not served (HTTP 403)
Fix: Publish /sitemap.xml listing your public pages, and reference it from robots.txt with a `Sitemap:` line.
API reference linked from the homepagedetailsWARN
no link to an API reference in the homepage HTML
Fix: If you have an API, link its reference from the homepage. If you don't, this check is safe to ignore.
Homepage has a descriptive titledetailsWARN
title is 123 characters (truncated in most surfaces)
Fix: Trim the <title> to 70 characters or fewer so it is not cut off.
Open Graph tags presentdetailsWARN
only og:title present
Fix: Add both og:title and og:description so link unfurls and agent previews show something meaningful.
Canonical URL declareddetailsPASS
https://www.algolia.com
Documentation linked from the homepagedetailsPASS
5 docs link(s), e.g. /developers/lp-mcp
Homepage has a meta descriptiondetailsPASS
181 characters
Brand findable in agent searchdetailsN/A
search-based checks are deferred — excluded from the score
Listed in an MCP registrydetailsN/A
registry lookup not implemented in v1 — excluded from the score rather than guessed
robots.txt allows agent crawlersdetailsN/A
no robots.txt to evaluate — nothing is blocked by rules that don't exist
robots.txt points at the sitemapdetailsN/A
no robots.txt
Accessibility 15/33.3
Homepage responds to an agent requestdetailsFAIL
HTTP 403 for an agent User-Agent
Fix: Return 200 for agent requests to the homepage. A non-2xx here means nothing downstream can be evaluated.
llms.txt is publisheddetailsFAIL
/llms.txt not served (HTTP 403)
Fix: Publish /llms.txt: a plain-markdown index that tells an agent what this product is and where the authoritative docs live. It is the cheapest high-leverage file you can add.
Same response for agents and browsersdetailsFAIL
browser got HTTP 200, agent User-Agent got HTTP 403
Fix: Your CDN or WAF is blocking non-browser clients. Allow well-identified bots, or at least return a 200 with readable content instead of a challenge page.
llms-full.txt is publisheddetailsWARN
/llms-full.txt not served
Fix: Optional but cheap: publish /llms-full.txt with your docs inlined as one markdown file, so an agent can read everything in a single fetch.
Serves markdown when asked for itdetailsWARN
Accept: text/markdown → text/html; charset=UTF-8
Fix: Optional but increasingly expected: honour `Accept: text/markdown` by serving a markdown rendering of the page, so agents skip HTML parsing entirely.
Content-to-markup ratio is reasonabledetailsWARN
ratio 0.0339 — 10275 readable chars in 303213 bytes of HTML
Fix: Most of what you serve is markup and inline script rather than content. Reduce inline payloads or server-render more text so the signal-to-noise ratio favours readers.
Served over HTTPSdetailsPASS
https://www.algolia.com/
Structured data (JSON-LD) on the homepagedetailsPASS
1 valid block(s)
Homepage has readable text without JavaScriptdetailsPASS
10275 characters of text in the served HTML
No long redirect chain on the homepagedetailsPASS
0 redirect(s)
Docs are readable without JavaScriptdetailsN/A
/docs not served (HTTP 403) — docs may live on another path or host
Links in llms.txt resolvedetailsN/A
no llms.txt
llms.txt is structured markdowndetailsN/A
no llms.txt to parse
Usability 22.2/44.4
agents.md is publisheddetailsWARN
/agents.md not served (HTTP 403)
Fix: Publish /agents.md: what an agent may do here, which endpoints matter, auth requirements, and rate limits. It is the agent-facing counterpart to a README.
A documentation endpoint respondsdetailsWARN
/docs → HTTP 403
Fix: Serve docs at the conventional /docs path, or redirect it to wherever they live. Agents try conventional paths first.
Errors are machine-readabledetailsWARN
a nonexistent path returned HTTP 403, not 404
Fix: Return 404 for paths that do not exist. A 200 on a missing page makes an agent believe it found something.
OpenAPI document publisheddetailsWARN
/openapi.json not served (HTTP 403)
Fix: If you have an HTTP API, publish its OpenAPI document at a predictable path (/openapi.json). It is the difference between an agent reading your contract and an agent guessing it. If you have no HTTP API, ignore this.
.well-known/mcp.json advertises an MCP serverdetailsWARN
/.well-known/mcp.json not served (HTTP 403)
Fix: If you run an MCP server, advertise it at /.well-known/mcp.json so agents discover it without being told its URL.
The /api root behaves predictablydetailsN/A
/api → HTTP 403 (no API at the conventional root)
MCP server completes the initialize handshakedetailsN/A
no MCP endpoint found to probe (none in the input URL and none advertised at /.well-known/mcp.json)
MCP tool parameters are typed and describeddetailsN/A
no listed MCP tools to inspect
Every MCP tool has a descriptiondetailsN/A
no listed MCP tools to inspect
MCP server lists toolsdetailsN/A
no MCP endpoint to probe
OpenAPI declares its auth schemedetailsN/A
no parseable OpenAPI document
OpenAPI operations are describeddetailsN/A
no parseable OpenAPI document
OpenAPI documents error responsesdetailsN/A
no parseable OpenAPI document
OpenAPI document is structurally validdetailsN/A
no parseable OpenAPI document
Payments not applicable — excluded from the score
Serves a 402 payment challengedetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Declares AP2 / ACP supportdetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Publishes x402 payment metadatadetailsN/A
no agent-payment rail published — not applicable. This layer is excluded from the score rather than counted against the site.
Badge
Shows the current scan score and grade for this domain, straight from the latest static pre-check.
[](/score/algolia.com)<a href="/score/algolia.com"><img src="/api/badge/algolia.com" alt="agent readiness score" /></a>