SEO and AEO documentation

Make documentation easier for people to find in search and for answer engines to retrieve, interpret, and cite accurately. Content-level SEO and AEO rely on many of the same qualities: clear intent, descriptive titles and headings, direct answers, consistent terminology, useful links, and accurate information.

Improve the documentation itself rather than writing for a presumed algorithm. Optimization can improve discoverability and answerability; it cannot guarantee indexing, rankings, inclusion, traffic, or citations.

Follow the source of truth

Before writing or editing:

• Read the relevant project instructions, style guide, terminology list, templates, and nearby documentation when available.
• Treat the user's requirements and supplied house style as authoritative. Preserve established voice, terminology, formatting, and content types unless the user asks to change them.
• Use product specifications, source code, existing canonical docs, or other supplied authoritative material for factual claims. Do not invent behavior, limits, examples, prerequisites, or availability.
• If authoritative sources conflict or omit a fact needed for an accurate answer, flag the issue instead of guessing.
• When a style guide uses numbered rule IDs, apply and cite its existing IDs during review. Do not create, reuse, or renumber IDs unless the user asks to update that guide.

Establish the search and answer intent

Identify, from the request and available context: