Google announced a new core update on November 10. It is still rolling out, with an estimated duration of up to two weeks. The Search Status Dashboard shows the start at 10:06 Pacific on November 10, 2026, and its only post is the 10:07 PST release note.
No completion entry has been posted. Google's announcement describes a regular update meant to better surface relevant, satisfying content for searchers from all types of websites. Google hasn't disclosed a more specific target.
The practical question is whether anything on your website needs to change.
A falling traffic line isn't enough to answer that. You need to know which pages lost clicks, which queries changed position, and whether demand, reporting, or a technical problem could explain the difference. Start collecting that evidence now. Let the rollout finish before drawing broad conclusions about its effect.
TL;DR
- Save a starting point. Export the pages and queries driving clicks before November 10.
- Find the pattern. Separate changes by topic, page type, country, and device.
- Check competing explanations. Review deployments, indexing, reporting issues, and seasonal demand.
- Act on confirmed faults. A known technical problem needs attention during a rollout.
- Assess the settled result. Compare a complete post-rollout week with your baseline, accounting for holiday demand.
For the deeper diagnosis and recovery process, see the core update recovery guide.
The November 2026 core update at a glance
Each row pairs what we know or observe with the decision it implies, and exact timestamps, past rollouts and tracker methods come later in the guide:
| What we know or observe | What it means | What to watch or do | Evidence and limits |
|---|---|---|---|
| The rollout is in progress, and Google's incident page shows no completion entry | Mid-rollout comparisons mix rankings from different stages of the update | Check the incident page daily and hold speculative content edits | The incident record holds one post. The up-to-two-week estimate is a planning window, not a deadline. |
| Google recommends waiting at least a full week after completion, then comparing with a week before the start | Early gains or losses aren't a settled outcome | Save your pre-start baseline export now | Core updates guidance, page last updated 2025-12-10. If the rollout runs its full estimate, the week after completion contains Thanksgiving (November 26). |
| Core updates are broad and don't target specific websites or pages | A drop is distinct from a penalty | Compare periods before you edit anything | Same guidance. Timing alone doesn't establish the cause of a drop. |
| A confirmed fault such as an outage, accidental noindex, security issue or manual action | The rollout doesn't explain it | Fix it now and log the date | Manual Actions and Security Issues reports in Search Console. No spam update is active at cutoff, but other causes and unannounced changes remain possible. |
| The update applies globally and to all languages | No market or language is exempt | Split data by country and device before reading totals | Same incident record. Specific ranking changes remain unknown. |
| Observers reported ranking volatility before the November 10 start | Pre-start movement has another cause | Treat early tracker charts and reports as leads, not results | The dated observations appear in the confirmed, observed and unknown section below. |
| No disclosed Search Console data anomaly after the August 2026 entries | That doesn't establish that every metric is error-free | Recheck before every comparison | The anomalies page can have entries added after the fact. |
Confirmed timeline and event boundaries
Every 2026 ranking update on Google's Search Status Dashboard before this one finished before November 10, so the current rollout has the window to itself at cutoff. Times are US/Pacific, as the dashboard prints them:
| Event | Start (PT) | End (PT) | Source | Status |
|---|---|---|---|---|
| March 2026 spam update | 2026-03-24 12:00 | 2026-03-25 07:30 | Search Status Dashboard | Complete |
| March 2026 core update | 2026-03-27 02:00 | 2026-04-08 06:00 | March incident | Complete, 12 days 4 hours |
| May 2026 core update | 2026-05-21 08:40 | 2026-06-02 05:40 | May incident | Complete, 11 days 21 hours. Last completed core update |
| June and August 2026 spam updates | 2026-06-24 09:00 and 2026-08-18 09:27 | 2026-06-26 10:00 and 2026-08-21 01:49 | Search Status Dashboard | Complete |
| September 2026 spam update | 2026-09-24 09:15 | 2026-10-08 01:00 | September incident | Complete, 13 days 16 hours |
| November 2026 core update | 2026-11-10 10:06 | Not posted | November incident | No completion posted at cutoff |
| November estimated window | Up to two weeks from November 10 | No end date published | Same post | Estimate only |
Why the last completed update is May 2026
The May 2026 core update is the most recent core update with a start, an end and a completion entry. Its rollout ended on June 2 at 05:40 PDT, and Google posted its completion note at 05:43. March and May provide completed 2026 comparisons, not a forecast for November, which is the latest announced update and has no end yet.
Overlapping windows blur comparisons. Three spam updates ran between May and November, and September's spam update ran into October 8. A baseline week in early October therefore sits inside a different rollout. Keep your baseline in the stretch between October 8 and November 10, and read the observations section before you settle on the week immediately before launch.
How a core update reassesses pages
A core update changes how Google's ranking systems assess content across the web. Google's guidance says these changes are broad and don't target specific websites or individual pages. A page can lose position while nothing on it changed, and Google also notes that positions in its results aren't fixed in place.
The mechanism table separates what the guidance states from what follows by reasoning:
| Input | Mechanism | Consequence | Implication | Basis |
|---|---|---|---|---|
| Google's assessment of content across many websites | Broad change to ranking systems, no website targeted | Pages move with no change on the page | Diagnose by comparing periods before editing anything | Established (guidance) |
| Whether the website as a whole produces helpful, reliable, people-first content | Systems learn and confirm this over time | Improvements can take effect in a few days or take several months | Assess the whole website and the most affected pages | Established (guidance) |
| The rollout window | Changes reach results progressively until completion | Mid-rollout data mixes old and new rankings | Wait for the completion entry | Inferred from the two-week estimate and completion logging |
| Smaller, unannounced core updates | Google updates continually | Gains can appear between announced updates | No fixed waiting period applies | Established (guidance) |
Core updates versus spam updates and manual actions
Check the dashboard and Search Console before choosing a response. An announced ranking update and a website-specific manual action require different checks:
| Event type | How it shows up | Where Google reports it | Response | Basis |
|---|---|---|---|---|
| Core update | Position changes may coincide with a broad ranking reassessment | Search Status Dashboard incident | Wait for completion and compare. For a large, sustained drop, self-assess the whole website and the most-affected pages | Established guidance. Timing alone doesn't establish the cause of a drop |
| Spam update | Websites violating spam policies can rank lower or disappear from results | Search Status Dashboard, per Google's spam updates documentation | Review the spam policies and confirm compliance. Systems can take months to recognize compliance. Discounted spammy-link benefits cannot be regained | Established guidance. A traffic drop alone doesn't establish a policy violation |
| Manual action | A human reviewer demotes pages or the whole website for a policy violation | Manual Actions report in Search Console | Fix every listed issue, select Request Review, and document the fix. Reviews usually take several days or weeks | Established Search Console Help guidance. Review duration is not a promised recovery time |
| Unexplained drop with no event | Movement with no identified dashboard incident or manual action | No announcement or action identified | Check technical causes and seasonality first | Working diagnostic inference. No announcement doesn't rule out an unannounced ranking change |
What is confirmed, observed and still unknown
The announcement describes a regular update designed to better surface relevant, satisfying content for searchers from all types of websites. It named no targeted industries, formats or ranking signals, and it gave no completion date.
Confirmed facts are the purpose, the global and all-language scope, and the estimate of up to two weeks. Observed and attributed evidence is the pre-launch movement some observers have reported. Unknown at cutoff are the completion date, the final winners and losers, and any measured before-and-after impact report with a stated baseline, since none exists yet. The table dates each item:
| Item | Category | Date | Source | What you can conclude |
|---|---|---|---|---|
| Rollout start at 10:06 PT | Confirmed | Nov 10, 2026 | Incident record | Your post-start window opens November 10 |
| Global, all languages | Confirmed | Nov 10, 2026 | Same record | Every country segment is in scope |
| Up to two weeks | Confirmed estimate | Nov 10, 2026 | Same record | Google has supplied an estimated window, not a completion date |
| Update-specific guidance | None in the announcement | Nov 10, 2026 | The incident post carries scope and duration only | General core guidance applies |
| Early ranking volatility over November 8 and 9 | Observed, community chatter | Nov 9, 2026 | Search Engine Roundtable | Movement before the start can't be credited to this update |
| Similarweb SERP Seismometer desktop risk rated Very High | Observed, tracker | Nov 3, 2026 | Similarweb SERP Seismometer | The week before launch carried its own volatility |
| Numeric tracker readings for the rollout days | Unknown | Nov 10–11 | None | Don't read early charts as results |
| Measured owner or analyst impact reports | None with a baseline | As of Nov 11 | None | No measured case evidence with a stated baseline is available at cutoff |
| Final duration, winners, losers | Unknown | Pending completion | None | Don't plan around predicted outcomes |
Early observations conflict and why
Without dated numeric readings for November 10–11, tracker agreement or disagreement remains unknown. MozCast tracks a hand-picked US keyword set, SISTRIX's radar reads mobile results for one selected country, and Semrush Sensor scores day-over-day change on its own fixed keywords. Different samples can produce different peak days, but that possibility doesn't establish disagreement during this rollout.
Timing adds another limit. The Similarweb spike on November 3 and the chatter on November 8 and 9 both predate Google's start time, so any tracker reading that blends those days with November 10 and 11 mixes pre-start and rollout-period movement. Advanced Web Ranking has also reported that gaps between tracked and manually checked rankings, affecting every rank tracker and SERP data provider, peaked in September and October 2026. Use tracker readings to cross-check your Search Console data rather than substitute for it.
Owner reports are self-selected rather than a representative sample. A single website's recovery from a depressed base cannot establish an all-website success rate. Treat every early report as a lead to check against your own Search Console data.
How this update compares with March and May 2026
The two completed 2026 core updates set the expectations for November, and the November column stays mostly unknown:
| Item | March 2026 | May 2026 | November 2026 |
|---|---|---|---|
| Start (PT) | Mar 27, 02:00 | May 21, 08:40 | Nov 10, 10:06 |
| Completion (PT) | Apr 8, 06:00 | Jun 2, 05:40 | Not posted |
| Duration | 12 days, 4 hours | 11 days, 21 hours | Unknown, estimated up to two weeks |
| Adjacent ranking event | Spam update ended Mar 25, two days before | None within two weeks | None at cutoff. September spam update ended Oct 8 |
| Observed effects | Moz reports no new guidance from Google | SISTRIX found little UK ecommerce impact across 451 domains, a strong net negative across 77 UK news domains, and US changes lagging the UK | Unknown |
March 2026 ran 12 days, 4 hours, and May 2026 ran 11 days, 21 hours. Each finished inside the up-to-two-week estimate Google gave at release.
November carries the same estimate, which works as a planning window. Google's November incident page shows a single post, the 10:07 PST release note on November 10, and no completion entry. Past durations do not establish when November will finish or when its largest movements will occur.
Rollout duration is how long Google takes to apply the update. Recovery after content improvements runs on its own clock, which the response section covers.
AI Overviews and AI Mode effects on visibility
AI features can coincide with fewer clicks even when rankings hold, so investigate click loss separately before attributing it to the core update. Two terms keep the analysis clean. A citation is a link to your URL inside an AI Overview or AI Mode answer. A mention is your brand named without a link. Because Search Console applies its impression and click rules to links, it does not monitor unlinked brand mentions.
Google counts AI Overview and AI Mode activity inside the Web search type, and an AI Overview occupies a single position that every link inside it shares. You can't filter AI Overview clicks apart from other Web clicks, and the Generative AI performance report reports impressions for AI Overviews and AI Mode, not AI-specific clicks. Google says the report became available worldwide by August 31, 2026, after a June launch that began with a subset of websites, an initial rollout description that is now historical.
Historical browsing data shows an association with fewer clicks. Pew Research Center analyzed browsing data from 900 US adults in March 2025 and found that users who saw an AI summary clicked a traditional result in 8% of visits, compared with 15% for users who didn't.
This older study explains why click loss deserves a separate check. It does not measure the November 2026 rollout or establish the cause of an individual website's decline. Whether the November update changes which pages AI Overviews cite is unproven. Keep it out of your explanation until you have evidence for it.
Monitor the rollout before you act
During the rollout, record ranking changes and defer speculative content edits. Fix confirmed technical or security problems immediately. Treat every pattern in the table below as a clue to investigate rather than proof of what the update did.
Save a usable baseline now. Export Search Console Performance data for the week before November 10, and for a quiet October week after the September spam update ended on October 8. Split each export by page, query, country, device and search type, and note the dates in Pacific time.
Websites with more pages or queries than the report table shows can export through the Search Analytics API, which returns up to 50,000 rows per day per website per search type. The bulk data export to BigQuery is not affected by the daily row limit. This working monitoring method adapts Google's sequence of confirming completion, waiting a full week, comparing with a pre-start week, then segmenting:
| Signal | What to examine | Conditional action | Check |
|---|---|---|---|
| Dashboard status | The November incident page | If a completion entry appears, start the seven-day clock | Completion date written down in Pacific time |
| Data freshness | The last two days of Search Console data, which may be preliminary. The 24-hour view uses your browser's time zone, and other views use Pacific | Exclude preliminary days from any comparison | Comparison uses complete days only |
| Search type | Web, Image, Video and News tab separately. Discover and Google News have their own reports | If one type moves alone, analyze it alone | Each type compared on its own baseline |
| Top pages | Pages sorted by the Difference column | Log the pages with the largest losses for post-completion review | List saved with positions before and after |
| Top queries | Position change per query | Classify each move as small (for example, 2 to 4) or large (for example, 4 to 29) | Classification recorded, no edits yet |
| Technical health | Outages, accidental noindex, security issues, manual actions | Fix confirmed problems immediately | Fix logged with a date, so it can be separated from the update |
| Country and device | Examine country and device segments separately, since the update applies globally and to all languages. | If one segment moves alone, check local causes before crediting the update. | Each segment is compared against its own baseline. |
| Persistence | Examine the same logged pages and queries across several days of complete data. | Treat a one-day move as a note, and flag only moves that hold. | The observation dates are recorded. |
| Ranking corroboration | Examine whether click changes on a page line up with position changes on its queries. | If clicks fall while position holds, investigate CTR, AI Overviews and search-result layout rather than ranking. | Click and position changes are logged together. |
| Competing results | Examine which URLs now appear above yours for logged queries. | Note new or moved competitors as a lead, not a reason to edit. | The query and date are noted. |
| Reporting issues | Examine the Search Console data anomalies page before each comparison. | Flag affected dates and reports; avoid using the affected metrics to infer ranking changes. | The date the page was checked is written down. |
| Holiday demand | Examine the same weeks of 2025 in the last-16-months range, since search demand rises toward Thanksgiving on November 26. | If a drop resembles last year's curve, test seasonality as one explanation alongside ranking, technical and reporting changes. | A year-over-year week is saved. |
| Downstream outcomes in GA4 | Examine organic sessions and conversions in GA4. Compare them with GA4's own baseline, and never add them to or substitute them for Search Console clicks, which are a different measurement. | If GA4 moves without a matching Search Console change, or the reverse, log both and investigate each source on its own terms. | GA4 and Search Console are logged in separate columns. |
Two Search Console limits shape this work. The Performance table shows at most 1,000 rows, and anonymized queries are left out of tables while still counting in totals. Filtered query views may therefore total less than your chart totals.
Rule out confounders before blaming the update
This update's distinctive problem is the calendar. If Google posts completion around November 24 and you wait a full week, your post-completion week runs through Thanksgiving on November 26, Black Friday on November 27 and Cyber Monday on November 30. Your pre-start week, meanwhile, overlaps the November 3 volatility. Both ends of Google's recommended comparison are disturbed, so test each explanation before you settle on one:
| Signal | Possible explanations | What distinguishes them | Next check | Limit |
|---|---|---|---|---|
| Traffic down in late November | Holiday seasonality or update impact | Seasonality repeats in last year's same weeks | Use Search Console's last-16-months range and compare late November 2025 | Last year's calendar and SERP layout differ |
| Baseline week already shows movement | Pre-launch volatility from November 3 and November 8–9 | The movement predates 10:06 PT on November 10 | Add a second baseline in mid-to-late October | October still follows the September spam update's tail |
| Clicks down, impressions and position flat | AI Overview click loss | Position holds while CTR falls on queries with AI Overviews | Compare CTR for those queries against queries without them | No click-level AI Overview filter exists |
| Sudden drop on specific pages | Manual action or spam issue | A Manual Actions report entry | Open the Manual Actions and Security Issues reports | No spam update is active at cutoff |
| Gaps or spikes in reported metrics | Logging or reporting issue | An entry on the anomalies page | Recheck the page before comparing | Entries can be added later |
| Losses on pages you edited | Your own change | Drop starts on the deploy date | Match losses against your release log | Edits during rollout confound both readings |
Use weekly granularity for the comparison. Search Console's help notes that weekly or monthly views neutralize the day-of-week effect that a daily comparison picks up.
Before blaming the update, check the timeline
A change that shows up during a rollout doesn't identify its own cause. The two cases below are historical examples. They do not establish what is causing any movement during the November 2026 rollout.
In August 2024, Google's core update ran from August 15 to September 3. A separate ranking bug ran from August 15 to 20, and Google said it was unrelated to the core update. A decline during that window could have come from either event, or from neither, so check the Search Status Dashboard and other possible explanations before deciding what to change.
In June 2025, Glenn Gabe documented a website whose search visibility rose on June 21, more than a week before the June 30 core update launched. His write-up of the June 2025 update shows why a zoomed-out chart can make the two events look connected. The movement began before the announced update, so the update can't be the starting point for that change.
Use the Search Console prompt below to establish when performance changed, which pages and queries changed together, and what else happened around that date. Those checks help you investigate competing explanations; timing alone does not prove the update caused the change.
Decide your response after the rollout completes
Match your response to what you can confirm:
- Fix confirmed technical, security or indexing faults immediately, whatever the rollout status.
- Record and investigate uncertain movement during the rollout, without speculative edits.
- Assess sustained content-related losses only after completion plus at least a full week, using complete, comparable data. Keep the comparison against your pre-start baseline, then test the October and year-over-year comparisons.
For that later assessment, run Google's self-assessment to check whether the website overall, not just individual pages, delivers helpful, reliable, people-first content. Then evaluate the most-affected pages. Avoid quick fixes based on perceived SEO rules, and treat deleting content as a last resort.
Review each affected page by asking whether it shows first-hand experience, shows who is responsible for it, and is reliable. E-E-A-T is a way of judging quality, not a score or numeric ranking factor you can measure. Where several thin pages cover the same need, improving them or consolidating them into one stronger page is a justified option, while deletion stays a last resort.
CTR means clicks divided by impressions. Google's position examples, 2 to 4 for a small drop and 4 to 29 for a large one, illustrate moves without setting universal thresholds.
Use the full recovery process for a deeper assessment after these November-specific checks:
| If you see | Then | Avoid | Basis and limit |
|---|---|---|---|
| Small position drops (for example, 2 to 4) | Leave well-performing content alone | Rewrites made on a hunch | Google guidance. These positions are examples, not a numerical cutoff |
| A large drop across the website that persists in complete post-completion data | Run the self-assessment across the whole website and examine the most-affected pages | Blanket deletion of old or low-traffic pages | Google guidance. Check competing causes before attributing the drop to this update |
| A drop matching the late-November 2025 curve | Test seasonality against both baselines and recheck in December | Attributing the drop to the update from timing alone | Year-over-year comparison is a diagnostic check. Similar curves don't rule out other causes |
| Flat position with falling CTR on AI Overview queries | Investigate click loss separately from ranking, including query mix and search-result layout | Content edits aimed at ranking before diagnosing the click loss | Search Console counting rules. Aggregate Web metrics cannot isolate AI Overview clicks or prove their effect |
| A manual action | Fix every listed issue and request review immediately | Waiting for the next core update | Search Console Help. The action requires a response even during a core rollout |
| Gains after completion | Record the change and its timing without claiming causation | Treating gains as proof your recent edits worked | Timing and selected outcomes cannot establish the effect of your edits |
Waiting on speculative content changes is active monitoring, and it's a different thing from ignoring a real fault. Keep logging what you change, segmenting pages and queries, and rechecking your numbers. If you find a confirmed technical, security or indexing problem, fix it right away.
Author boxes and word count aren't demonstrated universal remedies, and pruning pages solely by age or traffic can remove useful content without addressing the cause of the drop. Google promises no recovery date or outcome, and your changes carry no guarantee of a noticeable effect. Timing alone doesn't prove that the update, or your edit, caused a change.
After improving content, you may see effects in a few days or after several months, including between announced updates. You don't have to wait for the next core update.
Copy an analysis prompt for your Search Console data
Use this prompt if you have Google Search Console connected to your assistant, or if you use the GrowthX platform with your Search Console data available. It only analyzes connected data and doesn't change your website. Let the rollout finish and allow a full week of complete post-rollout data before using it to assess impact. If you run it earlier, it should save a baseline and return provisional observations, not a conclusion about the update's impact.
Analyze my website's Google Search Console data to find whether any pages appear to have been affected around the November 2026 core update.
First confirm the property, Google's official rollout dates, and that a full week of complete post-rollout data is available. If the rollout is still active or the comparison period is incomplete, say so, preserve the baseline, and limit the output to provisional observations.
Use all available Search Console rows, with enough earlier history to identify existing trends. If access is limited by row limits, anonymized queries, connector limits or missing dates, state the limitation and never call a partial extract complete. Use only connected, authorized data, and do not change pages, website settings or Search Console settings.
Compare a complete post-rollout week with a complete pre-start week. Match weekdays and account for Thanksgiving, Black Friday, seasonal demand and known reporting issues. State the date ranges, data limits, filters and any missing data.
Find when changes actually began rather than assuming they began with the update. Analyze clicks, impressions, CTR and average position by:
- Website section or URL directory and topic, where supported
- Page type, such as articles, product pages, landing pages and documentation
- Individual page and query
- Country, device, search type, and branded versus non-branded queries where identifiable
Show absolute and percentage changes, and identify which groups account for the largest losses and gains. Distinguish ranking changes from changes in demand or click-through. Use correct aggregate calculations and keep unknown classifications explicit.
Return the following:
- A short summary
- A ranked table of affected sections and page types
- The individual pages worth investigating, each with the apparent start of the change, supporting data, alternative explanations, and a recommendation to monitor, investigate, or address a confirmed fault
Treat timing as evidence to investigate, not proof that the update caused the change. Recommend no bulk rewrites or deletions from this analysis alone.Take any pages the output flags for investigation through the post-completion checks above before you approve content changes.
Selected sources and related reading
These are the sources the guide relies on, with dates:
- November 2026 core update incident, Google Search Status Dashboard. Start 2026-11-10 10:06 PT, single post at 10:07 PST, no completion at cutoff.
- May 2026 core update incident, the last completed core update, 2026-05-21 to 2026-06-02.
- Google Search's core updates and your website, current guidance last updated 2025-12-10. It describes today's process and isn't historical advice.
- Search Console data anomalies, the list of disclosed reporting issues to recheck before any comparison.
- Search ranking volatility, November 9, Search Engine Roundtable, pre-launch chatter dated November 9, 2026.
- May 2026 visibility analysis, SISTRIX, UK ecommerce and news domain results for the last completed update.
- Google core update recovery: a study guide, the parent guide to open once your post-completion comparison shows a large, sustained drop.

