What is a CDN?
A CDN, or content delivery network, is a group of servers spread across many regions that cache copies of your site's files and serve each request from a location near the visitor. Instead of every request traveling to your origin server in one data center, a visitor in Sydney is served from a Sydney edge server and a visitor in Berlin from one in Europe.
CDNs are not a ranking factor on their own. They matter for SEO because they make pages faster and more reliable for both visitors and crawlers, and because a misconfigured CDN can block or confuse search engine bots.
How it works
When a request arrives, the CDN edge checks its cache. On a cache hit, it returns the stored file immediately. On a cache miss, it fetches the file from your origin, returns it, and keeps a copy for the next request. Cache rules and headers such as Cache-Control decide how long copies live.
Most CDNs cache static files (images, CSS, JavaScript, fonts) by default. Some can also cache full HTML pages at the edge, which is where the biggest gains in time to first byte come from, since the origin server no longer builds every page on demand.
Many CDNs also act as a reverse proxy with extra features: image resizing and format conversion, compression, HTTP/2 and HTTP/3, TLS certificates, and bot and DDoS protection.
SEO benefits
- Faster pages. Shorter distance and edge caching improve TTFB and Largest Contentful Paint, two parts of Core Web Vitals.
- Stability under load. Traffic spikes and crawler bursts hit the edge, not your server. Google adjusts crawl rate to server health, so a fast, stable site can be crawled more.
- Fewer 5xx errors. Some CDNs can serve a cached copy when the origin is down.
What to check
- Bot protection is not blocking crawlers. Aggressive firewall or bot-fight settings can challenge or block Googlebot and Bingbot. Check Search Console's Crawl stats and URL Inspection for failed fetches after enabling a CDN.
- Status codes pass through correctly. A CDN error page served with
200becomes a soft 404. Maintenance pages should return 503. - Canonical host is consistent. Images on a separate CDN hostname are fine, but HTML pages should resolve on your main domain with correct canonical URLs.
- Cached HTML is purged on updates, or visitors and crawlers see stale titles and content.
- Personalized or logged-in pages are not cached and shown to everyone.
In WordPress
WordPress sites commonly pair a page cache plugin with a CDN, either a proxy CDN in front of the whole domain or one that rewrites media URLs to a CDN hostname. For the full set of speed steps, see improving Core Web Vitals in WordPress and reducing TTFB.
Common questions
Does a CDN improve rankings?
Not directly. It improves speed and reliability, which feed page experience signals and make crawling smoother. Content and relevance still decide rankings.
Can a CDN cause duplicate content?
It can if pages are reachable on a CDN hostname as well as your main domain. Serve HTML only on your main domain, or make sure canonical tags point there.
Is a CDN worth it for a small local site?
If most visitors are near your server and pages are already fast, the gain is small. Many CDNs have free tiers, so trying one costs little.