Google Core Updates: How to Diagnose Traffic Loss and Plan a Response

A core update is a broad change to Google’s ranking systems, not a penalty. When traffic drops during one, the first job is to establish whether the update is actually the cause, because several other events produce the same graph. Google’s own guidance sets the order: confirm the update has finished rolling out, wait at least a full week after it completes, then compare the right periods in Search Console. Only after that does it make sense to ask what about the content should change, and even then Google says there is no guarantee that changes will produce a noticeable effect, or that the effect will come quickly.

What a core update is and is not

Google describes core updates as “significant, broad changes” to its search algorithms and systems, made several times a year, and points site owners to the Search Status Dashboard for each update’s start and end dates. Google’s core updates guidance says there might not be anything fundamentally wrong with content that loses positions after one (Google’s guidance on core updates). The traffic-drop guide adds that “positions aren’t static or fixed in place” (debugging Search traffic drops).

A core update is not:

• a manual action. Manual actions are applied by human reviewers and appear in the Manual Actions report. Core updates leave no entry there and cannot be reversed with a reconsideration request.
• a spam update. Spam updates target practices that violate Google’s spam policies and have their own entries on the status dashboard. Google’s spam updates page says recovery from them may take months and that changes might not produce improvement after a link spam update (Google on spam updates).
• a statement about a specific site. Core updates are announced for all sites on the Search Status Dashboard, and a loss after one does not by itself mean something is wrong with the site’s content.

Since March 2024, the helpful content system that used to run separately has been part of the core ranking systems, according to Google’s ranking systems guide (Google’s ranking systems guide). Older advice that treats it as a separate classifier describes a system Google lists as retired.

Step 1: confirm the timing

1. Open the Google Search Status Dashboard and find the update’s start and completion dates.
2. Mark both dates on the Search Console Performance chart.
3. Google’s core updates guidance says to confirm that the core update has finished rolling out, and recommends “waiting at least a full week after a core update completes before analyzing your site in Search Console”.

A drop that began weeks before the rollout, or one that started during an unrelated event such as a site migration, points away from the update.

Step 2: rule out other causes

Google’s traffic-drop guide lists the families of causes. Check each before attributing the change to the update. A site that never gained traffic in the first place needs a different starting point: the zero-traffic diagnosis.

Google notes that technical problems can be site-wide (the site is down) or page-wide (a misplaced noindex), and that page-level problems produce slower drops because they depend on recrawling.

Step 3: compare the right periods

Google recommends comparing “this week with a week before the core update started rolling out” after the waiting period, and the traffic-drop guide suggests comparing the last three months with the previous period or with the same period a year earlier to separate seasonality.

Then segment the change:

• By page. Is the loss concentrated on some pages or spread across the site?
• By query group. Did informational queries move differently from commercial ones?
• By size of position change. Google’s traffic-drop guide distinguishes a small drop in position (its example: from position 2 to 4) from a large drop (its example: from the top 10 to position 29). A small drop for a few queries can look dramatic in clicks without signalling a broad reassessment. A large drop across a wide range of terms is the case where Google suggests self-assessing the site as a whole, “not just individual pages”.

Step 4: decide whether to act

Google’s guidance on core updates frames the response around helpful, reliable, people-first content and asks site owners to assess their content honestly, using the questions in its helpful content guide (creating helpful, reliable, people-first content). Some questions from that guide that apply directly to a post-update review:

• Does the content provide original information, reporting, research or analysis?
• Does it provide a substantial, complete or comprehensive description of the topic?
• If it draws on other sources, does it add substantial value and originality instead of copying or rewriting them?
• Are dates being changed to make pages look fresh when the content has not substantially changed?

The decision has three branches:

• Small position changes, no clear quality problem: Google’s traffic-drop guide recommends “avoiding making radical changes if your page is already performing well”. Monitor.
• Large, broad losses with identifiable weaknesses: improve or consolidate the weak content; remove or rework pages that exist mainly to attract search traffic.
• Losses to pages that are genuinely strong: accept that other results may now be judged more relevant, and invest in what makes the page distinct instead of rewriting for its own sake.

Step 5: set expectations for recovery

Google’s guidance on time and uncertainty:

• “Some changes can take effect in a few days, but it could take several months for our systems to learn and confirm that the site as a whole is now producing helpful, reliable, people-first content in the long term”.
• “If it’s been a few months and you still haven’t seen any effect, that could mean waiting until the next core update”.
• “However, you don’t necessarily have to wait for a major core update to see the effect of your improvements”.

And from the traffic-drop guide: “there’s no guarantee that changes you make to your website will result in noticeable impact in search results”. No plan should promise recovery by a date.

A differential diagnosis worksheet

For each traffic drop, fill in:

1. Dates: first day of decline; update start and completion dates.
2. Scope: site-wide, section, page group or single page.
3. Metric pattern: impressions down, clicks down, position down, or clicks down with impressions stable.
4. Excluded causes: technical (checked how), security (report state), manual action (report state), demand (Trends result), site move (yes or no).
5. Position change size: small shifts within the top results or large drops out of them.
6. Content assessment: which pages, which questions from Google’s guide they fail.
7. Decision: monitor, improve, consolidate or accept.
8. Review date: when to compare again.

Diagnosing a 30 percent loss after an update

Say a home improvement site loses 30 percent of organic clicks in the month after a core update completes.

• Timing: the decline starts two days after the rollout began. No migration or technical change happened that month.
• Reports: no manual action, no security issue, Page indexing stable.
• Demand: Google Trends shows steady interest in the site’s main topics.
• Segmentation: product comparison pages lost the most, falling from positions 3 to 6 on average; how-to guides moved little.
• Assessment: the comparison pages list specifications copied from manufacturer pages with no testing or original analysis, while competing pages that rose show hands-on testing.

Decision: a fall from 3 to 6 is closer to Google’s small-drop example than to its large-drop example, so the case for acting rests on the content assessment, not on the size of the drop. Rework the comparison pages with original evaluation or remove the weakest ones, leave the how-to guides alone, and review again after the next update. The record states that the update coincided with the loss and that the content assessment found a credible weakness; it does not state that the update “penalized” the site.

Responses to avoid after an update

• Calling a core update a penalty or filing a reconsideration request for it.
• Making sweeping site changes during the rollout, before data has settled.
• Changing publication dates without changing content.
• Promising a recovery timeline.
• Treating one query’s position as evidence about the whole site.

Core updates reorder results across the web. The response that holds up is a careful diagnosis, a content assessment based on Google’s own questions, and changes that would be worth making even if no update had happened.