← ClaudeAtlas

seo-programmaticlisted

Use when designing, auditing, or improving scaled/template-driven SEO pages, data-backed landing-page systems, or large URL inventories; require source data, usefulness, variation, indexing controls, and rollout safeguards rather than scale or keyword coverage targets.
oegeyilmaz9/seo-aeo-geo-ultimate · ★ 2 · AI & Automation · score 75
Install: claude install-skill oegeyilmaz9/seo-aeo-geo-ultimate
# Programmatic SEO ## Purpose Assess or plan scalable page systems without creating index bloat, misleading content, or unmaintainable templates. The unit of review is the page system: input data, template logic, user task, content differentiation, URL/canonical rules, quality controls, and rollout behavior. Read `references/scaled-page-protocol.md` before approving a template or rollout. Read [editorial-vs-indexability.md](references/editorial-vs-indexability.md) before deriving publication or search status from record fields. Read [corpus-propagation-contract.md](references/corpus-propagation-contract.md) before changing a canonical, redirect, sitemap, discovery, locale, or whole-corpus rule. ## Input gate Require the page-system purpose, target reader/task, data dictionary and provenance, source update cadence, template/rendered examples, locale/market rules, canonical/indexability policy, internal linking logic, quality owner, and proposed rollout. Do not infer product facts, locations, prices, availability, comparisons, or user demand from keyword lists alone. ## Workflow 1. **Model the user value and product decision.** Explain what distinct decision/task each page can satisfy, what evidence or data makes it different from nearby variants, and the explicit product-owner end state for the bounded corpus. 2. **Inspect inputs and template.** Verify data ownership, freshness, null/error handling, sourced claims, locale logic, entity identity, URLs, canonical behavior