Workflow guide · 4 minute read
Audit heading structure
Heading issues are easy to count and awkward to diagnose in a raw export. Put the page and its H1 and H2 values in one view, confirm what is really missing or repeated, and trace the fix to the right page, component, or template.
Best for template QA, redesigns, CMS migrations, and content audits
18-second workflow
Find the page, then read the heading evidence.
Recorded in the installed SEO Crawler 0.1.8 app using deliberate public fixtures. This crawl contains real Multiple H1s and Missing H2 findings; it does not fabricate a Missing H1 result. The player loads only the recording that matches your theme.
What happens in the demo
Start with the completed crawl
The Issues panel stays open and the table shows URL, Status Code, H1, and H2. No result is selected yet.
Choose Multiple H1s
The issue filter reduces the crawl to the technical-audit fixture, the only page with more than one H1 in this crawl.
Identify the affected page
The URL is selected first so the heading evidence remains attached to the page that produced it.
Inspect both H1 values
The H1 cell shows “Technical audit fixture” and “Duplicate H1 fixture,” confirming the issue without opening the page source.
Switch to Missing H2
Nine fixture pages appear. The final selection pairs the migration-checklist URL with its empty H2 cell.
Catch template drift before it spreads.
Heading structure often changes quietly when a hero, card, or CMS block is reused. The page still renders, but its primary subject may disappear or the same level may be assigned to several unrelated elements.
Use this workflow after redesigns, component releases, content imports, and migrations. Reviewing the affected URLs together helps you spot whether one page is unusual or one shared layout is creating the same problem repeatedly.
Review the page and its headings together.
- 1.
Run a complete crawl
Enter the site URL and wait for the crawl to finish. The demo uses the public Lil Robots fixture site so the result is safe and repeatable.
- 2.
Keep the page and headings together
In Pages, show URL, Status Code, H1, and H2. Freeze URL before moving horizontally so the heading text never loses its page context.
- 3.
Review H1 findings
Expand Headings in the Issues panel. Choose Missing H1 or Multiple H1s when those groups contain results, then compare the URL with the H1 cell.
- 4.
Review pages without H2s
Choose Missing H2 and inspect page purpose before assigning work. A short page may not need subsections, while a long guide often benefits from them.
Practice with the public crawler fixtures. Their heading problems are intentional test data.
Treat each group as a question, not a verdict.
- Missing H1
- Check whether the page has a clear visible subject and whether its template omitted the primary heading. Add one when it improves page meaning and accessibility, not merely to satisfy a count.
- Multiple H1s
- More than one H1 is not automatic proof of harm, but repeated page-level headings often reveal duplicated components or a layout that promotes section labels too aggressively. Inspect the actual text and template.
- Missing H2
- An H2 is useful when a page contains distinct subsections. A concise utility page may legitimately have none. Treat this group as a review queue, not a blanket requirement.
Fix the source, then crawl again.
Make the change in the page, CMS block, or shared component that generated the heading. After deployment, run a fresh crawl and confirm that the intended URLs have left the issue group without creating a new hierarchy problem elsewhere.
A useful handoff includes the affected URL, the current heading values, the intended hierarchy, and the owning template or component. When one shared cause affects many pages, assign one implementation task and keep the URLs as verification cases.
Export the affected pages for handoff