Google core update traffic drop: how to diagnose it step by step

What is a Google core update, and what does it change?

A core update is a significant, broad change to Google's ranking systems, made several times a year to keep results helpful and reliable. Google says these changes are not aimed at particular sites or pages, so a ranking move is not automatically a penalty.

How does Google describe core updates?

Google's page on core updates, last updated December 10, 2025, says core updates are broad in nature, that most sites do not need to worry about them and that a site moving down is not necessarily bad because other pages may now deserve a place. That framing matters because it changes how you read a traffic dip: it may reflect relative improvement elsewhere, not a fault on your site.

Is a core update the same as a spam update?

No. Spam updates target policy violations described in Google's spam policies, while core updates reassess helpfulness and relevance broadly. The Search Status Dashboard lists both kinds separately, and your diagnosis differs for each.

Which recent updates has Google listed?

The Search Status Dashboard lists, most recent first: a September 2026 spam update starting September 24, an August 2026 spam update starting August 18, a June 2026 spam update starting June 24, a May 2026 core update starting May 21, a March 2026 core update starting March 27, a March 2026 spam update starting March 24, a February 2026 Discover update starting February 5 and a December 2025 core update starting December 11. The dashboard gives start dates and durations, so end dates are approximate, and you should confirm them there.

Why do dates matter?

Your analysis windows depend on them. If you compare the wrong weeks, you may blame an update for a change that happened earlier or later.

How long do rollouts take?

Google's page does not state a fixed duration and points to the Search Status Dashboard for start and end dates. Rollouts have taken from days to a few weeks, so never assume. Wait for the dashboard to show completion.

What should you do in the first days after you notice a drop?

Do nothing drastic. Confirm whether an update is rolling out or has finished, record what you see and wait. Changing a site in the middle of a rollout makes it impossible to tell what caused what.

How do you confirm that an update is the cause?

Check the Search Status Dashboard for dates, then look at your Search Console performance graph. If the change begins within the rollout window, an update is a plausible cause. If it began earlier or later, look for other explanations, such as a technical fault, a seasonal change or a competitor. Our technical SEO audit checklist covers the technical causes.

Which non-update causes should you rule out?

Check for accidental noindex or robots.txt changes, server errors, broken redirects after a release, lost tracking, seasonal demand shifts and manual actions in Search Console.

Why should you wait a full week?

Google advises waiting at least a full week after the update completes before analyzing Search Console, because positions can settle and data needs time to stabilize. Analysis done too early mixes the update's effect with temporary movement.

What should you do during the wait?

Gather baseline data, list your most important pages and queries and keep a log of any site changes you made in the previous month. Do not publish large changes just because of the update.

What should you tell stakeholders?

Say what you know, what you do not know yet and when you will analyze. Avoid promising a quick recovery, because Google says there is no guarantee that changes will produce a noticeable impact.

How do you measure the drop in Search Console?

Compare the week after the update finished with the week before it started, then break the change down by page, query and search type. Google's page recommends this approach and adds that you should review each search type separately.

Which comparison should you run?

In the Performance report, set a custom comparison of the two equal periods and review clicks, impressions, click-through rate and average position. Sort by clicks lost to find the pages and queries that moved most, and note whether the position change is small or large.

What counts as small and what as large?

Google gives an example: a move from position 2 to 4 is small and needs no drastic action, while a move from position 4 to 29 is large and sustained, and warrants a deeper assessment. Use that distinction as your starting point.

Why split by search type?

Web search, Google Images, video and the News tab behave differently. A fall in Web search with growth in Images means something different from a fall in all of them. Analyze each separately so that you target the right content.

What about Discover?

Discover has its own update history on the dashboard, such as the February 2026 Discover update. If a large share of your traffic comes from Discover, check it separately from search.

How do you control for seasonality?

Compare with the same period last year as well as the previous week, and note holidays and seasonal demand. A seasonal dip can look like an update effect if you compare only adjacent weeks.

How do you classify the drop to decide what to do?

Classify the drop by size, spread and duration. A small, narrow drop needs patience, while a large, widespread, sustained drop needs a quality review of the whole site.

What does a localized drop tell you?

If only one template or section lost visibility, the cause is more likely to be a quality or technical problem there than a site-wide judgment. Compare that section with healthy sections on content depth, originality, internal links and speed.

