Google Algorithm Update Tracker

Live status from Google's own dashboard, plus what SEOs are seeing.

Rolling outCore update

November 2026 core update

Started
Google says
Up to 2 weeks (my estimate: about )
Last 3 core updates took
12, 12, 18 days

“Released the November 2026 core update, which applies globally and to all languages. The rollout may take up to 2 weeks to complete.”

What to do if your traffic moves

  1. Hold big changes until it settles. Rankings move for days during a rollout. A fix made mid-way is hard to judge.
  2. Wait a week after it finishes. Then compare daily Search Console impressions before the start with the days after.
  3. Look for a step, not a slope. A sharp drop in 24 to 48 hours that holds is the pattern worth acting on. How to tell an algorithm hit from other problems.
  4. Check who replaced you in the results. Compare what their page answers that yours does not.

Status and dates come from Google. Coverage is collected automatically from a fixed list of SEO news sites and practitioners. The site data is my own, not independently audited, and includes no client sites.

What SEOs are reporting about the November 2026 core update

Short extracts from SEO news sites and from named SEO practitioners on Bluesky, each linked to the original. They are collected twice a day from a fixed list of sources, only when they name the update. Last new item: .

Every confirmed Google ranking update

Dates come from Google’s Search Status Dashboard (Ranking). Where my own panel has a result, the last column links to it.

Confirmed Google ranking updates, last 12 months. Select a bar to jump to its entry.

Core Spam Other Still rolling out (Google’s 2-week estimate)

UpdateStartedFinishedLengthMy sites
November 2026 core updateCoreRolling outOngoingAfter rollout ends
September 2026 spam updateSpam14 days57 sites: 35 up, 9 down
August 2026 spam updateSpam3 days66 sites: 22 up, 21 down
June 2026 spam updateSpam2 days54 sites: 19 up, 13 down
May 2026 core updateCore12 days44 sites: 22 up, 16 down
March 2026 core updateCore12 days16 sites: 3 up, 7 down
March 2026 spam updateSpam1 day14 sites: 2 up, 7 down
February 2026 Discover updateDiscover22 daysNot tracked
December 2025 core updateCore18 days10 sites: 4 up, 4 down
August 2025 spam updateSpam27 days9 sites: 0 up, 8 down
June 2025 core updateCore17 daysToo early in my data

“Up” and “down” mean Search Console impressions moved 20% or more between the windows explained in how I measure each update.

How did my sites change after each Google update?

In the September 2026 spam update window, 35 of 57 eligible sites rose by 20% or more and 9 fell by 20% or more. In the May 2026 core update window, 22 of 44 rose by 20% or more and 16 fell by 20% or more. In May the median was up and pooled impressions were down. In September both were up, by very different amounts. A few large sites moved differently from most of the panel. I run the same test on every confirmed core and spam update since June 2025. The June 2025 core update cannot be measured, as the note under the table explains.

UpdateRollout (Google status)nUp 50%+Down 50%+Up 20%+Down 20%+MedianPooled
June 2025 core30 Jun to 17 Jul 20250n/an/an/an/an/an/a
August 2025 spam26 Aug to 22 Sep 20259*0608n<30n<30
December 2025 core11 to 29 Dec 202510*2244n<30n<30
March 2026 spam24 to 25 Mar 202614*†1527n<30n<30
March 2026 core27 Mar to 8 Apr 202616*†2637n<30n<30
May 2026 core21 May to 2 Jun 2026441872216+18.9%-18.6%
June 2026 spam24 to 26 Jun 202654831913+0.2%+14.3%
August 2026 spam18 to 21 Aug 2026669112221-1.0%+8.5%
September 2026 spam24 Sep to 8 Oct 202657226359+38.8%+1.9%

"Up 20%+" includes the sites in "Up 50%+", and "Down 20%+" includes "Down 50%+". Median is the middle site's change. Pooled is total impressions after against total impressions before, summed across the n sites. * means n is under 30, so only counts are shown. † means the two March 2026 updates sit 3 days apart, so each window picks up the other update. The June 2025 core update cannot be measured: Search Console only holds 16 months, and the earliest data I can pull starts on 20 June 2025, after the 16 June start of its before window.

