Fix guides · Accessibility
How to fix heading order (skipped heading levels and empty headings)
Headings that jump from H1 to H4, or exist only for styling, break the page outline screen reader users navigate by. How to fix them on Shopify, WordPress, Webflow, Wix, Squarespace and Next.js.
- Time to fix
- 15–45 minutes
- Skill needed
- No code
- Who notices
- Screen reader users, and search engines reading your structure
Why it matters
Screen reader users often jump from heading to heading to scan a page, the way sighted visitors skim. Heading levels tell them how sections relate: an H3 belongs to the H2 above it.
Skipping levels (H2 straight to H4) or using a heading just to make text big makes that outline misleading. Empty headings are announced as headings with nothing in them.
“Skipped heading levels were present on 41.8% of all pages, up from 39% in 2025.”
Before you start
- Use one H1 per page for its main topic, then H2 for sections, H3 for parts of those sections, and so on, without skipping levels on the way down.
- Choose the level by meaning, not size. If you want a heading to look smaller, change its style, not its level.
- Text that isn't a heading (a tagline, a price, a big quote) should be a paragraph styled to look large.
Fix it on your platform
Shopify
- Shopify's theme accessibility guidance asks for headings in sequence, with the h1 for the page's main topic.
- Section headings are set in theme code. Some themes let you pick a heading size in the theme editor, but the level (h2, h3) is fixed in the section file; change it in Edit code, or ask your theme developer.
WordPress
- Select each Heading block and check its level in the toolbar. In most themes the page title is the H1, so headings in your content start at H2.
- Use the List View or the Document Overview to see every heading on the page in order.
- Headings in the header, footer or sidebar come from your theme or widgets; fix those in the Site Editor or theme settings.
Webflow
- Open the Audit panel from the left toolbar; it flags skipped heading levels on the page.
- Select the heading, open the Settings panel (D) and press the correct heading type (H1–H6). If it then looks wrong, adjust its class rather than its level.
- Use a Paragraph or Text Block for large text that isn't a heading.
Wix
- Wix recommends an H1 on every page with the following tags in sequence, and adding headings to the page body rather than the site header.
- In the Accessibility Wizard, scan the site, open Detected issues and choose the page to fix its heading structure. You can also set a text element's HTML tag in the editor.
- To break a heading over two lines, press Shift + Enter; Enter creates a new heading.
Squarespace
- Use the text toolbar to set headings, with one Heading 1 per page and smaller levels for sections, as Squarespace recommends.
- Don't use heading styles for text that isn't a heading; use paragraph text and change its size instead.
Next.js
- Pass the heading level into reusable components (for example a Card that renders an h2 on one page and an h3 on another) instead of hard-coding it.
- Don't render a heading element when its text is empty.
Any other site
- Nest headings in order and keep one h1. Style with classes, so look and level are separate.
<h1>Running shoes</h1>
<h2>Road</h2>
<h3>Cushioned</h3>
<h2>Trail</h2>
<p class="text-large">Free returns for 30 days</p>Check that it's fixed
- Install a headings browser extension (such as HeadingsMap) and check the outline reads like a table of contents.
- Re-run your StudioLNC audit: the issue should be gone.
Find every issue like this on your site
Free audit of performance, accessibility, SEO and security, with fixes for your platform.