Your ZeroPress site is live on Cloudflare’s blazing-fast global network. The final touch of professionalism is pointing your own existing domain (e.g., www.yourbusiness.com) to your new static site, replacing the temporary .pages.dev address.
This guide requires that you already own a domain name purchased from a registrar like Namecheap, GoDaddy, or Porkbun.
Step 1: Add Custom Domain in Cloudflare Pages
- Navigate to your Cloudflare Dashboard and select Workers & Pages.
- Click on the project you just deployed.
- Switch to the Custom domains tab.
- Click Set up a domain.
- Enter your full domain name (e.g.,
blog.mycompany.comormycompany.com) and click Continue.
Step 2: Configure your DNS Records
Depending on whether your domain’s DNS is already managed by Cloudflare or by your original registrar, the process varies slightly.
Scenario A: DNS is managed by Cloudflare (Recommended)
If you’ve already added your domain to Cloudflare’s core service (which we highly recommend for optimal performance and security), the process is practically automatic.
Cloudflare will detect that it manages the DNS and simply ask you to click Add domain or Activate. It will automatically create the necessary CNAME records behind the scenes.
Scenario B: DNS is managed externally (GoDaddy, Namecheap, etc.)
What you can do here depends on whether you’re connecting the root domain or a subdomain.
Root domain (mycompany.com): this only works if the domain is a Cloudflare zone. Add the domain to Cloudflare (the free plan is enough), then change its nameservers at your registrar to the two Cloudflare gives you. Before you switch, check that Cloudflare imported all your existing DNS records, especially the MX and TXT records for email — if one is missing, your email stops working. From that point you’re in Scenario A and Cloudflare creates the record for you. A CNAME at your registrar won’t work for the root domain.
Subdomain (www.mycompany.com, blog.mycompany.com): you can keep your DNS where it is. Add a CNAME record at your registrar:
- Type: CNAME
- Name/Host:
www(orblog, etc.) - Target/Value:
your-project-name.pages.dev
Log in to your domain registrar, find the “DNS Management” or “Edit Zone Records” section, and add this record. Remove any existing record for the same name that points to your old WordPress server.
Order matters: do Step 1 (add the domain in the Pages dashboard) before creating the CNAME. A CNAME pointing to
pages.devwithout the domain added in Pages fails with a 522 error.
Step 3: Wait for Propagation and SSL
Once the DNS records are updated, Cloudflare will verify the connection. A CNAME change is usually live within minutes; a nameserver change can take up to 24–48 hours.
Once verified, Cloudflare automatically provisions a free SSL certificate for your domain. If your domain has CAA records, make sure they allow Cloudflare’s certificate authorities, or the certificate can’t be issued.
The ZeroPress Transformation is Complete
Congratulations! You have successfully migrated from a slow, vulnerable WordPress database to a static site served from a global CDN powered by ZeroPress.
Your content is secure in GitHub, your site loads in milliseconds via Cloudflare, and you never have to worry about a “Plugin Update Required” notification again. Welcome to the future of web publishing.
Still running WordPress?
If you landed here while setting up Cloudflare Pages but haven’t moved your site off WordPress yet, that migration is exactly what ZeroPress automates. Start by exporting your WordPress content, then import it into ZeroPress to get a clean, static version of your site in minutes — no plugins, no database, and no monthly hosting bill.
Worried about your Google rankings? They carry over — here’s why migrating to static won’t cost you your SEO.
Switching a domain that already serves a live WordPress site? Follow the low-risk go-live guide so you can roll back if needed.