How to Move a SaaS Site to a CDN Without Overloading Your Origin or Blocking Googlebot
Google just explained why crawler traffic spikes after a CDN switch. Here is the plan for B2B SaaS sites.
- Desk
- Technical SEO
- Format
- How-to
- Reading time
- 8 min
- Published
- Nov 18, 2026
When you move a SaaS site to a CDN, Googlebot can crawl faster, not slower, because quick edge responses signal a healthy server. The catch is a cold cache: every first request for a URL still hits your origin. Warm the cache, exempt verified crawlers from bot challenges, and use a short 429 or 503 only if needed.
This guide is for B2B SaaS marketers, founders and the engineers who own their site's infrastructure. It covers what Google says happens after a CDN move, how to avoid blocking Googlebot by accident, and what to watch for two weeks afterward. cekpr covers technical SEO for software sites, and CDN moves are one of the changes where a small mistake quietly removes pages from search.
Google's Search Central team published new guidance on this on November 11, 2026. The advice is practical, and it matches how most SaaS sites are built: a marketing site, a docs section, a changelog and thousands of integration pages.
Why Does Googlebot Crawl Harder After You Move a SaaS Site to a CDN?
Googlebot crawls harder after a CDN move because faster, steadier responses raise your crawl capacity limit. Google's systems read quick edge responses as proof that your infrastructure got stronger, so they increase the request rate when there is demand. The same move that protects your origin can briefly add load to it.
Google explains the mechanism in its crawl budget documentation. The crawl capacity limit caps how many connections Googlebot opens and how fast it fetches. It goes down when responses slow or errors appear. It goes up when responses are fast and stable.
The moment your DNS points at a CDN edge, connection times drop. Googlebot sees a dramatic speed gain. It starts asking for more URLs, and it asks for them across your whole inventory, not only your homepage.
Crawl demand still matters. A site with a few hundred pages will not see a flood, because Google has little to fetch. A SaaS site with thousands of docs, glossary, integration and changelog pages has far more room for a spike.
What Does a Cold Cache Do to Your Origin Server?
A cold cache sends every first request for a URL through to your origin server. The CDN has no stored copy yet, so the edge fetches the page, saves it and serves it. Only later requests for that URL are cache hits. Until the cache fills, the origin still does the heavy lifting.
Human visitors and crawlers behave differently here. Visitors cluster around a small set of pages, such as your homepage, pricing page and top articles. Those warm up fast. Crawlers do the opposite. They walk the long tail, and the long tail is where most cache misses happen.
Here is an illustrative example. Say a SaaS site has 40,000 crawlable URLs and Googlebot fetches 10 per second. That is 4,000 seconds, or about 67 minutes, of requests where nearly every one is a miss. If each miss triggers a database query or a server-side render, the origin feels all of it.
Google notes that Googlebot does not jump to a higher rate instantly, and many CDNs smooth out spikes with connection pacing. Treat that as a cushion, not a guarantee. At cekpr, we recommend planning for the miss storm instead of hoping the CDN absorbs it.
Image-heavy sites feel this more. Screenshots and product shots are large files, and each one is another cache miss. Serving modern formats helps, and our post on which image formats a SaaS site should use covers what Google supports.
How Does Blanket Bot Protection Hide Your Site From Google?
Blanket bot protection hides your site from Google when a CDN or firewall challenges every automated request. Googlebot cannot solve a CAPTCHA. It receives an error or challenge page instead of your content, treats the site as restricted or broken, and backs off. Pages can then drop out of search.
This usually happens during the stress of a migration. An admin sees a spike in automated requests in the origin logs and switches on the strictest bot setting in the CDN dashboard. The spike is Googlebot, and the setting now blocks it.
Google's own advice is to allow verified bots in your CDN and firewall settings. Most major CDNs and web application firewalls (WAFs) have a managed rule or toggle for known good bots. You can also confirm that a request really comes from Google by checking Google's published IP ranges and verification steps.
A better option than a global block is a targeted rule. If a specific scraper is the problem, block that user agent or IP range. Use robots.txt for crawlers that respect it. Leave verified search crawlers alone.
Check one thing before launch day: fetch a handful of key URLs as Googlebot with the URL Inspection tool in Search Console. A live test shows whether your new edge setup returns real content or a challenge page.
How Do You Warm a CDN Cache Before Moving All Traffic?
You warm a CDN cache by requesting your most important URLs through the CDN at a controlled pace before you route all traffic to it. Start with the pages that earn revenue and links, then work outward to the pages Googlebot requests most often.
Build the list from data you already have. Three sources work well for a SaaS site:
- Your top landing pages from Search Console and analytics.
- The URLs Googlebot requested most in the last 30 days of server logs.
- Upcoming launch pages, such as a new feature page or a seasonal promotion.
Then run a simple script that requests each URL through the CDN hostname. Keep the pace modest, for example 5 requests per second, so the warm-up itself does not stress the origin. Google also suggests a low-tech version: ask a few colleagues to open two distinct URLs each.
Warm both HTML and the assets those pages call, such as CSS, JavaScript bundles and images. If your marketing site renders client-side, a cached shell with slow API calls will still look slow to Googlebot. Check that your edge cache rules respect your cache-control headers and do not cache personalized app pages by mistake.
Finally, stage the move. Many CDNs let you shift a percentage of traffic or a single subdomain first. Move the docs subdomain, watch the logs for a few days, then move the main site.
When Should You Return a 429 or 503 to Slow Googlebot?
Return a 429 or 503 only when crawl volume is putting critical load on your origin and caches are still warming. Google's guidance says to use these codes for a short window, a few hours or one to two days at most. Longer than that risks pages dropping from the index.
Google's page on how to reduce the crawl rate lists 500, 503 and 429 as the signals Googlebot respects. Configure the response at the CDN rate-limiting layer, scoped to Googlebot traffic, so your human visitors never see an error.
Do not use robots.txt for this. It changes which URLs Googlebot may fetch, not how fast it fetches them. Our walkthrough of how to reduce Google's crawl rate safely on a SaaS site covers the Retry-After header and the order of steps.
Write down when you switched the brake on and when you removed it. Those dates matter later, when someone asks why crawl counts dipped in the report.
What Should You Monitor in the First Two Weeks?
Monitor server response time, the share of Googlebot requests that return 200, and the crawl stats report in Search Console. A healthy migration shows crawl requests rising for a few days, then settling as caches fill and origin load falls back to normal.
Use this short checklist each morning:
- Origin requests per minute from Googlebot, compared with the week before the move.
- Status codes served to verified Googlebot, with any 403, 429 or 5xx flagged.
- Cache hit ratio at the edge, which should climb daily.
- Indexed page counts for your docs, blog and integration sections.
Search visibility reports can also show trouble. If you track AI features, the data in Search Console's generative AI performance report is worth a glance for unexplained dips in the same window.
One honest limit: a clean crawl does not prove rankings are safe. Page speed gains can help users, but Google has not promised ranking changes from a CDN move alone. Judge the result by indexing, crawl health and real traffic.
A Simple CDN Migration Plan for a B2B SaaS Site
A safe CDN migration follows a fixed order: prepare, test, warm, move in stages, then watch. Skipping the order is how sites end up with blocked crawlers or an overloaded origin in the same week. The table below turns the guidance into a schedule.
| Stage | Action | What to check |
|---|---|---|
| Before | Allow verified bots in the CDN and WAF | URL Inspection live test returns real content |
| Before | Build the pre-warm URL list from logs | Top 500 URLs listed by crawl frequency |
| Launch | Move one subdomain, then the rest | Origin load stays inside your limit |
| Week 1 | Brake with 429 or 503 only if needed | Dates of the brake window recorded |
| Week 2 | Compare crawl stats with the pre-move week | Crawl rate settles, indexing holds |
Treat the table as a starting point. A site with a heavy app shell or many regional subdirectories needs more stages. A small site with a static marketing page can combine the first two rows.
The Bottom Line on CDN Moves and Googlebot
A CDN is worth doing for most growing SaaS sites. The risk sits in the transition, not in the technology. Faster responses invite more crawling, a cold cache turns that crawling into origin load, and a blunt firewall rule can turn it into a block.
Your next step is small. Open your CDN's bot settings today and confirm that verified crawlers are exempt. Then pull a list of your most-crawled URLs, so the warm-up plan is ready before the DNS change, not after.
Will moving to a CDN hurt my SaaS site's rankings?
How long does a CDN cache take to warm up?
Should I block bots in my CDN during a migration?
When is a 503 better than a 429 for slowing Googlebot?
Up next · SEO How to Analyze Your SaaS Traffic After Google's November 2026 Core Update 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.