Heading Structure
Fix H1–H6 hierarchy and on-page heading SEO so landing pages and articles rank clearly without multiple H1s or broken outline logic.
Overview
heading-structure is an agent skill most often used in Launch (also Grow) that optimizes H1–H6 hierarchy and heading SEO for on-page content.
Install
npx skills add https://github.com/kostja94/marketing-skills --skill heading-structureWhat is this skill?
- On-page scope: one H1 per page, logical H1–H6 hierarchy, primary keyword near H1 start
- Initial assessment for page type, primary keyword, and section outline
- Reads .claude/project-context.md or .cursor/project-context.md for target keywords when present
- Best-practice tables for H1 principles and header tag structure
- Points to seo-strategy skill for full SEO workflow beyond headings
Adoption & trust: 768 installs on skills.sh; 586 GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your pages have messy headings, duplicate H1s, or weak keyword placement so search engines and users cannot scan the content outline.
Who is it for?
Solo builders polishing marketing pages, docs sites, or blogs after content exists but before or after publish.
Skip if: Full technical SEO audits (crawl budget, Core Web Vitals-only work) or sites with no editable HTML/content layer.
When should I use this skill?
User wants to optimize heading structure (H1–H6), fix hierarchy, or mentions H1, heading tags, heading SEO, or multiple H1—or for on-page heading work before broader seo-strategy.
What do I get? / Deliverables
You get a corrected heading hierarchy and keyword-aware H1–H6 recommendations that match page intent and your project keywords.
- Recommended H1–H6 outline
- Heading hierarchy fix list aligned to primary keyword
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Launch/SEO is the primary shelf because the skill targets searchable page structure and keyword placement in headings. SEO subphase matches explicit triggers: heading hierarchy, heading SEO, multiple H1, and content structure fixes.
Where it fits
Before publishing a product landing page, set one keyword-rich H1 and nest feature sections under descriptive H2s.
Refresh an old blog post whose H3s skip levels so the outline matches search intent and readability.
Structure waitlist page headings so the value prop H1 matches the hero and sections follow a single hierarchy.
How it compares
Use for heading-tag on-page structure; pair with seo-strategy instead of expecting keyword research and link planning here.
Common Questions / FAQ
Who is heading-structure for?
Indie founders and marketers who write their own landing pages and articles and need fast, correct H1–H6 SEO structure.
When should I use heading-structure?
Use it at Launch when shipping SEO pages, in Grow when refreshing blog posts, and whenever you mention H1, heading hierarchy, heading tags, or multiple H1 issues.
Is heading-structure safe to install?
It is editorial guidance only; review the Security Audits panel on this Prism page and avoid letting the agent change production CMS content without your review.
Workflow Chain
Then invoke: seo strategy
SKILL.md
READMESKILL.md - Heading Structure
# 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: 1. **Page type**: Homepage, article, product, etc. 2. **Primary keyword**: Target search query 3. **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](https://developers.google.com/search/docs/appearance/title-link) ## 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