GEO FixAI search readiness check

AI search fix

How to add llms.txt in Docusaurus

In Docusaurus, publish llms.txt as a static asset so production serves it at /llms.txt after build and deploy. Keep the file short: title, summary, and links to core documentation pages. Then confirm HTTP 200 on your live domain. Docusaurus makes static publishing straightforward, but usefulness still depends on crawl access and content quality.

If your docs site sits behind Cloudflare, check that AI crawlers are not challenged at the edge. A valid static file is not enough when a WAF blocks requests.

Docusaurus llms.txt setup

  1. Place llms.txt in the static assets path for root-level output.
  2. Add a brief summary and links to core documentation pages.
  3. Build and deploy; verify /llms.txt on production returns 200.
  4. Review robots and edge policy for trusted AI user-agents.
  5. Update llms.txt when docs IA or versioned routes change.

Free · 2 minutes · no card

See what AI crawlers hit on your site

Technical blockers, missing context, weak AI-readiness signals — in one HTML report.

No card and no payment for the free check. Prices for Starter and Pro exclude VAT as shown on the site. GEO Fix does not guarantee AI visibility or citations.

You'll get an HTML report on llms.txt reachability and AI crawler access for your docs domain.

Frequently asked questions

Can llms.txt live under /docs/ instead of the root?

Best practice is the root path /llms.txt on the primary host.

Do versioned docs break llms.txt links?

They can. Prefer stable canonical links and review after each release.

Does Docusaurus llms.txt guarantee assistant citations?

No. It aids orientation but does not force source selection.

Updated