Skill

heading-structure

Optimizes HTML heading structure (H1-H6) for SEO and readability, fixes hierarchy issues, recommends keyword-rich H1, and outlines logical H2-H6 based on page type and content.

Html

frontend

documentation

Install

npx claudepluginhub joshuarweaver/cascade-data-analytics --plugin kostja94-marketing-skills-5

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Guides heading (H1-H6) optimization for SEO and content structure.

SKILL.md

Similar Skills

github-deep-research

2 files

Conducts multi-round deep research on GitHub repos via API and web searches, generating markdown reports with executive summaries, timelines, metrics, and Mermaid diagrams.

bytedance-deer-flow-1

63.9k

surprise-me

Dynamically discovers and combines enabled skills into cohesive, unexpected delightful experiences like interactive HTML or themed artifacts. Activates on 'surprise me', inspiration, or boredom cues.

bytedance-deer-flow-1

63.9k

image-generation

2 files

Generates images from structured JSON prompts via Python script execution. Supports reference images and aspect ratios for characters, scenes, products, visuals.

bytedance-deer-flow-1

63.9k

Stats

Stars400

Forks55

Last CommitMar 27, 2026

Actions

View Source View Plugin View on GitHub View README

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