Search intent coverage (SERP → outline)
You help the user build an outline that matches what Google is ranking and adds differentiated value.
Shared context first
Run the shared preflight in ../docs/credentials-and-tooling.md. Read .seo-context.md when present, reuse its saved market, audience, topic, and competitor context, and ask only for query- or draft-specific gaps.
Inputs to collect
- Primary query
- Market (language + country)
- Intended audience and content type, when they are not clear from context
- Business goal or desired reader action, when it affects the outline
- Optional: the user’s current URL/draft
Tooling & credentials
- Auth mode:
none or mcp, depending on the SERP source
- Requires: live SERP access through a structured provider API, SERP MCP, or browser tool
- Fallback: use a browser to inspect live results, or analyze user-provided competitor URLs or outlines and label the result
competitor-only
- If no live SERP path is available: use the documented
competitor-only branch without claiming current SERP coverage
Live SERP analysis needs a live SERP source. Use structured data from a provider API or MCP when available, and use a browser when it is not. If no live source is available, continue with the documented competitor-only branch when the user provides suitable pages or outlines.
Workflow
- Fetch the SERP for the query (top 10), or record that the run is
competitor-only and use the supplied pages.
- Identify dominant intent type:
- informational / commercial / transactional / navigational
- Extract patterns:
- repeated H2 topics
- repeated definitions/FAQs
- common “proof” elements (examples, templates, calculators)
- Build a non-overlapping outline:
- above-the-fold “answer fast”
- core explanation
- decision help (when commercial)
- pitfalls, FAQs, examples
Give each section one job, remove repeated topics, and note any intentional overlap (such as a short answer that expands later).
- Add 2–3 differentiated elements (proprietary angle), labeling each as one of:
- checklist, interactive component idea, original data, teardown, template
Prefer three when evidence supports them; return two when a third would be decorative or weak, and explain the omission.
Output
- “What people want” (1 paragraph)
- Non-overlapping outline (H1 → H2 → H3)
- “Differentiators to win” (2–3 bullets, each tied to a gap or evidence point)
1---2name: search-intent-coverage3description: Build a standalone search-intent analysis or content outline from localized SERP evidence or competitor pages. Use when the user wants to understand and plan coverage without drafting the complete article.4---56# Search intent coverage (SERP → outline)78You help the user build an outline that matches what Google is ranking **and** adds differentiated value.910## Shared context first1112Run the shared preflight in [`../docs/credentials-and-tooling.md`](../docs/credentials-and-tooling.md). Read `.seo-context.md` when present, reuse its saved market, audience, topic, and competitor context, and ask only for query- or draft-specific gaps.1314## Inputs to collect1516- Primary query17- Market (language + country)18- Intended audience and content type, when they are not clear from context19- Business goal or desired reader action, when it affects the outline20- Optional: the user’s current URL/draft2122## Tooling & credentials2324- Auth mode: `none` or `mcp`, depending on the SERP source25- Requires: live SERP access through a structured provider API, SERP MCP, or browser tool26- Fallback: use a browser to inspect live results, or analyze user-provided competitor URLs or outlines and label the result `competitor-only`27- If no live SERP path is available: use the documented `competitor-only` branch without claiming current SERP coverage2829Live SERP analysis needs a live SERP source. Use structured data from a provider API or MCP when available, and use a browser when it is not. If no live source is available, continue with the documented `competitor-only` branch when the user provides suitable pages or outlines.3031## Workflow32331. Fetch the SERP for the query (top 10), or record that the run is `competitor-only` and use the supplied pages.342. Identify dominant intent type:35 - informational / commercial / transactional / navigational363. Extract patterns:37 - repeated H2 topics38 - repeated definitions/FAQs39 - common “proof” elements (examples, templates, calculators)404. Build a non-overlapping outline:41 - above-the-fold “answer fast”42 - core explanation43 - decision help (when commercial)44 - pitfalls, FAQs, examples45 Give each section one job, remove repeated topics, and note any intentional overlap (such as a short answer that expands later).465. Add 2–3 differentiated elements (proprietary angle), labeling each as one of:47 - checklist, interactive component idea, original data, teardown, template48 Prefer three when evidence supports them; return two when a third would be decorative or weak, and explain the omission.4950## Output5152- “What people want” (1 paragraph)53- Non-overlapping outline (H1 → H2 → H3)54- “Differentiators to win” (2–3 bullets, each tied to a gap or evidence point)
younesbenallal