Back to the homepage
SEO

How to Respond to Google's November 2026 Core Update on a B2B SaaS Site

A practical plan for B2B SaaS teams: when to check Search Console, how to segment a drop by page type, and which pages deserve a rewrite.

Molly Ashcroft · Content Strategy Editor
Start reading ↓
Desk
SEO
Format
How-to
Reading time
7 min
Published
Nov 17, 2026

Wait until Google finishes rolling out the November 2026 core update, then wait one more full week. Compare that week with the week before November 10 in Search Console, split by page type. Change nothing on pages that moved a few positions. Act only on large, sustained drops, and fix helpfulness instead of chasing tricks.

This guide is for B2B SaaS marketers and founders who run their own SEO. It covers what Google has said, when to pull your data, how to read a drop by page type, and what to change. cekpr covers SEO and AI search for software companies, so the focus is on product, comparison and integration pages rather than generic advice.

What did Google say about the November 2026 core update?

Google said the update applies globally, in all languages, and may take up to two weeks. It called the release a regular update meant to surface relevant, satisfying content. As of the announcement, Google named no specific target and had published no blog post explaining the changes.

macbook, manzana, job, mac

The rollout began on November 10 at 10:06 a.m. Pacific time, according to Search Engine Journal's report on the Search Status Dashboard. It is the third core update of 2026 and the eighth ranking update on the dashboard this year. The March update ran about 12 days, and the May update ran almost 12 days.

Google's own documentation says core updates are broad and do not target specific sites or pages. That matters for SaaS teams. A drop on your pricing page does not mean Google penalized pricing pages. It means other pages now fit the query better for that period.

When should a SaaS team check Search Console after the rollout?

Check after the rollout ends and a full week has passed. Google's guidance is to compare that week with the week before the update began. For this update, the baseline week is the one before November 10. Earlier checks mix real changes with rollout noise.

Noise is real this time. Search Engine Roundtable reported that rank tracking tools showed more volatility on November 14. It also noted that some tools are partly blocked and that Search Console reporting has lagged. If you rely on a third-party tracker, read our guide to how to verify rank tracker data before you trust a chart.

A full two-week rollout would finish around November 24. The comparison week then lands on U.S. Thanksgiving, Black Friday and Cyber Monday. Holiday weeks change how people search for software. A plain week-over-week comparison can show a decline that has nothing to do with the update. Add the same week from last year as a second reference.

Use this schedule for the next three weeks:

  1. Now through the end of the rollout: freeze large template, navigation and URL changes.
  2. Today: export a baseline for the week of November 3 to 9, by page and by query.
  3. When the dashboard shows the update is complete: write down the end date.
  4. Seven days after that: export the comparison week with the same filters.
  5. The next day: sort pages by change in clicks and average position, then segment.

How should you read a core update drop by page type?

Start with Google's own thresholds. A small drop in position, such as from 2 to 4, does not call for drastic action. Google even advises against editing content that is already performing well. A large drop, such as from 4 to 29, deserves a deeper review.

magnifying, glass, detective, lens

Then split the data. Google's documentation recommends analyzing different search types separately, because web search, images, video and news can move in different directions. For SaaS, add a second split by page type. The table below shows what to ask of each group.

Here is a worked example. Say a comparison page averaged position 3 in the baseline week and averages position 4 in the comparison week. That is a small drop, and Google's advice is to leave it alone. Say a feature page fell from position 4 to position 29 over the same dates. That page needs a close look, because very few people click past the first page.

How should you read a core update drop by page type?
Page typeWhat to compareQuestion to ask
Product and feature pagesNon-branded clicks, positionDoes the page answer the buyer's task?
Comparison and alternatives pagesPosition on 'vs' queriesIs the page fair, current and specific?
Integration pagesImpressions by queryDoes each page add real setup detail?
Blog guidesClicks by topic clusterDoes a better page now exist elsewhere?
Pricing and docsBranded clicksDid people just stop searching your name?

Branded traffic needs its own view. On November 16, Google added a branded queries option to the Search Analytics API. The Search Central announcement says you can group or filter by branded classification. Branded clicks follow demand for your name, not core update quality signals. Strip them out before you judge the update.

If the drop is large and sitewide, use our checklist on how to diagnose a SaaS organic traffic drop. It separates update effects from tracking breaks, seasonality and technical faults.

What should you change after a large drop?

