Agent Skills
› sediman-agent/OpenSkynet
› heading-structure
heading-structure
GitHub用于优化H1-H6标题层级结构，修复逻辑跳跃、多H1等问题，提升SEO与内容可读性。适用于提及heading、H1、标题层级等场景。
Trigger Scenarios
用户希望优化标题结构（H1-H6）
修复标题层级混乱
改进内容结构
提到 H1, heading, heading hierarchy, content structure, H2, H3, heading tags, heading SEO, multiple H1, heading structure
Install
npx skills add sediman-agent/OpenSkynet --skill heading-structure -g -y
SKILL.md
Frontmatter
{
"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,\" \"content structure,\" \"H2,\" \"H3,\" \"heading tags,\" \"heading SEO,\" \"multiple H1,\" or \"heading structure.\" For SEO workflow, use seo-strategy."
}
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
Version History
- c9d8953 Current 2026-07-05 19:59
