Google has started the November 2026 core update. The useful response today is to preserve your evidence, check that your site works, and set a sensible review window before deciding what to rewrite.
Google's Search Status Dashboard announcement records the start as November 10, 2026, at 10:06 a.m. US/Pacific. Google says the update applies worldwide, across all languages, and may need as long as two weeks to roll out. At the time of writing on November 11, the dashboard lists the update as active.
Those are the confirmed facts. The announcement does not establish that a particular page, content format, or AI-search strategy will win or lose. Treat early observations as information to investigate rather than a finished assessment of the update.
When should you assess the impact?
Google's core-update guidance recommends confirming completion, then allowing at least a full week before analyzing Search Console performance. Compare that later week with a week before the rollout began. Google also recommends inspecting individual pages and queries and separating search types when investigating a decline.
A possible two-week rollout is not a guaranteed completion date. Check the dashboard for the actual end before setting your final comparison window.
The workflow below is my recommended way to organize the work during that period. It is not a list of new ranking factors announced by Google.
1. Save a baseline you can actually reproduce
Export the search performance of your priority pages and their important queries for a complete period before November 10. Keep the reporting dates, country, device, and search type with the export.
Choose pages because they serve an important customer need: a product explanation, a useful comparison, a pricing question, or a service enquiry. Include both branded and non-branded queries, so a shift in one group does not obscure the other.
Add a short change log. A new landing page, revised navigation, a paid campaign, or an analytics change can affect the numbers you later compare. Recording them now gives the team better explanations to test when performance moves.
2. Check for concrete faults while the update runs
Waiting to judge the rollout does not mean leaving a broken customer journey untouched. Check whether your important pages load, whether their intended indexing settings remain correct, and whether the next action works on a phone.
For example, if a recent release accidentally removed a contact link or introduced an unwanted redirect, the repair has a clear purpose independent of the update. Record what you found and when you fixed it.
This is also a useful distinction in team communication. “The quote form fails on mobile” is a reproducible defect. “Google dislikes our new service page” is a hypothesis that needs evidence.
AI already decides how your brand shows up.
Every prompt, citation, and recommendation is a signal. igeo.ai turns that behavior into clear answers and the next action, whether that’s a page to rewrite, a schema to add, or a story to publish.
3. Review the buyer decision before rewriting the page
For each priority page, write down the decision it should help a visitor make. Then read the page against that task.
Does a buyer understand who the offering suits, what it includes, what its limits are, and how to continue? Can they find the evidence supporting an important claim? Are examples, prices, and product details still accurate?
These questions produce specific editorial work. An outdated product description needs a factual correction. An unclear comparison needs clearer criteria. Neither requires guessing which paragraph caused a ranking change.
Keep a record of substantial edits. If you change several important pages during the rollout, you will want to know which version was live when an observation was made.
4. Keep your AI-search question set steady
SEO performance and visibility in generated answers answer different questions. For GEO and AEO work, preserve the buyer questions you were already monitoring, along with the engines, markets, and dates of observation.
Suppose your important question is “Which platform helps an agency monitor AI brand visibility?” Check it under consistent conditions and inspect the actual answer. Record whether your brand appears, what the answer says, and which sources it cites. Avoid replacing the question with an easier one simply because this week's result looks worse.
igeo.ai monitoring supports reviewing prompts, mentions, competitors, and sources across monitored AI answers. Use those observations to identify questions worth investigating. A change in an answer does not, by itself, show that Google's core update caused it, especially when the observation comes from another provider.
5. Track the pages behind the answers
When a priority page changes, save its URL and the purpose of the edit. Review its search performance alongside any observed citation activity, keeping those records separate.
AI Search Console starts with a published URL and follows observed crawling and citations. It helps a team investigate whether content appears as a source in the answers its account monitors. A crawl records access; it does not guarantee a citation, ranking improvement, or sale.
For a deeper measurement workflow, use our AI search visibility guide. Keep your prompt observations, page evidence, and qualified business outcomes available for the same review.
6. Put a decision on the review calendar
Once Google confirms completion and the review window is available, compare your saved baseline with the later period. Look for patterns at the page and query level, then investigate the largest meaningful changes.
Consider what else changed between those periods: promotions, seasonality, publishing volume, or a different mix of visitors. For retailers, late November trading can make a simple week-to-week comparison particularly difficult to interpret. State those limitations when reporting the result.
Leave the review with a short action list: the page, the customer problem, the evidence, the proposed improvement, and the next check. That is more useful than a site-wide rewrite based on one unsettled day.
What to do today
Save the pre-update baseline, verify your highest-value customer journey, and keep your existing AI-search monitoring consistent. Use the confirmed rollout timeline to plan the assessment, and use page-level evidence to decide what deserves attention.
Book a demo of igeo.ai to explore how buyer-question monitoring and URL-level citation tracking can support your SEO, GEO, and AEO review.
