> ## Documentation Index
> Fetch the complete documentation index at: https://docs.synscribe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# How to Optimize a Documentation Site for SEO, GEO, and Agent Discovery

> Research user questions, write focused documentation pages, and build the technical foundation that helps search engines and AI agents find and use them.

To optimize a documentation site for SEO, GEO, and agent discovery, give every important user
question one complete answer at one stable URL. Align the URL, title, description, opening, and
headings around that question, then deliver the same answer in crawlable HTML and clean machine-readable
formats.

This five-lesson course takes you from the business case to the finished technical foundation. You
will learn how to evaluate a page, optimize its discovery surface, research the questions worth
owning, and verify that search engines and agents can retrieve the published answer without guessing.

## Learn documentation SEO and GEO in five lessons

| Lesson                                                                                                              | What you will be able to do                                                                                         |
| ------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------- |
| [Why documentation matters for discovery](/theory/documentation-site/why-documentation-matters)                     | Explain how documentation supports users and helps people, search engines, and agents discover a product            |
| [What makes a good documentation page](/theory/documentation-site/what-makes-a-good-documentation-page)             | Evaluate whether people and agents can find and use a page, then identify the required archetype                    |
| [Optimize documentation pages for SEO and GEO](/theory/documentation-site/optimize-documentation-pages-for-seo-geo) | Align a page's URL, title, description, H1, opening, and headings around one searchable question                    |
| [Research documentation questions](/theory/documentation-site/research-documentation-questions)                     | Replace assumptions with a Question Map, evidence, one owner URL per question, and a prioritized backlog            |
| [Build the technical foundation](/theory/documentation-site/technical-foundation)                                   | Deliver one crawlable identity, canonical HTML, accurate inventories, clean Markdown, contracts, and crawler policy |

The course teaches the practical discovery rewrite before question research on purpose. It answers
“What should I change on this page?” first, then teaches how to replace assumptions and placeholders
with evidence.

## Follow the documentation optimization sequence

Follow the core lessons in order:

1. Understand the support and growth case the course will prove.
2. Separate the page's find and use jobs, then choose its archetype.
3. Improve the page's discovery surface so its exact job is clear.
4. Research real questions and replace editorial assumptions with evidence.
5. Make the answer crawlable, canonical, machine-readable, and version-correct.

Do not begin with `llms.txt`, schema, or an AI-crawler switch. Those features can reduce retrieval
friction after a useful answer exists. They cannot create the answer, demand, relevance, or trust.

## Start with the documentation task you need

* **Improving an existing page for discovery:** start with the
  [page optimization lesson](/theory/documentation-site/optimize-documentation-pages-for-seo-geo),
  then use
  [question research](/theory/documentation-site/research-documentation-questions) to validate its
  assumptions.
* **Planning a new documentation site:** follow the five core lessons in order.
* **Migrating or repairing a docs platform:** start with the
  [technical foundation](/theory/documentation-site/technical-foundation).

The standard throughout this section is observable completion. A title that gains impressions but
sends readers to the wrong page is a failure. A Markdown endpoint that returns `200` but loses the
warning or code example is a failure. A generated answer that cites the docs but produces an invalid
request is a failure.