What’s the first thing to check after a ranking drop, page or site level?
- Published November 6, 2026
- Linked from 3 answers
- In a cluster of 77
Check that the drop is real, then check how wide it is. Confirming it first stops you from fixing a tracking fault or a seasonal dip; measuring its width then tells you where to look. Google’s guide to debugging traffic drops frames the second question the same way, asking whether the drop happened “across the whole site, a group of pages, or even just one very important page in your site”.
Step 1: confirm the drop
- Compare two data sources. If Search Console shows the fall and your analytics does not, or the reverse, look at measurement first: a removed tag, a consent change, a filter, or a reporting delay. The two tools count differently, so compare Search Console clicks with organic sessions for the same pages and dates before deciding which one is wrong.
- Compare the same period last year. The Performance report keeps 16 months of data and offers a year-over-year comparison, which helps separate a real decline from a dip that happens every year; one earlier year is a single cycle, so use your analytics for older years where you have them.
- Check demand. Google’s guide points to Google Trends for telling whether interest in a query fell across the web or only your traffic did.
A drop that survives these three checks is the one to explain first. A mismatch between tools or a seasonal pattern lowers the odds of a real ranking loss without ruling it out.
Step 2: measure the scope
| Scope of the drop | Where the cause sits | First places to look |
|---|---|---|
| The whole site | Something shared by every page: server, robots.txt, a site-wide noindex, a security issue, a manual action, or a broad update | Crawl stats, Page indexing, Security Issues and Manual actions reports; Google's update dates |
| A group of pages | Something those pages share: one template, one folder, one page type | Recent changes to that template or section; whether the group is still indexed |
| One page | The page itself or the query it competes for | Its edit history, its canonical, links it lost, and the results that now rank above it |
To find the scope, compare the drop period with a similar period in the Pages table and sort by the change in clicks. If a single URL carries the loss while the rest of the site holds, the shared layer is working, and auditing healthy pages wastes the time the fallen page needs.
What comes next
The scope decides the next question. A site-wide or group-wide drop leads to telling an update from a technical break; a single-page drop leads to comparing that page with whatever replaced it. Whether to fix now or wait is a separate decision, and it depends on whether you have named a cause you control. Until the drop is confirmed and its scope is known, leave every page as it is.
Add a comment