agentleFS
gaznilgaznil/seo-skills-by-gaznil/skills/heading-structure/SKILL.md

heading-structure

Skill0 starsChanged 3 months agoMITView on GitHub

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.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check for project context first: If .claude/project-context.md or .cursor/project-context.md exists, read it for target keywords.

    line 21

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.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:

  1. Page type: Homepage, article, product, etc.
  2. Primary keyword: Target search query
  3. Content outline: Main sections and subsections

Best Practices

H1

PrincipleGuideline
One per pageSingle H1 per page
Primary keywordInclude target keyword naturally
DescriptiveClearly describe page content
Match intentAlign with title tag and user intent

H2-H6 Hierarchy

PrincipleGuideline
Logical orderH1 -> H2 -> H3; don't skip levels
One idea per headingEach heading = one topic
ScannableHeadings should summarize section content
Keyword variationUse related keywords in subheadings

Structure

H1 (page title)
-> H2 (section 1)
   -> H3 (subsection)
   -> H3
-> H2 (section 2)
   -> H3
-> H2 (section 3)

Common Issues

IssueFix
Multiple H1sUse single H1; use H2 for other sections
Skipped levelsUse H2 after H1, H3 after H2
Generic headingsMake descriptive; avoid "Introduction," "Conclusion"
Keyword stuffingNatural 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.