September 2026 spam update

Number of sites by change in impressions, 10 to 23 Sep vs 15 to 28 Oct 2026, 57 sites
Number of sites by change in impressions, 10 to 23 Sep vs 15 to 28 Oct 2026, 57 sites
September 2026 spam updateValue
Rose 50% or more22 sites
Rose 20% to 49%13 sites
Moved less than 20%13 sites
Fell 20% to 49%3 sites
Fell 50% or more6 sites

Source: Author's own portfolio data, Google Search Console API

How I measure each update

I compare 14 days of impressions before the start with 14 days that begin 7 days after the rollout finishes. The before window ends the day before Google's start date. The after window skips the first week after completion so the rollout has settled. Start and completion dates come from Google's own incident pages, in US Pacific time. I count spam and core updates only.

A site is eligible if Search Console holds data from before the before window starts and it had 100 or more impressions in the before window. Impressions are whole-property daily totals, web search only. A second script, written separately, recomputes every row and matches all nine. The rollout dates in the table come from Google's Search Status Dashboard.

What the tracker cannot tell you

These are before and after windows, and I claim no cause. Four limits apply.

  • Survivorship: the panel is my own owned sites, so it says nothing about Google's index as a whole.
  • Seasonality: I have not removed it. A 14-day window in late October is not the same as one in early September.
  • Young properties: about 33 of the 100 properties first show impressions in March 2026. I use that as a proxy for property age. That is why n runs from 9 to 66 and why early updates have so few sites. Young sites that are still growing may inflate the "up" counts. I did not test this.
  • Overlap: a site can be hit by an unrelated change inside the same window, such as a redesign, a redirect or an indexing problem.

I add each new row about four weeks after Google marks an update complete. The after window closes 20 days after completion and Search Console data takes a few days to finalise.

May 2026 core update, restated

The May 2026 result changed because the method changed. My first cut used 28-day windows (23 April to 20 May against 3 to 30 June) and 46 sites. It showed 21 sites up 50% or more, 9 down 50% or more, a median of +30.2% and flat pooled impressions (+0.3%). The tracker uses 14-day windows (7 to 20 May against 9 to 22 June) and 44 sites. It shows 18 up 50% or more, 7 down 50% or more, a median of +18.9% and pooled impressions down 18.6%. The direction of the median is the same. The pooled figure flipped because the data source changed. The first cut summed page-level impressions, which count a site once for every page it shows on a results page. The tracker uses whole-property totals, which count it once. On one large site the two differ threefold for 9 to 22 June 2026 (100,189 against 33,513). That one site contributed to the positive old pooled figure. The old 28-day windows on whole-property data (47 sites) give a median of +28.1% and pooled -15.6%. Where median and pooled disagree, most sites moved one way and the biggest sites moved the other. Neither cut isolates the update.

Case study: two of my sites dropped within 24 hours

I checked Search Console data across 21 of my own sites, 20 June to 15 September 2026. Two of them, in unrelated niches, dropped 87% and 91% of daily impressions within 24 hours of each other. Neither has recovered.

Updated 5 October 2026: a later measurement of the redlighttherapy.expert drop compares average daily Google impressions on 15 to 19 July with 22 to 31 July. That comparison shows a 96% fall. Its windows differ from the 91% drop and 14-day windows below. The EV charging directory case study covers the monthly clicks of the growing EV site.

This is data from sites I own. No client sites are included.

Which two sites dropped 24 hours apart?

tradecost.uk (an import-cost checker) and redlighttherapy.expert (a health/wellness niche site) share no niche, content structure or backlink profile. Both were performing normally through 18 July.

On 19-20 July, both lost the bulk of their impressions:

  • tradecost.uk: daily impressions fell from 374 (18 July) to 62 (19 July) to 48 (20 July), an 87% drop. Average position went from 41.7 to 71.2 in the same window and never recovered. It sits at 0 clicks/day as of 15 September.
  • redlighttherapy.expert: daily impressions fell from 1,583 (19 July) to 225 (20 July) to 148 (21 July), a 91% drop. Position moved from 15.3 to 17.9 to 23.9. It partially stabilised but never returned to its pre-drop range.

