Google’s November core update: Don’t rush a website rewrite

Google’s November core update began rolling out on November 10, and it is still active as of November 12, 2026. If your business depends on unpaid Google traffic, an early ranking drop is a reason to watch carefully—not to rewrite your website immediately. Google recommends waiting until at least a full week after the rollout finishes before assessing its impact.

The November core update is live, but not finished

According to the Google Search Status Dashboard incident record, the update started on November 10 at 10:06 a.m. US/Pacific. It applies globally and across all languages, and Google says the rollout could take up to two weeks.

That is a rollout window, not a promised completion date. The dashboard still identifies the update as active as of November 12, with Ranking listed as the affected product. There is no completion announcement in the incident record.

This is a released ranking update, not an experiment or a feature Google plans to introduce later. Search Engine Journal reports that Google describes its purpose as improving the visibility of relevant, satisfying content from all types of websites.

For a business owner, the distinction that matters now is between “started” and “finished.” You can monitor your website while the rollout continues, but Google’s recommended assessment period has not started yet. Do not treat the first few days as the final result.

The assessment clock starts after completion

Google’s core update guidance says to wait at least one full week after an update finishes. Then compare that week’s Search Console performance with a week before the rollout began.

This means there are separate checkpoints: confirmation that the update is complete, the full waiting period afterward, and the comparison itself. Counting a week from the announcement would skip the first checkpoint and would not follow Google’s guidance.

Google also explains that core updates make broad changes rather than targeting particular websites or individual pages. A decline during the rollout is therefore not, by itself, evidence that Google singled out your business or that your entire website needs replacing.

A ranking dip during an unfinished rollout is not a website rebuild brief.

The practical response is to separate observation from action. Note what you are seeing now, but reserve conclusions about the update’s impact until the recommended comparison window is available. That gives your eventual content review a clearer starting point than an isolated early decline.

What to do this week instead of rewriting pages

Your immediate job is to prepare for a useful review. You do not need to turn an unfinished rollout into a website-wide editing project.

• Record the start date. Mark November 10 as the beginning of the rollout so you can choose a comparison week from before it started.
• Check for actual completion. Use Google’s incident record rather than assuming that the stated two-week window guarantees a particular finish date.
• Identify the pages and searches that matter to your business. Make a list of the important pages and search queries you will review in Search Console after the waiting period.
• Keep search types separate. Google’s guidance recommends separating Web Search from other search types when assessing performance.
• Hold off on speculative fixes. Do not delete useful pages or commission sweeping rewrites simply because rankings have moved early in the rollout.

If someone else manages your SEO, ask for a monitoring plan now and an assessment after the appropriate waiting period. The immediate question is not “What are we rewriting?” It is “When will we have the comparison Google recommends?”

OnlyaClick tip: Keep one update note with the rollout start, the confirmed completion date when available, your planned comparison weeks, and any holiday-demand context.

That note can keep the discussion focused on the same dates and evidence, whether you review performance yourself or work with a marketer.

Holiday timing could make the comparison harder

Retailers have another issue to consider: the calendar. Search Engine Journal notes that a full two-week rollout would finish around November 24. The following comparison week would fall amid Thanksgiving, Black Friday and Cyber Monday.

November 24 is an estimate, not a confirmed end date. Still, the possible overlap matters for holiday-sensitive businesses. A simple before-and-after traffic comparison could reflect changes in seasonal demand as well as the ranking update.

Our recommendation is to flag that context explicitly when reviewing results. Do not automatically label every increase an update win or every decline an update loss. Start with Google’s recommended comparison, then acknowledge where holiday timing makes interpretation less straightforward.

For example, your review can distinguish what you observed from what you can confidently explain. A page’s search performance may have changed; the timing alone does not establish how much of that change came from the update rather than holiday demand.

This is not a reason to abandon measurement. It is a reason to avoid presenting a complicated comparison as a clean verdict on your website.

Persistent losses call for a closer look, not guesswork

Once the update is complete and the waiting period has passed, the size and persistence of any decline should guide your response. Google advises against drastic action for small ranking drops and recommends deeper assessment for sustained, large losses.

Begin with the affected pages and queries rather than assuming everything needs attention. Review the content for usefulness, clarity and ease of navigation. The goal is to understand where a visitor’s experience could genuinely improve, not to make edits merely to show that something is being done.

Useful review questions include:

• Does the affected page clearly answer the questions it is meant to address?
• Is the information useful and easy to understand?
• Can visitors navigate the content without unnecessary confusion?

Avoid turning that review into a deletion exercise. Google treats deleting content as a last resort, not the default response to a core update.

If you bring in help for SEO services, ask for recommendations tied to the affected content and the post-rollout comparison. A proposed rewrite should have a clear purpose beyond reacting to an early ranking movement.

The bottom line

As of November 12, the rollout is unfinished, so it is too early for a final assessment. Record the start date, watch for Google’s completion announcement, and wait at least a full week afterward before comparing Search Console performance with a pre-update week.

For holiday-sensitive businesses, add seasonal context before drawing conclusions. If substantial losses persist, investigate the affected content carefully. The sensible next move is not to ignore the update or rebuild in a hurry—it is to prepare a measured review and act on what that review supports.