November 2026 Google Core Update: A Small-Business Review Plan
Check the confirmed November core update dates, separate ranking changes from tracking issues, and prioritise a useful small-business content review.

The quick read
Key questions at a glance
When did the November 2026 Google core update start?
Google records the start as November 10, 2026 at 10:06 US/Pacific. Its announcement says the global rollout may take up to two weeks.
Was the November update complete on November 22?
The official incident entry checked for this article on November 22 did not display a completion notice. Check the linked dashboard for the latest status.
Does this update specifically punish every AI-written page?
The public announcement does not establish that claim. Assess the actual usefulness and accuracy of your content rather than assuming every AI-assisted page has the same outcome.
What is confirmed about the November 2026 core update?
Google records the November 2026 core update as starting on November 10 at 10:06 US/Pacific. The announcement says it applies globally across languages and may take up to two weeks. The incident entry checked on November 22 did not show a completion notice. Recheck the live dashboard before making a post-rollout comparison. Google Search Status Dashboard
A ranking chart moves. Someone shares a dramatic prediction. Suddenly a small-business owner is wondering whether every page needs rewriting. Before authorising that work, establish what changed on your own website and what it affected.
Edward Sturm's video about the November update discusses both the announcement and predictions about its likely effects. Predictions about a particular target or severity are not the same as Google's confirmation. This article provides an original Brands Essential review worksheet for owners who need to protect enquiries and make proportionate decisions.
Separate three questions that often get mixed together
Ask whether your website works, whether search visibility changed and whether the business received fewer suitable enquiries. These are connected questions, but they require different evidence.
A broken contact route can reduce enquiries without a ranking decline. A change in the mix of searches can alter an average position. A seasonal business may receive fewer requests even when its important pages remain visible. Begin with a short incident record that states the observation without assuming the cause.
For example: “Accepted website enquiries fell during this period, and we need to establish whether traffic, suitability or delivery changed.” That description leaves room to investigate. “The algorithm destroyed the website” skips several checks and encourages expensive action before the cause is understood.
Check the customer route first
Open the relevant service page on a phone. Find the main action, submit an authorised test where appropriate and confirm that the request reaches the business system. Check the reply process as well. Record the test so it is excluded from commercial reporting.
If the route fails, identify the failure and fix it. A verified form fault should not wait for a ranking rollout to finish. Record when the repair happened so future comparisons do not confuse its effects with other changes.
Also check whether the business changed availability, service areas or offers. A campaign paused because you were fully booked may explain fewer visits. An unannounced change to the phone number can explain lost contact attempts. Gather those operational facts before interpreting a search chart.
Keep a dated change log
List website deployments, page edits, redirects, analytics changes, consent changes and major campaigns. Include who made each change and what they intended to achieve. An update period becomes harder to interpret when nobody can reconstruct what happened locally.
Keep observations and explanations in separate fields. “The pricing page moved to a new address on November 12” is an observation. “That move caused the traffic drop” is a hypothesis until you examine the evidence.
If the business has multiple websites, verify the property and host you are reviewing. A report for the main domain may not represent the Insights subdomain. Use the correct property and consistent filters for the comparison. Our indexing guide explains the importance of inspecting the intended URL in its relevant Search Console property.
Use comparable reporting windows
Google recommends confirming rollout completion and waiting at least a full week afterwards before analysing the impact in Search Console. Its guidance also calls for reviewing affected pages, queries and search types. Google Search Central: core updates
For your own worksheet, record the selected property, dates, country, device and search type. Keep those settings consistent when investigating a particular change. Use comparable business periods where possible, and note holidays or campaigns that make the comparison imperfect.
Avoid treating an incomplete day as a full day's decline. Save the report settings alongside the conclusion. If you later share a screenshot with an adviser, the context should make clear what it includes and excludes.
Build a page-and-query investigation list
Start with the pages that matter commercially. For each, record the customer's task, the relevant query group, clicks, impressions and received business outcomes where you can reconcile them. Keep branded searches separate from broader service questions.
Use the list to describe the pattern. Did one guide change, or did most service pages move together? Are the affected searches actually relevant to your current offer? Did visibility fall for an outdated service you no longer sell? An overall total can hide those differences.
Take a few representative queries and examine the current results as a customer would. Note the page types and questions answered. This is a qualitative inspection, not a substitute for the reporting. Save examples so the team can discuss an actual difference rather than a vague idea of quality.
Review whether the page helps someone finish a decision
Pick one page and state its job. A page about website migration should help a customer understand migration work, responsibilities and potential disruption. A long section about unrelated content planning does not become useful because it contains marketing terminology.
Check whether the opening answers the main question, whether examples fit the topic and whether the steps can be followed. Look for claims without support, outdated instructions, invented credentials and evidence that does not demonstrate what the page says it does.
Google's people-first guidance asks publishers to consider originality, completeness and trust. Use it as a reference for the review, then make your own page-specific decisions. Creating helpful, reliable content
Write a concrete revision brief. “Explain how to map old URLs to their new destinations, identify the owner and add a verification example” is actionable. “Add 1,000 words for SEO” leaves the user's problem unresolved.
Triage pages by business usefulness
Create four possible actions: maintain, improve, consolidate or retire through a reviewed plan. Choose an action from the page's purpose, evidence and relationship to the rest of the website. Keep a record of the reason.
A useful service page with a broken example may need a focused repair. Two articles answering the same question may need one clearer destination. An obsolete page may still receive links or support existing customers, so check those dependencies before removing it.
Avoid applying the same action to every page just because they were produced using the same tool. Assess the actual content. A human-written page can be inaccurate, and an AI-assisted draft can become useful after substantive research and editing.
Worked example: an apparent search problem with two causes
Imagine a fictional business comparing two equal reporting periods. Search visits to a service page are lower, and enquiries are down. Investigation finds that a mobile form stopped accepting requests partway through the second period. It also finds that the page lost impressions for a group of broad informational searches.
Those findings justify two separate actions. Repair and verify the form immediately. Review the search change on its own evidence once the appropriate comparison window is available. Rewriting the entire page before checking the form would not have restored the missing requests.
The example illustrates diagnosis, not a measured Brands Essential case study. Your own records may show a different pattern. The value of the worksheet is that it keeps each claim connected to a source and a decision.
Write an incident note before commissioning changes
Use a short record with the date observed, affected business outcome, relevant pages and supporting evidence. Add the known local changes and the person responsible for each check. Separate confirmed findings from explanations still under investigation.
For example, record “mobile requests failed during an authorised test” as a verified fault. Record “search visibility may have changed for these queries” as a reporting observation. Keep a proposed relationship between those facts in a hypothesis field until the evidence supports it.
This record helps when several people are involved. A developer, marketer and owner may otherwise use the word traffic to mean different things. Agree whether the discussion concerns clicks, sessions, accepted forms or suitable enquiries before assigning work.
At the end of the initial review, list what you know, what you do not know and what check comes next. The note can remain brief. Its value is keeping the investigation coherent while the public conversation around the update becomes noisy.
Examine a migration article as a content-quality example
Imagine a fictional article whose title promises a website migration checklist. The opening defines migration, but the middle shifts into generic advice about social posting and brand consistency. The page is long, yet it leaves the reader unable to prepare for the move.
A useful revision brief would start with the actual task. It could require an inventory of existing pages, a destination mapping process, ownership of technical checks and a plan for testing customer actions. It should identify which instructions depend on the actual platform and need specialist verification.
Add an illustrative worksheet row: old address, intended new address, responsible person and verification status. Explain that a blank destination is an unresolved decision. Include the contact and booking routes in the review because a migration affects more than article addresses.
This example is an editorial assessment, not a claim about what the November update targets. The page deserves improvement because it fails its own promise to the reader. That is a reason the business can evaluate without asserting knowledge of an undisclosed ranking mechanism.
Prioritise repairs without creating another problem
Rank confirmed defects by customer impact and the effort required to resolve them. A broken business action, inaccessible page or incorrect service fact has an immediate practical consequence. A speculative redesign intended to influence rankings requires a different decision and evidence.
Before consolidating or retiring a page, inspect its role. Does it support an existing customer? Does another page link to it as the official answer? Is its information still required somewhere? Plan the replacement route and verification before changing the address.
For a content revision, keep a clear brief and review the full result. Removing a weak section can accidentally remove the only explanation of an important condition. A new paragraph can introduce an unsupported promise. The reviewer should assess the page as a whole and test the important links afterwards.
Record the published version and change date. If later reporting changes, you can discuss what actually happened. Avoid relying on memories of which edits were probably made during the update period.
Prepare a post-change review with honest limits
For each completed change, write what it was intended to improve and the observation that would support that conclusion. A repaired form can be verified through the customer route. A clearer service explanation can be reviewed against recurring enquiry questions. A search effect requires its own appropriate reporting window.
Keep the results distinct. The form working again does not establish a ranking recovery. A rise in clicks does not prove that one paragraph caused it. A lower number of unsuitable requests can still be commercially useful even if total enquiries fall.
If results are inconclusive, document the limitation and the next review point. The responsible response is a bounded investigation, rather than filling the gap with a story about the algorithm. Use the same discipline when the results look positive.
A useful final handover contains the original issue, evidence, actions, verification and remaining uncertainty. That gives the owner a record they can use for maintenance and future decisions. It also makes the work reviewable without requiring them to become a search specialist.
Ask for a page-specific work estimate
Before approving a large content rewrite, ask which pages need work and what each change will accomplish. Separate research, writing, technical implementation and verification. A proposal should identify dependencies such as access to a business expert, current screenshots or confirmation of a service fact.
Request a representative example. A reviewer can show one weak section, explain the missing customer information and prepare a revision brief. That demonstration makes it easier to assess the proposed standard before committing to a site-wide programme. It also helps prevent generic padding from being sold as depth.
Agree the acceptance criteria. A migration checklist should contain the decisions and checks needed for that task. A cost guide should explain its assumptions and scope variables. A service page should make the offer and next step clear. These are editorial and business checks you can review directly, regardless of later search movement.
Include the cost of maintaining changing information. A guide that relies heavily on platform instructions needs a responsible owner. A one-off rewrite with no maintenance plan may recreate the same problem later. The budget discussion should make that responsibility visible.
Keep the reporting promise proportionate. The provider can commit to completing and verifying the agreed work. They can explain how later performance will be reviewed and where attribution is uncertain. Those are concrete deliverables; a guaranteed ranking position is not a result they can control.
Keep the original observation in the handover. If the investigation changes your explanation, record the new evidence and why the conclusion changed. That history helps the owner distinguish a verified repair from a later interpretation of search performance.
Ask for a review you can evaluate
A useful SEO review should show the reporting settings, affected URLs, specific findings, proposed work and what remains uncertain. Ask which recommendations address confirmed defects and which are experiments. Agree how changes will be logged and reviewed.
Be cautious about forecasts presented as certainties. The work can improve the usefulness of the website and its customer journey, but nobody can commit Google's future results to a timetable. Google's own guidance states that improvements do not guarantee a noticeable ranking impact. Core-update guidance
Brands Essential can help assess your website, content and enquiry route with a practical scope. Bring the affected pages, a dated description of the change and your budget. Contact us for a focused website and search review.
Frequently asked questions
Questions, answered
When did the November 2026 Google core update start?
Google records the start as November 10, 2026 at 10:06 US/Pacific. Its announcement says the global rollout may take up to two weeks.
Was the November update complete on November 22?
The official incident entry checked for this article on November 22 did not display a completion notice. Check the linked dashboard for the latest status.
Does this update specifically punish every AI-written page?
The public announcement does not establish that claim. Assess the actual usefulness and accuracy of your content rather than assuming every AI-assisted page has the same outcome.
When should I analyse a possible core-update impact?
Google recommends confirming completion and waiting at least a full week afterwards before analysing the comparison in Search Console.
Should I stop fixing a broken contact form during a core update?
No. Record and fix a verified business or technical fault. Keep it distinct from speculative changes intended to respond to ranking movement.
Can an SEO agency guarantee recovery?
No. A responsible review can identify evidence, prioritise improvements and monitor outcomes, but it cannot promise a particular ranking or recovery date.
Build a website around your customers and budget.
Tell Brands Essential what you need, what is already working and the budget you can sustain. Agree a useful first phase and the responsibilities before adding more.



