Page-Level or Site-Wide? Locating the Scope of an Update Hit

When traffic drops after a Google update, the first useful question is not “why?” but “where?”. A loss spread evenly across every page points to a different cause, and a different fix, than a loss concentrated in one blog folder or one page template. Getting the scope right saves weeks of work on the wrong problem.

This guide shows you how to locate the scope of an update hit using Google Search Console and a simple spreadsheet. You will learn how to split losses by page, directory and template, how to read the patterns you find, and what each pattern usually suggests. It pairs well with our walkthrough on diagnosing a core update drop in Search Console.

Key Takeaways

• Google says its ranking systems are designed to work on the page level, but site-wide signals and classifiers also contribute.
• Measure scope before you act: compare equal periods before and after the rollout, then segment by page, folder and template.
• A loss concentrated in a few pages or one section usually calls for targeted work, not a site-wide overhaul.
• A broad, even decline across unrelated sections is more consistent with a site-level quality assessment, but it is still a hypothesis, not proof.
• Rule out tracking errors, seasonality and technical problems before blaming the update.

How Google Describes Page-Level and Site-Wide Signals

Google’s guide to its ranking systems answers part of this question directly:

“Our ranking systems are designed to work on the page level”

— Google Search Central, A guide to Google Search ranking systems

The same page goes on to say that site-wide signals and classifiers are also used and contribute to Google’s understanding of pages, and that having some good site-wide signals does not mean every page will rank highly. Google’s page experience documentation says something similar: core ranking systems generally evaluate content page by page, but Google does have some site-wide assessments. We explore that balance in more depth in site-wide vs page-level signals.

In practice this means both patterns are possible. Your job is to find out which one your data looks like, without assuming the answer.

Step-by-Step: Locating the Scope of a Drop

1. Confirm the rollout dates. Check the Google Search Status Dashboard for the update’s start and end. Google’s core update documentation suggests waiting at least a full week after a rollout finishes before comparing.
2. Rule out non-update causes. Check for tracking changes, migrations, indexing errors and seasonal demand. Our post on tracking errors vs real ranking drops covers the quick checks.
3. Compare equal periods. In the Search Console Performance report, compare the week after completion with the week before the rollout started, then repeat with longer windows (for example 28 days) to smooth noise.
4. Export the Pages table. Sort by clicks difference, as Google’s traffic-drop debugging guide suggests, and export to a spreadsheet.
5. Group URLs. Add columns for directory (e.g. /blog/, /products/), page template (article, category, product, location) and content type. Regex filters help here; see our guide to regex in Search Console.
6. Calculate share of loss. For each group, work out its share of total clicks before the update and its share of total lost clicks after. A group that held 20% of clicks but accounts for 70% of the loss is your hot spot.
7. Check the long tail. Count how many URLs lost more than a set percentage. A few big losers and a stable long tail looks very different from hundreds of small, even losses.
8. Repeat by search type and country. Google advises checking Web, Images, Video and News separately, and filtering by country and device to see whether the drop is limited to one segment.

Reading the Patterns

Once the data is grouped, most drops fall into one of a handful of shapes. The table below is a reading guide, not a diagnosis; treat each “suggests” as a hypothesis to test.

Pattern	What it looks like	What it often suggests	First move
Single pages	A handful of URLs lose most of the clicks; the rest are flat	Those pages were outranked for specific queries, or intent shifted	Run query-level and SERP analysis on those pages
One directory	A folder such as /blog/ or /reviews/ drops; others hold	A content type or section is judged weaker than competing pages	Audit that section’s quality and purpose
One template	All product pages or all location pages fall together	Shared template issues: thin boilerplate, duplication, or a technical change	Compare template versions and recent deployments
Topic cluster	Pages on one subject decline across folders	Competitors now serve that topic better, or the SERP format changed	Study who gained for those topics
Site-wide, even	Most sections and pages lose a similar percentage	Consistent with a site-level quality assessment, or a technical/measurement issue	Re-check technical causes, then review the whole site honestly
Mixed winners and losers	Some sections grow while others fall	The update re-weighted relevance rather than demoting the site	Double down on winners; study losers individually

