Google started rolling out its November 2026 core update on November 10 at 10:06 a.m. Pacific. According to the Google Search Status Dashboard, it applies globally, to all languages, and may take up to two weeks to finish.
If your traffic dipped this week, the worst move is to start rewriting pages. Some drops come from the update. Others come from something you broke, and that kind you can fix today.
Here's how to tell them apart, using Google's own guidance.
First: don't judge it mid-rollout
Google's core updates documentation is specific about timing. Wait until the dashboard shows the rollout is complete, then wait at least a full week more before you analyze anything.
When you do compare, Google recommends comparing the week after the update finished with a week before it started. Comparing yesterday with last Tuesday mostly measures noise.
So for now, use the time to rule out the problems that aren't the update.
1. Check whether the drop is site-wide or narrow
Open Search Console, go to Performance, and use the Compare tab. Check whether the drop is limited to:
- specific queries or pages
- one country
- one device type
- one search type (Web, Image, Video, News)
This is the most useful split you can make. A drop on one device or in one country rarely comes from a broad core update. A drop spread across your whole site might.
2. Look for a technical problem first
Google's guide to debugging traffic drops points to two reports: Page indexing and Crawl stats. Look for a spike in errors that lines up with your drop.
Then run URL Inspection on a few pages that lost traffic and use the live test. It shows whether Googlebot can actually fetch the page right now.
You can also do a quick status-and-robots check from your terminal. This doesn't prove what Googlebot sees, but it catches obvious mistakes like a stray noindex after a deploy:
while read -r url; do
code=$(curl -s -o /tmp/page.html -w "%{http_code}" "$url")
header=$(curl -sI "$url" | grep -i '^x-robots-tag' | tr -d '\r')
meta=$(grep -io '<meta[^>]*name="robots"[^>]*>' /tmp/page.html | head -1)
echo "$code | $url | ${header:-no x-robots-tag} | ${meta:-no meta robots}"
done < urls.txt
Put the URLs that lost the most clicks into urls.txt, one per line.
A trap worth knowing: if you test with a bot's user agent, your CDN may answer 403. Many CDNs block requests that claim to be Googlebot or Bingbot but don't come from their IP ranges. That's normal and proves nothing about the real crawler. Only the search engine's own live test can confirm that.
3. Check the Security Issues report
If Google has detected malware or phishing on your site, it will show in Security issues in Search Console. It's a one-minute check, and it's a very different problem from a core update.
4. Check Manual Actions
A manual action means someone at Google decided part of your site breaks the spam policies. It shows under Manual actions. Again, this isn't the core update, and it has its own fix and review process.
5. Rule out search interest and seasonality
Sometimes nothing is wrong with your site. People are just searching less.
In the Performance report, filter to the queries that lost the most clicks. Check each one in Google Trends. Then switch to the 16-month date range and see if the same dip happened last November.
If demand fell everywhere, your rankings may be fine.
6. Think about what you changed recently
New theme, URL changes, a migration, a plugin update that touched SEO settings? Google's guide notes that a medium-sized site can take a few weeks for Google to process URL changes.
Drops that line up with your own deploy date are far more likely to be yours than Google's.
If it really is the core update
Google's documentation says a drop after a core update doesn't automatically mean something is wrong with your pages. Core updates are broad and don't target specific sites. Other pages may simply serve searchers better now.
Its advice:
- Small drop: no need for drastic changes.
- Large drop: do a deeper review of how helpful and reliable your content is.
- Avoid quick fixes. Make improvements that help readers long term.
Recovery isn't instant either. Google says it can take several months for its systems to recognize improvements, and sometimes the change only shows after the next core update.
The short version
| Symptom | Likely cause | Where to look |
|---|---|---|
| Drop on a few pages | Technical issue on those pages | URL Inspection live test |
| Spike in indexing errors | Technical issue | Page indexing, Crawl stats |
| Warning in Search Console | Security or spam | Security issues, Manual actions |
| Same dip last year | Seasonality | Performance, 16-month range |
| Broad drop, nothing else wrong | Core update | Wait, then compare full weeks |
Has anyone seen movement yet? I'm curious whether people are seeing site-wide shifts or drops limited to specific page types.
Top comments (0)