A slow site or a security scare often ends with the same suggestion from a developer: put the site behind a content delivery network. A CDN stores copies of a site on servers around the world, so pages load faster and the firm’s own server carries less traffic.
On November 11, Google’s Search Central blog warned that the switch itself can cause trouble, including bot protection that quietly locks Google out. For a law firm website CDN move, the real risk is not the technology. It is the practice area pages, attorney bios and blog posts that bring in clients dropping out of Google while the move settles.
The fix starts with knowing which pages those are.
A law firm website CDN move can put a firm’s best pages at risk if bot protection blocks Google’s crawlers, which Google says can make pages drop out of Search.
Before the switch, list the pages that bring in clients, make sure verified crawlers are allowed, and warm the cache with those pages first. Then check that Google can still reach them.
What Google Says Can Go Wrong
Google’s post covers two problems. The first is server load. Google says “a brand-new CDN starts with an empty (cold) cache,” so the first request for every page still goes back to the firm’s own server, and fast CDN responses can make Google’s crawlers speed up at the same time.
The second problem is the one that costs pages. Seeing a surge of automated requests, admins may turn on blanket bot protection. Google says its crawlers fail CAPTCHA challenges, get stuck on an error page, and back off. If the block stays, pages begin to drop out of Search.
Step One: List the Pages That Bring In Clients
Before the developer touches a setting, the firm should know which pages it cannot afford to lose. This inventory is practical advice, not Google’s:
- Practice area pages for every case type the firm wants more of
- Location or office pages for each area the firm serves
- Attorney bio pages for each lawyer at the firm
- Blog posts and FAQ pages that bring in steady visits or inquiries
- The home page and contact page
Analytics and Search Console show which of these draw Google visitors. That list becomes the checklist for the move, and it often shows which pages are thin, outdated or missing before the switch even starts.
Step Two: Hand the Developer Google’s Game Plan
Google’s post gives a short plan for the move itself:
- Allow verified bots. Most major CDNs and firewalls offer a toggle or managed rule that lets known, verified crawlers past CAPTCHA challenges.
- Block specific bots, not all bots. Target unwanted bots with robots.txt or specific rules instead of blocking every automated client.
- Pre-warm the cache. Before routing all traffic through the CDN, fetch the highest-traffic and most frequently crawled pages through it at a controlled pace. The firm’s page list from step one is the place to start.
- Use a short brake if needed. Google’s advice: “Use 429 or 503 if you need a temporary brake.” Google says to keep it to a few hours, or 1 to 2 days at most, and not to block crawlers with 403 walls or challenge pages.
Step Three: Check the Pages After the Switch
Once traffic runs through the CDN, the firm’s page list doubles as a test plan:
- Run the live test in Search Console’s URL Inspection tool on each key practice area page and confirm it returns the page, not a challenge.
- Watch those pages in Search Console’s Performance report for the next few weeks.
A blocked crawler can also show up in small ways, such as a missing favicon in Google results when Google cannot reach the home page. Security changes elsewhere on the site, like WordPress security fixes for law firm sites, deserve the same check.
Frequently Asked Questions
A CDN move can hurt a law firm’s visibility in Google if bot protection blocks Google’s crawlers. Google says its crawlers fail CAPTCHA challenges, back off, and pages can drop out of Search. Allowing verified bots in the CDN or firewall settings avoids this.
A law firm should check the pages that bring in clients after moving to a CDN: practice area pages, office pages, attorney bios, top blog posts and the contact page. Running the live test in URL Inspection confirms Google can still reach each one.
Crawler traffic can go up after moving to a CDN because faster responses signal to Google that the site can handle more requests. Google says a new CDN starts with an empty cache, so each first request for a URL still reaches the firm’s own server.
A law firm can return a 503 or 429 during a CDN move if crawl volume is overloading its server while the cache warms up. Google says to use these codes only for a short window, from a few hours to 1 or 2 days at most.
- Google says blanket bot protection can lock its crawlers out and make pages drop from Search.
- List the pages that bring in clients before the developer changes any setting.
- Allow verified bots and warm the cache with the firm’s key pages first.
- After the switch, test each key page with URL Inspection and watch its performance.
Protecting Your Pages During a Law Firm Website CDN Move
A law firm website CDN move is a technical job, but what is at stake is content: the pages that explain the firm’s practice and turn searchers into clients. List those pages first, make sure Google can still reach them, and check them again after the switch.
That list often shows something else too. Pages that are thin, outdated or missing are easier to fix while the site is already being worked on.
Lexicon’s legal content experts write and refresh practice area pages, attorney bios, FAQs and blog posts through Lexicon’s attorney website content service, with attorney review included. Call (877) 486-8123 to plan fresh page content alongside your next site change.