When a Google update hits a site with thousands of URLs, a page-by-page review is hopeless. You cannot read 8,000 product pages, and a list of the 50 biggest losers rarely explains the pattern. What usually does explain it is the template: the shared layout and content model behind each type of page.
Product pages, category pages, blog posts, location pages, tag archives and search-result pages each have their own strengths and weaknesses. An update that rewards original, in-depth information might lift your long-form guides while dragging down near-identical location pages. Grouping URLs by template turns a confusing traffic chart into a short list of findings you can act on.
This guide walks through how to classify URLs, which metrics to compare, how to read the results and which mistakes to avoid. It works for core updates, spam updates and unconfirmed ranking shifts alike.
Key Takeaways
- Group every URL into a page type (template) before analysing an update; patterns appear at template level that are invisible page by page.
- Compare clicks, impressions and indexed pages per template for equal periods before and after the update.
- A template that fell much more than the site average is your first investigation target.
- Google says its ranking systems mainly work at page level, but it also uses some site-wide signals, so look at both.
- Template findings point to what to improve, not to a quick fix; Google advises against short-term changes after core updates.
Why templates explain update impact
Google’s guide to its ranking systems says its systems are “designed to work on the page level, using a variety of signals and systems”, and adds that “site-wide signals and classifiers are also used and contribute to our understanding of pages.” Pages built from the same template tend to share the same strengths and weaknesses: the same amount of unique text, the same internal links, the same ads and interstitials, the same structured data and the same speed profile.
So when an update changes how Google weighs a quality characteristic, it tends to move whole page types together. Google’s own traffic-drop debugging guide asks you to work out whether a drop happened across the whole site, a group of pages or just one important page. Template analysis is the practical way to answer that “group of pages” question. For the wider page-versus-site question, see our guide to page-level versus sitewide ranking drops.
Step 1: Build a URL-to-template map
Most sites already encode the template in the URL path. Where they do not, a crawler can extract a page-type marker such as a body class or breadcrumb.
| Template | Typical URL pattern | Example regex for Search Console | Common update risk |
|---|---|---|---|
| Product page | /product/ or /p/ | ^https://www\.example\.com/product/ | Thin manufacturer copy, duplicate variants |
| Category page | /category/ or /c/ | /category/ | Little unique text, faceted duplicates |
| Blog / guide | /blog/ | /blog/ | Search-engine-first articles, outdated content |
| Location page | /locations/city-name/ | /locations/[^/]+/$ | Near-identical doorway-style pages |
| Tag / archive | /tag/ or /page/2/ | /(tag|page)/ | Low-value index bloat |
| Review / comparison | /reviews/ or /vs/ | /(reviews|vs)/ | Lack of first-hand evidence |
Search Console’s page filter accepts regular expressions, so you can save one filter per template and compare periods quickly. Our guide to Search Console regex filters has more patterns. For larger sites, export data through the API or a crawler so you are not limited by the interface’s row caps.
Step 2: Compare equal periods for each template
Once each URL has a label, compare the same number of days before and after the update. Google’s core update guidance recommends waiting at least a full week after an update completes before analysing your site in Search Console, so your “after” window should start once the rollout has finished and settled.
“We recommend waiting at least a full week after a core update completes before analyzing your site in Search Console.”
— Google Search Central, Google Search core updates
Then work through this process:
- Confirm the update window. Take the start and end dates from the Search Status Dashboard ranking history.
- Export page-level data for equal before and after windows: clicks, impressions, CTR and average position.
- Join the template label to each URL in a spreadsheet or BI tool.
- Aggregate by template: total clicks before, total clicks after, absolute change and percentage change.
- Compare against the site average. A template that dropped 40% when the site dropped 10% is the story.
- Check the share of URLs affected within each template. Is the loss spread evenly or concentrated in a few pages?
- Remove brand queries where possible, so brand demand does not hide the non-brand change (see our guide to the branded queries filter for update analysis).
Step 3: Read the pattern
Different shapes of result suggest different explanations. The table below is a starting point for interpretation, not a diagnosis.
| Pattern | What it may suggest | Next check |
|---|---|---|
| One template fell sharply, others stable | Something specific to that page type, such as thin or duplicated content | Manually review 20–30 pages from the template against current top results |
| All templates fell by a similar amount | A site-level factor or broad shift in the niche | Competitors, seasonality, technical health and the Manual Actions report |
| Losses limited to a few URLs within a template | Query-level shifts or intent changes for those topics | Query-level analysis for the affected URLs |
| Impressions stable, clicks down | SERP layout change, such as AI Overviews or other features | Compare CTR by template and inspect live results |
| Indexed page count fell in a template | Crawling or indexing issue rather than ranking | Page indexing report and crawl stats |
When impressions hold but clicks fall, you may be looking at a change in the results page rather than a ranking loss. Our article on AI Overviews CTR versus ranking loss explains how to separate the two. When only some queries move, query-level analysis after an update is the next layer down.
Step 4: Review sample pages by hand
Numbers show you where to look; reading pages tells you why. Pick a sample from the worst-performing template and compare each page with the pages now ranking above it. Use the self-assessment questions in Google’s people-first content guidance, such as whether the content leaves readers feeling they need to search again to get better information.
Look for differences that apply to the whole template, for example:
- Boilerplate text that makes up most of each page.
- Missing first-hand information such as original photos, testing notes or specifications.
- Heavy ads or interstitials above the main content.
- Weak internal linking that leaves the template poorly connected.
- Many near-duplicate URLs created by filters, parameters or variants.
Template-wide fixes are efficient because one change improves hundreds of pages. Our on-page optimization service often works at this level, and our category page SEO guide covers one of the templates most often caught out.
Common mistakes in template-level analysis
- Mixed templates in one bucket. If blog posts and landing pages share a folder, split them by another marker or your averages will mislead.
- Unequal date ranges. Always compare the same number of days, ideally the same weekdays.
- Measuring during the rollout. Numbers from the middle of an update are noisy; wait until it is complete.
- Ignoring seasonality. A product template may fall every January regardless of Google.
- Jumping to deletion. A weak template usually needs improving, not removing. Google’s guidance even questions removing content primarily to help rankings.
- Treating correlation as cause. A template falling during an update is a clue to investigate, not proof of what Google penalised.
Related Guides
- Diagnosing Update Impact Across Countries and Languages
- Prioritising Which Pages to Fix After a Core Update
- Algorithmic Demotion vs Manual Action: How to Tell Which You Have
Frequently Asked Questions
What is template-level analysis in SEO?
It is grouping URLs by page type, such as product, category, blog or location pages, and comparing performance for each group. It shows which kinds of pages an update affected most.
Which metrics should I compare per template?
Clicks, impressions, CTR and average position for equal periods before and after the update, plus the number of indexed URLs in each template. Compare each template against the site average.
Do Google updates target specific templates?
Google says core updates are broad and do not target specific sites or pages. Templates move together because pages built the same way share the same strengths and weaknesses.
How many pages should I review manually?
There is no official number. A sample of 20 to 30 pages from the worst-affected template, compared with current top results, is usually enough to spot shared issues.
Can I do this without paid tools?
Yes. Search Console regex page filters and a spreadsheet are enough for many sites. Larger sites benefit from API exports or a crawler to label URLs.
Conclusion: turn a traffic chart into a fix list
Template-level analysis cuts an overwhelming update review down to a few clear questions: which page types lost, by how much, and what they have in common. From there, improvements can be made once at template level and rolled out across hundreds of URLs.
If you want an expert team to segment your site and plan the work, our SEO services include update impact analysis. Request a custom quote and tell us which update affected you.
References
- Google Search Central: A guide to Google Search ranking systems
- Google Search Central: Debugging drops in Google Search traffic
- Google Search Central: Google Search core updates
- Google Search Status Dashboard: Ranking incident history
- Google Search Central: Creating helpful, reliable, people-first content
- Search Console Help: Performance report (Search results)
