Library / SEO page outline
SEO page outline
Draft a page title, meta description, outline, and FAQs without fake keyword volumes.
Install in Claude Code
Create a folder whose name matches the skill name field (seo-page-outline/). Save the text below as SKILL.md inside it. Personal skills go in ~/.claude/skills/seo-page-outline/. Project skills go in .claude/skills/seo-page-outline/. Claude Code discovers them from the filesystem.
Upload on claude.ai
Zip the skill folder (the zip should contain the folder, which contains SKILL.md) and upload it in Claude’s Skills settings. Anthropic’s current platform docs list custom uploads on Pro, Max, Ultra, Team, and Enterprise plans when code execution is enabled. Check the Claude Help Center for the latest plan details. Read the files before you turn a skill on.
Use with the Claude API
Custom API Skills are uploaded through the Skills API and referenced with the code execution tool. Skills do not sync automatically from Claude Code or claude.ai — install this folder again on the surface where you need it. See Anthropic’s Agent Skills overview.
---
name: seo-page-outline
description: Drafts SEO-minded page titles, meta descriptions, outlines, and FAQs from a topic and audience. Use when the user asks for an SEO outline, title tags, meta description, content brief, or page structure for search.
---
# SEO page outline
## Goal
Produce a brief a writer can execute. Optimize for a clear search intent and honest claims. Do not fabricate keyword volumes, rankings, or "difficulty scores".
## Workflow
1. Identify the primary query, audience, and job the page should do (learn, compare, or buy).
2. If the user did not specify intent, state the intent you inferred and offer one alternative framing.
3. Write 3 title options under about 60 characters and 2 meta descriptions under about 155 characters. Each should include the topic in plain language.
4. Outline H1–H3 sections that answer the query in a logical order. Put the answer near the top, not after a long history lesson.
5. Add FAQ candidates that match real follow-up questions, not keyword stuffing.
6. List internal-link suggestions as types of pages ("pricing", "comparison", "docs") unless the user provided actual URLs.
7. Note claims that will need a source before publishing.
## Output template
```markdown
# SEO outline: [topic]
**Primary intent:**
**Audience:**
**I inferred this because:**
## Title options
1.
2.
3.
## Meta descriptions
1.
2.
## Outline
- H1
- H2
- H3
## FAQ
- Q:
A: [short draft or "needs expert input"]
## Proof and sources needed
-
## On-page notes
- Avoid: thin intros, unverifiable superlatives, keyword repetition that hurts readability.
```
## Rules
- Never invent search-volume numbers, "KD" scores, or competitor rankings.
- If the user wants keyword data, tell them to pull it from their SEO tool and paste the export.
- Do not promise rankings or traffic.
- Write for a human first. Keywords belong where they sound natural.
You may copy and adapt this free skill for personal or commercial use. If you republish it, please credit Skillory with a link. Audit any skill — including this one — before enabling it in an environment with access to private data.
Related skills
Changelog writer
Turn commits and merged PRs into a readable changelog grouped the way users scan it.
Open skill →Code review
Review a diff like a careful teammate: correctness first, then security, then clarity.
Open skill →Git commit messages
Write conventional commit messages from a staged diff, without fluff or invented ticket IDs.
Open skill →