Turns a target keyword and the pages that currently rank for it into a content brief for a new page, covering the search intent, what the ranking pages cover, what they leave out, a proposed outline and the questions to answer. Use when someone needs an SEO content brief, an outline for a page to rank for a keyword, or a gap check against competitors.
Installs into .claude/skills of the current project.
Are you the author of search-intent-page-brief?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/proskillpacks-search-intent-page-brief)
---
name: search-intent-page-brief
description: Turns a target keyword and the pages that currently rank for it into a content brief for a new page, covering the search intent, what the ranking pages cover, what they leave out, a proposed outline and the questions to answer. Use when someone needs an SEO content brief, an outline for a page to rank for a keyword, or a gap check against competitors.
---
# Search intent page brief
You write a brief a writer can start from. It is built from what the ranking pages actually say, not from guesses about search volume or difficulty.
## What you need
1. The **target keyword or question**.
2. The **top results** for it: 3 to 5 URLs of pages that rank (the user copies them from a search). Fetch them with whatever web tool you have. If you cannot fetch, ask the user to paste each page's title, headings and any lists or tables.
3. A line on the **business or site** the page is for, and the audience. Optional: the page type (guide, service page, comparison, product page).
You cannot see live search results, volumes, rankings or keyword difficulty. Never state any of these. If the user gave no URLs, ask for them once; do not invent what ranks.
## Method
1. For each result page, record: title, the H1 and H2 headings in order, word count (rough), format (guide, list, tool, product page), and anything distinctive (a calculator, table, original data, a video, a definition near the top).
2. **Classify the intent** from the mix of formats: informational, commercial investigation, transactional, local or navigational. Give the evidence ("4 of 5 results are step-by-step guides"). If the results mix intents, say so and recommend which to serve.
3. **Coverage table**: topics and subtopics that appear in the results, with a count of how many pages cover each. Mark each as table stakes (3 or more pages), common (2) or rare (1).
4. **Gaps**: things a reader of this query would likely want that none or few of the pages give (be specific, tie each to what you saw missing, and label them as your judgement, not data).
5. **Outline**: proposed title options (under 60 characters), an H1, an H2 list with one line each on what the section must answer, and where to put a table, example or checklist. Keep to what the intent needs. Do not pad.
6. **Questions to answer**: the questions the results answer, plus those the gaps suggest. Use questions seen in the pages' own headings or FAQs; label your own additions.
7. **Terms and entities**: words, names and concepts that recur across the results. Only those you saw.
8. **Meta description draft** under 155 characters, and 3 internal-link slots described by topic (not URLs you have not seen).
## Output
**Keyword and intent** (with evidence), **Results reviewed** (table), **Coverage table**, **Gaps**, **Outline**, **Questions**, **Terms seen**, **Meta draft and link slots**, and **Not known**: volume, difficulty, freshness, backlinks, anything you could not fetch.
## Rules
- Do not copy sentences from the pages. Describe their structure and facts, in your own words.
- Do not recommend a word count as a rule; say "the results run about X to Y words" if you counted.
- No made-up statistics, rankings, tools or traffic claims. Do not promise ranking.
- If one page was blocked or empty, say so and exclude it from the counts.
- Short, plain sentences. No em dashes.