# Google's November 2026 Core Update Has Started: What to Do With Your Store or Site Before White Friday

Published November 17, 2026 · Updated November 17, 2026

<https://mqudah.com/en/insights/google-core-update-november-2026/>

Google suggests comparing a week after a core update with a week before it. This year that week may land on White Friday. Here's a decision table for Search Console and a reading calendar.

## The short answer

Google's November 2026 core update began on 10 November and was still rolling out on 17 November. It may run into White Friday, since a previous core update took 18 days. So don't edit a page that sells or delete pages. Fix only what Search Console shows as a technical error or a manual action. Judge by orders from organic search, not by the rank tracker. The serious reading comes in December.

## The bottom line

- Don't judge any day of the rollout. The update began on 10 November, and Google hadn't announced its completion by the morning of 17 November.
- If the rollout ends on 20 November or later, White Friday falls either in the comparison week Google asks for or inside the rollout itself. So compare page groups with each other, and with the same weeks last year.
- A ranking drop that doesn't move organic orders gets written down and watched, not fixed.
- A technical error, a manual action or a security alert in Search Console isn't the update. Fix it today.
- Don't delete a page, or rewrite a page that sells, before White Friday. Google says its systems can take months to pick up an improvement.

It's Tuesday morning, and a store owner opens his rank tracker. The category page that brings in most of his orders has slipped a few places. A product page he rarely thinks about has climbed. White Friday is 10 days away, and his designer is waiting for a decision. Does he rewrite the page now?

My answer is no. Google is still rolling out a core update that began on 10 November, and numbers from the rollout days can't be read. Open the order log before the rank tracker. If orders from organic search haven't fallen, write the drop down and leave it. The only thing to fix now is a technical error.

## What did Google announce on 10 November?

That a core update had started, and very little else. The announcement for the Google November 2026 core update sits on an incident page of the Google Search Status Dashboard. That's where Google posts the ranking updates it confirms. Here it is in full:

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

So it covers Arabic search in Saudi Arabia and Jordan too. As of this morning, the dashboard hasn't added a line saying it's complete.

Don't treat "two weeks" as a deadline, though. The dashboard's own history shows how long the three previous core updates ran:

| Core update | Started | Took |
|---|---|---|
| December 2025 | 11 December 2025 | 18 days, 2 hours |
| March 2026 | 27 March 2026 | 12 days, 4 hours |
| May 2026 | 21 May 2026 | 11 days, 21 hours |

Two of them finished inside two weeks. Last December's ran four days over.

## Why does this update collide with White Friday?

Because Google's own method for reading a core update puts the sales season inside the comparison. White Friday is the region's late-November sales season. This year it falls on Friday 27 November.

Google's page on core updates asks for three steps, in this order:

1. Make sure the rollout is over: "Confirm that the core update has finished rolling out."
2. Wait at least a full week after that before you analyze your site in Search Console.
3. Compare that week with a week before the rollout started.

These dates are my own arithmetic from Google's announcement. Google hasn't published any of them.

| What happens | Date |
|---|---|
| Baseline week, before the rollout | 3–9 November |
| Rollout starts | 10 November |
| Rollout ends, if it takes the full two weeks | about 24 November |
| White Friday | 27 November |
| Rollout ends, if it takes 18 days like December 2025 | about 28 November |
| Comparison week, if the rollout ends on 24 November | 25 November – 1 December |
| First possible reading of that week in Search Console | about 3–4 December |

Search Console data usually shows up after two or three days. That's why the last row lags.

Look at rows five and six. If the rollout ends between 20 and 26 November, the comparison week contains White Friday. If it runs long, as it did last December, White Friday falls inside the rollout itself. Only a finish by 19 November keeps it out, and even then the comparison week is the run-up to the sale. In every case, you won't be comparing before and after the update. You'll be comparing an ordinary week with a peak-season week.

The season can push your numbers either way. A store gets more searches for its name and its categories in a sale week, and that can hide a real ranking drop. A clinic or a repair company may see the opposite. People are busy shopping, so leads fall while rankings hold. That's my reading, not a published measurement. But it's reason enough to distrust any figure from that week.

So this year I adjust Google's method in three ways:

- **Compare page groups with each other.** Categories, products, articles and service pages are separate groups. If the season is behind the movement, they'll most likely move in the same direction. If all of them rise except one, examine that one.
- **Compare with last year.** In Search Console, open the same dates from 2025. Last year's White Friday week was 25 November – 1 December. Compare it with 3–9 November 2025. The gap is what the season alone does to your clicks. First, check the status dashboard to confirm no update was rolling out then.
- **Judge by orders.** For a store, open Reports, then Acquisition, then Traffic acquisition in GA4, and take the orders in the Organic Search row. A service business asks its sales team for leads from search.

To isolate each group with Search Console's page filter, use [the before-and-after sheet](https://mqudah.com/en/insights/google-spam-update-september-2026/) with this update's dates.

## What should you do this week? The decision table

Find the row that matches what you see, then follow the other two columns. The position examples in the first two rows are Google's own.

| What you see in Search Console this week | What to do | What not to do |
|---|---|---|
| A small drop in position for some queries, say from 2 to 4 | Note it in the sheet. Wait for the rollout to finish, then a full week more | Don't edit a page that sells. Google says there's "no need to take drastic action" and advises against changing content that's already performing well |
| A large drop in one page group, say from 4 to 29 | Start the deeper assessment on paper. Compare your pages with what now ranks above them, and write down what they genuinely lack for the searcher. Publish the improvements after the December reading. If those pages carry White Friday sales, cover their main searches with Google Ads for the season, and judge that spend by orders | Don't rewrite them before White Friday, don't delete them, and don't stuff keywords in a hurry |
| Fewer clicks, but organic orders are steady | Log it as a note and check it again in the December reading | Don't fix what isn't broken |
| A sudden jump in pages not indexed for "Server error (5xx)", "Not found (404)" or "Blocked by robots.txt" on pages that sell, an entry under Manual Actions, or an alert under Security Issues | Fix it today. This isn't the update | Don't wait for the rollout to finish before you start |
| Rankings or clicks going up | Check that stock and offers on the rising pages are ready for the season | Don't credit any change for the rise before the December reading |

