Products SEO & GEO Agent Paid Ads Agent Website Agent Conversion Agent
How it works Pricing FAQ Blog Book a call

Google core update rollout: what to track and when to act

Updated · 7 min read

Short answer During a core update, note the start date, keep leads and Search Console clicks in view, and change nothing. Rankings swing while it rolls out, lately for 12 to 18 days. One full week after Google marks it finished, compare that week with the week before it began, by page and query. Only a large, lasting drop calls for work.

Want help applying this to your business? Talk it through on a free 30-minute call.

Book a call

What to track during a Google core update, and when

Track a few numbers on a fixed schedule, and make no changes until the last step. Google's own order is: confirm the update has finished, wait a week, then compare (Google Search Central: core updates).

WhenWhat to doWhat not to do
The day Google announces itWrite the start date on your Search Console chart (an annotation, below)Edit pages
While it rolls outGlance weekly at leads and Search Console clicksJudge the result from daily swings
Google marks it finishedWrite the end date on the chartStart the comparison yet
One full week after it endsCompare that week with the week before it started, by page and queryRewrite pages that slipped a little
About a month after it endsCheck whether a large drop held or came backDelete content in bulk
The next core updateCheck whether improved pages recoveredExpect a fixed recovery date

Announcements and dates are on Google's Search Status Dashboard. The November 2026 core update started November 10, and Google said "the rollout may take up to 2 weeks to complete." On November 16 it was still rolling out (Search Status Dashboard: November 2026 core update).

Don't count on two weeks. Recent core updates on the dashboard ran from about 12 days (March and May 2026) to about 17 and 18 days (June and December 2025) (Search Status Dashboard: ranking incident history).

Which numbers to watch after a core update

Watch what pays the bills first, then what explains it. All of the search numbers are free in Google Search Console's Performance report.

NumberWhereWhat it tells you
Calls, form fills, bookingsGA4 key events, call tracking, your booking toolWhether the business felt it at all
ClicksSearch Console, PerformanceVisits from Google Search
ImpressionsSearch Console, PerformanceHow often you showed up in results
Average positionSearch Console, PerformanceYour typical spot; 1 is the top
Pages tabSearch Console, PerformanceWhich pages moved: service pages or blog posts
Queries tabSearch Console, PerformanceWhich searches moved: your money searches or side topics
Search type filterSearch Console, PerformanceWhether the change was in Web, Images, Video or News

Read clicks and impressions together. Google notes that steady impressions with falling clicks point to your page title and snippet, or a richer result above you, not lost rankings (Google Search Central: Debugging drops).

Don't fixate on position. Google's advice:

"In general, you shouldn't focus too much on your absolute position. Impressions and clicks are ultimately the measure of success for your site." (Google Search Central: Debugging drops)

To see who gained, search your money keywords and note which sites now sit above you. That shows what Google now prefers for those searches.

Leads come first because a drop on side-topic blog posts may cost you nothing. If calls and bookings hold while blog clicks fall, the update moved traffic that wasn't paying. Setting up those lead counts is in the GA4 key events guide.

Why waiting often wins

Because the first numbers are not the final ones, and changes made now muddy the answer later.

  1. Rankings move back on their own. Google says small shifts "can happen at any time (including moving back up in position, without you needing to do anything)" (Google Search Central: Debugging drops). A drop on day 3 of a rollout can be gone by day 12.
  2. Edits mix two causes. If you rewrite pages mid-rollout, you can't tell whether the later change came from Google or from you.
  3. Google says leave working pages alone. For a small drop, such as position 2 to 4, Google says:
"There's no need to take drastic action (in fact, we recommend avoiding making changes to content that's already performing well)." (Google Search Central: core updates)
  1. Fixes are slow anyway. Google says improvements can take "several months" to register, and sometimes until the next core update (Google Search Central: core updates). Waiting three more weeks to diagnose properly costs little.

