CDN Migration Checklist for Québec Websites
By2Friends · · 6 min read
A practical CDN migration checklist for Québec businesses: improve site speed without blocking Googlebot, privacy basics or French content this quarter.
A CDN migration can make your Québec website feel faster almost overnight. It can also hide pages from Google, break forms, or create privacy and language gaps if it is treated as a simple hosting switch.
Google published new guidance on November 11, 2026 about moving to a CDN without overwhelming your origin server or blocking Googlebot. For business owners, the message is simple: speed is good, but only if your website stays visible, measurable and compliant.
CDN migration checklist: what changed in November 2026
A content delivery network, or CDN, stores and serves parts of your site from servers closer to visitors. Google says this can lower visitor latency and protect the origin server from heavy traffic, which is why many growing sites use one before campaigns, launches and peak seasons. In its November 2026 Search Central guidance, Google also explains why the transition can be noisy.
Three points matter for a Québec SME:
- Faster responses can make Google crawl more pages, faster.
- A cold cache does not protect your server on the first request for each URL.
- Blanket firewall, CAPTCHA or bot rules can return 403 pages to Googlebot and hurt visibility.
That is why a CDN migration should be planned like a website launch, not like a plugin setting.
First, decide if you actually need a CDN
Not every website needs a big infrastructure project. A five-page brochure site on good hosting may need image cleanup, code cleanup and better caching before it needs a full CDN. A larger site is different.
A CDN is worth reviewing if you have:
- A bilingual website with many images, PDFs or blog posts.
- A Shopify or custom e-commerce store preparing for a campaign.
- A web app or client portal used by customers outside Montréal or Québec City.
- Slow mobile pages, especially on product, service or quote-request pages.
- Traffic spikes from ads, newsletters, seasonal campaigns or media mentions.
Before choosing a provider, take a baseline. Export your main landing pages, current Core Web Vitals, Search Console clicks, indexed pages, form conversion rate and server errors. If you do not measure before the move, you will not know whether the CDN improved the site or simply moved the problem.
Protect SEO before you change DNS
The most common mistake is flipping DNS first and testing later. Do the opposite.
Create a short pre-launch SEO list:
- Confirm that the English and French versions of each key page are still accessible.
- Test redirects from old URLs to current URLs.
- Verify canonical tags, hreflang tags and XML sitemaps.
- Make sure robots.txt does not include temporary staging blocks.
- Test important templates: home, service page, product page, blog article, cart, login and contact form.
- Open key URLs in Google Search Console’s URL Inspection Tool.
Google’s hosting-change documentation says to check that Googlebot can access the new infrastructure, remove temporary crawl blocks and monitor indexing in Search Console after the move. It also says crawl rate can drop temporarily and then rise over the next few days after hosting infrastructure changes, including CDN moves (Google Search Central).
For a business owner, that means one thing: schedule the launch when someone can watch it. Do not migrate Friday at 4:30 p.m. before a holiday weekend.
Configure bot protection without blocking buyers or Googlebot
A CDN often comes with a web application firewall, rate limiting and bot protection. These tools are useful. They can reduce spam, fake traffic and malicious requests. They can also be too aggressive.
Use this safer default:
- Allow verified search crawlers, especially Googlebot.
- Avoid CAPTCHA challenges on pages that search engines need to crawl.
- Do not return 403 errors to legitimate crawlers because of a generic bot rule.
- Use temporary 429 or 503 responses only when your origin needs a short break.
- Keep critical user paths simple: product page, cart, checkout, login, quote form, appointment booking.
Google’s November 2026 guidance specifically warns against blanket WAF or CAPTCHA rules that block Google crawlers and suggests verified-bot exemptions. It also recommends temporary 429 or 503 responses for short windows when the origin genuinely needs relief.
After launch, test as a real customer. Open the site on a phone, on mobile data, logged out, in both languages. Submit the contact form. Add a product to cart. Try the client portal login. A perfect CDN score is useless if your next lead cannot reach you.
Do not forget Québec privacy and French rules
This section is general information, not legal advice. A CDN migration can touch compliance because it may change where logs, form submissions, account data or support data pass through.
Under Québec’s Law 25, the Commission d’accès à l’information says organizations must carry out a privacy impact assessment for any project to acquire, develop or overhaul an information system or electronic service delivery system involving personal information. The CAI also says an assessment is required before communicating personal information outside Québec, and that businesses collecting personal information through technology must publish a clear privacy policy on their website (CAI, September 2023 obligations).
For a practical website migration, ask:
- Does the CDN process IP addresses, forms, account sessions or order data?
- Are logs stored outside Québec or outside Canada?
- Do contracts explain security, retention and subcontractors?
- Does the privacy policy still describe the real data flow?
- Is the person responsible for privacy listed on the website, as required by the CAI?
Language matters too. Éducaloi explains that websites and other commercial documents must be available in French when a business has an address in Québec and offers products or services to Quebecers. For e-commerce, the French version must include the information a customer needs to make a purchase, including product or service information, order forms, invoices and receipts (Éducaloi).
So before launch, compare the French and English paths. Do not only translate the home page. Test the complete journey: product, cart, checkout, email confirmation, portal messages, error messages and PDFs.
A simple 7-day migration plan
You do not need a 40-page document. You need ownership, timing and tests.
Day 1: Inventory. List the pages, forms, domains, subdomains, redirects, analytics tags and third-party tools.
Day 2: Baseline. Save Search Console data, speed scores, current crawl errors, conversion rates and screenshots of critical pages.
Day 3: Configure. Set caching rules, image rules, firewall rules, verified-bot exemptions and origin protection.
Day 4: Test on staging. Crawl the site, test French and English pages, submit forms and check checkout or portal login.
Day 5: Launch during a calm window. Lower DNS risk, keep technical people available and avoid major campaign hours.
Day 6: Monitor. Watch server logs, CDN analytics, Search Console, 404s, 403s, form submissions and checkout errors.
Day 7: Clean up. Remove temporary rules, document the final setup and decide what to optimize next.
The goal is not only to go faster. It is to go faster without losing leads, search traffic or trust.
Build it with By2Friends
At By2Friends, we build and improve websites for Québec businesses that need performance, SEO, bilingual content, privacy basics and real business results to work together.
If you are planning a CDN migration, website redesign or performance cleanup, we can audit the current site, prepare the migration plan, configure the technical pieces and test the customer journey before launch. Start with our website service and we will help you decide what is worth doing now, what can wait and what should not be touched without a plan.
#cdn migration #website performance #seo #quebec business #googlebot