Changing a website address is a migration, even when the control panel makes the first click look like a rename.
You need the new domain connected, the site configured to use it, the old URLs redirected, and dependent services checked. Back up first and keep the old address active long enough to catch missed traffic.
Table of contents
- Decide what is changing
- Connect the new domain
- Update WordPress and content
- Redirect and verify
- How this fits the rest of the stack
- FAQ
Decide what is changing
Connecting a different domain to an existing hosting plan is different from editing a purchased domain name. Registered domains generally cannot be renamed; you register the new one and migrate the website. A WordPress Address change also affects application URLs, not the registration itself.
Inventory email accounts, subdomains, DNS records, analytics, search tools, third-party logins, webhooks, and hard-coded links before touching settings.
Connect the new domain
In Hostinger, locate the website and use the domain-change or connection workflow available for that hosting product. Point the new domain’s nameservers or DNS records as instructed, then wait for DNS propagation. Keep screenshots or an export of the old DNS zone.
Issue or activate an SSL certificate for the new hostname before forcing HTTPS. Test both apex and www variants and choose one canonical address.
Update WordPress and content
Back up the database and files. Update the WordPress Address and Site Address through the dashboard when possible, then run a serialization-safe search and replace for old absolute URLs. Do not use a plain SQL replacement on serialized options.
Clear application and edge caches, resave permalinks, and test media, forms, login, checkout, and password-reset links.
Redirect and verify
Create a 301 redirect from every old path to its matching new path, not merely every request to the new home page. Update canonical tags, sitemap, robots references, analytics properties, and search-console settings where available.
Crawl both hosts, monitor 404 logs, and retain the old domain registration. Email DNS changes deserve special care: copy MX, SPF, DKIM, and DMARC records before the switch.
How this fits the rest of the stack
A domain move is complete when users, search engines, certificates, and email all agree on the new address. If you are considering a fresh deployment, compare it in the RunxBuild calculator and manage the site from the RunxBuild dashboard.
Useful related references:
- What Is a Static Website? Benefits, Examples, Hosting
- Website Management: What It Covers and What It Should Cost
- Deploy an Astro Website for Free
- Services on RunxBuild
FAQ
Can I rename a domain I already registered?
Usually no. Register the new domain, connect it to the site, and redirect the old domain.
Will changing the domain hurt SEO?
It can temporarily affect discovery, but path-by-path 301 redirects, updated canonicals, and continued ownership of the old domain reduce the risk.
How long does DNS propagation take?
Changes may appear quickly but can take longer depending on record TTLs and resolver caches.
Will my email keep working?
Only if the new domain has the correct mail records and accounts. Copy and verify MX, SPF, DKIM, and DMARC settings.