Heading Structure in the WordPress Block Editor

Choose WordPress heading levels from document hierarchy, never from desired font size.

The page title usually supplies H1. Main sections then use H2, with subsections beneath.

Confirm the frontend template first. Themes can change which heading represents the visible title.

Understand heading hierarchy

Headings name sections and describe their relationships. Levels communicate nesting within the document.

An H3 belongs inside the nearest preceding H2 section. An H4 belongs inside an H3.

The official Heading block guide documents levels, shortcuts, Outline access, styles, and settings.

Think in nested sections

• H1 names the page.
• H2 names a main section.
• H3 names an H2 subsection.
• H4 names an H3 subsection.
• H5 and H6 continue deeper nesting.

Depth should reflect meaning. It should not reflect the design’s available text sizes.

Start with the page purpose

Write one sentence describing the page’s job. That sentence helps constrain the section plan.

Every main heading should support that job. Remove sections belonging to another search intent.

A focused outline makes level choices easier. Mixed purposes create competing hierarchies.

Draft the outline before styling

1. Write the working page title.
2. List the main reader questions.
3. Group related questions.
4. Name each group with H2 text.
5. Add necessary H3 subsections.
6. Remove duplicate or orphaned sections.
7. Then apply visual styles.

This order separates information architecture from decoration. Later design changes cannot distort meaning.

Confirm who owns H1

WordPress commonly renders the post or page title as H1. The theme template controls that output.

Some landing templates hide titles or use custom hero headings. Inspect the public page.

Do not add another H1 reflexively. First establish whether the template already provides one.

Handle hidden page titles

A hidden title may still render in markup. CSS visibility and semantic presence are different questions.

Inspect the frontend element and accessibility tree. Do not rely on the editor canvas.

If no meaningful H1 exists, assign one through the supported template or content workflow.

Use H2 for main sections

Main sections divide the page’s central argument or task. Each should remain understandable independently.

Use descriptive language matching reader needs. Avoid generic labels like “More information.”

Several H2 sections can exist. There is no magical ideal count.

Use H3 for genuine subsections

An H3 should elaborate one active H2 topic. It should not begin an unrelated main section.

Ask whether the heading needs its parent for context. If not, H2 may fit better.

Do not use H3 because its theme size looks convenient. Choose a style instead.

Use H4 through H6 sparingly

Deep levels can represent complex reference material. Ordinary articles rarely need extensive depth.

Many deep headings can signal overlong sections or confused grouping. Consider splitting the page.

Never jump deeper merely to shrink text. Typography and hierarchy remain separate.

Do not choose levels by visual size

Theme styles can make one level larger or smaller. The number still communicates section depth.

Use typography controls, block styles, or theme settings for appearance. Preserve semantic relationships.

A small H2 remains an H2. A giant Paragraph remains a Paragraph.

Separate display headings from semantics

Marketing designs often need large slogans or eyebrow labels. They may not introduce document sections.

Use Paragraph blocks and appropriate styles for decorative display text. Do not pollute the outline.

Conversely, real section labels need Heading blocks. Small visual treatment does not remove meaning.

Write headings for scanning

Readers often scan headings before choosing a section. Make every label specific and informative.

Prefer “Choose fixed-width cells” over “Settings.” The first predicts the section’s decision.

A heading should still make sense outside nearby decoration. Screen reader navigation depends on text.

Keep heading text concise

Long headings can wrap awkwardly and overwhelm navigation lists. Remove unnecessary setup words.

Do not sacrifice specificity for extreme brevity. “Benefits” says little without context.

Use the shortest wording that still predicts the section accurately. Then answer immediately.

Avoid keyword-stuffed headings

Repeated query variants create noisy outlines. They also make the page feel machine-written.

Use natural terms where they describe the section. Synonyms should arise from meaning.

Google explicitly discourages keyword stuffing. Useful organisation matters more than repetition.

Avoid empty headings

An empty Heading block creates an unnamed section or unnecessary markup. Delete accidental placeholders.

Patterns can contain instructional placeholders. Replace or remove every one before publication.

Check Outline for blank entries. Then inspect the public page.

Avoid headings without content