How do you compare sections fairly?

Pick matched pairs, such as two similar articles or two similar categories, one affected and one not, and list the differences. Patterns often emerge quickly.

What does a broad drop tell you?

It suggests that Google's systems revisited how helpful and reliable the site seems overall. In that case, a review of content quality, authorship, originality and user experience is warranted, as Google's guidance recommends, and it will take time to show an effect.

Should you remove content?

Google says deleting content is a last resort for content that cannot be salvaged, and that removing sections that seem built for search engines instead of people may help the rest of the site. Do not mass-delete.

How do you run a quality review using Google's own questions?

Use the self-assessment questions in Google's helpful, reliable, people-first content guidance, last updated October 5, 2026, on your most affected pages. Ask them honestly, and involve people who are not connected to the site.

Which questions matter most?

Does the content provide original information, reporting, research or analysis? Is the heading descriptive without exaggeration? Does it look carefully produced? Is it mass-produced across many creators or sites? Does it give readers reasons to trust it, such as clear sourcing and information about the author? Would an expert reviewer find factual errors that are easy to verify?

How do you score the answers?

Use a simple scale for each page and note the weakest areas. A page with thin, generic content and no author information needs different work than a page with good content and poor navigation.

Why ask outsiders?

Google's page suggests asking trusted people unaffiliated with your site to review it objectively. Owners tend to overrate their own pages, and a neutral reader finds the gaps quickly.

What should reviewers do?

Give them a task, such as finding an answer to a question the page claims to answer, and ask where they got confused, doubted a claim or wanted more detail.

How does E-E-A-T fit?

Google explains that E-E-A-T stands for experience, expertise, authoritativeness and trustworthiness, that trust is the most important and that it is not itself a ranking factor but describes qualities that its signals can identify. Show who wrote a page, how it was produced and why it exists. Show who wrote a page, how it was produced and why it exists, as we do with our author page.

What should you improve, and what should you leave alone?

Improve what helps readers, such as clarity, depth, evidence and navigation, and leave alone what already works. Google's page warns against quick fixes and removing elements because of SEO advice you heard.

Which improvements are sustainable?

Adding original information such as your own data, photographs or tested procedures, restructuring content so that it is easier to read and navigate, clarifying authorship, correcting factual errors, consolidating duplicate or overlapping pages and improving internal links. These help readers whether or not rankings move.

How do you prioritize?

Start with pages that matter most to the business and were most affected, then work outward. Improve a small set well before touching hundreds.

Which changes should you avoid?

Rewriting everything at once, removing elements that users like, chasing keyword tweaks and publishing large volumes of new pages quickly. These add risk without evidence that they address the problem.

What about adding new content?

Add it only where it fills a real gap. Our article on scaled content abuse explains why volume for its own sake is risky.

How do you consolidate weak pages?

Merge pages that cover the same need into one strong page, redirect the others permanently and update links. Consolidation concentrates value and removes confusion, and it is safer than outright deletion.

How long does recovery take, and what should you expect?

Google says some changes can show effects within days, while others may take several months for its systems to confirm that a site consistently produces helpful, reliable, people-first content. There is no guarantee of a noticeable impact.

When should you check progress?

Review monthly, compare equal periods and look at trends over several months, not single weeks. Smaller, unannounced core updates may also lift positions for improved content, so movement can occur between named updates.

What if nothing changes?

If a few months pass with no effect, Google's page suggests waiting for the next core update. Continue improving the site in the meantime and keep records of what you did.

How do you stay patient without being passive?

Keep a prioritized improvement plan, work through it steadily and report progress on content quality measures, such as the number of pages reviewed and improved, along with traffic. Progress on quality is real even when rankings lag.

How do you avoid panic changes?

Adopt a rule that no site-wide change is made in response to an update until the analysis is complete and reviewed by a second person.

How do core, spam and Discover updates differ, and why does it change your response?

Google lists several kinds of ranking updates on its Search Status Dashboard, and each calls for a different response. Treating them all as "an algorithm update" leads to the wrong fix.

What should you do after a spam update?

