Moving your site to a CDN without blocking Googlebot: what to check
Google published its guide on November 11, 2026 for moving to a CDN without overloading your server or blocking Googlebot. Here are the 3 key steps.
You move your site to a CDN on a Friday afternoon so it loads faster. On Monday, your old server is at its limit and, even worse, Google can no longer reach half of your pages. Nothing looks broken to your customers, but your organic traffic starts to drop.
Google has just published exactly the warning that prevents this scare.
What did Google say about moving a site to a CDN?
That right after the change, crawling toward your origin server often spikes. In its Search Central blog post of November 11, 2026, Google explains that its crawl capacity goes up when response times go down. Because a CDN responds faster, crawlers pick up the pace.
This applies to Cloudflare and to any other CDN. If your site already lives on Cloudflare, first review how the orange cloud and the proxy work.

Why does the server struggle if the CDN is supposed to help?
Because a new CDN starts with an empty cache. According to Google, the first request for each URL is a cache miss that travels all the way to your server, and only the following ones are served from the edge.
Your visitors concentrate on a few popular pages, which warm up quickly. Crawlers, on the other hand, explore the whole URL inventory, so many requests the cache does not know yet reach the origin.
| Who visits | What it requests | Effect with an empty cache |
|---|---|---|
| Visitors | A few popular pages | The cache warms up quickly |
| Crawlers | The whole URL inventory | Many requests reach the origin |
Can my bot protection block Googlebot?
Yes, and it is the most serious risk. Google warns that broad CAPTCHA or firewall rules treat Googlebot like any other bot. Crawlers can get stuck on challenge or error pages, and that can lead to your pages dropping out of Google.
Common mistake: turning on an aggressive anti-bot mode on migration day and never checking again. If Googlebot gets a 403 or a challenge instead of your page, you see nothing odd from your browser, but Google does.
If you already use security rules, review how to set up the WAF and Bot Fight Mode on the free plan and confirm that your own rules do not clash.
What steps does Google recommend before migrating?
Three: allow verified bots, pre-warm the cache and, if needed, slow things down temporarily. This is how Google's post sums them up:
- Allow verified bots. If you block bots, use the verified bots option or the managed rules of your CDN or WAF. Google asks you to verify its crawlers with the IP ranges it publishes. For bots you do not want, use robots.txt or targeted rules instead of blocking every automated client. In which AI bots to allow or block in robots.txt you will find the details of that file.
- Pre-warm the cache. Before sending all traffic through the CDN, request your most visited pages, your upcoming promotion or launch pages and your most crawled pages, at a controlled pace.
- Slow things down temporarily if needed. If crawling keeps straining your server, respond with 429 (too many requests) or 503 (service unavailable) for a short window: a few hours and, at most, one or two days.

How do I know if there is already a problem after the change?
Watch two signals in the following days: your server health and the status of your pages in Google. The same post recommends monitoring origin performance and crawl activity to catch overload in time.
For the second one, open Search Console and check whether new pages with problems show up. If something changes, this guide explains what each status of non-indexed pages means. And if the migration is from WordPress to a static site, first follow this checklist to avoid losing SEO.
Does this affect me if my site is small?
It affects you less if your site has few pages, but the rule of not blocking Googlebot applies to everyone. A small site rarely overloads a server, although any protection turned on in a hurry can leave it out of Google. If your goal is to sell more, it is worth adding your site speed and Core Web Vitals, which is precisely why many people move to a CDN.
In short
The Friday of the migration does not have to end in a Monday of falling traffic. Allow verified bots, pre-warm the cache and keep the 429 or 503 as a short emergency brake. If you want someone to do it with you, check out our hosting and domains service.
Frequently asked questions
Why does Google crawling go up when I move my site to a CDN?
According to Google, its crawl capacity limit goes up when response times go down, so crawlers speed up right after the change.
What does it mean to pre-warm a CDN cache?
It means requesting your most visited pages, your upcoming promotion pages and your most crawled pages through the CDN, at a controlled pace, before sending it all your traffic.
Can my bot protection block Googlebot?
Yes. Google warns that broad CAPTCHA or WAF rules can leave crawlers stuck on challenge or error pages, and that pages can drop out of Google.
How long can I slow down crawling with a 429 or a 503?
Google recommends doing it only for a short window: a few hours and, at most, one or two days.
How do I allow verified bots without opening the door to all of them?
Use the verified bots option or the managed rules of your CDN or WAF, and block the bots you do not want one by one instead of blocking them all.
Do not stop at the theory: apply it to your business
We implement hosting and domains end to end, with your real operation. The first conversation is free.




