Google began rolling out its November 2026 core update on November 10, 2026. Learn what core updates are and what to do if your search traffic drops.

Google’s November 2026 core update is rolling out, and for many businesses it arrives at one of the busiest times of the year. Marketing teams may be seeing shifts in search rankings and traffic over the next few weeks and it can be hard to tell which changes deserve attention. This guide explains what core updates are and what your team should do while the rollout is in progress.
A core update is a broad change to Google's search algorithms and systems used to rank search results. Google releases several each year to keep its results relevant as content across the web changes. Core updates don’t target specific websites, pages, or industries. Instead, they adjust how Google evaluates content overall.
Because of this, a ranking drop during a core update doesn’t automatically mean a page did something wrong or violated Google’s guidelines. In many cases, Google’s systems now consider other pages more relevant or useful for that search. Core updates can also affect visibility in Google Discover, featured snippets, and other search features.
Core updates are different from spam updates, which target sites that violate Google’s spam policies. Both appear on Google’s Search Status Dashboard, but they affect websites in different ways.
Google announced the update on November 10th on its Search Status Dashboard.
The entry reads, “Released the November 2026 core update, which applies globally and to all languages.”

In a LinkedIn post, Google Search Central described it as “a regular update designed to better surface relevant, satisfying content” for all types of sites. Google hasn’t shared specific goals for this update or published a Search Central blog post about it. It has said it will update its ranking release history page once the rollout is complete.

As of November 19, the dashboard still lists the update as in progress.
The November update is Google’s third core update of 2026, following the March and May updates.
Google has also released four spam updates this year, in March, June, August, and September, along with a Discover update in February. That makes the November core update the eighth ranking update of 2026.
For a full history of past and current updates, visit the Google Search Status Dashboard.
During the rollout, you may see fluctuations in your Google Search Console and Google Analytics data, including changes in rankings, impressions, clicks, and organic traffic. Rankings often shift more than once before a core update finishes, so early movement doesn’t always reflect where a page will settle. A drop in one search also doesn’t necessarily reflect how your entire website is performing.
Not every change during this period will be caused by the update. Search visibility can change for several reasons at once. Another website might publish a stronger page, customer demand might change with the season, or a recent update to your website might affect how pages are accessed or indexed.
Keep these possibilities in mind before attributing every change to the update.
A drop in Search Console during a core update can be concerning, but the most useful response is a measured one. It’s important to separate changes caused by the update from other factors and decide if any pages need attention.
Google recommends waiting at least one full week after a core update finishes before evaluating the effect in Search Console. Its core update guidance suggests comparing that later week with a week before the rollout began, then reviewing your top pages and queries.
Until then, rankings may continue to shift. Decisions based on mid-rollout data can lead to unnecessary changes.
Check Google’s dashboard for the actual completion date before scheduling that review.
While you wait, record a baseline so you have something reliable to compare against later.
Focus on a handful of pages that matter most to your business, such as a service page that drives inquiries or a product category that supports sales. Record the search queries for each page as well as its page-level data. If your team uses Google Analytics, also record organic search sessions and the conversions you already track. Keep in mind that Search Console clicks and Google Analytics sessions are measured differently, so the numbers won’t necessarily match.
Waiting to evaluate the update doesn’t mean ignoring problems on your website. Technical performance also affects how your site appears in search. If Google can’t crawl or index a page, that page can’t rank, and Google’s ranking systems also consider page experience factors such as loading speed and mobile usability.
A few key areas to check on the technical side of your website include:
If you find a problem, fix it as part of normal site maintenance. Keep a short log of what you find, including the date, the page affected, the issue, and any action taken. If an issue is sent to a developer, note who owns it and when you expect it to be resolved.
Also record recent website launches, URL changes, ad campaigns, and promotions. This log helps separate confirmed technical problems from questions you’re still investigating, and it gives your team context when you compare data later.
For a faster check, Semrush’s Site Audit tool scans your website and creates a site health report that shows the most important issues to fix.
Once the rollout has been complete for a full week, compare that week’s Search Console data with your baseline week from before November 10th.
Use the same filters for both periods, and look at the pages and queries you prioritized rather than only the site-wide totals. A stable total can hide a decline on an important service page.
Seasonality deserves a closer look this year. The week after the rollout is expected to end overlaps with Thanksgiving, Black Friday, and Cyber Monday, so many businesses will be comparing holiday traffic with a normal week.
If you have enough historical data, compare the same period from last year as well, especially for products and services affected by the holidays. Treat that comparison as context, since pricing, promotions, inventory, and tracking changes can make this year different from the last.
If your team uses Semrush, Position Tracking can keep a dated record of selected keyword rankings, while Site Audit can flag technical issues to investigate. Compare these signals with Search Console rather than treating a tracking report as proof of an update’s effect.
The value of a tracker is having a consistent record for the keywords and locations you chose. Search Console gives a separate view of your actual Google Search performance. If the two reports point in different directions, check the dates, devices, and locations before deciding which page needs attention.
Look for patterns that hold across several comparable days rather than reacting to one unusual result. A small change in average position on its own isn’t a reason to rewrite a page that’s performing well.
Semrush’s Organic Research tool can also show whether competitors’ rankings shifted at the same time, which helps you tell whether a change is specific to your site or affecting your entire industry.
Note: Some SEOs have reported that third-party rank trackers are showing inconsistent data during this rollout, which makes Search Console an especially important point of reference.
If a substantial decline continues after the rollout, review the affected pages from your customer’s perspective. Google’s guidance on helpful content focuses on whether a page provides useful, reliable information written for people rather than for search engines.
Ask whether each page:
If something is outdated, incomplete, or hard to read, improve it and record the change. Content and SEO Improvements can take time to be reflected in search results. An edit doesn’t guarantee a recovery.
Assign one person to own the baseline and schedule a follow-up review once Google confirms the rollout is complete. Share the baseline with whoever will make or approve changes, including the period reviewed, the pages that matter most, and any technical issues already assigned.
This makes it much easier to discuss priorities later than trying to piece together what happened from screenshots.
At each follow-up, review meaningful changes, confirm whether known technical issues have been resolved, and decide which pages deserve a closer look. Keep the original observations and the dates of any changes so the next review can build on the last one.
If you need help making sense of your search data and deciding what to address first, contact the WD Strategies team.