Compare your site with Google's spam policies, which were last updated on August 28, 2026. Look for scaled content abuse, link spam, thin affiliation, expired domain abuse and site reputation abuse. Our guide to site reputation abuse and the article on scaled content explain how to review each.

Are all drops after spam updates penalties?

Some are demotions of content that systems judged to be spam, and some are effects of others being demoted. Check Search Console for a manual action message to see whether a human reviewer has taken action.

What should you do for a serving incident?

Wait. The dashboard marks these as issues on Google's side, such as a serving problem on a particular date, and they usually resolve without changes on your site. Make a note of the date so that you do not attribute the dip to something else.

How do you avoid confusing overlapping updates?

When updates overlap, as a spam update and a core update sometimes do, analyze by cause: technical, policy and quality, and avoid blaming one update for everything.

How do you build a baseline before the next update?

A baseline is a record of how your site performs when nothing unusual is happening. With one in hand, you can measure an update's effect in an hour instead of a week.

What should the baseline include?

Monthly clicks, impressions and average position for your top 100 pages and top 100 queries, split by device and search type, plus indexed page counts, Core Web Vitals field data, a list of major site changes and the dates of Google updates. Store exports in a shared folder with consistent names.

How often should you update it?

Monthly, and always before a planned release or migration, so that you know what normal looked like.

Why keep a change log?

A dated list of releases, content changes, migrations and outages lets you separate the effect of an update from the effect of your own work. When a drop appears, the first question is always what changed on our side.

What belongs in the log?

Template changes, redirects, robots.txt edits, plugin updates, content publication and pruning, hosting changes and any tracking changes, each with a date and an owner.

Which technical checks should you run before blaming an update?

Run a short technical check first, because technical faults can mimic an update and are far easier to fix. If the problem is technical, no content rewrite will solve it.

What should the checklist include?

Confirm that key pages return 200 status codes and are indexable, that robots.txt has not blocked important sections, that canonical tags and redirects are correct, that structured data is valid, that server errors have not risen and that your sitemap lists the right URLs. Check the Pages report and Crawl stats in Search Console for changes. Our guides to log file analysis and server response time show how to look deeper.

How quickly can you do it?

A focused check takes a few hours. Do it before any content work.

What if everything is technically sound?

Then the drop is more likely related to how the update reassessed your content, and a quality review is the right next step. Note that you ruled out technical causes, which shortens future conversations.

How do you document it?

Record what you checked, the result and the date, in the same place as your change log.

How do you report on a core update to stakeholders?

Report with a short, factual summary: what changed, how big it is, what you ruled out, what you will do and when you will review. Clear reporting reduces panic and prevents rushed decisions.

What should the report contain?

The update name and dates from the dashboard, the comparison periods, the change in clicks, impressions and positions, the most affected pages and queries, the classification of the drop, the technical checks performed, the plan with owners and the next review date. Use plain language and charts, and avoid speculation.

How do you handle questions about recovery?

Say what Google says: effects may appear within days or may take months, and there is no guarantee. Offer a plan and a review schedule, not a promise.

How often should you update stakeholders?

After the initial analysis, monthly. Include progress on quality work, not only traffic, so that effort is visible even while rankings lag.

What does a core update diagnosis look like in practice?

The example is fictional and illustrates the method. Its numbers and outcomes are invented for demonstration.

What happened?

A fictional home services company sees organic clicks fall noticeably in the weeks after a core update. The graph begins to decline inside the rollout window listed on the Search Status Dashboard.

What did the analysis show?

After waiting a week past the end date, the team compared equal periods. Most service pages moved by a few positions, while a large set of city pages with near-identical text lost a lot of visibility. Blog articles with named authors and original photographs held steady.

What did they decide?

They left the stable pages alone, merged the near-duplicate city pages into a smaller set of pages with real local detail such as projects, regulations and team members and added author information to older articles. They did not delete content wholesale.

What did they monitor?

They tracked clicks, impressions and positions monthly for the changed pages against a similar unchanged group, and noted that improvement, if any, would take months and could not be promised.

How do you audit content quality page by page after an update?

Audit by sampling the most affected pages and scoring each against a fixed set of questions. A consistent method lets you compare pages and find patterns, instead of arguing about individual opinions.

What does the scoring sheet contain?

