majiayu000/claude-skill-registry-data/heading
Claude Code and agent skill by majiayu000/claude-skill-registry-data
- community
Checking that the SKILL.md file is still in the repository.
Author "majiayu000" has blocked skill(s)
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," "content structure," "H2," "H3," "heading tags," "heading SEO," "multiple H1," or "heading structure." For SEO workflow, use seo-strategy.
Install
npx vskill@latest install majiayu000/claude-skill-registry-data/headingSKILL.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
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
Security
- Security scanPassed, 95 of 100Pattern checks on the skill's files.
- Model reviewPassed
Quality evaluation
- Task evaluationNot runNo evaluation yet. Run one in Skill Studio.
Source
- SKILL.md in the repositoryCheckingother/heading/SKILL.md
Popularity
- 7-day trend score
- 5
Not refreshed yet.
Works with
Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.
- Claude Code
- Cursor
- GitHub Copilot
- Windsurf
- Codex
- Gemini CLI
- Cline
- Amp
- Roo Code
- Goose
- Continue
- Kilo Code
- Junie
- Trae
- OpenHands
- Qwen Code
- AI Agent
- Tabnine Chat
- Sourcegraph Cody
- Amazon Q
- Firebase Genkit
- Sweep
- Devin
- Phind
- Mentat
- Claude Desktop
- Aider
- GPT Pilot
- Plandex
- bolt.new
- v0
- Replit Agent
- Anse
- TypingMind
- BetterChatGPT
- LibreChat
- Warp AI
- Pieces
- Fig AI
Embed badge
[](https://verified-skill.com/skills/majiayu000/claude-skill-registry-data/heading)