Different niches, different content. Same owner, same stack (Astro on Cloudflare Pages), same build tooling. That shared tooling is itself a candidate cause.

tradecost.uk drop

tradecost.uk daily impressions, 18 to 20 July 2026
tradecost.uk daily impressions, 18 to 20 July 2026
tradecost.uk dropValue
18 Jul374
19 Jul62
20 Jul48

Source: Search Console, own data

For redlighttherapy.expert specifically, the drop is Google-only. GA4 sessions from Google fell from 344 to 40 over the same 14-day window, while Bing sessions rose 308 to 396 and DuckDuckGo rose 464 to 602. Other search engines did not see the same page get worse. On-site remediation shipped 2-3 August (a fake-expert byline removed, 12 doorway pages redirected) produced no recovery in the six weeks that followed.

Search engine sessions

GA4 sessions by search engine, 14 days before and after the redlighttherapy.expert drop
GA4 sessions by search engine, 14 days before and after the redlighttherapy.expert drop
Search engine sessionsValue
Google (before)344
Google (after)40
Bing (before)308
Bing (after)396
DuckDuckGo (before)464
DuckDuckGo (after)602

Source: GA4, own data, 14-day window

Did a named Google update cause the drops?

I have not matched either drop to a named, publicly confirmed Google update. Two drops 24 hours apart out of four drop dates in this sample could still be chance. It's worth reporting because the two sites share no niche or content, and because the remediation that normally fixes a content-quality problem didn't move the needle on one of them.

The same pattern, a fast sustained drop rather than gradual decline, showed up on two other sites, each on a different date:

  • calculator.place: daily impressions were running 700-1,600 through early August, then fell to 20-250 on 3-4 August, with average position worsening from the mid-20s to the 60s-80s.
  • template.how: this one was climbing (position improved from 60 to the high teens through early August) before reversing sharply on 16 August and falling back to the 60s-80s.

Four sites, four confirmed drop dates, no single explanation that covers all of them.

Four sites, four confirmed drop dates, no single explanation that covers all of them.

On the portfolio drop pattern

What was growing at the same time?

Three sites were growing steadily across the same period:

  • chargefinder.uk (EV charging): position improved from the low 30s to the low-to-mid teens, clicks grew from ~20-40/day to 60-120/day.
  • deadhangs.com (fitness): clicks grew from ~30-50/day in June to 100-134/day by mid-September, with a temporary dip in average position (7 to 11) around 10-21 August that fully recovered.
  • noisecheck.uk: a similar shape, a dip to position 17-18 in mid-August, recovered to 6.7-8 by mid-September, clicks roughly tripling over the period.

deadhangs.com and noisecheck.uk both dipped in mid-August, the week template.how reversed, and both recovered within two weeks.

The full 21-site table

Scroll horizontally if columns extend beyond the screen.

