Checklist

Agent readiness checklist for docs sites

Documentation sites usually win or lose on structure. If assistants cannot identify canonical guides, reference pages, navigation paths, and setup flows, content depth matters less than it should.

Run a fresh scan llms.txt hub

Most common gap

Canonical docs paths are unclear

Most important surfaces

Index, setup, reference, policies

Best companion file

llms.txt plus sitemap.xml

Checklist

The first pass for a docs public surface

Canonical structure

There is one obvious docs home or index.

Reference and guide pages are not mixed randomly.

The newest canonical page wins over stale duplicates.

Navigation clarity

Important setup paths are reachable in one or two clicks.

Breadcrumbs, section labels, and headings are descriptive.

Related docs are linked with meaningful anchors.

Trust and operations

Auth, limits, pricing, or support boundaries are easy to find.

Policy pages are public if they affect real usage.

Versioning and freshness are visible enough to avoid stale interpretation.

Machine-readable layer

robots.txt, sitemap.xml, and canonical tags are in place.

llms.txt prefers setup guides, docs index pages, and reference pages.

No important docs path depends only on hidden client-side navigation.

Use it well

What this checklist should expose quickly

Docs look complete, but there is no single obvious starting point for assistants.

Reference and guide content both exist, but they are mixed too loosely to feel canonical.

Setup pages are public, yet auth, pricing, or usage boundaries are still hard to verify.

The docs are technically crawlable, but internal paths still depend too much on app-like navigation.

Continue through the cluster

Agent readiness checklist for SaaS

A practical checklist for pricing, docs, trust, and action paths.

llms.txt vs robots.txt

See where each file helps and where it does not.

canonical tags example for docs sites

See how canonical tags should point assistants toward the stable docs version, not stale duplicates.

Next step

Review the live docs surface before you tune the files

Start by checking whether setup, reference, policy, and navigation paths already feel canonical. Then use llms.txt as a support layer for that structure.

Run a fresh scan llms.txt hub