Example: A visual module creates an incorrect heading hierarchy
A page builder can output any large module header as H1. As a result, several headlines of the same rank appear on the page, although the editorial team expects a logical subdivision. A similar effect occurs when hidden desktop and mobile variants remain in the document at the same time.
Finding the triggering point
Open the list of headings in the rendered document and assign each entry to the visible module. Check the configuration of the HTML tag separately from font size and design. Compare the output at different screen widths and with dynamically open areas.
Checking a limited fix
In the module, separate the semantic level from the visual size. The actual page header gets its clear role; section headers adapt to the content structure. Remove duplicate variants only if no required mobile or accessible display is lost.
Check the corrected component on several pages where it is used. A module that functions as H2 on a landing page may need H3 in a deeper article structure. The solution chosen should allow this embedding, rather than re-establishing a rigid global level.
Symptoms in the audit
- Important content only appears after JavaScript
- Heading structure is inconsistent
- Images or links missing in rendered HTML
Then they test the cause.
- 1. Compare rendered HTML with source code
- 2. Test builder components individually
- 3. Check template for mobile and desktop
Fixed route
- Send critical content to the server
- Standardize heading and image components
- Maintain builder-specific SEO fields