인터페이스는 현지화되어 있으며, Skill 소개와 설명 문서는 선택한 언어로 AI가 자동 번역합니다. 코드·명령어·경로·전문 용어는 원문을 유지하며 원작자 문서가 우선합니다.
Skills 둘러보기
데이터 및 연구 · SKILL.md

heading-structure

heading-structure

When the user wants to write or optimize H1-H6, fix heading hierarchy, improve content structure, rewrite an H1, or align headings with page intent. This skill owns actual heading changes; page-metadata may only check and report metadata-to-heading alignment.

Independent GitHub snapshot · Automated classification · Original documentation governs

Skill 문서

GitHub

name: heading-structure description: When the user wants to write or optimize H1-H6, fix heading hierarchy, improve content structure, rewrite an H1, or align headings with page intent. This skill owns actual heading changes; page-metadata may only check and report metadata-to-heading alignment. metadata: version: 2.0.0

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: Clear visible page headline that confirms the user's task and value
  • Header tags (H1-H6): Logical content hierarchy and one coherent section per heading

Initial Assessment

Project context: Read root contextus.md when present and load only the modules relevant to this task. Without Contextus, use available project material or user-provided facts and ask for missing information; do not create a parallel context system.

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
Primary page headingPrefer one clear H1 that identifies the page; audit accessibility and template semantics before treating an extra H1 as a ranking emergency
Search languageInclude the primary concept naturally when useful; do not force exact-match phrasing
DescriptiveClearly describe page content
Match intentServe the same page intent and promise as the title tag without requiring identical wording

H2-H6 Hierarchy

PrincipleGuideline
Logical orderUse heading levels to express document structure; do not choose a level for visual size alone
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 H1sConfirm the template and accessibility semantics; prefer one clear primary H1, but do not present extra H1s as an automatic ranking failure
Visual styling encoded as hierarchyKeep semantic level based on structure and style it separately
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: Checks and reports title/H1/body alignment; routes actual heading edits here
  • 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 and title share page intent but may use different natural variants
  • schema-markup: Article schema uses headline (often H1)
  • content-strategy: Content outline informs headings
저장한 Skills