Google started rolling out a core update on 10 November 2026, at 10:06 Pacific time, which is 20:06 in Bulgaria. The Search Status Dashboard says the November 2026 core update "applies globally and to all languages" and that "the rollout may take up to 2 weeks to complete." Black Friday is on 27 November. If the rollout takes the full two weeks, it finishes around the 24th, three days before the sale.
That overlap is the whole problem. Positions can move while you are trying to get a sale page found, and a Tuesday dip is easy to misread as a reason to rip the site up. Here is what Google actually published, what I would snapshot today, and what I would leave alone until the update has finished.
What did Google actually say?
On 10 November, at 10:07 Pacific, Google posted a single line on the dashboard: it had released the November 2026 core update, worldwide and in every language, with a rollout that may take up to two weeks. That is the official notice. There is no blog post that names a type of site, a kind of query or a market.
This is the third Search core update of 2026. The same dashboard lists a March core update, which started on 27 March, and a May core update, which started on 21 May. February's Discover update is a different system. It does not belong in this count.
Google's standing page, Google Search's core updates and your website, is the document to read, not a thread about what the update "targets". It says core updates are broad changes to the systems that rank pages, made several times a year, and that they "don't target specific sites or individual web pages." It also says most sites do not need to worry, and may not even notice that one has happened. A page that drops is not, on that evidence, being punished. Google's analogy on the same page is a list of restaurants that gets reshuffled: the ones that move down "aren't necessarily 'bad'."
I would treat those sentences as the boundary of what we know. Anything beyond them is guesswork.
Snapshot your numbers today
Open Search Console today, before you change a heading. Go to the Performance report for Search results, set the date range to the last 28 days, and export it. Save the file with today's date in the name. Then export the same report again with a custom range that ends on 9 November, the day before the rollout started, covering at least the week of 3 to 9 November. That second file is the baseline Google later asks you to compare against. If you wait until mid-rollout to take it, you will be comparing a messy week with another messy week and calling the difference a conclusion.
While you are there, write down clicks, impressions and average position for the pages that bring in the most money, for the week before 10 November, each next to its URL. If you already filter by query, export that too, because a page can hold its impressions while the queries that sit in position 3 drift to position 8, and you will miss that in a site-wide total. I also take a screenshot of the Page indexing report and of URL Inspection for the home page and the sale page, including the last crawl date and the verdict "URL is on Google" or not. Those screenshots are what let you tell a ranking movement from a page that fell out of the index, and they take five minutes. If the sale page is new, the crawl date and the index verdict matter more than the position, because a page that is not in the index cannot have been hit by the update; it was never in the results to drop from. Export the daily rows. The chart in the interface smooths a noisy week into a line that looks calmer than it is, and those daily rows are what you will want in late November, when someone asks whether the 12th was a bad day or the start of a slide.
One file, dated, in a folder you can find in three weeks.
That is the whole job today.
Don't rewrite the site mid-rollout
Google's own guidance is blunt about rewrites during a rollout. For a small drop, its example is a page moving from position 2 to 4, and it says there is no need to take drastic action; it even recommends "avoiding making changes to content that's already performing well." For a large drop, its example is position 4 to 29, and even then the next step is a deeper assessment after the rollout has finished, not a rewrite tonight.
I would not retitle ten service pages, merge two blogs, or strip a section because a position moved on a Wednesday in the middle of a two-week rollout. Those changes mix with the update, and in three weeks you will not be able to tell which of them did what. If a page is already doing the job, selling the product, answering the query, leave it. Leave it alone. The sale week is a bad moment to discover that a rewrite you rushed out on the 15th is the thing Google is now trying to recrawl.
What I will change mid-rollout is a fault, not a hunch: a 404 on a URL that was live last week, a noindex that travelled over from a staging copy, a sale page that does not load on a phone. Those belong in the last section. They are not tweaks to chase a Tuesday position.
Keep the Black Friday pages coming
The update does not freeze the calendar. Black Friday is still 27 November, Cyber Monday is still 30 November, and Google still needs days or weeks to find a new page. I wrote about how to get a Black Friday page into Google before the sale. That advice does not change because a core update is running. If the page is not live yet, put a plain version at the permanent URL this week, link it from the home page and the menu, put it in the sitemap, and request indexing. Improving it at the same address is fine. Taking it down because rankings look jumpy is not.
Do not use daily positions between 10 and about 24 November to decide whether the sale page worked. It will be crawling, the update will still be rolling out, and a midweek wobble is not a verdict. Keep shipping the page. Judge it later, against the baseline you exported today.
How do you read the numbers a week after it ends?
First confirm on the Search Status Dashboard that the rollout has finished, and write down the end date. Wait a full week. Then compare that week with a week before 10 November, which is why the 3–9 November export matters. Google says that comparison is how you pinpoint what changed. Comparing 11 November with 18 November, both inside or on the edge of the rollout, will not do it.
Look at the pages and queries you wrote down, and at Web Search separately from Images, Video and News, because Google asks you to analyse those types on their own. A small move, of the 2-to-4 kind, I would leave. A large, sustained drop for the site as a whole is when Google's self-assessment questions are worth an afternoon: is the site helpful, reliable and written for people, and are the pages that fell doing a worse job than the pages now above them? Improvements, if you then make them, can show in a few days, or they can take several months, and Google says there is no guarantee they will move the result. You may be waiting for a later update. I would not promise a recovery date to anyone, including myself.
A week that includes Thanksgiving in the United States, then Black Friday and Cyber Monday, is also a poor "after" period if you sell online, because the traffic shape is the sale, not the algorithm. Compare like with like: a normal week after the rollout, or the same sale week last year only as a seasonal check, never as proof of the update.
When is a drop a site problem, not the update?
A drop is a site problem when the page is no longer on Google, or no longer reachable. Open URL Inspection for the URLs that fell. If the verdict is "URL is not on Google", or the last crawl is blank, or Crawl allowed? or Indexing allowed? says no, you are not looking at a core update. You are looking at a noindex tag, a robots.txt rule, a canonical that points somewhere else, or a page Google has not fetched. I go through those faults in why your site isn't showing in Google.
The same applies if the URL now returns an error, or if the sale page takes so long on a phone that the main content misses Google's 2.5-second target and the layout jumps as it loads. Google's guide to debugging Search traffic drops treats a technical issue across the site as a different shape of drop from an algorithmic one, and it also tells you to check the Manual actions and security reports. A core update is not a manual action and it is not a hack. Check those reports first.
The one thing I cannot tell you from the outside is whether a given drop on your site is the update or a fault on the site. The crawl and index reports are what settle it, and they settle it in an afternoon. Guessing from a ranking tracker, without those reports, is how people rewrite a healthy page and leave a noindex in place.
If the sale page itself is the problem, a slow template, a header that hides the offer on a phone, a form that fails in an in-app browser, that is SEO work sitting next to the build. I would rather fix the fault, or rebuild the front of the page as a custom React site if the theme will not take the change, than invent a content overhaul because a position moved in week one of a rollout. An existing WordPress theme can be tightened when the structure is already sound. The theme is not the first question. The fault is.
Export the 28 days today. Do not take the sale page down because a position moved on a Tuesday.

