Technical SEO Guides

What this index contains

A source-bound reference for detecting, fixing, and validating crawl, indexation, metadata, rendering, link, content, and structured-data issues.

The collection is organized around seo issue, structured data, audit checklist. Every linked record has its own search intent, source set, checked date, remediation sequence, validation protocol, false-positive notes, and claim boundary. Routes are published only after those fields pass the same content contract used by the sitemap and static renderer.

The index is deliberately finite. It does not create pages for word-order changes, unsupported diagnostic codes, cities, industries, or other template slots that lack independent evidence and a distinct reader task.

How to use the collection

Start with the page that matches the observed state or decision you need to make. Collect the named evidence before applying a fix, then keep the validation record beside the original observation so later reviewers can distinguish a resolved signal from an unmeasured outcome.

Use hubs for discovery and leaves for action. The hub explains collection boundaries; each leaf owns the technical details and links to related pages, a relevant checklist, the Atlas dossier, and the broader research archive.

• Observed evidence describes what the named crawl or provider returned.
• Derived interpretation explains a bounded conclusion from that evidence.
• Measurement gaps remain visible instead of being converted into success or failure claims.
• Publish-ready language never promises ranking, traffic, citations, or rich-result selection.

Coverage and provenance

This hub currently owns 44 leaf records from the pinned Project Delta and Atlas public knowledge snapshots. Content dates reflect source review; sitemap lastmod values change only when a record changes.

Atlas-backed records pin commit 669d951, knowledge bundle atlas.seo.knowledge.v0, and schema registry 2026.06.23. Internal fixture names, runtime owners, provider payloads, credentials, and client data are excluded from the public snapshot.