A heading should introduce meaningful content. One sentence may be enough, but decorative labels need reconsideration.

Consecutive headings often reveal an empty section. Confirm the nesting intent before publishing.

Move the lower heading or add the missing section explanation. Do not leave ambiguity.

Avoid skipped levels while authoring

Move from H2 to H3 for a child section. Avoid jumping directly toward H4.

A skip may reflect pasted formatting or visual choice. Correct the semantic level first.

Google says order is not a magical ranking rule. Logical order still helps navigation.

Do not worship perfectly sequential levels

Semantic clarity serves people and assistive technology. It should not become superstitious SEO theatre.

Google’s guide says out-of-order headings do not create a special search penalty.

Fix structure because it improves the document. Do not promise ranking gains from renumbering.

Use the Heading block toolbar

Select the Heading block and choose its level through Transform. The sidebar also exposes levels.

Confirm the new level after conversion. Copying content can retain unexpected settings.

Do not change level accidentally while applying a visual style. Review Outline afterwards.

Use slash shortcuts carefully

Typing `/heading` inserts a Heading block. Shortcuts like `/h2` can select a level directly.

Hash shortcuts also create headings from new lines. More hashes produce deeper levels.

Speed should not bypass hierarchy decisions. Choose the intended parent section before typing.

Use Document Overview while drafting

The Outline tab shows page headings in sequence. It provides a quick hierarchy view.

Review it after creating main sections. Catch missing parents before writing thousands of words.

Outline reflects editor content. Template headings may require separate frontend inspection.

Use List View for nested layouts

List View shows headings inside Groups, Columns, Covers, and patterns. Visual layouts can obscure order.

Move the complete section container when appropriate. Moving only its heading separates ownership.

Check underlying order after column changes. Visual position can differ from reading sequence.

Structure comparison pages

Use H2 for major comparison questions. Use H3 for criteria within one question.

Card titles need heading levels only when each card forms a real subsection.

A repeated product name can be plain text. Do not create dozens of unnecessary headings.

Structure how-to pages

Use H2 for major phases or complete steps when sections contain substantial explanation.

Use ordered lists for short steps. Every list item does not require a heading.

Place troubleshooting sections after the main process. Their headings should name observable failures.

Structure reference pages

Reference pages may need deeper hierarchy. Group properties or concepts before creating many headings.

Consistent level choices support predictable scanning. Repeated entry templates can help.

Split very deep references into linked pages. One enormous outline can become unusable.

Structure FAQ sections

Use one H2 for the FAQ group. Individual questions may use accordion headings or summaries.

Do not assume every disclosure summary becomes a document heading. Inspect its rendered semantics.

Use separate H3 questions only when visible sections need heading navigation. Keep the pattern consistent.

Structure sidebars and callouts

A callout title may introduce a complementary section. Choose level from its document relationship.

Decorative labels such as “Tip” can remain Paragraph text. They need not enter the outline.

Repeated callout headings can clutter navigation. Use semantic headings only when readers benefit.

Structure card grids

Card titles often represent parallel subsections beneath one grid heading. H3 can fit that relationship.

However, navigation cards may only label links. Headings are not automatically required.

Choose one model across comparable cards. Mixed semantics create confusing outlines.

Structure Columns blocks

Columns control visual layout, not document hierarchy. Heading levels still follow content relationships.

Reading order usually follows source order before visual columns. Test narrow stacking and assistive navigation.

Do not give each column an H2 merely for symmetry. Section importance may differ.

Structure Query Loop output

A Query Loop can repeat Post Title blocks. Their configured levels affect the page outline.

Use one section heading before the results. Choose repeated title levels beneath it.

Pagination pages can repeat the same structure. Test archives and embedded loops separately.

Structure template parts carefully

Headers, footers, and sidebars can contain headings on every page. Those headings join each document.

A footer widget title may add repeated outline entries. Confirm whether a heading provides navigation value.

Review templates alongside content. Authoring rules cannot ignore shared site regions.

Handle repeated patterns

Patterns can preserve appropriate levels for one context. Reuse elsewhere can change the necessary depth.

Use adaptable patterns or document their placement assumptions. A reusable H3 needs an H2 parent.

