Two findings from my audit folder, both of which any crawler would file under the same heading.
A Shopify homeware store: 1,562 URLs with a missing or empty H1.
A chiropractic clinic: 7 H1 tags on the home page, several of them blank.
Sort those by severity and the tool puts the first one two hundred times higher. Both are wrong in the same direction, because the heading structure does not describe the page, and neither is remotely as serious as the number implies. They are also, both of them, a single afternoon’s work, because in each case one template is producing every instance.
This is the whole problem with issue counts. The number tells you how many pages use a template. It does not tell you how many decisions were made badly, and it does not tell you what anything costs you.
The same label, five different problems
Here is what “missing H1” actually looked like across five of these audits.
- 1,562: a Shopify theme that never outputs an H1 on product or collection pages. One theme file.
- 1,301: a car parts retailer, same shape, same cause.
- 809: a continuing-education platform, again templated.
- 141: a classic car marketplace, plus a separate list of URLs with duplicate H1s and another with duplicate page titles.
- 48: a medical education provider.
And then the clinic: six blog posts with no H1 at all, and a home page with seven of them.
The clinic has the smallest number on the list and the most interesting problem, because those same blog posts also render with no header menu. A tool reports “H1 missing on 6 URLs” and moves on. What is actually happening is that the blog is structurally detached from the rest of the site: no heading, no navigation, no path to anything that sells. The H1 is a symptom of the template being broken, and the template being broken is the finding.
No crawler will ever tell you that. It has no way of knowing the six URLs are the same six URLs in three different reports.
The three questions I ask of anything a tool flags
- 1. How many causes, not how many instances? Divide the count by the number of templates involved. Usually it comes out at one. An issue affecting 1,562 URLs from one template is a smaller job than an issue affecting nine URLs that were each hand-broken in a different way, and the second is far more likely to come back.
- 2. Is this the same page-set as the finding above it? If two counts match exactly, they are describing one group of pages. On one site, 8,317 orphan pages and 8,317 canonical faults turned out to be the same URLs from one template. Chasing them as separate line items is how a 400-row report gets built and never implemented.
- 3. What breaks if I do nothing? For a missing H1 on a page nobody was ever going to rank, nothing. For a missing H1 on the service page the business is built on, you have thrown away the clearest statement you get to make about what the page is. Same issue, same severity score, completely different answer.
What tools over-weight
Two things get flagged loudly and almost never deserve the position they are given.
Missing meta descriptions. HTTP Archive’s 2025 Web Almanac found one on 67.2% of mobile pages, so a third of the web has none, including a great many pages ranking at the top of results you care about. It is not a ranking factor, Google rewrites it much of the time anyway, and on a 1,300-page catalogue writing them by hand is weeks of work for close to nothing. Write them on the twenty pages that earn money and leave the rest.
Heading level order. An H3 following an H1 is reported as an error. It is not one. It is untidy, it matters for screen readers, and it has no bearing on whether the page ranks. I put it in audits under a different heading from the things that do.
For scale on how routine that is: WebAIM crawled the top million home pages in February 2026 and found skipped heading levels on 41.8% of them, up from 39% the year before. Two pages in five. If it were a ranking problem, two fifths of the web would be broken.
What tools under-weight, or miss entirely
The inverse list is shorter and more useful.
An invalid element inside the <head>. The Almanac found this on 10.3% of mobile pages, one in ten, most often a stray <img> or <div>. It matters more than almost anything on a standard issues list, because the browser closes the head at the first invalid element and everything after it is treated as body content. Your canonical, your meta robots, your hreflang: if they sit below the break, they are not being read. The tool will happily report that your canonical is present, because it is present in the source. It is just not in the head any more.
Anything requiring a judgement about intent. Whether a page should exist. Whether forty location pages are a legitimate structure or a doorway. Whether the thing ranking for your best query is the page you wanted ranking. No tool has an opinion on any of that, and those are usually the findings that change the outcome.
Whether the site says what the business is. Every crawler I have used will pass a home page that describes a mood rather than a company.
So what do you do with the 400
Not triage it top to bottom. Read it once for structure, then throw away the ordering.
Group by cause rather than by issue type: which template, which plugin, which platform default. Most reports of four hundred rows collapse to somewhere between six and twelve actual causes, and that list is short enough to have an opinion about.
Then sort those causes by what they are costing, which is a question about the business and not about the crawl. A template fault on the product pages outranks a template fault on the author archives even if the author archives generated more rows.
Then do three of them. Three is usually the honest number for what actually gets implemented between an audit landing and the next quarter starting, and picking the three is the part of the job that the tool cannot do for you.
The short version
- An issue count measures template reach, not severity. 1,562 and 7 were the same class of fault and the same size of fix.
- Divide by causes. Four hundred rows is usually six to twelve real problems.
- Matching counts across findings mean one page-set. Do not chase them separately.
- Ask what breaks if you do nothing. On most flagged URLs the answer is nothing.
- Meta descriptions and heading order are over-weighted. A third of the web has no meta description and ranks fine.
- An invalid tag in the
<head>is under-weighted and silently disables everything below it. One page in ten has one. - The findings that matter need a judgement about intent, and no tool has one.
If a site should be ranking and it isn’t, that’s the work I do. What I check first is the sequence I run before I open any tool at all. If you’re holding a report you can’t prioritise, that’s what an SEO audit is for.
