Skip to content
Marketing
Skill

/heading

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

From plugin
kostja94-marketing-skills
872172 skills
Install
$ npx -y skills add kostja94/marketing-skills --skill heading --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/heading

Context preview

The summary Claude sees to decide when to auto-load this skill.

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

SKILL.md

heading.SKILL.md
name: heading-structure
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.
metadata:
  version: 1.0.1

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
Read more
Ships withkostja94-marketing-skills

Markdown skill library for AI agents - SEO, content, pages, paid ads, channels, strategies. Add project context + skills; your agent delivers tailored, production-ready output. Works with Cursor, Claude Code, OpenClaw, Lovable, and any AI that reads markdown.

Get the whole plugin
Stats
875
Stars
122
Forks
Maintained
Maintenance
MIT
License
2mo ago
Last commit
5mo ago
Created

Repo: kostja94/marketing-skills

Other skills on kostja94-marketing-skills.