Missing H1
h1_missingShort answer
No <h1> on the page. Google can rank pages without one — headings are a weak signal — but the H1 is how readers, screen readers and Google's own title rewriting understand what the page is about. Add a single H1 with the main topic.
Why it matters
Google uses headings to understand structure and, when it rewrites a title link, often takes the H1. Screen-reader users navigate by headings. A page with no H1 is usually a template where the visible headline is styled as a div or an h2, so the fix is mostly markup.
How Glimana detects it
The rule fires for an indexable 200 page with zero <h1> elements in the rendered-as-HTML response.
How to fix it
- Find the affected pages in Glimana. Open Issues › Missing H1. Every affected page is a row; open one to see the evidence Glimana recorded for it (the measured value, the offending element or the target URL). The same list sits on the task card under Tasks, and the page's own detail view under Pages shows its full signals.
-
Apply the fix on your platform.
Themes usually print the post title as H1 on single posts. On the home page or archives the logo or site title may be the only candidate; add an H1 to the template (
header.php/ block theme template) or make the hero heading an H1 in the page builder's heading block.In the section's Liquid, change the headline tag to
<h1>; product titles are H1 by default in most themes.Make the page's primary heading an
<h1>; use<h2>–<h4>for the rest. -
Publish and clear caches. Save and publish, then make sure the crawler will see the new version: WordPress — clear the page cache in your cache plugin and purge the CDN; Shopify — theme and content changes go live on save, but purge any CDN in front of the store; custom code — deploy and purge the edge cache. Check in a private window or with
curl -s https://your-domain/page | grep -i '<title\|canonical\|robots'that the live HTML has changed; Glimana reads what the server sends, not what your browser has cached. - Verify in Glimana. Open the task under Tasks and click Mark as done. The affected pages are queued for a verification crawl within a few hours, and the task closes when the page has an H1. If the check still fails, the task returns to New with a note; when it passes, the task is listed under Resolved technical issues on Impact reports. To check sooner, use Re-crawl affected pages on the issue.
How the fix is verified
Re-crawl; the task closes when the page has an H1.