maps.express
Last scanned maps.expressCustom platform5 pages tested
AI agents have real trouble using these docs. Start with the top fixes. maps.express scores 59 out of 100 (grade F), passing 11 of 19 checks. 8 still need work.
The score is held at 59 because no llms.txt was found, and a site without one cannot score higher.
Developer docs
Kind of site
11/19
Checks passed
1
Partly passed
7
Failed
Access
Content discoverability3 failed
llms.txt exists
No llms.txt found at any candidate location (https://maps.express/llms.txt, https://maps.express/docs/llms.txt)
Create an llms.txt file at your site root containing an H1 title, a blockquote summary, and markdown links to your key documentation pages. This is the single highest-impact improvement for agent access to your docs.
Check your fix:
curl -sI https://maps.express/llms.txtreturns 200 with a text content type.Pages point agents to llms.txt
No llms.txt directive found in HTML of any of 5 pages
No agent-facing directive pointing to llms.txt was detected in the HTML of any tested page. Add a visually-hidden element near the top of each page (e.g., a div with CSS clip-rect) containing a link to your llms.txt. If your site serves markdown versions of pages, mention that in the directive too so agents know to request it.
Check your fix:
curl -s https://maps.express/ | grep -n llms.txtfinds the link near the top of the HTML.Markdown pages point agents to llms.txt
Could not fetch markdown for any of 5 pages; 5 had no markdown version
No llms.txt directive was detected in the markdown of any tested page. Add a blockquote near the top of each markdown page (e.g., "> For the complete documentation index, see [llms.txt](/llms.txt)").
Check your fix: The Markdown version of https://maps.express/ (its .md URL, or the page fetched with
Accept: text/markdown) has the llms.txt line in its first few lines.llms.txt follows the standard structure
Skipped: dependency check did not pass
llms.txt fits in an agent's context
Skipped: dependency check did not pass
llms.txt links work
Skipped: dependency check did not pass
llms.txt links point to Markdown
Skipped: dependency check did not pass
Markdown availability2 failed
Pages are available as Markdown
No pages support .md URLs (0/5 tested)
Your pages don't return markdown when .md is appended to the URL. Configure your docs platform to serve .md variants for all documentation pages.
Check your fix:
curl -sI https://maps.express/.mdreturns 200 with a text/markdown or text/plain content type.Server returns Markdown when asked
Server ignores Accept: text/markdown header (0/5 pages return markdown)
Your server ignores Accept: text/markdown and returns HTML. Some agents (Claude Code, Cursor, OpenCode) request markdown this way. Configure your server to honor content negotiation.
Check your fix:
curl -sI -H "Accept: text/markdown" https://maps.express/returnscontent-type: text/markdown.
Page size and truncation2 passed1 failed
Content starts near the top
1 of 5 pages have content starting past 50% (worst 67%)
1 of 5 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
Skipped: dependency check did not pass
Content is in the HTML without JavaScript
All 5 pages contain server-rendered content
HTML pages fit in context
All 5 pages under 50K chars (median 6K HTML → 3K markdown (67% boilerplate))
Content structure2 passed
Code blocks are well-formed
Site does not serve markdown content; nothing to analyze
Tabs don't bloat the page
No tabbed content detected across 5 pages
Headings inside tabs name their variant
No tabbed content found; header quality check not applicable
URL stability2 passed
Missing pages return a real 404
All 5 pages return proper error codes for bad URLs
Redirects stay on the same host
No redirects detected across 5 pages
Content health1 passed
llms.txt covers the whole site
Skipped: dependency check did not pass
Markdown matches the HTML page
Skipped: dependency check did not pass
Cache headers allow timely updates
All 5 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 5 pages are publicly accessible
Crawler access1 passed1 partly
Sitemap lists the docs pages
The sitemap at https://maps.express/sitemap.xml lists 5 of the 6 docs pages found through llms.txt and page links.
Generate the sitemap from the same source as the docs, so every page is listed. Agents and crawlers use it to find pages that navigation does not link.
Check your fix:
curl -s https://maps.express/robots.txt | grep -i sitemapnames a sitemap, and that sitemap lists the pages the report names as missing.Crawlers and AI assistants may read the docs
robots.txt lets Googlebot, Bingbot, OAI-SearchBot, PerplexityBot, Claude-SearchBot and Claude-User read the docs.
Freshness
Maintenance2 passed1 failed
Pages say when they were last changed
0 of 5 sampled pages state when they were last changed.
Publish a last-modified date on every page: as article:modified_time or dateModified in the page, a visible "Last updated" line, or a Last-Modified header. Agents can then tell how current a page is; the date itself is not judged.
Check your fix:
curl -sI https://maps.express/ | grep -i last-modifiedreturns a date, or the page carriesarticle:modified_timeor a visible "Last updated" line.Links and section anchors work
All 1 links checked on the sampled pages work.
Sitemap entries still exist
All 7 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
Not part of the score: optional extras that help agents use your docs.
MCP server is discoverable
No MCP server was found for these docs.
Offer a read-only MCP server with a search tool over your docs, and link it from llms.txt, so agents in Cursor, Claude and ChatGPT can query your docs directly.
llms-full.txt is available
No llms-full.txt found at https://maps.express/llms-full.txt.
Publish /llms-full.txt with the full text of your docs in Markdown, so an agent can load everything in one request instead of crawling page by page.
Check your fix:
curl -sI https://maps.express/llms-full.txtreturns 200.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
- Oct 8, 2026
- Pages tested
- 5 of 5 found
- Platform
- Unknown
- Kind of site
- Developer docs
- AFDocs score, on its own
- 59 (F), 8 of 23 checks pass
- Based on 5 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.
- 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 (5)
- https://maps.express/
- https://maps.express/en/
- https://maps.express/en/kontakt
- https://maps.express/en/impressum
- https://maps.express/en/datenschutz
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/maps)HTML
<a href="https://documentation.ai/agent-score/maps"><img src="https://documentation.ai/agent-score/badge/maps.svg" alt="Agent Readiness Score: 59 (F)" height="20"></a>Agent-ready docs by default
Live in under 5 min · No credit card required