What should UK businesses do now? Check that customers can still find and contact you, separate ranking changes from falling click-through or demand, and fix genuine technical faults. Monitor the November core update without rebuilding your site in response to daily fluctuations. A drop in clicks is a symptom to investigate, not a diagnosis.
For a local trades business, a lost quote request matters more than a movement on an informational keyword. For a retailer, seasonal shopping behaviour can complicate the comparison. Start with the customer journey, then work backwards through the evidence.
November 2026 core update: status checked 22 November
Google's official entry records a start on 10 November 2026 at 10:06 US/Pacific, affecting Search globally across all languages. It says the rollout may take up to two weeks. Completion was not confirmed in that entry when checked on 22 November 2026. Do not turn the estimate into an assumed end date. 1
Core updates are broad changes, not updates targeted at a particular business or page. A ranking loss does not, by itself, establish that your site has been penalised. Google's assessment guidance is to confirm completion, wait at least a full week, then compare performance against a pre-update week. Small position movements do not call for drastic changes. 2
The workflow below is practical judgement based on Google's wider guidance, not a claim about special November ranking targets.
Identify which problem you actually have
Several problems can happen together. Google recommends investigating technical issues, security or spam problems, migrations, seasonal demand and data anomalies alongside algorithmic changes. 3
Positions fall for established queries and pages
Ranking visibility may have changed. Compare the same query and page groups over comparable periods, rather than relying on the sitewide average.
Impressions remain similar but clicks fall
Investigate lower click-through or a different mix of searches. Examine query-level CTR and relevant search results before deciding what to change.
Search visibility drops alongside indexing or availability problems
A technical fault may be involved. Inspect affected URLs, indexing reports and recent releases to identify whether pages became inaccessible or ineligible.
Positions look steady but relevant impressions fall
Demand may have changed. Compare seasonal history and relevant search interest, keeping promotions and moving shopping dates in context.
Search traffic looks steady but enquiries fall
The conversion journey or its measurement may be broken. Test forms, calls, checkout and tracking before commissioning a ranking recovery campaign.
These are starting points, not proof. An average position can stay similar while individual commercial queries decline and unrelated queries improve. Stable impressions with fewer clicks can reflect titles, snippets or richer competing results; it does not automatically establish that AI answers caused the loss. 3

Conceptual editorial illustration of four diagnostic checks. This is not Search Console data or a chart of the update's effects.
Protect real enquiries before chasing rankings
Make a test enquiry from a mobile phone. Does the form submit, show a confirmation and reach the correct inbox? Does the telephone link dial the right number? Can a shopper complete the important checkout steps? Check the privacy and consent journey too, rather than bypassing it to make tracking look healthier.
Compare Search Console clicks with analytics landing-page sessions and actual enquiries or orders. They measure different things and need not match exactly. If a tracking change coincides with the apparent loss, establish whether measurement changed before concluding that customers disappeared.
Keep a simple working record: affected landing pages, relevant query groups, genuine enquiries, faults found and changes made. Separate branded searches from searches for your services. A branded visit from someone who already knows you answers a different question from discovery by a new customer.
This is also a useful brief for SEO support in Manchester: identify the commercial pages at risk and what evidence would justify action.
A sensible Search Console workflow
1. Preserve a baseline and choose fair periods
Open the Performance report for Search results. Start with Web search, select the UK if that is your market, and compare equal-length periods with the same weekdays. Keep a pre-update baseline and annotate launches, outages, redirects or tracking changes.
During rollout, use the comparison to spot issues rather than declare a final update impact. After Google confirms completion, follow its advice to wait at least a full week before comparing with a pre-update week. 2
Use the longer view too. Google's traffic-drop guidance recommends looking at up to 16 months of data to understand patterns and compare relevant periods. A year-on-year view can help with seasonality, but moving promotions and shopping dates still need context. 3
2. Find the affected page groups
Check whether the change is sitewide or concentrated in service pages, product categories, articles or a recently altered section. Then narrow it by country and device. Inspect other search types separately where relevant; a Web report is not the whole picture. These filters are part of Google's recommended diagnostic approach. 3
Export the affected rows so you can revisit the same group. Avoid judging the whole business by its largest traffic-generating article if that article rarely leads to an enquiry.
3. Compare queries within those pages
Review clicks, impressions, average position and CTR together. Look for changes on searches that match what the page sells or explains. Split branded and non-branded queries, then inspect the phrases with clear buying or booking intent.
For lower CTR, review whether the title accurately describes the page and gives the searcher a reason to visit. Inspect relevant results for context, but treat a manual search as a snapshot, not a reliable sitewide ranking report. Do not add exaggerated promises or irrelevant keywords to win a click.
4. Rule out faults before commissioning rewrites
Use URL Inspection and indexing reports for representative affected pages. Check whether they are accessible, indexable and associated with the intended canonical URL. Review recent changes to redirects, robots directives, templates and navigation. Check security issues and manual actions separately. Google lists these kinds of problems among potential traffic-drop causes. 3
A blocked service page needs a technical fix, not more paragraphs. If the evidence points here, prioritise technical SEO checks.
Two hypothetical examples: different causes, different responses
Hypothetical trades example: A plumbing business sees fewer organic enquiries during rollout. Its repair-page queries appear broadly steady, but a mobile form fails after a website change. The first action is to repair and test the form, then check enquiry delivery. Rewriting every service page would leave the immediate problem unresolved. This illustrates a diagnosis, not a client result.
Hypothetical retailer example: An independent homeware shop sees fewer clicks to a category page. Some query positions have slipped, while other searches remain visible but attract fewer clicks. The owner separates those groups, checks stock and landing-page relevance, and compares the promotion calendar with the previous period. Late-November retail comparisons can be affected by holiday demand, as independent reporting on the launch notes. 6
The shop should not attribute every change to the core update or to AI. A ranking review, a click-through review and a demand review may each produce a different action. Neither example implies a measured performance outcome.
What to change during rollout, and what to leave alone
Fix clear failures now: inaccessible pages, accidental indexing blocks, broken contact routes and materially incorrect service information. Save a record of each fix so later comparisons have context.
For unsettled rankings, keep monitoring and prepare a page review rather than replacing everything. Avoid changing titles, copy, URLs and navigation together; doing so makes it harder to understand what helped or harmed the site.
Once a substantial, sustained ranking loss is established, assess affected pages against genuinely useful alternatives. Google advises against quick fixes and treats content deletion as a last resort. Improvements may take days to months to have an effect, with no guaranteed recovery. 2 Our guide to how long SEO takes provides broader planning context, not a November recovery deadline.
Strengthen service pages without spamming locations
Read a priority service page as a customer deciding whether to enquire. Can they tell what you do, what is excluded, where you actually work and what happens after contact? Explain relevant practical details: preparation, access requirements, suitability, limitations and the information needed for an initial assessment.
Use original photographs where appropriate and describe what they show. Add accurate authorship or business responsibility, and evidence you can substantiate. Do not invent credentials, reviews or project stories. Google's helpful-content guidance stresses original usefulness, accurate sourcing and satisfying the reader's task. It does not prescribe an arbitrary word count or reward a fresh date without a substantive change. 5
For locations, start with honest coverage information. Create a separate page only when you can offer meaningful local detail or a distinct service proposition. Copying one page and swapping town names gives a customer little additional help. This is our practical recommendation, not an announced November rule. Local SEO should help people assess whether you can serve them, rather than inflate the page count.
When assessing an agency's approach, look for a clearly explained problem and documented work in its case studies, rather than accepting a recovery promise.

