Google’s November 2026 core update is still rolling out. It began on November 10 at 10:06 a.m. Pacific time, applies globally and to all languages, and may take up to two weeks to complete. The safest move now is to save a clean baseline, check for unrelated technical problems, and avoid rewriting pages because of a few volatile days. Google recommends waiting until the rollout is complete—and then waiting at least one full week—before judging the impact in Search Console.
Quick action plan
- Record November 10, 2026 as the rollout start.
- Export a pre-update baseline from Search Console now.
- Fix only confirmed technical failures—not speculative “SEO fixes.”
- Wait for Google’s dashboard to mark the rollout complete.
- Wait another full week, then compare equivalent periods.
- Investigate sustained, large page/query losses; leave small moves alone.
Status checked: November 13, 2026. Use Google’s official incident page for the live completion status.
What Google has confirmed
The official Search Status Dashboard says the update started on November 10, applies worldwide and across all languages, and may take up to two weeks. Google describes core updates as broad changes intended to keep Search results helpful and reliable; they do not target a specific site or individual page.
That distinction matters. A ranking decline during a core update is not proof of a penalty, a broken page, or a single bad ranking factor. Results can continue moving during the rollout, so reacting to three days of data can create more uncertainty rather than solve it.
Do this now: a 15-minute baseline
1. Open the Search Console Performance report
In Google Search Console, open Performance → Search results. Turn on all four metrics: clicks, impressions, average click-through rate and average position. Google’s Performance report can be grouped by query, page, country, device, search appearance and date.
2. Export a stable pre-update period
Choose a complete period that ends before November 10. A full seven-day period is easy to compare later. If your business has strong weekday/weekend differences, compare matching days of the week. Export both the Pages and Queries tabs and keep the untouched files.
3. Save context that could distort the comparison
Write down launches, migrations, outages, promotions, holidays, paid campaigns, news spikes and tracking changes. For retailers, the likely end of a two-week rollout sits close to major late-November shopping days, so a simple before/after traffic comparison may mix algorithm movement with seasonal demand.
4. Check technical health without redesigning the site
Confirm that important pages still return HTTP 200, remain indexable, use the intended canonical URL, and appear in the sitemap. Check Search Console for manual actions, security issues, sudden indexing errors and server failures. Repair a real outage or accidental noindex immediately; do not postpone an obvious technical fix because an update is running.
Copy-paste core update tracking template
Paste this header into Google Sheets or a CSV file. Add one row for every important page that changed materially after the comparison window is valid.
URL,Primary query,Page type,Before clicks,After clicks,Click change %,Before impressions,After impressions,Impression change %,Before avg position,After avg position,Position change,Search type,Country,Device,Technical issue found,Content gap found,Competitor advantage,Action,Owner,Change date,Review date,Notes
Use the sheet as a decision log, not a list of pages to rewrite. A page should earn an action because the loss is sustained, material and understandable—not just because one metric turned red.
What not to do during the rollout
- Do not rewrite every page. You will lose the clean baseline and will not know whether the rollout or your edit caused the next movement.
- Do not delete content in bulk. Google calls deletion a last resort when content cannot be salvaged.
- Do not chase one rumored ranking factor. Google advises against quick fixes based on claims that a particular page element is “bad for SEO.”
- Do not refresh dates without meaningful changes. A new date is not a substitute for more accurate or more useful content.
- Do not treat average position as an exact rank. Review clicks, impressions, CTR, pages and queries together.
When and how to compare the data
First, wait until the official incident page says the rollout is complete. Then wait at least one full week. Google recommends comparing that week with a week before the update began. Use equivalent weekday patterns and separate Web, Image, Video and News data where relevant.
Start with pages, then open the queries
- Sort pages by lost clicks and lost impressions.
- Open each materially affected page and inspect its query changes.
- Separate brand and non-brand queries when possible.
- Check country and device segments for a localized or mobile-only problem.
- Label each page: stable, small movement, large sustained loss, or gain.
Google’s own example treats a move from position 2 to 4 as a small drop that does not call for drastic action. A move from position 4 to 29 is the kind of large drop that deserves a deeper assessment.
How to review a page after a large sustained loss
Compare the affected page with the current results for the same search intent. The purpose is not to copy competitors. Look for a concrete reason another result may serve the reader better.
Answer and intent
- Does the page answer the main question in the first screen?
- Is the format right for the query: guide, comparison, tool, checklist, definition or current update?
- Can readers finish the task without returning to Google?
Original value
- Does the page add firsthand testing, screenshots, examples, calculations, templates or original analysis?
- Does it go beyond summarizing the same sources as every competing page?
- Are claims linked to primary sources where possible?
Trust and authorship
- Is the author clear, with a real bio and relevant background?
- Are dates, prices, policies and product details current and verifiable?
- Are limitations and uncertainty stated instead of hidden?
Page experience and technical delivery
- Does the important content load and work on mobile?
- Are intrusive overlays, broken navigation or layout shifts blocking the task?
- Are canonical, indexing and structured-data signals consistent?
Google’s people-first guidance emphasizes originality, completeness, clear sourcing, expertise, trust and a satisfying experience. It also warns against mass-producing unrelated trend content or summarizing other pages without substantial added value.
A simple decision rule
- Stable or small move: monitor; do not disturb a useful page that still performs.
- Large loss plus technical fault: fix the fault, document the change and request recrawling when appropriate.
- Large loss plus clear content gap: improve the page for the reader, not for a guessed keyword count.
- Large loss but no clear cause: gather more data and obtain an independent review before making broad changes.
- Gain: identify what the winning page does well and protect it from unnecessary edits.
Frequently asked questions
Is the November 2026 Google core update finished?
Not as of November 13, 2026. Google’s incident page still shows the rollout and says it may take up to two weeks. Check the official dashboard for the current status.
Should I change my website during the rollout?
Do not make speculative changes in response to temporary ranking movement. Fix confirmed problems such as downtime, accidental blocking, security issues or broken pages. Save content changes until you have a valid post-rollout comparison and a specific improvement to make.
When should I check Search Console?
Save a baseline now, but do not judge the update yet. Google recommends waiting until the rollout finishes, then waiting at least one full week before comparing that week with a week from before the rollout began.
Does a traffic drop mean Google penalized my site?
No. Core updates are broad ranking-system changes and do not target individual sites or pages. Check for manual actions and technical failures separately, then assess sustained changes after the rollout.
How long can recovery take?
Google says improvements may show in days, but site-wide reassessment can take several months. There is no guaranteed recovery date, and a site does not necessarily have to wait for another major core update to see improvement.