Oh yes, I wasn’t paying attention. I was looking in the browser’s development tools. But in fact, in the source code, I realize that the H1s aren’t there…
This explains why content appears in blocks on web pages, in a confusing order.
I hope it doesn’t hurt the search engines too much …
I’ll get used to living with SEO alerts.
Thanks for your reply.
PS If you want to have a look anyway : fixmyspace.ch
This usually happens when SEO audit tools are not looking at the same version of the page that a browser renders. Many modern websites load content dynamically, so the H1 tag may exist in the rendered DOM but not in the initial raw HTML. Tools like Ahrefs or Ubersuggest sometimes flag missing H1 when they only scan the source code or fail to fully execute JavaScript. Another common reason is multiple templates or conditional layouts where the H1 appears only in specific states, which creates inconsistent detection results across crawlers.
Mobile and real-time audit tools can reduce this confusion because they simulate rendering more closely. A good example is checking the same page through a mobile-based analyzer such as Website SEO Checker & Analyzer which highlights differences between raw HTML and rendered elements, especially for headings and on-page structure. The app available on Google Play focuses on on-device SEO auditing, so it often reflects how search engines interpret dynamic pages more accurately than basic source-only crawlers.
When multiple tools consistently report missing H1, it’s usually worth verifying the rendered output in Search Console’s URL inspection tool as well, since that shows how Google actually sees the page.