Docs discoverable by AI assistants & search
Make your docs discoverable by AI assistants
The files AI crawlers actually look for
Structured data on every page
Summaries you write, not ones a model invents
How it works in DSR Docs
Make your docs discoverable by AI assistants DSR Docs makes your documentation citable by AI assistants by generating the machine-readable files crawlers look for — llms.txt, llms-full.txt, sitemap.xml, and robots.txt — on every content build, plus per-page JSON-LD and summaries. Most documentation sites give language models nothing to work with no machine-readable index, no per-page summaries, no structured data. So when someone asks an AI a question your docs answer, your page is the one it cites — not a competitor's blog, and not a hallucinated guess. The files AI crawlers actually look for On every content build, DSR Docs writes four discoverability files to your site root - — a clean, structured index of your documentation. It leads with your site title and tagline, then an admin-editable preamble, a Start here list of your featured pages, and a Full index of every public page. Each entry is a title, a link, and a one-line summary — exactly the map an assistant needs to find and cite the right page. - — the full Markdown body of every public doc page, concatenated with per-page URL and description headers, so a model can ingest your entire corpus in one fetch (capped at 5 MB). - — every published page, with drawn from each file's modification time so edited pages get re-crawled promptly. - — sane crawl rules that allow your public docs and disallow admin, edit, and API routes. Structured data on every page Each page renders JSON-LD structured data — for doc pages, otherwise — plus Open Graph tags ( , , ) and a canonical link. That gives search engines and AI answer engines an unambiguous, typed description of what each page is , not just a wall of HTML to parse. Summaries you write, not ones a model invents Two controls decide how you're represented - A site-wide llms preamble , edited live from the admin panel, tells assistants how to describe your product and which pages matter. - A per-page (set in each page's SEO panel, alongside , , and ) becomes the one-line description in . Write it once and that's the sentence an assistant is most likely to echo. [!IMPORTANT] and / are only emitted once you set an absolute in the admin panel. Without it, DSR Docs can't write the absolute URLs these files require, so it skips them (and removes any stale copies) rather than publish broken links. and per-page JSON-LD/Open Graph still render. If your docs run private ( ), these public discovery files are withheld by design. How it works in DSR Docs Set your and write a short llms preamble in the admin panel. Add an to the pages you most want cited, and mark your key pages as featured so they lead the Start here list. Rebuild content, and DSR Docs regenerates , , , and — all served from your own infrastructure, no external SEO service in the loop. [!IMPORTANT] Sounds like your case? Write to docs@dsr-corporation.com. We'll show you the engine on documentation like yours, and say plainly what a move would involve.