Google’s November core update: what stores should check

Google’s global core update began on 10 November. Keep a clear baseline before attributing holiday trading changes to search rankings.

SSophie Harrington2 min read

13 November: a reporting error overlaps the rollout

Google’s Search Console anomaly notice identifies lower reported impressions in the Generative AI performance report for 9–11 November 2026. Google says this is a logging issue only. It does not establish a loss of actual visibility, and the notice does not say that every Search Console report is affected.

Annotate those dates before comparing charts around the core update. Keep the affected report separate from other search reports, store orders and analytics. The current notice does not state that the missing November data has been restored; do not apply the restoration note for an older incident to this one.

The core-update status entry still has no completion notice as checked on 13 November. A reporting correction and a ranking rollout are separate events.

Google began its November 2026 core update on 10 November at 18:06 UTC. The official status notice says it applies globally, in all languages, and may take up to two weeks. The rollout was still active when checked on 11 November.

For stores approaching Black Friday, the useful immediate action is to keep a clean record of search performance and store changes. The announcement does not identify affected retailers or establish why any particular store’s traffic has moved.

Keep the rollout window separate from the verdict

Google’s core-update guidance recommends waiting until the rollout has finished, then at least a full week, before comparing Search Console performance with a week before the update began. It advises reviewing pages and queries, separating search types, and avoiding drastic changes in response to a small ranking movement.

That does not mean ignoring a broken store while the update runs. Our recommendation is to keep operational checks separate from an assessment of ranking changes: confirm that important pages still load, products can be bought and measurement is working. A checkout fault or an accidental page restriction needs its own investigation.

A useful record for a busy retail week

  • Save a dated baseline for important product and collection pages, including clicks, impressions and the queries that bring shoppers to them.
  • Keep a change log for promotions, stock availability, product-page edits and site releases. Those changes can complicate a simple before-and-after comparison.
  • Compare equivalent page groups and markets rather than treating a site-wide total as a diagnosis.
  • Record campaign activity and trading-calendar differences alongside the search figures. A holiday promotion and an ordinary week are not interchangeable baselines.

These are measurement precautions, not a formula for reversing a core update. If a substantial decline persists after the rollout and comparison window, investigate the affected content and competing results rather than deleting pages or rewriting a whole catalogue on the strength of one day’s chart.

This is a new core update, separate from the September spam update that finished in October. Check the official incident entry for completion rather than treating the two-week estimate as a fixed end date.

📅
Rollout began 10 November. As checked on 11 November, Google had not announced completion. The two-week estimate is not a confirmed completion date.
Filed underMarketing

More from Marketing

See all →