Group related pages
Pages with the same structure and purpose land together — product, category, article, location. You are looking at a family, not a list of one-off URLs.
Repeated issues, shared metadata, and the count of affected URLs stay grouped by page type — so the unit of work is the template.
Group pages that share a type, decide whether the weakness is structural or topical, then turn the pattern into one brief with reach attached.
Pages with the same structure and purpose land together — product, category, article, location. You are looking at a family, not a list of one-off URLs.
A missing H1 on every product page is a template problem. Thin coverage in one category is a topic problem. The map keeps those two diagnoses from collapsing into the same ticket.
Hundreds of findings become one implementation note: the pattern, example URLs, and how many useful pages improve if it is fixed once. Engineering gets a cause, not a spreadsheet of symptoms.
Find canonicals, directives, and metadata patterns by page type.
Compare headings, substance, and internal paths across templates.
Prioritize the fix that improves the largest useful page group.
Example questions include: Show me internal linking opportunities, Audit this site, Where should I start?, Find pages competing for the same intent, What changed since the last crawl?.
Crawl a site, then ask what needs attention.
free to start