Why Templates Deserve Their Own Lens

Directories and templates are not the same. A /services/ folder might contain hand-written pages next to hundreds of generated city pages. If you only group by folder, a template problem can hide inside an otherwise healthy section. Tag the template type separately; our post on template-level update analysis goes deeper.

Signs a template is the issue:

• Pages share most of their wording, with only a city name or product attribute changed.
• The template was edited or redeployed shortly before the drop.
• Losses are similar in size across all pages using that template, regardless of topic.
• Competing results for those queries offer clearly more unique information per page.

When the Drop Really Is Site-Wide

An even, site-wide decline is the most stressful pattern, and the one most often misread. Before concluding it is a quality issue, confirm it is not caused by a robots.txt change, a canonical mistake, a CDN or hosting problem, or analytics changes. If technical causes are clear, Google’s core update guidance suggests reviewing the site as a whole against its helpful content self-assessment questions and asking trusted people unaffiliated with the site for an honest opinion.

Check	Where to look	Red flag
Indexing	Search Console Page indexing report	Sudden rise in excluded or “not indexed” pages
Crawling	Crawl stats report, robots.txt	Spike in errors or blocked sections
Canonicals and noindex	URL Inspection on sample pages	Pages pointing canonicals elsewhere or carrying noindex by mistake
Measurement	Analytics tags vs Search Console clicks	Analytics dropped but Search Console clicks did not
Demand	Google Trends, 16-month Search Console view	The same dip appears in previous years
Manual actions	Manual Actions report	Any listed issue

Even then, do not rewrite everything at once. Google’s documentation warns against changing content that is already performing well. Start with the pages that matter most, and read our main ranking drop recovery guide for the broader process.

Common Mistakes

• Comparing a mid-rollout week with a pre-update week. Rankings move during rollouts, so wait until it is finished.
• Comparing unequal periods or periods with different weekday mixes.
• Looking only at total clicks instead of each group’s share of the loss.
• Assuming a site-wide pattern means a “penalty”. Core updates are not penalties; Google says they do not target specific sites.
• Ignoring the Images, Video or News search types, where a loss may be isolated.
• Rewriting stable pages because the overall graph is down.

Related Guides

• Query-Level Analysis After an Update: Which Searches Did You Lose?
• Who Took Your Rankings? SERP Competitor Analysis After an Update
• Running a Content Quality Audit After a Core Update

Frequently Asked Questions

Does Google rank pages or whole websites?

Both play a part. Google says its ranking systems are designed to work on the page level, but site-wide signals and classifiers also contribute to its understanding of pages.

How long should I wait before measuring an update’s impact?

Google’s core update guidance suggests waiting until the rollout is complete and then at least a full week before comparing with the week before the rollout began.

What if only a few pages dropped?

Treat it as a page-level problem. Look at which queries those pages lost and which pages now rank instead, and improve or reposition those specific pages.

Can a technical problem look like a site-wide update hit?

Yes. Indexing errors, robots.txt mistakes, broken canonicals and tracking changes can all cause even, site-wide declines. Rule them out first.

Is a site-wide drop a penalty?

Not necessarily. Manual actions appear in Search Console’s Manual Actions report. Core update declines are algorithmic re-assessments, not penalties.

Conclusion

Scope is the foundation of every good recovery plan. Find out whether you lost a few pages, a section, a template or the whole site, and the next steps become far clearer. If you would like an experienced team to segment your data and build a prioritised plan, our SEO services team can help. Request a quote to get started.

References

1. A guide to Google Search ranking systems (Google Search Central)
2. Understanding page experience in Google Search results (Google Search Central)
3. Google Search's core updates and your website (Google Search Central)
4. Debug Google Search traffic drops (Google Search Central)
5. Google Search Status Dashboard: ranking incident history