Review inserted patterns through Outline. Reuse should not mean semantic blindness.

Style headings through Global Styles

Global Styles can define typography and spacing for heading levels. Central rules reduce local hacks.

Make neighbouring levels visually distinguishable without extreme jumps. Maintain readable contrast and line height.

Do not change semantic levels to escape poor theme styles. Fix the style owner.

Use block styles for alternate appearances

A Heading block style can change appearance while preserving its level. That separation is useful.

Name styles by purpose, not fixed pixels. “Section label” communicates more than “Twenty-four.”

Test each style across supported levels. Avoid combinations that erase hierarchy visually.

Avoid inline formatting as hierarchy

Bold text can emphasise words. It does not introduce a navigable document section.

Convert genuine section labels into Heading blocks. Convert decorative pseudo-headings into styled Paragraphs.

Make the decision from content role. Visual weight alone remains ambiguous.

Plan headings in content briefs

A brief can propose H2 questions and expected H3 depth. Writers can adjust from evidence.

Do not freeze headings before research. New findings may change the argument’s structure.

Mark mandatory topics and optional examples separately. This prevents accidental hierarchy inflation.

Set collaborative heading rules

• Page title usually owns H1.
• Main content sections use H2.
• Subsections use sequential child levels.
• Styles never determine levels.
• Headings remain descriptive and concise.
• Patterns require context review.
• Frontend templates require final inspection.

Simple rules improve consistency. Exceptions should document their structural reason.

Review heading changes during editing

Moving sections can change their parents. Update levels when hierarchy changes.

Deleting an H2 can orphan later H3 headings. Promote or relocate those subsections deliberately.

Copy edits can also weaken labels. Recheck whether headings still predict their content.

Test the frontend outline

1. Open the public page.
2. Identify the rendered H1.
3. List every heading in order.
4. Include template and widget headings.
5. Check nested section relationships.
6. Compare mobile reading order.
7. Test heading navigation with assistive technology.

Editor Outline is valuable but incomplete. Shared template regions join the final document.

Test heading links and anchors

Heading blocks can carry HTML anchors. Stable anchors support direct links toward sections.

Changing heading text need not change a manual anchor. Preserve durable fragment identifiers.

Test sticky-header offsets and focus behaviour. Reaching a heading should expose it visibly.

Do not link entire long headings

The Heading block supports inline links. Linking the whole label can create unexpected section navigation.

Use a separate descriptive link when the heading’s main job is section labelling.

If a card heading links, ensure the relationship remains obvious. Avoid duplicate nearby links.

Handle translations

Translated headings can expand significantly. Test wrapping and spacing without changing levels.

Language structure may require different wording. Preserve section relationships rather than literal brevity.

Manual HTML anchors may remain language-neutral. Document the policy before translation begins.

Handle imported content

Document imports can carry style-driven headings or bold paragraphs. Inspect every converted level.

Do not trust visual similarity after pasting. Use Outline and List View to confirm structure.

Remove empty headings and formatting remnants. Conversion is the start of review.

Handle plugin blocks with title fields

Some blocks render title text as headings. Others use paragraphs or generic containers.

Check whether the level is configurable. Inspect rendered output when documentation remains unclear.

A visually prominent title may never enter the outline. Decide whether that semantics fits.

Know when fewer headings work better

Short pages need little hierarchy. Several paragraphs can sit under one clear section.

Adding headings every few sentences can interrupt flow. Group content by meaningful topic changes.

This is the honest weak case. More headings do not equal more SEO.

Use the heading-authoring checklist

1. Define the page’s purpose.
2. Confirm the template’s H1.
3. Draft main H2 sections.
4. Add genuine child subsections.
5. Choose levels from parent relationships.
6. Style appearance separately.
7. Use descriptive natural wording.
8. Review Document Overview.
9. Review nested blocks in List View.
10. Inspect the complete frontend outline.
11. Test heading navigation.
12. Recheck after structural edits.

Frequently asked questions

The verdict

Core Heading covers ordinary authoring well. Try free specialist tools for unusual workflows. Then compare the $299 lifetime suite when several Pro blocks fit maintained sites.