How to compare before and after correctly

Use Google's comparison, and remove the noise before you trust it.

  1. Pick the right weeks. One full week after the rollout ends, compare that week with the week before it started (Google Search Central: core updates). For the November 2026 update, the "before" week is November 3 to 9.
  2. Check the calendar. If the "after" week holds a holiday the "before" week didn't, the drop may be the holiday. If the November 2026 rollout ends near its two-week mark, the "after" week falls around US Thanksgiving (November 26). Canadian Thanksgiving was in October, so Canadian sites face less of this.
  3. Look a year back. Set the date range to the last 16 months and check whether the same dip happened last year. Google suggests this to rule out seasonal drops (Google Search Central: Debugging drops).
  4. Sort by size. A slip like position 2 to 4 needs nothing. A fall like 4 to 29 across many pages needs a real look (Google Search Central: core updates). What to do then is in traffic dropped after a core update.

Set up tracking before the next update

Two Search Console features make the next update easier to read.

  • Annotations. Right-click the Performance chart, choose "Add annotation" and write a note "up to 120 characters" on a date (Google Search Central Blog, November 2025). Note update dates and your own site changes. Everyone with access to your Search Console sees them, so keep them free of private details.
  • The 24 hours view. It shows hourly data "with a delay of only a few hours," and marks incomplete data with a dotted line (Google Search Central Blog, December 2024). It's good for spotting a sudden break, like a site outage. It's too short and too noisy for judging a core update.

When not to wait

Some drops aren't the update, and waiting makes them worse. Act now if:

Google lists technical problems, security issues and site moves as separate causes of traffic drops, each with its own graph shape (Google Search Central: Debugging drops).

Example

A plumber on day 4 of the November 2026 rollout

Clicks are down 25% from last week; calls are flat. Action: annotate November 10, change nothing, and compare once the update has been finished for a week.

A bookkeeper comparing weeks after a rollout

Service pages moved from position 3 to 4; the blog fell from page 1 to page 3 on many searches. Action: leave the service pages alone. Review the blog posts against Google's self-assessment questions.

A landscaper whose "after" week held a holiday

Clicks fell 30%, but the same dip shows in last year's data for that week. Action: none. Compare the next normal week.

FAQ

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

Google usually says up to two weeks. Recent ones on its status dashboard took about 12 to 18 days, so wait for Google to mark it complete rather than counting days.

Should I check my rankings every day during a core update?

You can, but don't act on them. Rankings swing during a rollout, and Google's comparison starts one week after it ends.

My traffic went up after a core update. Should I do anything?

No. Keep tracking it through the same schedule; gains can shift during the rollout too. Avoid big changes to pages that are performing well.

Do rank tracking tools show core update damage better than Search Console?

They show positions for the searches you chose, from set locations. Search Console reports real searches, clicks and impressions from Google itself, which Google calls the measure of success.

Are core updates the same in the US and Canada?

The November 2026 update applies "globally and to all languages" (Search Status Dashboard). What differs is the calendar, like the Thanksgiving dates.

Different for you?

Keep learning

NextGoogle algorithm changes for creators: protect your trafficCreators and small publishers: how to keep traffic steady through Google updates with first-hand content, an audience that asks for you, and channels you own.

Do it yourself

Google core update checklist: get your site ready beforehandA Google core update checklist for owners: save a baseline, test your top pages against Google's own questions, fix what's thin, and set rules for update week.

Ask us one question

One line is enough. We reply by email.

Sources

  1. Google Search Central: Google Search's core updates and your website
  2. Google Search Central: Debugging drops in Google Search traffic
  3. Google Search Status Dashboard: Ranking incident history
  4. Google Search Status Dashboard: November 2026 core update
  5. Google Search Central Blog: Adding context to your Search Console data with custom annotations (November 2025)
  6. Google Search Central Blog: An improved way to view your recent performance data in Search Console (December 2024)