SEO Roadmap Prioritization
Use this skill to turn SEO ideas into product-style roadmap items that can compete for resources, survive planning, and ship through cross-functional teams.
This skill is derived from Eli Schwartz's Product-Led SEO and uses transformed guidance with durable book-topic references. Do not copy book prose into user outputs.
Quick Start
- Load
guidelines.md to choose the relevant reference.
- Use
workflows/prioritize-seo-roadmap.md for roadmap work.
- Translate SEO asks into business language, not SEO jargon.
- Score initiatives by impact, effort, confidence, and strategic fit.
- Include owners, dependencies, resource asks, and measurement.
Default Output
When asked for a roadmap or prioritization, return:
- Roadmap table - initiative, why, fix/build, impact, effort, confidence, owner, dependencies, timing.
- Recommended sequence - now, next, later.
- Resource asks - engineering, product, design, content, data, executive support.
- Executive pitch - business KPI framing and expected payoff.
- Risks and tradeoffs - what may be displaced or delayed.
- Measurement plan - leading indicators and business outcomes.
Contents
| Need |
Start Here |
| Understand SEO as product roadmap work |
references/core/knowledge.md |
| Apply prioritization rules |
references/core/rules.md |
| See scoring examples |
references/core/examples.md |
| Build a roadmap |
workflows/prioritize-seo-roadmap.md |
| Route by task |
guidelines.md |
1---2name: seo-roadmap-prioritization3description: Prioritize SEO initiatives as product roadmap work with impact, effort, confidence, resourcing, executive pitch, cross-functional ownership, quarterly planning, and business KPI alignment. Use when building SEO roadmaps, scoring SEO work, requesting engineering/design/content resources, annual planning, executive buy-in, or turning SEO recommendations into product-ready asks.4license: MIT5---67# SEO Roadmap Prioritization89Use this skill to turn SEO ideas into product-style roadmap items that can compete for resources, survive planning, and ship through cross-functional teams.1011This skill is derived from Eli Schwartz's *Product-Led SEO* and uses transformed guidance with durable book-topic references. Do not copy book prose into user outputs.1213## Quick Start14151. Load `guidelines.md` to choose the relevant reference.162. Use `workflows/prioritize-seo-roadmap.md` for roadmap work.173. Translate SEO asks into business language, not SEO jargon.184. Score initiatives by impact, effort, confidence, and strategic fit.195. Include owners, dependencies, resource asks, and measurement.2021## Default Output2223When asked for a roadmap or prioritization, return:24251. **Roadmap table** - initiative, why, fix/build, impact, effort, confidence, owner, dependencies, timing.262. **Recommended sequence** - now, next, later.273. **Resource asks** - engineering, product, design, content, data, executive support.284. **Executive pitch** - business KPI framing and expected payoff.295. **Risks and tradeoffs** - what may be displaced or delayed.306. **Measurement plan** - leading indicators and business outcomes.3132## Contents3334| Need | Start Here |35|------|------------|36| Understand SEO as product roadmap work | `references/core/knowledge.md` |37| Apply prioritization rules | `references/core/rules.md` |38| See scoring examples | `references/core/examples.md` |39| Build a roadmap | `workflows/prioritize-seo-roadmap.md` |40| Route by task | `guidelines.md` |
ConcertoNotes