seo-action-plan
SEO Action Plan
Markdown delivery contract
Read markdown-delivery-contract.md for every task. Write a substantive .md document for every material work step and register its direct destination in the work index.md. For public-site work, apply the owner-required Markdown discovery profile across the full eligible inventory; preserve native standards and immutable evidence formats.
Lane outputs: action-plan.md; acceptance-map.md (combine small related steps with stable section links). Carry owner-required Markdown discovery as a publisher requirement with evidence-linked content/transport acceptance, not a claimed engine requirement. Bind every approved action ID to a substantive .md document, owner, exact affected routes, verification and rollback.
Purpose
Turn evidence-backed findings into a sequenced implementation plan that a content, engineering, analytics, product, or legal owner can approve and execute. This skill plans work; it does not change a site, publish content, modify crawler controls, deploy code, or approve its own recommendations.
Use it after seo-aeo or seo-geo has produced a validated optimization-brief.json, or after a conventional SEO specialist has produced a validated seo-findings.json bundle. For a normal conversational audit without a validated artifact, provide a clearly labelled provisional action list and name the evidence needed before it becomes a formal plan.