On desktop, CSS styling rules hide the main heading, but it is visible on mobile. Check whether visitors can see the page title on both screen sizes. Then find the CSS hiding the main heading (H1): an old media query—a CSS rule for a specific screen width—may have been left behind after a design change.
Where visitors see the page title
Google recommends keeping the main content comparable across mobile and desktop versions. Official documentation.
First, check where visitors can find out what the page is about on desktop. The H1 may have been replaced by a visible title in another component, or it may have disappeared accidentally. Compare the design with the actual implementation. The number of H1s alone does not tell you whether the interface is clear. Do not assume there is an automatic penalty for a second heading or a hidden responsive element. Note which heading users should see on each screen. If the text is intentionally hidden, check whether it is still available to a screen reader—a program that reads the interface aloud—and whether another title is repeated nearby.
Fully hidden versus visually hidden
| Heading | How it is hidden | What to consider | How to check the page |
|---|---|---|---|
| display:none on desktop | The heading is completely hidden | Check its purpose | The page topic is clear |
| Visible H1 on mobile | A different layout | Compare the content | No accidental loss |
| Visually hidden text | A separate technique | Check accessibility | Do not confuse it with display:none |
| Increased zoom | Line wrapping changes | Check the interface | No overlap |
display:none removes the element from the display and accessibility tree. Visual hiding can leave it available to assistive technologies. MDN description of display.
Check the computed styles for the H1
In your browser's developer tools (DevTools), find the H1. In the Computed tab, check the final values for display, visibility, and dimensions: they show which CSS rules have been applied. Identify the media query that changes the rule and the corresponding CSS file. Then check the accessibility tree using an available browser tool. Compare the original HTML with the HTML after scripts run—the DOM: a component may replace the heading after loading. Also check for containers overlapping it and for content clipped by the overflow property; the element may exist and have display:block but still not be readable. A screenshot at a single screen size does not show the cause, so note the rule, viewport width, and state of the relevant element.
Select the H1 in the Elements tab and run this in the browser console:
[...document.querySelectorAll("h1")].map(el => ({ текст: el.textContent, display: getComputedStyle(el).display, visibility: getComputedStyle(el).visibility, ширина: el.getBoundingClientRect().width }));If display changes around 1024 px, find the corresponding media query in Styles. display:block does not rule out clipping by a parent's overflow: check both the element and its container.
Check widths around the media query breakpoint
If the element starts being hidden at 1024 pixels, check widths immediately below and above the breakpoint. Then change the page zoom and text size. Page zoom can change the effective layout and cause the two versions to overlap. For example, in the old first-screen layout, the heading was hidden above 1024 px. After the redesign, that rule remained, even though the new version should show the H1. Remove only the obsolete condition. Compare desktop, mobile, and an intermediate width, where both responsive copies often appear. Do not judge the result based only on the device name.
Restore the heading in the shared component
If the H1 should be visible, remove the hiding style and check its spacing and line wrapping next to the main text. Do not create a separate local copy if the shared component already serves both screen sizes. If hiding is an intentional accessibility technique, confirm its purpose and correct implementation. Keep the semantics clear for any visible alternative title. Testing with a keyboard and assistive technology can help identify unnecessary duplication. The presence of an H1 in the HTML does not confirm the fix: read the heading on the page and check it in the accessibility tree.
Check two screens and increased zoom
The page title is readable on desktop, mobile, and at increased zoom. The two responsive copies do not overlap or repeat in the accessibility tree. A neighboring page using the shared component also displays correctly.
Read also: How HTML errors affect SEO and indexing and Color contrast under WCAG: accessibility requirements and testing. Website checks are available on the reChecker technical audit page.