--- copyright: "© 2026 DSR Corporation" title: "Found by Google — and by AI" slug: seo-and-discoverability order: 40 type: doc description: "Built-in docs SEO — sitemaps, llms.txt, per-page titles, Open Graph, and JSON-LD, generated on every build." seoTitle: "Docs SEO: sitemaps, llms.txt, Open Graph & JSON-LD" seoDescription: "Built-in documentation SEO — auto sitemaps, per-page titles and descriptions, canonical URLs, Open Graph cards, JSON-LD, and an llms.txt so AI assistants cite your docs." icon: Globe visibility: public llmSummary: "DSR Docs generates SEO and AI-discoverability artifacts (sitemap.xml, robots.txt, llms.txt, llms-full.txt, per-page Open Graph, JSON-LD, and title/description overrides) automatically on every content build. Pages are indexable by default with per-page noindex/draft/hidden opt-outs, and guest-access modes split public from private on one deployment. Sitemap and llms.txt require an absolute https baseUrl. The artifacts are self-hosted and served from the deployment itself with no external SEO service." faq: - q: "Does DSR Docs generate a sitemap and robots.txt automatically?" a: "Yes, on every content build. The engine writes sitemap.xml with every published page and a robots.txt for your domain, so there is no SEO plugin to install and nothing to regenerate by hand. Both need an absolute https baseUrl configured, so the URLs they emit resolve to your live site." - q: "What is llms.txt, and does DSR Docs generate one?" a: "It is a structured map of your documentation written for AI assistants rather than browsers. DSR Docs emits llms.txt and llms-full.txt on every build, so ChatGPT, Claude, Perplexity and the rest can read and cite your documentation instead of guessing at it." - q: "Can I stop a documentation page from being indexed?" a: "Yes. Pages are indexable by default, and any page can opt out: mark it noindex, keep it as a draft, or hide it entirely. If you need a public surface and a private internal set on one deployment, guest-access modes let anonymous readers see what you choose and gate the rest." - q: "Does every page get its own title, description and social preview?" a: "Yes. Each page carries its own SEO title and description overrides, an Open Graph card for link previews, and JSON-LD structured data — generated by the same build that produces the sitemap." - q: "Do I need an external SEO service or plugin?" a: "No. Every artifact is produced by the engine itself and served from your own deployment. The site you are reading is the proof: its sitemap.xml, robots.txt and llms.txt were written by the last content build on this box, with no third-party service involved." --- # Found by Google — and by AI Docs nobody can find aren't worth writing. DSR Docs treats discoverability as a first-class feature: every page is public and indexable by default, and the build emits everything search engines and AI crawlers expect — no plugins, no config marathon. ## What SEO files does DSR Docs generate on every build? - **`sitemap.xml`** — every published page, ready for Search Console. - **`robots.txt`** — sane crawl rules, generated for your domain. - **`llms.txt` and `llms-full.txt`** — a clean, structured map of your docs so LLMs cite *you* instead of guessing. This is the raw material behind [making your docs discoverable by AI assistants](/docs/use-cases/make-your-docs-discoverable-by-ai-assistants). - **Per-page SEO** — title and description overrides, Open Graph cards, and JSON-LD structured data on every page. The sitemap and `llms.txt` files need an absolute `https` `baseUrl` configured so the URLs they emit resolve to your live site. ## How do I control which pages get indexed? Pages are indexable by default, but every page can opt out: mark it `noindex`, keep it as a draft, or hide it entirely. Need a public marketing surface *and* a private internal set? [Guest-access modes](/docs/use-cases/expose-api-docs-to-external-customers) let anonymous readers see what you choose and gate the rest — same site, one deployment. ## Why does documentation SEO matter? Great docs are a sales channel. When a prospect searches a problem your product solves — or asks an AI assistant — DSR Docs makes sure your answer is the one that surfaces. It's the same [single engine](/docs/guides/one-engine) that renders your OpenAPI, GraphQL, and C/C++ references, so every kind of page ships with the same discoverability baked in. > [!TIP] > **You're reading proof, not a pitch.** This site runs on DSR Docs — so the artifacts above aren't a roadmap, they're already live under it. Open [`/sitemap.xml`](/sitemap.xml), [`/robots.txt`](/robots.txt), or [`/llms.txt`](/llms.txt) in another tab and you'll see this very documentation indexed by the same engine you'd deploy. No external SEO service generated any of it; the engine wrote those files on the last content build, served straight from the box this site runs on. > [!IMPORTANT] > **Want this on your own documentation?** Write to docs@dsr-corporation.com. Ask about migration, licensing, or anything this page didn't cover.