Checking WordPress page templates for duplicate headings
The page title appears once at the top. Then again, right underneath, in slightly different styling. Two H1s, both saying the same thing.
The page still looks fine to most people. But repeated or out-of-order headings confuse screen-reader users and blur the page’s structure. Before you touch the body copy, look at the template and the rendered page together.
Duplicate headings can come from the theme, page builder, block content or reusable sections. A page-level edit may not solve the issue if the template is generating the second heading everywhere.
Inspect the rendered heading structure
Choose representative pages that use the template and inspect the visible content and heading elements. Note the text, level and source of each heading. A page title may be rendered as an H1 automatically, while the editor has also added the same text as a block heading.
Check the browser’s accessibility tree or use a screen reader to understand how the headings are announced. Look at the page outline and ensure the sections form a useful hierarchy. Heading levels should reflect structure, not just visual size; use styles for appearance rather than skipping levels to make text smaller.
Don’t rely only on a crawler report. I always look at the page myself before deciding what the report means. A duplicated heading may be hidden visually, included in an off-canvas menu or generated by a plugin. Confirm whether it is available to visitors and whether it serves a real purpose.
Trace the source
Review the WordPress template, theme options, page builder settings and reusable blocks. Determine whether the title is automatically output and whether a template option can suppress it on selected pages. Check custom post types and archives, which may use different templates.
If a plugin adds breadcrumb or schema headings, inspect the actual markup and settings before removing it. Avoid deleting a heading from the editor when the template is the cause. I’m not a fan of fixing a template problem one page at a time. That creates a page-specific workaround and leaves the underlying issue in place.
Test a safe change in staging. Update the template or content source once, then inspect several pages that use it. Watch for a title disappearing on pages where it was the only H1 or for a shared change affecting unrelated content types.
Balance semantics and design
A page can have one clear H1 without forcing it to be visually large. Use CSS or theme styles to match the design while preserving a meaningful heading level. If a visual hero title is decorative, confirm that the accessible structure still communicates the page topic.
Subheadings should describe the sections that follow. Avoid repeating the page title as a section heading unless the repetition genuinely helps the reader. Check the rest of the hierarchy after resolving the duplicate; a page may also skip levels or use headings for bold styling.
Retest on mobile and other templates
Templates can render differently at breakpoints or when a page has a long title. Check desktop, mobile and relevant post types after the fix. Document which template changed and who owns the setting so a future redesign does not reintroduce the duplicate.
Check templates and content types separately
WordPress may render the site title as an H1 on a homepage, while single posts use the post title and archives use a different heading. Page builders can also add a visible title independently from the theme. Build a test set that includes the homepage, a post, a static page, an archive and any custom post type. Do not assume that one template represents the entire site.
Review mobile and desktop output. Some themes hide one heading visually at a breakpoint while leaving it in the document, or duplicate a title only on mobile. Check the accessibility tree and source where necessary to understand what users and assistive technology receive.
If a duplicate appears only when a featured component is present, inspect the component’s conditions and field mapping. It may render the page title and a manually entered heading together. Correct the template logic or update the content model so editors are not asked to remember a workaround.
Make a regression test
After a template change, compare a small set of known URLs. Confirm that each page still has a clear title, a logical heading order and no repeated H1. Check that a post without a custom heading still has an accessible page topic. Save the test URLs for future theme updates.
When an SEO plugin or page builder changes, review its title and heading output again. Updates can alter defaults or add markup that was previously absent. Keep track of the responsible component and who owns future changes.
Explain the fix to editors
Tell content owners whether they should enter a page title in the editor or let the template display it. If the template controls the H1, do not ask editors to add the same text manually. Clear guidance prevents the duplicate from returning with new content.
Consider search and accessibility tooling
A crawl can identify pages with multiple H1 elements or missing headings, but it may not show whether the page is understandable. Use automated checks to find patterns, then inspect a sample manually. A screen reader’s heading list can reveal whether the sequence helps someone navigate or simply repeats design labels.
Don’t treat one H1 as a magic ranking requirement. I don’t think it ever was. The practical goal is a clear topic and logical structure. A page can have an accessible hierarchy even if its visual design uses several prominent text styles, and a page with one H1 can still be confusing if its subheadings are poor.
If the site has templates in several languages, check longer translations and right-to-left pages. Heading order and title duplication may appear only when the text wraps or a translated template uses a different field. Document the test case and review after theme updates.
Related reading
- Reviewing WordPress excerpt settings across post templates
- How to review a WordPress search plugin before deployment
- How to assess the search impact of merging WordPress categories
A clean heading structure starts with knowing which layer creates each heading, and the fix should live where the duplicate is created. Open one post, one page and one archive and list every heading in order. Which one is printing the title twice: the editor’s content or the theme?