Review the whole site first, then the most affected pages. Google's self-assessment asks whether content is helpful, reliable and written for people first. Ask someone unaffiliated with your company to score it. Founders are poor judges of their own feature pages.

digital marketing, content strategy, content planning, digital marketer

For each hit page, find the pages that now outrank it. Look at what they do better. Often it is plain: a clearer answer, a real screenshot, a current price, or a fair account of who the product is wrong for. Comparison pages are a common weak spot, and our guide on how to update SaaS comparison pages covers the rewrite.

Google's guidance also warns against quick fixes. Do not remove a page element because someone online said it hurts SEO. Make changes that serve readers and will still make sense in a year. Rewriting or restructuring a page so it is easier to follow is a better bet than swapping headings.

When is deleting pages the right response?

Deleting is the last resort. Google says to consider it only when content cannot be salvaged. It adds that wanting to delete whole sections is a sign they were built for search engines first. In that case, removing them can help the rest of the site.

blog, seo, internet, web

If you do remove thin pages, handle the old URLs properly. Our walkthrough on how to handle 404 errors on a SaaS site explains when to return a 404, when to redirect and when to keep a page.

Keep a change log while you work. Write one line per edit, with the date, the URL and the reason. At cekpr, we treat any ranking move that appears before the rollout ends as noise until the log and the data agree. A log also stops you from crediting a rewrite for a gain that arrived on its own.

What does the early chatter tell you about this update?

Very little. Search Engine Roundtable collected reports from forums and social posts that ran in both directions. Some site owners saw traffic gains, others saw drops above 20 percent, and several saw odd click and impression jumps in Search Console. Most of the talk started on the weekend after the announcement, which suggests the changes reached results a few days after the rollout began.

Treat these reports as anecdotes. Owners post when something changes, and many shared charts that predated the update. Your own baseline, built from your own pages, is the only comparison that counts. Read the chatter for ideas about what to check, not for a verdict on what Google rewarded.

How long does recovery take after a core update?

Recovery can take days or several months. Google says its systems need time to confirm that a site now produces helpful, reliable content over the long term. If months pass with no change, you may need to wait for the next announced core update.

The calendar shows why patience matters. The May update finished on June 2, more than five months before this one started. Google also runs smaller, unannounced core updates, so improvements can show up between big releases. No change guarantees a result, and positions are never fixed in place.

What is the practical plan for the next three weeks?

Use these rules to decide whether to act or wait:

  • Act when non-branded clicks fall sharply across a whole topic cluster and the drop holds for the full comparison week.
  • Wait when the move is a few positions, or when only branded queries fell.
  • Wait when the gap lines up with a holiday week or a site change from your own log.

Treat this update as a measurement project first and a content project second. Freeze risky changes, capture the baseline, wait for the rollout and the extra week, and segment before you act. Fix only the pages where the drop is large and the cause is clear. Leave the rest alone and keep writing useful pages.

How long does the November 2026 core update take to roll out?
Google said the rollout may take up to two weeks from its November 10 start, so it should finish around November 24. Earlier core updates this year took about 12 days. Check the Search Status Dashboard for the official completion date before you start comparing Search Console data.
Should a SaaS company change its content during a core update rollout?
Avoid large changes while the rollout runs. Edits made mid-rollout make it hard to tell whether the update or your own work moved a page. Fix clear errors, such as wrong prices or broken links, and log each edit. Save broader rewrites for after you have clean comparison data.
What is a normal ranking drop after a core update?
Google treats a small drop, such as from position 2 to 4, as normal movement that needs no drastic action. A fall from position 4 to 29 is large and deserves a deeper review. Judge changes over a full week against a baseline, not by one day of data.
Can I recover from a core update without waiting for the next one?
Sometimes. Google says some improvements can take effect in days, while its systems may need months to confirm that a site is consistently helpful. Smaller unannounced core updates also run between big releases. If months pass with no change, the next announced update may be the next chance.

Written by

Molly Ashcroft

Molly writes about planning, briefing and editing B2B content that holds up under scrutiny. She focuses on the review steps that keep fast content programs accurate.

More from Molly
Up next · Measurement How to Read Search Console's Generative AI Performance Report for SaaS
The Thursday letter · free

join the club.

The week's best SEO and AI search posts, plus one thing to check in your own Search Console, every Thursday morning. Unsubscribe whenever.