Seo Plan

---
name: seo-plan
description: Use when sequencing validated SEO findings and approved action-plan items into an owner-based roadmap with dependencies, review gates, measurable outcomes, and risk controls; do not use it to invent work, fixed uplift forecasts, or a one-size-fits-all calendar.
---

# SEO Strategy and Delivery Plan

## Markdown delivery contract

Read [markdown-delivery-contract.md](references/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: `roadmap.md; dependencies.md` (combine small related steps with stable section links). Sequence query decisions, source content, inventory/maps, routing, parity review, local acceptance, authorized release and full delivery checks. Preserve both keyword ambition tracks, maintenance owners and direct document links.


## Purpose

Turn validated evidence and approved actions into a delivery roadmap that a team can execute and review. This skill coordinates scope, sequencing, and measurement; it does not create technical/content facts, approve releases, or promise business outcomes.

Read `references/roadmap-protocol.md` before planning a cross-team program.

## Input gate

Require current business goal, audience/market, constraints, owners/capacity, validated audit/research artifacts, approved action-plan items, baseline/report availability, and known dependencies. When inputs are incomplete, produce a discovery plan with explicit assumptions—not a fabricated quarter-long backlog.

## Workflow

1. **Frame decisions.** State the goal, target audience/market, change scope, non-goals, risk tolerance, and measures that are actually available.
2. **Use validated work only.** Include confirmed issues and approved actions. Keep experimental work in a separate learning track. Declined/risky changes remain visible with their conditions.
3. **Sequence dependencies.** Establish source data, site prerequisites, content/technical dependencies, product decision, separate implementation/release/provider approvals, rollout, verification, and rollback before downstream work. For compound work, preserve the router's chain from research and baseline through local acceptance, authorized release, live verification, any separately authorized provider operation, and delayed comparison.
   For broad organic growth, preserve two concurrent roadmap tracks: nearer-term capture/defense and high-volume head-term/category leadership. Put the leadership track's owner and foundation work into the active roadmap even when authority building and leading-position milestones span later stages; do not replace it with quick wins.
4. **Assign outcomes honestly.** Give each initiative owner, acceptance criteria, verification method, guardrail, and review date. A roadmap may target a measurable behavior, but cannot forecast rankings, citations, traffic, or revenue as a guarantee.
5. **Report changes.** Compare only like-for-like observations. Separate delivery status, technical state, search reporting, visibility observations, referrals, and conversions.

## Output

Return a roadmap organized by decision gate and owner: prerequisite, approved action, dependency, delivery milestone, verification/guardrail, and unresolved risk. For broad organic growth, show the nearer-term and head-term leadership tracks separately, including the canonical owner, competitive gap, supporting work, and observable visibility bands. Use target dates only when supplied by a real owner/capacity plan; otherwise label the sequence rather than inventing timing.