Conceptual editorial illustration of service-page improvements. It does not depict a client website or measured ranking results.
Where Google AI search fits, and where it does not
Google says traditional SEO remains relevant to its AI features. Supporting links require pages to be indexed and eligible to appear with a snippet. There is no special AI schema or new machine-readable file requirement, and inclusion is not guaranteed. llms.txt is not a Google ranking requirement. 4
Keep important information in accessible text, use crawlable internal links and quality images, and ensure structured data matches visible content. Keep business information current. These are shared foundations, not a separate November recovery trick. Google's documentation distinguishes Googlebot controls for Search from Google-Extended controls for other training and grounding uses. 4
Google AI-feature activity is included within Web performance reporting, so a combined Search Console trend cannot tell you exactly how many clicks came from AI features. 4 Our article on AI and search traffic explores the wider concern. The Google AI SEO guide and our AI SEO service cover visibility work without treating Google's requirements as identical to every other AI platform's.
Your priorities, in order
- Repair faults that prevent access, enquiries or purchases.
- Verify measurement and preserve a comparable baseline.
- Separate ranking, CTR and demand changes by commercial page and query group.
- Confirm rollout completion, then allow Google's recommended assessment interval.
- Improve genuinely weak pages with useful, accurate information and review sustained outcomes.
Frequently asked questions
Has the Google November 2026 core update finished?
- Completion was not confirmed in Google's official status entry when checked on 22 November 2026. The entry says the rollout may take up to two weeks, but that is an estimate, not a confirmed end date.
Should I change my website while the update is rolling out?
- Fix genuine technical faults and broken enquiry journeys immediately. Record ranking changes, but avoid wholesale rewrites based on a few unsettled days. Google recommends waiting at least a full week after confirmed completion before assessing the impact.
Does a fall in clicks mean the core update affected my rankings?
- No. Lower clicks can also reflect reduced demand, lower click-through, technical problems or changes to the searches your site appears for. Compare impressions, positions, queries and landing pages before deciding that a ranking change is the cause.
Do I need special schema or llms.txt for Google AI search?
- Google says its AI search features do not require special schema or a new machine-readable file. llms.txt is not a Google ranking requirement. Focus on accessible, indexed pages that are eligible for snippets and useful to readers.
Should I create a service page for every nearby town?
- Only create a separate location page when it offers genuinely useful information for customers there. Explain your actual coverage and service details. Repeating the same page with different town names does not solve a core-update diagnosis.
How quickly can a business recover after a core update?
- There is no fixed recovery timetable or guarantee. Google says improvements can take days to several months to have an effect. Judge progress through sustained visibility and genuine enquiries, rather than expecting a particular change to restore yesterday's rankings.
Get a clearer diagnosis
If the evidence is mixed, request a free SEO audit. Share your website, when the change began and which enquiries or pages concern you. That gives the review a business question to answer, rather than a daily ranking movement to chase.
References
Status and supporting sources checked for this article on 22 November 2026.
- Google Search Status Dashboard: November 2026 core update
- Google Search Central: core updates and your website
- Google Search Central: debugging drops in Google Search traffic
- Google Search Central: AI features and your website
- Google Search Central: creating helpful, reliable, people-first content
- Search Engine Journal: Google November 2026 core update reporting