Learn · Search · Beginner

How to check a traffic drop against a Google update

Learn to line up a fall in search traffic with Google's announced ranking updates, judge whether the drop is small or large, and avoid changes that Google advises against.

By Dean Cruddace · 45 minutes to do · Updated · Last reviewed

What a Google update is

Several times a year Google makes broad changes to its search systems, called core updates. It also improves its automated spam detection from time to time, which it calls spam updates. Google lists notable ones on a public page, the Google Search Status Dashboard.

If your search traffic fell around the same time, it is tempting to blame the update and rewrite the site. This guide shows a calmer routine: put the dates side by side, wait for the right moment to compare, judge how big the fall really is, and only then decide whether anything needs to change.

Why an update does not always mean a problem

Google says that if you suspect an update caused a drop, there might not be anything fundamentally wrong with your content, and that core updates are broad changes that do not target specific sites or pages. It warns against "quick fix" changes and calls deleting content a last resort. See Google's core updates guidance.

What you need to check a traffic drop against a Google update

  • Access to Google Search Console for the site
  • Your best guess at the date the drop began
  • A notes file to record dates and changes

Check a traffic drop against a Google update, step by step

  1. 1

    Date the start of the drop

    In Search Console open Performance, choose the Date filter and select Last 16 months, so you can see whether the dip repeats every year. Then use the Compare tab to compare the last three months with the previous period, and click the tabs (queries, pages, countries, devices) to see where the change happened. See Google's traffic-drop guide.

    You will know it worked when You have written down the date the fall began, and you know whether it repeats yearly.

  2. 2

    Look up announced updates

    Open Google's ranking updates history and find any core or spam update near your date. Note its start and end dates. Google also makes smaller core updates that are not announced, so an empty list does not prove nothing changed.

    You will know it worked when Your notes show the drop date and any update's start and end dates side by side.

  3. 3

    Wait for the rollout to finish, plus a week

    Google says to confirm a core update has finished rolling out, then wait at least a full week before analysing Search Console. Then compare that week with the week before the update started. In the history, 2024 core updates ran from about six to 45 days. If the update is still running, come back later.

    You will know it worked when The update has an end date, a week has passed, and you have two date ranges to compare.

  4. 4

    Judge the size of the drop in position

    In Performance, review your top pages and queries and note their average position before and after. Google's examples: a small drop is position 2 to 4, and a large drop is position 4 to 29. With a small drop you may see a noticeable fall in traffic without a big change in impressions. Use the Search type filter to check web search, images, video and news separately.

    You will know it worked when Each top page or query has a before and after position, labelled small or large.

  5. 5

    Leave things alone if the drop is small

    Google says small fluctuations in position can happen at any time and can reverse without you acting. It recommends avoiding radical changes, and changes to content already performing well.

    You will know it worked when You have decided to leave well-performing pages unchanged and check again later.

  6. 6

    Assess the whole site if the drop is large and sustained

    Google asks you to review the site as a whole, not only single pages, using the questions in its helpful, reliable, people-first content guidance. It suggests being objective, asking trusted people outside your site to answer them too, and looking closely at the most affected pages.

    You will know it worked when You have a list of the most affected pages with your answers to the questions beside each.

  7. 7

    Rule out other causes, change carefully, then wait

    Google's traffic-drop guide also lists technical, security and spam problems, site moves, seasonality and reporting glitches. Rule those out. Then make changes that serve users and last, and avoid quick fixes. Google says changes can take effect in days or take several months, you will likely want to wait a few weeks before checking again, and it guarantees no noticeable effect.

    You will know it worked when Your notes list each change with its date, and a date a few weeks ahead to compare again.

Common mistakes when you check a traffic drop against a Google update

  • Analysing while the update is still rolling out. Google says to wait until it ends, plus a full week.
  • Making a quick fix, such as removing a page element because you heard it was bad for SEO.
  • Deleting content early. Google calls it a last resort, for content that cannot be salvaged.
  • Changing page dates, or adding or removing lots of content, to look fresh. Google says this will not work.

Terms used when you check a traffic drop against a Google update

Core update
A significant, broad change to Google's search systems, announced on its ranking updates list.
Spam update
A notable improvement to Google's automated spam-detection systems, also on that list.
Rollout
The period between an update's start and end dates, while the change is applied.
Position
Where a page appears in search results for a query. Search Console reports an average.
A drop that lines up with a Google update?

Tell Dean the dates, the pages affected and what the update status dashboard says. A reply from Dean is the next step, not a sales sequence.

Talk to an SEO specialistSEO strategy: plan the content →