Google’s November 2026 core update began on November 10 and is still rolling out as of November 17. If your search visibility has moved this week, record what changed, but don’t rewrite a winning page on the strength of a few days’ data. Google says the rollout may take up to two weeks; that is an estimate, not a promised finish date. Check the Google Search Status Dashboard for the actual end date.
Two other events landed alongside the update: a change to Google’s AI answers and a reporting error in one Search Console report. They are separate events, and separating them is the first step toward a useful diagnosis.

What changed in Google Search?
The November core update is a broad change to Google’s ranking systems. Google says it applies globally and in all languages. Core updates do not target a particular site or page as a penalty: Google reassesses which results best answer a searcher’s question. A page can move down because another result becomes more useful, even if nothing is technically broken on yours. Google announced the rollout on November 10 and explains how to assess its effects in its core update guidance.
That does not mean every change you see was caused by this update. Seasonal demand, a different mix of searches, changes to the search results page, and ordinary site problems can move clicks or impressions too. A ranking tracker is useful for spotting a pattern, but Search Console’s page-and-query data is where you check whether that pattern affected your own site.
Did Gemini 4 Hydrogen cause the ranking changes?
There is no public evidence that the new Gemini model changed ordinary organic rankings. On November 12, Google announced Gemini 4 Hydrogen in Search, describing better handling of complex questions, more visual responses and links to a wider range of sites. Google has also identified AI Mode and difficult AI Overview questions as uses for the model. The timing overlaps with the core update, but timing alone cannot tell us which change produced a particular rise or fall.
If your concern is being cited in AI answers, look at whether your pages provide an answer worth linking to: a specific explanation, a first-hand example or a useful distinction that another page leaves out. Our guide to making a page useful to AI search covers what is supported by evidence and what is guesswork. None of this requires inventing an “AI version” of every page.
Why do some Search Console impressions look wrong?
Google confirmed a logging error in the Generative AI performance report in Search for November 9–11. It caused reported impressions to fall on those dates, but Google says the issue affected data logging only. It did not cause an actual loss of visibility. Do not use those three days of that report to calculate the core update’s impact.
This is a specific report and a specific metric. It is not a reason to discard all Search Console data from that week. If your ordinary Web Search clicks or rankings changed, investigate them on their own terms rather than attributing them to the Generative AI logging error.

How should you check whether your site was affected?
Start with the update’s confirmed end date, then compare like with like. Google recommends waiting at least one full week after a core update completes before analyzing Search Console. Compare a complete week after the rollout with a comparable week before it began; for a noisy business, look at more than one complete week. Keep day-of-week and holiday demand in mind. Thanksgiving and Black Friday can change what people search for even if your rankings hold steady.
- Separate search types and appearances. Check Web Search independently from Images and other search types. If you report organic positions, separate merchant listings from ordinary organic results; a shopping appearance is not a blue-link ranking.
- Split branded from non-branded searches. An increase in people searching your company name can hide a decline in service-related terms, or the reverse.
- Look at pages and the queries that lead to them. Did a cluster of service pages move, or one article? For the same important queries, count how many are in positions 1–3, 4–10, 11–20, 21–50 and 51+, rather than relying on one site-wide average.
- Check whether the searches matter commercially. A high-impression query is not automatically a lead opportunity. Review clicks, realistic search demand and the actual search results before assigning it priority.
- Rule out other causes. Confirm important pages are accessible and indexed, and check whether you changed templates, redirects or canonical tags around the same time. A real technical issue needs fixing now, even during a rollout.
For example, if a service page falls from position 4 to 29 across several relevant non-branded queries and stays there after the rollout, it warrants a closer review. If one keyword shifts from position 2 to 4 for a day, Google specifically advises against drastic changes to a page that already performs well. The threshold is not a magic formula; the point is to distinguish a sustained loss from routine movement.
What should you change if rankings stay down?
Fix clear faults immediately; otherwise, investigate before editing. Google cautions against “quick fix” changes made just because someone claims a particular page element is bad for SEO. Read the pages that gained ground on your important searches. Do they answer a question earlier, explain the work more clearly, show a better comparison or make their information easier to check? Then improve your page where it genuinely falls short.
Search Console’s “Crawled – currently not indexed” status is worth investigating for important pages, but it is not proof that this core update rejected them. It can reflect quality concerns or a technical problem. Google’s John Mueller described both possibilities when discussing sites with many excluded pages. Check the affected URL, its canonical, its internal links and what the page adds before assuming that writing more copy will solve it. For service or location pages, useful details might include the actual scope of work, an example of how you handle a common problem, and pricing information if you can substantiate it. Do not manufacture testimonials or copy the same city paragraph dozens of times.
Improvement does not come with a guaranteed recovery date. Google says some effects may appear in days, while others can take months as its systems reassess the site. Deleting pages indiscriminately is a last resort, not a core-update treatment.
What should you do this week?
Save a dated baseline of your important pages, non-branded queries and current positions. Note any site changes already in flight. Check the Search Status Dashboard for completion, and leave the affected Generative AI impressions out of comparisons for November 9–11. Once a full post-rollout week has passed, compare the same query-and-page groups against the pre-update period. That gives you a defensible starting point, even if the holiday shopping period makes the final interpretation less tidy.
If you want a second set of eyes on those changes, Web Moves’ SEO and AI Search service can help separate a ranking loss from reporting noise or shifting demand. Contact Web Moves with the pages and queries you’re concerned about.