heading-structure
When the user wants to optimize heading structure (H1-H6), fix heading hierarchy, or improve content structure. Also use when the user mentions "H1", "heading", "heading hierarchy" or "content structure". For SEO workflow, use seo-strategy.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 12
- Forks
- 0
01 前言 Front Matter
- name
- heading-structure
- metadata
- { "version": "1.0.1" }
- description
- When the user wants to optimize heading structure (H1-H6), fix heading hierarchy, or improve content structure. Also use when the user mentions "H1", "heading", "heading hierarchy" or "content structure". For SEO workflow, use seo-strategy.
03 SKILL.md 正文
SEO On-Page: Heading Structure
Guides heading (H1-H6) optimization for SEO and content structure.
When invoking: On first use, if helpful, open with 1-2 sentences on what this skill covers and why it matters, then provide the main output. On subsequent use or when the user asks to skip, go directly to the main output.
Scope (On-Page SEO)
- H1 tag: One per page; clear headline; matches content; primary keyword near start
- Header tags (H1-H6): Logical hierarchy; keyword in headers; one idea per heading
Initial Assessment
Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for target keywords.
Identify:
- Page type: Homepage, article, product, etc.
- Primary keyword: Target search query
- Content outline: Main sections and subsections
Best Practices
H1
| Principle | Guideline |
|---|---|
| One per page | Single H1 per page |
| Primary keyword | Include target keyword naturally |
| Descriptive | Clearly describe page content |
| Match intent | Align with title tag and user intent |
H2-H6 Hierarchy
| Principle | Guideline |
|---|---|
| Logical order | H1 -> H2 -> H3; don't skip levels |
| One idea per heading | Each heading = one topic |
| Scannable | Headings should summarize section content |
| Keyword variation | Use related keywords in subheadings |
Structure
H1 (page title)
-> H2 (section 1)
-> H3 (subsection)
-> H3
-> H2 (section 2)
-> H3
-> H2 (section 3)
Common Issues
| Issue | Fix |
|---|---|
| Multiple H1s | Use single H1; use H2 for other sections |
| Skipped levels | Use H2 after H1, H3 after H2 |
| Generic headings | Make descriptive; avoid "Introduction," "Conclusion" |
| Keyword stuffing | Natural language; avoid forced keywords |
Output Format
- H1 recommendation (with keyword)
- H2-H6 outline for content
- Hierarchy check
- References: Google headings
Related Skills
- featured-snippet: H2/H3 for snippet extraction; semantic HTML for list/table snippets
- page-metadata: Hreflang, meta robots; metadata complements heading structure
- content-optimization: H2 keyword placement, quantity, tables, lists; complements heading structure
- article-page-generator: Article page H1-H3 structure, intro/body/conclusion
- title-tag: H1 should align with title tag
- schema-markup: Article schema uses headline (often H1)
- content-strategy: Content outline informs headings
04 同仓库更多 Skills
youtube
Download YouTube video transcripts when user provides a YouTube URL or asks to download/get/fetch a transcript from YouTube. Also use when user wants to transcribe or get captions/subtitles from a YouTube video.
write-plan
Use when you have a spec or requirements for a multi-step task, before touching code. Produces an engineering plan complete with TDD tasks, DRY/SOLID/YAGNI principles, a required Test Plan & Verification section, and a coverage target — then auto-runs /plan-eng-review as an independent double-check before execution.
worktrees
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification
web-perf
Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.
verify
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
validate-idea
Validate a business idea using the minimalist entrepreneur framework. Use when someone has a business idea and wants to test if it's worth pursuing before building anything.