SEO
AuraScore 89/100

Growth SEO Lead Developer Documentation Indexation Checklist

Optimize public software documentation, API references, and code libraries for search engine visibility.

Use this checklist to audit developer hubs and technical documentation portals for technical search discoverability. It ensures versioned documentation avoids canonical cannibalization and ranks for core developer queries.

Template

Role: Principal Growth SEO Engineer specializing in developer tooling, open-source documentation, and API discovery.

Context

  • Documentation platform: {{docs_platform}}
  • Target programming languages: {{target_sdk_languages}}
  • Focus search themes: {{primary_search_keywords}}
  • Canonical root domain: {{canonical_root_domain}}
  • Versioning setup: {{versioning_structure}}
  • Code snippet format: {{code_sample_format}}

Task

Produce a technical SEO audit checklist for public-facing software documentation that resolves duplicate version indexing, optimizes code snippet discoverability, and captures high-intent technical search traffic.

Method

  1. Assess how {{docs_platform}} handles canonical tags across deprecated, active, and beta releases under {{versioning_structure}}.
  2. Verify meta robot directives across archive versions to prevent SERP dilution against {{canonical_root_domain}}.
  3. Evaluate code block indexation and syntax rendering for {{code_sample_format}} across {{target_sdk_languages}}.
  4. Review structured data markup (TechArticle, SoftwareApplication) implementations for high-value API endpoints.
  5. Audit internal breadcrumbs, module hierarchy, and sub-nav crawlability across {{primary_search_keywords}} clusters.
  6. Formulate search engine crawl budget controls for dynamic search, filtering, and tag pages.
  7. Define exact verification commands or tools for inspecting each documentation node.

Constraints

  • MUST structure output with clear markdown checkboxes ([ ]) grouped by technical domain.
  • MUST include explicit instructions for managing outdated version URLs under {{versioning_structure}}.
  • MUST NOT suggest noindexing the current latest version of any documentation branch.
  • Limit checklist explanations to two sentences per item.

Output format

A structured markdown checklist broken into: Canonical & Versioning Control, Crawlability & Indexation, Semantic Hierarchy, and Rich Snippets. Include an estimated effort score (Low/Med/High) for each item.

Self-review

  • Verify all 6 context variables are properly integrated into the checklist checks.
  • Ensure specific remediation commands or tool checks are listed for each item.
  • Check that developer-focused SEO nuances (like SDK syntax and version canonicals) are maintained.
AuraScore breakdown
89/100Provisional
Instruction clarity15/15 · Strong

Explicit role, a named task, and discrete steps the model can follow.

Context architecture12/12 · Strong

Background, inputs and variables the model needs before it starts.

Constraint engineering10/12 · Adequate

Hard boundaries — what the model must and must not do.

Output specification14/14 · Strong

A named, field-level shape for the response.

Reasoning structure10/10 · Strong

Ordered work items that force analysis before an answer.

Model compatibility10/10 · Strong

Length and structure that travel across frontier models.

Token efficiency7/10 · Adequate

Signal density — instruction weight without padding.

Reusability7/7 · Strong

Documented variables so the scaffold adapts to new inputs.

Robustness3/5 · Adequate

Quality bar, assumptions and behaviour when inputs are thin.

Observed performance1/5 · Thin

How much real usage the template has behind it.

marketing
marketing-seo
technology-software
developer-docs
seo-audit
api-seo