One row per page with columns for the main question the page answers, whether it offers original information, whether the author and sources are clear, whether the content is complete for the topic, whether it is accurate, how it reads on mobile, how many ads or interruptions it carries, how many internal links point to it and whether another page on your site covers the same need. A three-level score for each column is enough.

How many pages should you review?

Twenty to fifty of the most affected pages, plus ten healthy pages for comparison. Patterns appear quickly with that sample.

What patterns usually appear?

Thin or generic content, near-duplicate pages, outdated information, unclear authorship, pages written mainly to capture a keyword and sections that exist only to carry affiliate or advertising links. Group findings by pattern, because each pattern has its own remedy.

How do you decide between improving and consolidating?

Improve a page if it serves a real need and can be made clearly better. Consolidate it if it overlaps with a stronger page. Remove it only if it has no value and cannot be salvaged.

How do you protect strong content?

Mark the healthy pages as protected, and do not edit them for the sake of change. Google's own advice is to avoid changing content that already performs well.

What are the common mistakes after a core update?

The common mistakes are reacting too early, changing everything at once, deleting content in bulk and blaming the update for unrelated faults. Each makes the problem harder to solve.

Which mistakes come from impatience?

Analyzing before the update ends, making changes during rollout and judging results after a few days all confuse cause and effect.

Which mistakes come from weak analysis?

Looking only at total traffic, ignoring search type, forgetting seasonality and skipping technical checks lead to wrong conclusions.

How do you avoid them?

Follow Google's guidance on timing, compare equal periods, classify the drop and make measured improvements.

How should you review user experience and trust signals?

Review how real visitors experience the page, because helpfulness includes how easy a page is to use and trust. Layout, ads, navigation and clarity all affect whether a reader leaves satisfied.

Which experience factors deserve attention?

Readability on mobile, intrusive pop-ups or ads that interrupt reading, slow loading, confusing navigation, missing contact and policy information and unclear page purpose. Fix those that frustrate readers, and test with a few people who are new to the site.

What trust information should be present?

Clear authorship with credentials, an about page, contact details, editorial and review standards where relevant and honest disclosure of any commercial relationships.

How do you test with real users?

Ask three to five people to complete simple tasks on affected pages and watch where they struggle. Their confusion points to concrete improvements that no dashboard will show.

How do you record findings?

Write each issue with a screenshot, the page and a proposed change, and add it to the improvement plan.

How do you build a site that is resilient to future updates?

Resilience comes from serving readers well, keeping the technical base sound and watching your data regularly. No site is immune to ranking changes, but sites built on useful, original content and clear trust signals tend to be affected less and recover with less drama.

Which habits create resilience?

Publish only what helps your audience, keep pages current, show authorship and sources, maintain a clean technical foundation, avoid practices listed in Google's spam policies and keep a baseline and change log. Review them quarterly as part of your normal SEO routine, and use industry coverage, with caution, to spot themes worth testing.

What should you avoid depending on?

A single traffic source, a single page type or tactics that only work while a loophole lasts. Diversify channels and keep your own audience through email and direct relationships.

How does AH SEO Agency help after a core update?

We confirm the update dates, rule out technical causes, analyze Search Console by page, query and search type, run a quality review with Google's questions and build a prioritized, evidence-based improvement plan. We do not promise recovery, and we avoid quick fixes.

Where can you learn more?

See our SEO audit service, read about how long SEO takes or request a free SEO audit.

What can you do today, before any update arrives?

Export twelve months of Search Console data by page and query, save it with a clear date, write down the dates of your last five site releases and add the current Google update dates from the Search Status Dashboard to a shared document. Then choose one owner for update analysis and agree a simple rule: no site-wide changes until the analysis is reviewed. Those three steps take under an hour, and they turn the next update from a crisis into a routine check.

Summary: how should you diagnose a traffic drop after a core update?

Confirm the dates, wait for the rollout to end plus a week, compare equal periods by page, query and search type, classify the drop and respond in proportion. Improve quality sustainably and give changes time.

• Core updates are broad and do not target specific sites.
• Use the Search Status Dashboard for dates and Search Console for comparisons.
• Small drops need patience. Large sustained drops need a site-wide quality review.
• Avoid quick fixes and mass deletion.
• Recovery can take months, and nothing is guaranteed.