ZCraft Studios

Last scanned zcraftstudios.comCustom platform15 pages tested

AI agents can use most of these docs. A few fixes would make them reliable. ZCraft Studios scores 84 out of 100 (grade B), passing 20 of 26 checks. 6 still need work.

This covers the whole site. The documentation seems to live at docs.zcraftstudios.com: scan it for a docs-only score.

Fix it with Documentation.AI
#15 on the leaderboardShare on XShare on LinkedIn

Get this report by email

We send the full report to your inbox. Nothing on this page needs an email.

Use your work email. We only send what you asked for, and every email has an unsubscribe link.

Developer docs

Kind of site

20/26

Checks passed

4

Partly passed

2

Failed

Access

Content discoverability4 passed2 failed1 partly

  • llms.txt links point to Markdown

    Same-origin links point to HTML and no markdown alternatives detected (46 external links excluded)

    Your llms.txt links point to HTML pages. Update them to .md URL variants so agents receive markdown instead of converted HTML.

    Check your fix: Links in llms.txt point at .md URLs, or URLs that return text/markdown.

  • Pages point agents to llms.txt

    No llms.txt directive found in HTML of any of 14 sampled pages; 1 failed to fetch

    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://docs.zcraftstudios.com/_mcp | grep -n llms.txt finds the link near the top of the HTML.

  • Markdown pages point agents to llms.txt

    llms.txt directive found in markdown of 1 of 13 sampled pages (12 missing); 2 had no markdown version

    An llms.txt directive was found in the markdown of some pages but is missing from others, or is buried deep in the page. Ensure the directive appears near the top of every markdown page.

    Check your fix: The Markdown version of https://docs.zcraftstudios.com/_mcp (its .md URL, or the page fetched with Accept: text/markdown) has the llms.txt line in its first few lines.

  • llms.txt exists

    llms.txt found at 2 locations; using https://www.zcraftstudios.com/llms.txt as canonical

  • llms.txt follows the standard structure

    llms.txt follows the proposed structure (H1, blockquote, heading-delimited link sections)

  • llms.txt fits in an agent's context

    llms.txt is 8,149 characters (under 50,000 threshold)

  • llms.txt links work

    All 1 same-origin links resolve (47 total links)

Markdown availability1 passed1 partly

  • Server returns Markdown when asked

    Content negotiation partially supported: 12 correct type, 0 wrong type, 2 HTML only; 1 returned error pages

    Your server returns markdown content for Accept: text/markdown requests but with an incorrect Content-Type header. Set the response Content-Type to text/markdown for proper agent handling.

    Check your fix: curl -sI -H "Accept: text/markdown" https://docs.zcraftstudios.com/_mcp returns content-type: text/markdown.

  • Pages are available as Markdown

    13/14 sampled pages support .md URLs (93%)

Page size and truncation4 passed

  • Content is in the HTML without JavaScript

    All 15 sampled pages contain server-rendered content

  • Markdown pages fit in context

    All 13 pages under 50K chars (median 6K, max 13K)

  • HTML pages fit in context

    All 15 sampled pages under 50K chars (median 67K HTML → 8K markdown (75% boilerplate))

  • Content starts near the top

    Content starts within first 10% on all 15 sampled pages (median 4%)

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 19 code fences properly closed across 15 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

    No redirects detected across 15 sampled pages

Content health1 passed1 partly

  • Markdown matches the HTML page

    8 of 12 pages have minor content differences between markdown and HTML; 1 failed to fetch

    8 pages have minor content differences between their markdown and HTML versions.

  • llms.txt covers the whole site

    No sitemap found; cannot assess llms.txt coverage without a sitemap as ground truth

  • Cache headers allow timely updates

    All 17 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://www.zcraftstudios.com/sitemap.xml lists 58 of the 61 docs pages found through llms.txt and page links.

Freshness

Maintenance2 passed1 partly

  • Pages say when they were last changed

    7 of 12 sampled pages state when they were last changed, and 1 more has a date only in the sitemap.

    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://docs.zcraftstudios.com/_mcp | grep -i last-modified returns a date, or the page carries article:modified_time or a visible "Last updated" line.

  • Links and section anchors work

    All 38 links and 15 section anchors checked on the sampled pages work. 7 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

    Found https://www.zcraftstudios.com/openapi.json, but the sampled pages mention no endpoints to compare against it.

CurrencyNot applicable

  • Deprecated operations are marked as such

    https://www.zcraftstudios.com/openapi.json marks no operation as deprecated, so there is nothing to compare.

Additional checks

Not part of the score: optional extras that help agents use your docs.

  • MCP server is discoverable

    An MCP server answers at https://docs.zcraftstudios.com/_mcp.

  • llms-full.txt is available

    llms-full.txt found at https://www.zcraftstudios.com/llms-full.txt (13,177 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
Oct 15, 2026
Pages tested
15 of 45 found
Platform
Unknown
Kind of site
Developer docs
AFDocs score, on its own
82 (B), 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 6 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.zcraftstudios.com/_mcp
  • https://www.zcraftstudios.com/auth
  • https://www.zcraftstudios.com/blog/bluemap-web-map-setup
  • https://www.zcraftstudios.com/blog/geyser-floodgate-bedrock-crossplay-setup
  • https://www.zcraftstudios.com/blog/luckperms-ranks-setup-guide
  • https://www.zcraftstudios.com/blog/mysql-cross-server-player-data
  • https://www.zcraftstudios.com/blog/velocity-proxy-network-setup
  • https://www.zcraftstudios.com/faq
  • https://www.zcraftstudios.com/legal/terms
  • https://www.zcraftstudios.com/minecraft-configs/advancedban
  • https://www.zcraftstudios.com/minecraft-configs/luckperms
  • https://www.zcraftstudios.com/pricing
  • https://www.zcraftstudios.com/products/eternaltags-clean-modern-tags-gui
  • https://www.zcraftstudios.com/products/premium-tab-scoreboard-configuration
  • https://www.zcraftstudios.com/sitemap.xml

Show your score

Add the badge to your docs or README. It updates each time the site is scanned.

Agent Readiness Score badge

Markdown

[![Agent Readiness Score: 84 (B)](https://documentation.ai/agent-score/badge/zcraftstudios-2.svg)](https://documentation.ai/agent-score/zcraftstudios-2)

HTML

<a href="https://documentation.ai/agent-score/zcraftstudios-2"><img src="https://documentation.ai/agent-score/badge/zcraftstudios-2.svg" alt="Agent Readiness Score: 84 (B)" height="20"></a>

Agent-ready docs by default

Documentation.AI sites ship with llms.txt, Markdown pages, a sitemap and an MCP server, and our agent keeps the content current.
Start for FreeBook a Demo

Live in under 5 min · No credit card required