SEO Tools
Heading outline diff.
Paste the old and new HTML of a page. The tool extracts each H1-H6 outline, aligns them with a longest-common-subsequence diff, and shows what was added, removed, moved or re-levelled.
Inputs
Result
Paste old and new HTML, then press Compare.
How the heading outline diff works
Each input is parsed for native H1 through H6 elements and elements with role="heading" plus aria-level, in source order. The two lists of (level, text) pairs are aligned with a longest-common-subsequence diff, the same idea used by text diff tools. Text is compared after collapsing whitespace and ignoring letter case.
What each label means
- Added / Removed: a heading that exists on only one side.
- Moved: the same level and text appears on both sides but in a different position in the outline.
- Level changed: the same text appears on both sides at a different level, for example H3 became H2.
- H1 count: flagged when the number of H1 headings differs between old and new.
- Skipped levels: flagged in either outline when a heading is more than one level deeper than the one before it, such as H2 followed by H4.
The diff is a structural comparison of heading text and level only. It does not judge whether a change helps or hurts search performance, and duplicate headings are paired in source order.
Sources
- MDN: H1-H6 HTML section heading elements
- MDN: ARIA heading role and aria-level
- Longest common subsequence problem (reference for the diff method)
MDN heading-element and ARIA guidance reviewed September 30, 2026.
Common mix-ups
-
Often assumedAny jump of more than one heading level in an outline, such as h4 followed by h2, is an error.
What the source saysThe W3C tutorial warns against skipping ranks going deeper, but says it is ok to skip ranks when closing subsections. A drop from h4 back to h2 ends sections and is not the same problem as h2 straight to h4. [1]
Checked against these sources on .
Heading outline diff FAQ
Why compare heading outlines before and after a redesign?
Templates and CMS migrations often reorder, rename or re-level headings without anyone noticing. A diff makes those structural changes visible so you can confirm they were intended.
What is the difference between moved and level changed?
Moved means the heading kept its level and text but sits at a different place in the outline. Level changed means the text is the same but the level (H2, H3 and so on) is different.
Does a changed H1 count hurt rankings?
The tool only reports that the count differs. A single descriptive H1 is the clearest pattern, but this tool makes no claim about ranking effects.
Can it fetch two URLs?
No. Browsers block reliable cross-origin fetching, so paste the HTML source of each version.
Is pasted HTML uploaded?
No. Parsing and comparison run locally in your browser, and pasted markup stays inert so embedded resource URLs are not loaded. The page itself still uses the site's analytics and advertising services.
Does it see headings that JavaScript adds after the page loads?
Only if they are in the HTML you paste. A page's source usually contains the HTML as the server sent it, so for client-rendered headings copy the rendered markup from your browser's developer tools instead and paste that into each box.
Why should a page have only one H1 and no skipped levels?
MDN recommends preferring a single h1 per page and nesting headings without skipping levels, because assistive technology users often navigate by jumping between headings and rely on the levels to understand how sections relate. The tool flags a changed H1 count and any heading more than one level deeper than the one before it.
Why compare outlines at all
Headings are the outline of a page. MDN notes that screen-reader users commonly navigate by jumping from heading to heading to find out what a page contains, and recommends preferring a single <h1> per page and nesting headings without skipping levels. W3C's accessibility tutorial on headings makes the same point: a heading's level says how it relates to the ones around it. When a template change, a CMS migration or a redesign touches the markup, headings are among the first things to be re-levelled, merged or dropped without anyone deciding to. A line-by-line diff of the HTML buries that in noise; a diff of just the outline shows it at once.
A worked example, with the real output
Suppose the old page has this outline:
H1 Trail Shoe Guide
H2 Fit
H2 Cushioning
H3 Midsole
H2 Price
H2 FAQ
and the redesigned page has:
H1 Trail Shoe Guide
H2 Fit
H2 Price
H2 Cushioning
H2 Midsole
H4 Weight
H2 FAQ
Pasting both into the tool gives four unchanged headings and three findings:
- Moved: "Cushioning" is still an H2 but now comes after "Price".
- Level changed: "Midsole" went from H3 to H2, so it is no longer a child of "Cushioning".
- Added: a new H4, "Weight". It is also flagged as a skipped level, because the previous heading was an H2 and an H4 jumps over H3.
The H1 count is one on each side, so no H1 warning appears. Each of these changes may be intentional, but none of them would show up in a visual check of the new page, and the skipped level in particular is the sort of defect that survives review.
How to use it in a redesign or migration
- Before the change, copy the HTML of each important template (home, category, article, product) and keep it.
- After the change, copy the same pages from staging. If headings are built by JavaScript, copy the rendered HTML from your browser's developer tools (Elements panel, copy the outer HTML of the main element) rather than the page source, because the source may not contain them.
- Paste old and new, run the diff, and walk through the list. For each removed or re-levelled heading ask whether it was a deliberate editorial decision.
- Fix the skipped-level and H1-count flags first; they are the cheapest to correct and the easiest to justify.
- Keep a short log of accepted differences so the next release is compared with the new baseline.
Common mistakes
- Choosing heading levels for size. MDN warns against using heading elements to resize text; use CSS for appearance and keep the level for structure.
- Comparing different pages. The tool compares two versions of the same page. Two unrelated pages will show nearly everything as added or removed.
- Counting headings hidden in navigation, footers or widgets. A theme that adds an H2 to every sidebar widget changes the outline of every page. Paste only the region you care about if you want to exclude them.
- Reading a clean diff as proof the page is fine. It shows the outline did not change, not that the original outline was good. Run the H1 & Heading Checker on the single version to audit order, empty headings and skipped levels.
- Treating a changed H1 as an automatic problem. Sometimes the H1 should change. The flag simply tells you to confirm it was meant.
How matching works, and its limits
Headings are matched on level and text after collapsing whitespace and ignoring letter case, so "Hello World" equals "hello world". When the same text appears more than once, matches are paired in source order. Because it works on pasted markup, the tool does not fetch URLs, execute JavaScript, or judge whether a changed outline helps or hurts search performance; it reports structure only. For the tags in the head of the page, use the HTML Head Diff Checker.
Sources
- MDN: H1-H6 HTML section heading elementsScreen-reader heading navigation, one h1 per page, no skipped levels, do not use headings to resize text. Retrieved 2026-10.
- MDN: ARIA heading role and aria-levelrole="heading" with aria-level as an alternative to native heading elements. Retrieved 2026-10.
- W3C WAI: Headings tutorialHeading levels convey how sections relate; nesting guidance. Retrieved 2026-10.
- Wikipedia: Longest common subsequence problemBackground on the alignment method used for the diff. Retrieved 2026-10.
Each source was opened and checked against the statements above in October 2026. Standards and vendor documentation change; follow the links for the current text.