A deep crawl now tells you which template is broken, not which pages

A deep crawl could already tell you that 480 pages were missing an H1. It could not tell you that they were all the same page template, which is the part that turns a report into an afternoon of work instead of a quarter of it. The clustering that answers this had been written and tested for a while and was wired to nothing, so every crawl report shipped without it.

It runs now. A finished crawl groups the pages it read into templates — product pages, blog posts, the homepage — and a new Templates tab lists them with the URL shape each one matches and how many findings belong to it. The issues list groups itself the same way, so a finding that repeats across a template appears once, under the template, rather than forty times under forty addresses.

Every count on that tab is over the pages the crawl actually read, and the tab says so. A crawl visits a sample of a site and never learns the site's true size, so "480 pages sampled" is the honest figure and a site-wide total would be one we invented. Where the crawl was too large for us to read every page back, you still get the templates, and the per-finding counts stay the ones measured across the whole crawl rather than quietly shrinking to the part we re-read.

The tab appears on a deep-crawl report and on a report you share with a client. An instant single-page audit has nothing to cluster, so it does not show one.