SiteNicheClicks (90d)Impressions (90d)Avg positionTrend
waterhard.ukWater hardness5,728275,72610.8Stable, strong
deadhangs.comFitness7,052294,3638.0Growing (recovered dip)
chargefinder.ukEV charging5,318243,39215.9Growing steadily
salarydata.co.ukSalary data574171,29916.9Improving
noisecheck.ukNoise/decibel3,88257,1299.7Growing (recovered dip)
redlighttherapy.expertHealth/wellness72853,64818.9Casualty: dropped 19-20 Jul
heatpumpchecker.co.ukHeat pumps11255,02337.7Stable
rentalyield.ukProperty yield31545,95524.3Volatile, no trend
solarhq.ukSolar3237,69254.4Declining
calculator.placeCalculators1538,90847.6Casualty: dropped 3-4 Aug
tradecost.ukImport cost7632,99950.3Casualty: dropped 19-20 Jul
e-bikereview.ukE-bike reviews1724,57674.8Chronic thin
towrating.orgTow rating7519,46843.8Improving (maturing site)
bestreviews.co.ukProduct reviews415,73182.5Chronic thin
zoningbase.comZoning/planning1859,06910.7Improving
selflandlord.comLandlord tools559,40366.0Flat, thin
epc.reportEPC checker328,66540.5Declining gradually
whitelabelseohub.co.ukWhite-label SEO18,05882.4Too new (20 days' data)
thebestmowers.co.ukLawnmower reviews36,16561.0Chronic thin
template.howTemplates255,93932.8Casualty: dropped 16 Aug
supplementcheck.orgSupplements1497611.6Improving (low volume)

Of the 21: 4 dropped sharply and stayed down, 6 grew or improved, 2 declined gradually, 9 were flat, thin or too new to call.

Portfolio outcomes

How 21 tracked sites moved, 20 June to 15 September 2026
4Dropped sharply
How 21 tracked sites moved, 20 June to 15 September 2026
Portfolio outcomesValue
Dropped sharply4
Grew or improved6
Declined gradually2
Flat, thin or too new9

Source: Google Search Console, own 21-site sample

All 21 are siteOwner-verified properties in the same Google Search Console account. Figures are 90-day totals, 20 June-15 September 2026.

Six more owned properties were checked and left out because the data is too thin to say anything: catchment.school, drugnote.com, radon.tips, postcode.page, qrcode.ink and checkamover.com each average under 5 impressions a day, which makes daily position swings statistical noise rather than signal. carehome.page is excluded from the trend calls above for the same reason: its near-zero visibility is a known, pre-existing indexation issue rather than a new drop.

This sample is 21 of the 100 properties in my panel. The update tracker below uses a separate cut of the same panel. Neither includes client data.

How do I check if my own site was hit?

Every casualty in the 21-site table broke inside a 24-48 hour window. A slow drift is a different problem with a different fix. Pull your own Search Console impressions by day, not just the 28-day summary, and look for a step change rather than a gradual slope. If the drop still holds a week after Google marks the update complete, my guide to algorithm hits, manual actions and indexing problems covers what to check next.

How was this data put together?

This dataset comes from 21 siteOwner-verified Google Search Console properties I own, pulled 20 June to 15 September 2026 for a 90-day trailing window. No client accounts are included. The update tracker uses a separate cut: the properties out of my 100 that pass the eligibility test for each update.

Evidence limits: this is a 21-site sample from one owner's portfolio, not a controlled study. It doesn't identify which Google system caused the four drop dates, and a site's niche, age, backlink profile and content depth all differ enough that none of these can be isolated as "the" variable. It does not prove a portfolio-wide cause, and two of the four drop dates had no matching second casualty at all. No client analytics, contracts, or independent audits were used to verify anything beyond what Search Console and GA4 report.

My data files, their windows and their licences are listed in the research data catalogue.

Related reading

Common questions

How long does a Google core update take to roll out?

Google usually says a core update may take up to two weeks. On Google's Search Status Dashboard, the last three finished core updates took 12, 12 and 18 days (May 2026, March 2026 and December 2025).

What should I do while a Google update is rolling out?

Avoid big changes while it rolls out, because rankings move for days and a fix made mid-rollout is hard to judge. Wait about a week after Google marks it complete, then compare daily Search Console impressions before the start with the period after.

Did two sites drop because of the same Google update?

Unconfirmed. tradecost.uk and redlighttherapy.expert both lost the bulk of their daily impressions within a 24-hour window on 19-20 July 2026, but this has not been matched to a named, publicly confirmed Google update. Two other owned sites dropped on two other unrelated dates in the same 90-day window, with no matching second casualty.

How do I check if my own site was hit by the same pattern?

Pull your own Search Console impressions by day, not just the 28-day summary, and look for a step change rather than a gradual slope. Every casualty in this dataset broke inside a 24-48 hour window; a slow drift is a different problem with a different fix.

Does this data prove a portfolio-wide Google update hit these sites?

No. This is a 21-site sample from one owner's portfolio, not a controlled study. It does not identify which Google system caused the four drop dates in the window, and two of those four dates had no matching second casualty at all.