Before you start
- Buy the new domain first (any registrar: GoDaddy, Hostinger, BigRock, Namecheap…)
- Your plan, files, databases and price stay the same — only the address changes
Change it
Open Domains, find the site, enter the new domain under Change domain name and confirm by typing the current domain. It takes under a minute.
What moves with it
- Files and folders (the folder is renamed to the new domain)
- www.newdomain — added automatically
- Apps: start command, environment variables and settings; the app restarts on the new address
- WordPress: the site address and links in your pages and posts
- Git deploys, releases and the deploy key
- Cron jobs that use the folder path
Point the new domain here
At the company that runs the new domain's DNS add:
- Type A, name @, value = our IP (shown on Domains)
- Type A, name www, value = our IP
- Delete any other A or AAAA records for @ and www (parking pages)
- Using Cloudflare? Proxied is fine; set SSL/TLS to Full (strict) once the certificate is issued
SSL
The free certificate for the new domain is issued automatically within about 30 minutes of the DNS pointing here (Domains → Check and issue now to try at once). The old domain stops working on this site straight away.
Other things to update
- Google Search Console: add the new domain and use Change of address
- Your app's own settings that contain the old address (API URLs, OAuth / Google login redirect URLs, payment gateway webhooks such as Razorpay, CORS lists, .env values like APP_URL or NEXT_PUBLIC_SITE_URL)
- Email: mailboxes @olddomain stay as they are. For email @newdomain, add the mail domain on the Email page and its DNS records
- Optional: keep the old domain and send visitors to the new one — connect the old domain again and set a Redirect
Stuck? Our engineers answer support tickets around the clock. Contact us, or create an account and open a ticket from the dashboard — the same guides are there too.