More than one H1
h1_multipleShort answer
The page has two or more <h1> elements. Google has said repeatedly that multiple H1s are fine and HTML5 sectioning allows them. Nothing to fix for search. If you want a cleaner outline for readers and screen readers, keep one H1 for the main topic and use H2/H3 below it.
Why it matters
It does not, for ranking. The row exists so you know your outline, and because accessibility guidelines prefer one main heading per page. Informational; no effect on the score.
How Glimana detects it
The rule fires when the page has more than one <h1>; the evidence shows the count.
How to fix it
- Find the affected pages in Glimana. Open Issues › More than one 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.
Keep one H1 that names the page's topic; demote the others to the level that matches their role (section titles → H2, widget titles → H3 or a plain
<p>). The usual extra H1s are the logo text, a sidebar "Recent posts" title, a hero slogan above the real title, or a page builder that gives every section an H1.View the page source and search for
<h1. The logo: themes often wrap the site name in<h1>on every page; change it to<p class="site-title">inheader.phpor the theme's customizer ("Site title tag") so only the front page keeps an H1 there. Widget titles: Appearance › Customize › Widgets, or in block themes change the Heading block level. Page builders (Elementor, Divi): set the heading block's "HTML tag" to H2 for every heading except the page title.In
sections/header.liquidthe shop name is usually<h1>only on the index template and<span>elsewhere; if your theme prints H1 everywhere, wrap it in{% if template.name == 'index' %}. In product and collection templates keepproduct.title/collection.titleas the H1 and change section headings (featured collections, recommendations) to<h2>.Put the H1 in the page template, not in the layout. Grep the layout, header and sidebar partials for
<h1and replace with the right level; in component libraries, make the heading level a prop. -
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 exactly one 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 exactly one H1.