Expo
AI agents can find, read and use these docs well.
Last scanned Sep 28, 2026docs.expo.devCustom platform15 pages tested
Score overview
Expo scores 93 out of 100 (grade A), passing 21 of 27 checks. 6 still need work.
- Kind of site
- Developer docs
- Checks passed
- 21/27
- Partly passed
- 3
- Failed
- 3
Access
Content discoverability6 passed1 partly
llms.txt fits in an agent's context
llms.txt is 55,090 characters (between 50,000 and 100,000; consider splitting)
Your llms.txt is 55,090 characters, which may be truncated on some agent platforms. If it grows further, split into nested llms.txt files with a root index under 50,000 characters.
Check your fix:
curl -s https://docs.expo.dev/llms.txt | wc -cprints less than 50000.llms.txt exists
llms.txt found at https://docs.expo.dev/llms.txt
llms.txt follows the standard structure
llms.txt follows the proposed structure (H1, blockquote, heading-delimited link sections)
llms.txt links work
All 15 same-origin sampled links resolve (559 total links)
llms.txt links point to Markdown
15/15 same-origin sampled links point to markdown content (100%) (1 external link excluded)
Pages point agents to llms.txt
llms.txt directive found in HTML of all 15 sampled pages, near the top of content
Markdown pages point agents to llms.txt
llms.txt directive found in markdown of all 15 sampled pages, near the top of content
Markdown availability2 passed
Pages are available as Markdown
15/15 sampled pages support .md URLs (100%)
Server returns Markdown when asked
15/15 sampled pages support content negotiation (100%)
Page size and truncation1 passed1 failed2 partly
Content starts near the top
1 of 15 sampled pages have content starting past 50% (worst 53%)
1 of 15 pages have content starting past 50% of the converted output. Agents may never see the documentation content. Reduce navigation, breadcrumb, and sidebar markup that precedes the content area.
Markdown pages fit in context
1 of 15 pages between 50K–100K chars (max 58K)
1 of 15 markdown pages are between 50K and 100K characters. These may be truncated on some agent platforms or routed through summarization. Consider splitting large pages.
HTML pages fit in context
1 of 15 sampled pages convert to 50K–100K chars (max 1215K HTML → 83K markdown (93% boilerplate))
1 of 15 pages convert to 50K-100K characters of markdown. Review pages for reducible boilerplate (navigation, serialized tabbed content). Consider providing markdown versions as a smaller alternative path for agents.
Content is in the HTML without JavaScript
All 15 sampled pages contain server-rendered content
Content structure3 passed
Tabs don't bloat the page
No tabbed content detected across 15 sampled pages
Headings inside tabs name their variant
No tabbed content found; header quality check not applicable
Code blocks are well-formed
All 85 code fences properly closed across 16 pages
URL stability2 passed
Missing pages return a real 404
All 15 sampled pages return proper error codes for bad URLs
Redirects stay on the same host
All 15 redirect(s) across 15 sampled pages are same-host HTTP redirects
Content health1 passed2 failed
llms.txt covers the whole site
llms.txt covers 558/1732 sitemap doc pages (32%); 1174 missing
Your llms.txt covers 32% of your site's pages (below 80% threshold). 1174 live pages are missing from the index. If unintentional, regenerate llms.txt from your sitemap or build pipeline. If intentional, lower the threshold or set it to 0 to make the check informational.
Markdown matches the HTML page
4 of 15 pages have substantive content differences between markdown and HTML (avg 13% missing)
4 pages have substantive content differences between markdown and HTML (avg 13% missing). If unintentional, agents are getting outdated content; regenerate markdown from source or fix the build pipeline.
Cache headers allow timely updates
All 16 endpoints have appropriate cache headers
Authentication and access1 passed
Gated docs offer another way in
All docs pages are publicly accessible; no alternative access paths needed
Docs are readable without logging in
All 15 sampled pages are publicly accessible
Crawler access2 passed
Crawlers and AI assistants may read the docs
robots.txt lets Googlebot, Bingbot, OAI-SearchBot, PerplexityBot, Claude-SearchBot and Claude-User read the docs.
Sitemap lists the docs pages
The sitemap at https://docs.expo.dev/sitemap.xml lists 559 of the 559 docs pages found through llms.txt and page links.
Freshness
Maintenance3 passed
Pages say when they were last changed
12 of 15 sampled pages state when they were last changed.
Links and section anchors work
All 42 links and 15 section anchors checked on the sampled pages work. 3 more could not be verified (timeouts or blocked requests) and are not counted.
Sitemap entries still exist
All 10 sitemap entries sampled still exist.
Consistency with the API specNot applicable
Endpoints in the docs exist in the API spec
No OpenAPI description was found, so the docs could not be compared with a spec.
CurrencyNot applicable
Deprecated operations are marked as such
No OpenAPI description was found, so deprecation notices could not be compared with a spec.
Additional checks
MCP server is discoverable
An MCP server answers at https://mcp.expo.dev/mcp; agents need to sign in to use it.
llms-full.txt is available
llms-full.txt found at https://docs.expo.dev/llms.txt (55,090 characters).
Agent skills are published
No agent skills index was found at /.well-known/agent-skills/index.json.
Publish an Agent Skills index at /.well-known/agent-skills/index.json with a SKILL.md for your main tasks, so agents can load task instructions without reading every page.
About this scan
- Scanned
- Sep 28, 2026
- Pages tested
- 15 of 558 found
- Platform
- Unknown
- Kind of site
- Developer docs
- AFDocs score, on its own
- 93 (A), 16 of 23 checks pass
- Based on 15 sampled pages, chosen deterministically from the sitemap and llms.txt. Pages outside the sample were not read.
- Pages were fetched without running JavaScript, the way most AI agents read the web.
- robots.txt stopped the scanner from reading 3 URLs; checks that needed them are unverified.
- Answerability, where an AI agent answers real questions written from these pages, runs in the open-source scanner with your own API key. This web score is made of Access and Freshness.
Methodology 2026-09.6 · AFDocs 0.20.0
Pages we sampled (15)
- https://docs.expo.dev/accounts/account-types
- https://docs.expo.dev/build-reference/app-extensions
- https://docs.expo.dev/custom-builds/functions
- https://docs.expo.dev/eas-insights/app-usage
- https://docs.expo.dev/eas/environment-variables/usage
- https://docs.expo.dev/eas/workflows/examples/e2e-tests
- https://docs.expo.dev/guides/localization
- https://docs.expo.dev/guides/using-supabase
- https://docs.expo.dev/push-notifications/faq
- https://docs.expo.dev/router/basics/core-concepts
- https://docs.expo.dev/troubleshooting/application-has-not-been-registered
- https://docs.expo.dev/tutorial/eas/manage-app-versions
- https://docs.expo.dev/versions/latest/sdk/captureRef
- https://docs.expo.dev/versions/latest/sdk/location
- https://docs.expo.dev/versions/latest/sdk/slider
Show your score
Add the badge to your docs or README. It updates each time the site is scanned.
Markdown
[](https://documentation.ai/agent-score/expo)HTML
<a href="https://documentation.ai/agent-score/expo"><img src="https://documentation.ai/agent-score/badge/expo.svg" alt="Agent Readiness Score: 93 (A)" height="20"></a>