Google core update mistakes to avoid before Black Friday 2026

Many site owners hear "wait until the update finishes" and conclude that they should freeze everything. That is the wrong reading. The advice to wait applies to judging what the update did to your rankings. It does not apply to repairing a broken checkout, fixing a wrong price or removing a stray noindex tag.

On November 11, 2026, Google's Search Status Dashboard listed the November 2026 core update as active, with a start time of November 10 at 10:06 a.m. US/Pacific. Google says it applies globally, to all languages, and may take up to two weeks. Check the dashboard again before you act, because that status can change.

Black Friday lands on November 27 this year, with US Thanksgiving on November 26 and Cyber Monday on November 30. So the rollout and the busiest shopping days overlap. The seven mistakes below are illustrative scenarios, not reported case studies, and they run from the most expensive in the short term to the slowest to hurt.

1. Freezing checkout and stock fixes

Picture a retailer that sees a ranking wobble and decides to touch nothing until the update ends. Meanwhile a promo code fails at payment, and a sold-out item still shows as available.

That hesitation costs real orders on the days when demand peaks. It can also trigger problems unrelated to Search rankings. Google's Merchant Center checkout requirements say shoppers must be able to add advertised in-stock products to their cart and finish the purchase, with availability matching across product data, product pages and checkout. A product submitted as in stock that is actually out of stock on the page or at checkout gets disapproved.

Price mismatches have a common cause too: starting or ending a sale without updating the product feed. Product data and site prices should change together, and the sale_price_effective_date attribute must match when the sale really runs.

Do this instead: place a test order from a product page to payment, on phone and desktop. Then compare feed, page and checkout for price and availability. These are listing and checkout issues, not a core-update penalty, so fixing them will not reverse a ranking change.

2. Blaming the update for blocked pages

Now picture a publisher whose traffic drops the same week the rollout began. The team assumes the update did it. In fact a developer pushed a template change, and a noindex tag now sits on a whole section.

Google lists server outages, robots.txt problems and misplaced noindex tags among the technical causes of lost traffic. A drop that coincides with an update does not prove the update caused it.

Do this instead: open the Crawl Stats and Page Indexing reports in Search Console and look for a matching rise in errors. Then inspect affected URLs. The first URL Inspection result shows Google's indexed version of the page, while Test live URL checks the current version. If the result shows a noindex tag or header you did not intend, remove it, because Google will not index the page until you do.

Two cautions. Robots.txt controls crawling, not reliable exclusion from the index, so do not treat it as a switch for hiding pages. And an indexing request or a passing live test does not guarantee indexing or an immediate return of traffic.

3. Rewriting useful pages after one bad day

A single bad day is a thin basis for a rewrite. Early movement during a rollout can settle, and if you rewrite your best pages now, you lose the evidence of what worked.

Google describes core updates as broad changes meant to improve helpfulness and reliability across results, not actions against particular sites. It also says a traffic change after a non-spam update does not mean you are spamming. Google gives a useful sense of scale: a move from position 2 to 4 does not call for radical changes, while a broad fall to position 29 deserves deeper assessment.

Do this instead: save your evidence. Export Search Console data for November 3 to 9, the seven days before the rollout began. That range is a practical baseline, not a Google requirement. Keep a change log of anything you edit.

This is not a publishing ban. Correcting a wrong fact or adding a new article is fine. Hold off on sweeping rewrites until you can read the results.

4. Deleting pages because traffic fell

Imagine a publisher that sorts its archive by lost clicks and removes the bottom third. It feels decisive. But low traffic does not mean a page is useless, and an old date does not either.

Google calls deleting content a last resort for material that cannot be salvaged. It does say that removing unhelpful sections created mainly for search engines can help.

Do this instead: judge each page by Google's helpful-content questions. Does it offer original reporting or analysis, substantial coverage, clear sourcing, and value beyond competing results? Improve what can be improved. Remove only what truly cannot be saved. Our guide to avoiding web design mistakes that cause a traffic drop covers other ways a site can lose visitors.

5. Comparing holiday traffic with an ordinary week

Here is how a retailer fools itself. The rollout may end around November 24, and the days right after include Thanksgiving, Black Friday and Cyber Monday. Set that against a quiet week in early November and almost any chart looks dramatic, up or down.

Google's own method is to confirm the update has finished on the dashboard, wait at least one full week, and compare it with a week before the rollout. That is the starting point. On top of it, add an event-aligned comparison. Black Friday was November 28 in 2025 and is November 27 in 2026, so the same calendar dates do not line up the event. Even then, a year-over-year comparison cannot isolate the update, since demand, offers, competitors and your own site changes differ.

Do this instead: break the data down by query, URL, country, device and search appearance, and look at Web, Images, Video and News separately. Check the long view too, because Google recommends 16 months of Search Console data to spot seasonal patterns. Falling clicks with steady impressions may point to weaker titles, snippets or competing rich results, not a ranking collapse.

6. Replacing established Black Friday URLs

Should a sale page get a new address every year? Google's Black Friday guidance is clear: reuse a meaningful recurring URL, such as /sale/black-friday, instead of creating a year-specific page.

A new address each year throws away the history the old page built. Google also warns that URL changes can cause ranking fluctuations while pages are recrawled and reindexed, which takes weeks for a medium-sized site and longer for a large one. Moving in the middle of a rollout adds noise to an already hard-to-read period.

Do this instead: update the existing page, link to it from the homepage or another prominent page, and keep it crawlable. For more on earning organic visits, see our piece on increasing website traffic through Google.

7. Faking freshness instead of improving information

The last scenario is a publisher that changes dates on old guides and pads them with filler, hoping the page looks current. Google's helpful-content guidance names changing dates without substantial content changes as a warning sign of search-engine-first publishing.

Padding fares no better. Google has no preferred word count, and it rejects adding large amounts of content, or removing older material, just to make a site look fresh.

Do this instead: verify the facts, replace outdated details, and add something a reader cannot get elsewhere, such as original information or clearer sourcing. A date that reflects real work is honest. Our note on what makes effective web copy can help with the writing.

Fix now or wait? A quick guide

Frequently Asked Questions

Should I keep publishing while the update is unfinished?

Yes, if the content is useful and accurate. The wait applies to reading the results, not to normal work. Log what you change so you can tell later what mattered.

Does a traffic drop mean my site is spamming?

No. Google says a traffic change after a non-spam update does not by itself mean a site is spamming.

Do I have to wait for the next big update to recover?

No. Google says improvements can show up through smaller, unannounced core updates. It also says effects can appear within days or take several months, and it does not promise a noticeable gain. Do not count on recovery before Black Friday.