Only the fourth row asks for work today. Most other reasons in the Pages report, such as Alternate page with proper canonical tag, are normal for a store and need no fix. Google's guide to debugging traffic drops lists other causes: technical issues, security issues, manual actions for spam, seasonality and site moves. Rule them out before you blame the update. Start with [the Search Console check in my technical SEO guide for online stores](https://mqudah.com/en/insights/technical-seo-online-store/).

Then put three dates in your calendar:

1. **Today.** Record baseline-week clicks for each page group. Next to them, record organic orders for the same week.
2. **The day the completion line appears on the dashboard.** Add seven days, then two or three more for the data delay. That's your reading date. If it falls before December, read it, but change nothing before the December reading.
3. **Reading day.** Fill in the sheet, read it against last year, then decide.

One distinction matters here. White Friday offer pages are seasonal work, so publish them as planned. The rule is about an existing page that sells, one you're tempted to change because its ranking moved.

## What should you ignore for now?

Anything that asks you for a decision before the rollout is done. Here are four things by name:

1. **Claims that the update targets AI-written content.** Google hasn't said that. Its question is broader. Is your site as a whole, not just individual pages, delivering content that's "helpful, reliable, and people first"? The questions for that self-check are on Google's page about [helpful content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content).
2. **Day-to-day swings in your rank tracker.** One day's reading mid-rollout is a snapshot of something unfinished. It says nothing about this week's orders.
3. **Quick fixes and deleted pages.** Google is blunt: "Avoid doing 'quick fix' changes", and it calls deleting content "a last resort". Improve content "in meaningful ways" later. A product page you delete today won't sell on White Friday.
4. **Disavowing links.** The announcement doesn't mention links at all. The exception is a manual action over links in the Manual Actions report. Handle that the way the report tells you to.

## My view: don't touch a page that sells this week

The 10 days before White Friday are the most expensive days of the year to break a page. An edit now won't pay off in time, because Google says its systems can take several months to learn and confirm a change. It could still break a page that sells, and it muddies the reading. If the numbers change in December, you won't know whether the cause was the update or your own hand.

My habit is to read the sales sheet before the ad report. Here, that means organic orders before the rank tracker.

I also know that real improvement is measured in months. At Argan Package in Saudi Arabia, organic sales rose 15% within four months. That came after Search Console and technical SEO issues were fixed. Organic sales also move with the season and with paid campaigns, so I don't credit the whole 15% to the fixes. The rise wasn't tied to a core update, and I don't tell it as a recovery story. I mention it because it was read in sales over months, not in one keyword's position over a week. The details are in the [Merchant Center and SEO case study](https://mqudah.com/en/case-studies/merchant-center-seo/).

## What's next?

For now, go back to [the White Friday plan](https://mqudah.com/en/insights/white-friday-preparation/). Over the next two weeks, that's where the difference gets made, not on Google's results page.

If the December reading shows a large drop in one page group, with organic orders down too, my [SEO services](https://mqudah.com/en/services/seo-services/) start with a deeper assessment that ranks what to improve first. If the Pages report shows errors you can't trace, start with a [technical SEO audit](https://mqudah.com/en/services/technical-seo-audit/). Request a consultation, and send the sheet filled in.

Want your team to read Search Console this way? See [corporate training programs](https://mqudah.com/en/training/).

## Questions

### Does the November 2026 core update target AI-written content?

Google hasn't said so. The announcement is two sentences long and names no type of content and no type of site. Anyone who tells you the target is guessing.

### How do I know the update has finished?

The Google Search Status Dashboard adds a completion line to the same incident page. As of the morning of 17 November, that line hadn't appeared. Once it does, wait a full week, as Google asks. Then allow two or three days for the last day's data to show in Search Console.

### An important page fell from the top positions to page three. Should I wait until December?

Google calls that a large drop and asks for a deeper assessment. Start it now, on paper. Check for technical errors first, then compare your page with what ranks above it and write down what it genuinely lacks for the searcher. I'd hold any major change until after the December reading, unless you find a technical error. A technical error gets fixed straight away.

### How long before an improvement shows?

Google says some changes can take effect in a few days, but its systems may need several months to learn and confirm them. If months pass with no effect, Google says that could mean waiting until the next core update.

### I run a service business, not a store. Does this apply to me?

Yes. The update is global and covers all languages. The difference is that you judge by leads, not orders. Ask your sales team how many calls, WhatsApp chats and quote requests came from search each week.

## Sources

- [November 2026 core update (incident)](https://status.search.google.com/incidents/WLxcJyC6jMWMfryxsKMc), Google Search Status Dashboard (opened 17 November 2026)
- [History | Google Search Status Dashboard](https://status.search.google.com/summary), Google Search Status Dashboard (opened 17 November 2026)
- [Google Search's Core Updates](https://developers.google.com/search/docs/appearance/core-updates), Google Search Central (opened 17 November 2026)
- [Creating helpful, reliable, people-first content](https://developers.google.com/search/docs/fundamentals/creating-helpful-content), Google Search Central (opened 17 November 2026)
- [Debugging drops in Google Search traffic](https://developers.google.com/search/docs/monitor-debug/debugging-search-traffic-drops), Google Search Central (opened 17 November 2026)
