WordPress Document Outline: Fix Headings Before Publishing

Open Document Overview, then select Outline. WordPress displays content counts, reading time, and the page’s heading hierarchy.

Use that hierarchy to find skipped levels, empty sections, and misleading structure. Fix meaning before adjusting visual styles.

The outline is a fast diagnostic. It does not prove accessibility, search quality, factual accuracy, or complete content.

What the WordPress document outline shows

• Character count.
• Word count.
• Estimated reading time.
• Paragraph count.
• Block count.
• Headings in their structural order.
• Heading levels and nesting.

The official block editor guide places Outline beside List View inside Document Overview. Those tabs answer different questions.

List View shows every block and parent. Outline shows the reader-facing heading skeleton. Use both during complex reviews.

Open the Outline tab

1. Open the post or page editor.
2. Select Document Overview in the top toolbar.
3. Choose Outline beside List View.
4. Read counts and heading order.
5. Select suspicious headings for inspection.

Interface labels can change across WordPress releases. Document Overview currently houses both structural tools. Use current official documentation when training.

Treat the outline as a table of contents

Read only the headings from top to bottom. Can you predict the page’s argument, sequence, and section boundaries?

A strong outline makes sense without body paragraphs. It does not need clever wording. It needs accurate, distinct section promises.

Repeated vague headings weaken navigation. “More information” says little. “How renewal dates affect access” gives a useful destination.

Do not force every heading into a question. Use questions when readers actually ask them. Use statements for clear concepts.

Understand heading levels

Level	Typical role	Common mistake
H1	Primary page topic	Duplicating the theme’s title
H2	Major section	Using it only for size
H3	Subsection within an H2	Appearing without a parent section
H4–H6	Deeper nested topics	Creating unnecessary depth

Each lower level should belong beneath the nearest higher level. H3 content should refine its preceding H2 section.

Check which element owns the H1

Many themes render the post title as an H1. Some custom templates behave differently. Inspect the actual frontend markup.

Do not add another H1 automatically inside content. Confirm template behaviour first. One clear primary heading usually creates simpler structure.

Site titles, logos, and navigation labels can also use headings poorly. The content outline may not expose every template-level element.

Audit the rendered page when H1 ownership matters. Browser inspection and accessibility tools provide stronger evidence than assumptions.

Find skipped heading levels

A jump from H2 to H4 usually signals missing structure or decorative level choice. Inspect the H4’s intended relationship.

If it starts a direct subsection, change it to H3. If another concept is missing, add the meaningful parent section.

Do not add empty headings merely to complete numbers. Headings need content and purpose. Repair the information architecture instead.

Occasional exceptions require context. Treat the warning as an investigation trigger. Verify navigation with assistive technology.

Find headings chosen for appearance

Editors sometimes choose H4 because it looks smaller. That changes document meaning. Use styles to change appearance instead.

Transform the block to the correct level. Then apply an approved block style or typography setting. Keep semantics independent.

Likewise, large bold Paragraph blocks do not enter the outline. If they introduce sections, convert them into proper headings.

Do not convert every prominent sentence. Calls to action and pull quotes may remain non-heading content.

Fix headings through the block toolbar

Select the Heading block. Choose the correct level from its toolbar or settings. Recheck the outline immediately.

Keyboard users can transform headings with platform shortcuts. The official shortcut guide lists current combinations.

Change one structural level at a time. Review descendants afterwards. Promoting a parent may require promoting its nested sections.

Make every heading describe its section

A heading should predict the content that follows. Avoid promises the section never answers. Avoid clever labels needing surrounding context.

• Weak: “Getting started.”
• Clear: “Create a staging copy before migration.”
• Weak: “Important considerations.”
• Clear: “Check licence ownership before client handover.”
• Weak: “The problem.”
• Clear: “Why nested Groups become difficult to select.”

Specific headings help scanning, search snippets, and AI retrieval. They also expose missing answers during editorial review.

Use question headings for direct answers

Question headings work when the section answers a recognisable query. Put the direct answer in the first following paragraph.

Then add conditions, steps, evidence, and limitations. This structure helps readers and answer systems identify a complete response.

Do not rewrite every heading as a question for optimisation. Repetition sounds mechanical. Mixed forms improve reading rhythm.

Use the words readers use when accurate. Avoid unnatural keyword repetition. One precise heading can own the query clearly.

Keep section depth proportionate

A short article rarely needs H5 or H6. Excessive depth makes scanning difficult. It can reveal overcomplicated information architecture.

Split very large sections when readers need distinct decisions. Merge tiny sections when each contains only one incomplete thought.

Heading frequency should follow content, not a fixed word interval. Long uninterrupted text still deserves review for scannability.

Check headings inside patterns

Patterns can insert preset heading levels. Their source cannot know every destination. Review the outline after insertion.

A card pattern may include H3 headings. That works beneath an H2 section. It fails when inserted without that context.

Design patterns with documented heading expectations. Use neutral content structures where possible. Test them in every approved context.

Synced patterns require extra care. A shared heading change can affect several page outlines. Review representative consumers first.

Check headings inside accordions and tabs

Plugin blocks may render headings that the editor Outline does not represent completely. Inspect their frontend HTML and keyboard behaviour.

Accordion titles need meaningful structure and control semantics. A visual heading alone does not make an accessible disclosure.

Tabbed interfaces can hide visible sections while preserving headings in markup. Test reading order, focus, labels, and relationships.

