seo-action-planlisted

# SEO Action Plan ## 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. ## Non-negotiable boundaries - Do not promise inclusion, ranking, citation, referral, traffic, revenue, or conversion lift. - Do not invent a platform requirement. In particular, do not prescribe `llms.txt`, special “AI schema”, chunk sizes, bot access, or a crawler-control change unless the supplied evidence and the applicable platform documentation support it. - Separate an observed issue from its likely cause and from the proposed change. - Never treat a crawler request or bot log as evidence of retrieval, grounding, citation, referral, or conversion. - Do not turn a speculative or experimental finding into a normal implementation action. Keep it as a monitored experiment or decline it. - Require human approval for production, policy, legal, accessibility, analytics, or crawler-control changes.