How to Investigate a Google Update Traffic Drop

Google update traffic drop

Affiliate disclosure: This article contains affiliate links to Semrush. If you sign up through them, Creaitz may earn a commission at no extra cost to you.

Your search traffic falls. You check the industry news and discover that Google has released two updates within days of each other.

Suddenly, every explanation sounds plausible.

Was it your content? Your backlinks? A technical change? Has a larger competitor taken your place?

Investigating a Google update traffic drop starts with three records: the dates of the decline, the pages affected and the changes made to your website.

Comparing those records with Google’s rollout timeline helps you identify which explanations deserve attention. You can then check tracking accuracy, technical issues, search demand and competing results.

This approach gives you a clearer basis for choosing repairs, prioritising content improvements and explaining the findings to clients or colleagues.

Establish When the Traffic Decline Began

Google released two updates within three days in March 2026. The spam update ran from March 24 to March 25, followed by the core update from March 27 to April 8.

The close timing makes attribution difficult. A website losing visibility during this period could also have experienced technical changes, stronger competition or shifts in search demand.

Record when the decline began, which pages were affected and what changed on your website around the same time. Comparing those details with Google’s rollout dates will help you narrow the investigation.

Build Your Google Update Traffic Drop Investigation

1. Put Google’s Dates Beside Your Own Changes

Create a short record containing:

  • The official update start and completion dates.
  • When the decline first appeared.
  • Recent website releases, migrations or plugin changes.
  • Changes to tracking, consent settings or analytics tags.
  • Promotions or seasonal events affecting demand.

If you manage a training website and course-page visits fall shortly after a theme update, compare those pages with sections that remained stable.

Inspect the course template’s changes, including indexing instructions, navigation and content rendering. Record any verified faults before deciding whether the content needs revision.

Google recommends waiting at least a full week after a core update completes before assessing its search impact. Repair verified faults, such as broken forms or accidental indexing restrictions, as soon as you identify them.

2. Establish What Actually Fell

“Traffic is down” can describe several different problems.

Compare the affected pages in Search Console and your analytics:

  • Did search impressions decline?
  • Did clicks fall while impressions remained relatively stable?
  • Did relevant rankings change?
  • Did analytics sessions fall without a similar change in Search Console clicks?
  • Were qualified enquiries or registrations affected?

Use the patterns to choose your next checks and record which explanations remain unresolved.

Use Semrush’s Position Tracking to review daily movements for your tracked keywords. Keep the location, device and keyword set consistent when comparing periods.

Tool demonstration using Coursera in Semrush Site Audit. Reviewing page-level technical findings within the configured crawl.

Group course-related terms separately from informational blog searches so you can review the affected section in detail.

If clicks fall while visibility remains relatively stable, our zero-click attribution guide explains how to review customer-discovery evidence alongside website activity.

3. Check for Problems You Can Verify

Before commissioning twenty rewrites, check whether the affected pages work as intended.

In Site Audit, investigate relevant errors involving broken links, crawlability, indexability and page responses.

Open the affected URLs, verify each relevant finding and record its scope.

Coursera affected pages in Semrush Site Audit

Also review Search Console’s Manual actions and Security issues reports.

A manual action follows human review. Automated ranking changes require a separate investigation, including when the Manual actions report is empty.

If the theme release introduced an accidental noindex instruction on course pages, correct it and verify the affected URLs. Our guide to crawled—currently not indexed pages covers additional indexing checks.

4. Inspect the Pages That Replaced Yours

When rankings decline, look at the results now appearing for the affected searches.

Semrush’s Organic Rankings can help identify competitor position changes and pages worth examining. Semrush estimates competitors’ organic traffic using keyword rankings and expected click-through rates.

Coursera organic ranking
Tool demonstration using Coursera in Semrush Organic Rankings. Reviewing ranking keywords and estimated Google organic visibility.

Then inspect the pages themselves.

For a course-related search, are users now seeing course directories, individual providers, comparison articles or videos? Does the replacement page answer a different interpretation of the query?

Google’s site reputation abuse policy addresses third-party content published to exploit a host website’s established ranking signals. Assess any suspected policy issue against those criteria and the available evidence.

Use competitor research to identify differences in page format, search intent and information quality that warrant closer investigation.

5. Turn the Evidence Into a Prioritised Response

Separate your findings into three groups:

  • Confirmed Problems: Repair verified technical faults or address an identified manual action.
  • Supported Improvement Opportunities: Strengthen pages where inspection reveals missing information, unclear purpose or a poor match to the search.
  • Unresolved Observations: Continue monitoring when the evidence does not yet support a specific explanation.

Record what you change and why. Avoid combining a redesign, URL migration and site-wide rewrite into one hurried recovery project.

An illustrative client-reporting example:

“The decline began near the update period and is concentrated on course pages. We found a template issue, corrected it and are monitoring those URLs separately. The update’s contribution remains uncertain.”

Separate confirmed findings, completed actions and unresolved explanations in your own report.

Choose the Next Action From Your Findings

Keep your investigation focused on the affected pages and the evidence you can verify. Record each repair or content change, assign a review date and monitor the relevant search and business measures.

Your findings may support a technical correction, a targeted content improvement or continued observation. Explain the reason for each decision and preserve any uncertainty.

You can try Semrush One free for seven days to establish ranking baselines, investigate technical findings and research competing pages. Give the evidence a hearing before putting the whole website on trial.