Use the Outline as one view. Provider documentation and rendered inspection remain necessary for specialised interactive blocks.

Check reusable and shared headings

Shared content can repeat identical headings across pages. Repetition is not automatically wrong. Context decides whether the heading fits.

A shared “Contact support” section may work consistently. A shared H2 may conflict when consumers need different hierarchy.

Record expected insertion level. Consider leaving the outer heading outside shared content. That gives each page structural control.

Find orphaned headings after content removal

Deleting body content can leave an empty heading. The outline still shows its promise, but no useful answer follows.

Review the space between consecutive headings. Confirm each section contains relevant content. Remove empty headings or restore the missing answer.

Also find body paragraphs placed beneath the wrong section. Moving headings without their content can create plausible-looking structural errors.

Use counts as clues, not targets

Word count and reading time help plan effort. They do not measure usefulness, accuracy, or search performance.

A short direct answer can outperform a padded section. A long technical guide may need detail. Match length to intent.

Paragraph and block counts can expose fragmentation. Many tiny Paragraph blocks may read poorly. One enormous block also deserves inspection.

Estimated reading time remains approximate. Audience knowledge, code, tables, and interactive content change actual reading speed.

Check heading order on mobile

Responsive layouts can visually reorder columns or stack them differently. The document outline follows source structure, not screenshots.

Preview narrow screens and read section transitions. Confirm headings remain near their content. Avoid layouts requiring visual position for meaning.

Keyboard and screen-reader navigation should follow a sensible sequence. Test the rendered page. The editor preview cannot prove this alone.

Check search and answer intent

Map each major heading to a reader need. Remove sections serving only internal enthusiasm. Add missing decisions supported by evidence.

Keep adjacent headings distinct. Two sections answering the same query compete within one page. Merge them or sharpen their boundaries.

Put definitions before exceptions. Put prerequisites before steps. Put consequences near decisions. Logical order helps extraction and comprehension.

Compare the title with the outline

Every major section should support the page title. Interesting tangents can still weaken topical focus. Move them elsewhere when necessary.

Check whether the outline answers the title’s implied promise. A “how to” title needs actionable stages and completion evidence.

A comparison title needs explicit criteria and tradeoffs. An explanation needs definitions, boundaries, examples, and limitations.

Review duplicate headings carefully

Duplicate heading text can be legitimate across repeated items. However, identical major headings often create weak navigation.

Add meaningful qualifiers when sections differ. “Costs for agencies” and “Costs for clients” produce clearer destinations than two “Costs” headings.

Do not vary wording only to avoid duplication. Distinctions must match content. Otherwise merge the sections.

Ignore common heading SEO myths

A heading level is not a ranking multiplier. Repeating keywords in every H2 creates weak prose and unclear sections.

Heading structure helps readers and systems understand relationships. It cannot rescue thin evidence, inaccurate claims, or mismatched intent.

Use important terms where they describe the section naturally. Prefer specific language. Avoid forced synonyms added only for perceived coverage.

Multiple H1 elements are valid in some technical contexts. Simpler publishing templates usually benefit from one clear page heading.

Review translated heading structures

Translations can expand headings and change familiar query language. Review meaning, hierarchy, and scanning in every supported language.

Do not translate keywords mechanically. Local editors know the questions readers use. Give them structural context and decision ownership.

A translated pattern may retain its heading level but lose its useful distinction. Test the full outline after localisation.

Check card and table headings separately

Card titles may be headings when they introduce distinct sections. They may be labels when repeated inside another structure.

Choose semantics from navigation and relationships, not card appearance. Repeated H3 cards usually need an H2 parent section.

Table header cells are not document headings. Use proper table headers for rows and columns. Do not substitute Heading blocks.

Inspect specialised blocks on the frontend. Their internal titles may not appear fully inside WordPress Outline. We looked at that in whether blocks help SEO.

Pair Outline with List View

Outline finds a structural heading problem. List View locates the surrounding blocks and parent containers. Use each tool’s strength.

The List View guide explains exact selection and hierarchy. Switch tabs without losing the wider document review.

After fixing, return to Outline. Confirm the hierarchy changed as intended. Then inspect the rendered frontend.

Run a pre-publish outline review

1. Confirm the frontend H1 owner.
2. Open Document Overview and Outline.
3. Read headings without body copy.
4. Find skipped or decorative levels.
5. Check every heading has relevant content.
6. Remove vague and duplicate promises.
7. Confirm patterns fit their destination.
8. Check section order against reader intent.
9. Preview narrow screens.
10. Inspect rendered heading markup.
11. Test keyboard heading navigation.

Repeat the review after major structural edits. A clean outline can deteriorate when sections move, duplicate, or disappear.

Know what Outline cannot verify

• Whether headings answer their promises accurately.
• Whether the page has one rendered H1.
• Whether plugin controls use accessible semantics.
• Whether visual order matches source order.
• Whether hidden content behaves correctly.
• Whether links and media are accessible.
• Whether search engines will rank the page.
• Whether AI systems will cite it.

It catches visible hierarchy problems quickly. Combine it with editorial review, frontend inspection, accessibility testing, and factual verification.

Frequently asked questions

The verdict

Specialist content blocks should preserve meaningful heading choices and markup. Test free versions first. Then compare the $299 lifetime suite when several Pro blocks fit the page structure.