Cloudflare Pages Custom Domain Setup Guide (2026)

Why this topic matters right now

In Google Search Console, Silvermine is already surfacing for queries like cloudflare domain setup guide, cloudflare pages default domain format, and cloudflare pages custom domain setup guide 2026. The problem is that impressions are not turning into clicks yet. That usually means the market exists, but the content either is not specific enough or does not match the searcher’s exact setup workflow.

So here is the version I would want if I were trying to get a Cloudflare Pages site live without losing traffic, breaking SSL, or splitting SEO signals across two hostnames.

Target keyword

Primary keyword: cloudflare pages custom domain setup guide 2026
Secondary keywords: cloudflare domain setup guide, cloudflare pages default domain format, www vs non-www cloudflare pages

Suggested meta title and meta description

Meta title: Cloudflare Pages Custom Domain Setup Guide (2026)
Meta description: Learn how to connect a custom domain to Cloudflare Pages, configure www/non-www redirects, verify DNS, and avoid the most common setup mistakes in 2026.

Outline

1. What Cloudflare Pages expects by default
2. How to connect your custom domain
3. How to handle www and non-www correctly
4. How to verify DNS and SSL
5. Common mistakes that break launches
6. Technical SEO checks before going live

What Cloudflare Pages expects by default

When you deploy a site to Cloudflare Pages, Cloudflare gives you a default *.pages.dev URL. That address is useful for testing, but it is not the version you want users or Google indexing long-term.

Your production setup should usually look like one of these:

• www.yourdomain.com as the canonical website, with yourdomain.com redirecting to www
• yourdomain.com as the canonical website, with www.yourdomain.com redirecting to the root domain

The key is not which one you choose. The key is that you choose one canonical host and redirect the other consistently.

How to connect your custom domain

Step 1: Open your Cloudflare Pages project

Inside Cloudflare, go to Workers & Pages and open the Pages project you want to publish.

Step 2: Add your custom domain

Use the Custom domains section to add your domain. If Cloudflare already manages your DNS zone, this is usually fast. If DNS is somewhere else, you need to point the correct records first or move the zone.

Step 3: Decide on your canonical host

For most marketing websites, I prefer www as the canonical hostname because it keeps redirects, DNS, and future subdomain architecture cleaner.

That means the target production URL becomes:

• https://www.yourdomain.com

And the apex/root version should 301 redirect to it:

• https://yourdomain.com → https://www.yourdomain.com

How to handle www and non-www correctly

This is where people accidentally create SEO problems.

If both versions resolve without redirects, Google can:

• split authority signals
• crawl duplicate content
• index inconsistent URLs
• show the wrong hostname in search

Your goal is simple:

1. make both hosts resolve
2. pick one canonical version
3. redirect the alternate version with a 301
4. keep internal links, sitemap entries, and canonical tags aligned with the preferred version

If your preferred URL is www, then:

• DNS must support both www and apex
• redirects must force apex → www
• your sitemap should only include https://www...
• your canonical tags should point to https://www...

DNS records to double-check

Before you blame Cloudflare, check these:

• Do you have an old A record still pointing at another host?
• Do you have conflicting CNAME records for www?
• Did you recently change nameservers and forget the zone is still propagating?
• Is the redirect configured at the right layer, or are both hosts independently serving content?

The fastest way to get stuck is to mix old registrar DNS, legacy hosting records, and a partially configured Cloudflare zone.

Common mistakes that break launches

1. Serving both hosts without redirects

This is the classic one. The site “works,” but SEO quietly gets worse.

2. Pointing www correctly but forgetting apex

Users type the root domain constantly. If it does not resolve or redirect, they bounce.

3. Updating DNS but not waiting for propagation

A lot of “Cloudflare is broken” tickets are really just propagation delays or cached results.

4. Forgetting canonical and sitemap consistency

Even if redirects are right, mismatched canonical tags or sitemap URLs create mixed signals.

5. Leaving the pages.dev version indexable

The pages.dev URL is great for testing. It should not become the preferred public version of your brand site.

Technical SEO checklist before launch

Before you call the site live, verify these five things:

1. Preferred hostname loads with HTTPS
2. Alternate hostname 301 redirects to the preferred hostname
3. Canonical tags point to the preferred hostname
4. XML sitemap lists only preferred-host URLs
5. Search Console property and sitemap submission match the live canonical setup

If you are running Astro, this is also the moment to verify your site URL config so generated canonicals and sitemap entries do not accidentally reference the wrong hostname.

When this becomes a business problem instead of a technical one

Bad domain setup is not just a developer inconvenience. It affects:

• branded search click-through rate
• crawl consistency
• launch velocity
• paid traffic landing behavior
• trust during first visits

A website that resolves inconsistently looks sloppy, and search engines notice the same mess users do.

Final recommendation

If your Cloudflare Pages site is already ranking for domain-setup searches, that is a sign of demand. The winning move is to publish an article that is painfully clear, current, and implementation-first.

If you want the short version: choose one hostname, redirect the other, align canonical tags and sitemap output, then verify everything in Search Console.

If you need help cleaning up Cloudflare Pages domain setup or technical SEO on an Astro site, start with our existing guides on technical on-page SEO for Astro and setting up your domain on Cloudflare.