The Site record
The canonical domain on the Site is updated first, so the platform and every tool that reads it — dashboard, API, MCP — agree on the new name from the moment the change begins.
Change a site's domain
Changing a live site's domain is a first-class operation, not a support ticket. Rename or re-point and the change cascades everywhere it needs to: the Site record, a WordPress site-URL search-and-replace, DNS, the CDN zone, a re-issued certificate and the origin mapping — orchestrated in order, from the dashboard and the MCP, with a clear nameserver-repoint warning on Cloudflare.
A domain name is threaded through a dozen places. Miss one and the site breaks or leaks the old name. So we treat the rename as a single cascading operation and update all of them.
The canonical domain on the Site is updated first, so the platform and every tool that reads it — dashboard, API, MCP — agree on the new name from the moment the change begins.
For WordPress sites we run a database-wide search-and-replace of the old URL for the new, across posts, options and serialized settings, so internal links, images and canonicals follow the domain instead of pointing back at the old one.
DNS records are repointed and the CDN zone is moved or updated for the new name, so traffic and caching follow the domain rather than being left behind on the old zone.
A TLS certificate is re-issued for the new domain and the origin mapping is updated, so the site is served securely on its new name end to end.
One case deserves a plain warning rather than a silent surprise. When a site is on Cloudflare, the CDN and the DNS are the same thing — the orange cloud is the zone — so a new domain usually has to have its nameservers repointed to Cloudflare before the zone can be authoritative for it.
We flag that during the change so the nameserver repoint is an expected, understood step, and we configure the Cloudflare zone for you once the nameservers are in place. On every other CDN, DNS is a free choice from the provider pool, so a domain change does not force a nameserver move — the warning is Cloudflare-specific, and we only raise it when it applies.
Everything that references the old name. We update the Site record, run a WordPress site-URL search-and-replace so links and stored URLs inside the database follow, repoint DNS, move or update the CDN zone, re-issue the TLS certificate for the new name, and update the origin mapping. It is one first-class operation, not a checklist you run by hand.
No. For WordPress sites the site-URL search-and-replace rewrites the stored URLs across the database — posts, options, serialized settings — so internal links, image sources and canonical URLs point at the new domain instead of leaving a trail of the old one.
The change is orchestrated so the pieces move in the right order — DNS, CDN, certificate and origin — to keep the switch clean. DNS and certificate propagation are inherent to any domain change; we sequence around them rather than leaving you to time it.
If the site is on Cloudflare, the new domain generally needs its nameservers repointed to Cloudflare for the zone to be authoritative — the orange cloud is the zone. We flag that clearly during the change so a nameserver repoint is an expected step, not a surprise, and we configure the zone for you once it is in place.
Yes. Changing a domain is a platform action available on the dashboard, the API and the MCP, so you can rename or re-point a site — or a batch of them — from your AI tool, with the whole cascade handled for you.
Start a card-free 7-day trial and change a site's domain as one operation — Site, WordPress URLs, DNS, CDN, certificate and origin all cascade together, from the dashboard and the MCP.
Start free