What to save before you compare
Google began rolling out its November 2026 core update on November 10 at 10:06 a.m. Pacific time. Google says it applies globally and could take up to two weeks. In Search Console, export the seven complete days before rollout, November 3–9, as a baseline. Save the daily totals and the page and query views you expect to compare later.
A drop in clicks alone does not tell you why traffic changed. Save impressions and average position alongside clicks, and record the search type and filters so you can reproduce the comparison.
How to build a baseline that you can trust
When you export or snapshot Search Console data, keep the setup consistent. The goal is to compare like with like, not to create a larger set of numbers that is hard to interpret later.
- Keep the same search type in both comparisons, such as Web, Image, or Video.
- Use the same page cohort in both periods, for example the same directory, template group, or set of URLs.
- Keep filters fixed, including country, device, query type, or any custom segmentation you normally use.
- Record the exact dates and use the Google Search Status Dashboard for the rollout start and completion dates.
- Avoid changing reports, filters, or URL groupings after you have saved the baseline.
Compare a full week after completion with the week before rollout
Google recommends waiting at least one full week after the rollout completes before analyzing the change. Once the dashboard confirms completion, use the first seven complete Search Console days after it ended and wait for those days to be finalized. Leave rollout days out of the comparison.
Compare that later week with November 3–9 inclusive, using the dates shown in Search Console (Pacific time for the standard Performance report). Each seven-day window covers every day of the week once. Look at the site-wide trend first, then use the same country, device, page and query filters to see where the changes are concentrated.
Check for promotion or indexing changes before you attribute the drop
Before you conclude that the core update caused a traffic or impression change, look for other explanations. A ranking shift may be real, but it may also be a side effect of something else on the site.
- Recent content promotions, homepage links, newsletters, or social campaigns that could temporarily change demand.
- Indexing changes such as newly indexed pages, removed pages, canonical changes, or noindex updates.
- Technical changes that affect crawlability or rendering.
- Seasonal demand changes that can alter clicks and impressions independently of rankings.
- Search Console property or filter changes that make the data non-comparable.
Log anything that changed between the two periods. Even if you find no obvious site change, a before-and-after comparison shows what moved around the update; it cannot prove what caused the change.
What Google says about core updates
Google’s core update guidance emphasizes that broad ranking changes are not targeted at specific pages or sites in the way a manual action would be. The practical takeaway is to monitor performance carefully, improve helpful content where needed, and avoid assuming that every fluctuation is caused by one update.
Google Search status page for the November 2026 core update
Google Search guidance on core updates
Before-and-after checklist
- Save a Search Console export now using a fixed setup.
- Document your search type, page cohort, and filters.
- Check the status dashboard for the completion date and wait at least a full week.
- Compare the first seven complete, finalized days after rollout with November 3–9.
- Review promotions, indexing changes, and technical updates first.
- Use the comparison to decide what to investigate next.
