Redirecting an entire domain is more than pointing one address at another. Use this practical checklist to forward a domain safely, preserve useful URL paths, keep HTTPS working, and avoid accidentally disrupting email or essential DNS records.
Overview
A domain redirect sends visitors and search engines from one hostname to another, usually with a permanent 301 redirect when the change is intended to last. Typical examples include moving from an old brand domain to a new one, consolidating several domains, changing from a non-secure HTTP address to HTTPS, or choosing whether the www and non-www versions should resolve to the same site.
The safest implementation depends on where you control the traffic. A registrar may offer simple domain forwarding, while a web server, reverse proxy, content delivery platform, or hosting control panel can provide more precise rules. DNS itself does not issue an HTTP redirect: it resolves a name to an IP address or another DNS target. The redirect normally happens after the browser has connected to a web service.
| Approach | Best suited to | What to check |
|---|---|---|
| Registrar domain forwarding | A simple domain-level destination | HTTPS support, path preservation, forwarding behaviour, and whether email records remain untouched |
| Web server redirect | Developers needing reliable, detailed rules | 301 status, host matching, query strings, rule order, and loop prevention |
| Hosting or edge platform | Managed infrastructure and multiple domains | DNS verification, certificate provisioning, caching, and deployment order |
| Application or WordPress redirect | Sites where server configuration is unavailable | Performance, plugin conflicts, fallback behaviour, and whether the old host is reachable first |
For a permanent move, point each important old URL to its closest relevant destination rather than sending every page to the new homepage. A domain-level redirect can be appropriate when the entire old domain has one clear replacement, but a site migration usually needs a redirect map.
Checklist by scenario
Before changing anything
- Record the current DNS zone, including A, AAAA, CNAME, MX, TXT, CAA, and any provider-specific records.
- Confirm who controls the registrar, DNS hosting, old web hosting, new web hosting, and certificate configuration.
- Export or document existing redirect rules and identify whether the old domain serves multiple subdomains.
- List important old URLs, including pages linked in marketing material, printed documents, QR codes, and email signatures.
- Decide whether the change is permanent. Use a 301 for a lasting move; use a temporary redirect only when the original address is expected to return. The guide to 301 versus 302 redirects provides further context.
When forwarding an entire domain
- Choose the final canonical hostname, such as
https://www.example.co.ukorhttps://example.co.uk. - Configure the old hostname and its common variants: HTTP, HTTPS,
www, and non-www, where your setup supports them. - Set a permanent server-side redirect to the new hostname.
- Test whether
/aboutbecomes the intended new/about, rather than losing the path or being sent to an unrelated page. - Check whether query strings are retained. Campaign parameters may need to survive, although tracking rules should be reviewed separately.
- Update links, XML sitemaps, canonical tags, structured data, analytics settings, and business listings where relevant.
For a brand change or site migration
Create a bulk redirect map with one old URL, one intended new URL, and a reason or status for every row. Redirect exact equivalents directly. If a page has no direct replacement, select the most relevant parent or category rather than applying a blanket homepage redirect. Remove unnecessary intermediate hops so the old URL reaches the final destination in one step. You can use the website migration redirect map template as a starting point.
For HTTP to HTTPS or www changes
Install and validate a certificate for every hostname users may request before enforcing HTTPS. This can include the old domain, the new domain, and both www and non-www names. Then test the redirect sequence from each variant. A visitor should not encounter a certificate warning before the redirect can be followed.
What to double-check
DNS and email records
Do not replace the entire DNS zone with a single forwarding record unless you have confirmed that no other services depend on it. MX records identify mail delivery routes. TXT records may support domain verification, sender authentication, or other services. A, AAAA, CNAME, and CAA records can also be required by websites, subdomains, hosting platforms, and certificate workflows.
- Keep MX records in place if the domain still receives email.
- Preserve relevant SPF, DKIM, and DMARC-related TXT or CNAME records.
- Check mail subdomains such as
mail.example.co.ukand service subdomains such asautodiscoverif they are in use. - Confirm that changing nameservers will not remove records held in the existing DNS provider.
- Lowering DNS TTL in advance may make planned changes easier to adjust, but it does not control browser or redirect caching.
HTTPS and hostname coverage
Test the old HTTP and HTTPS addresses independently. A redirect is only useful if the connection can be established safely first. Verify that the certificate covers every hostname being requested and that the final site does not redirect back to the old domain.
Redirect behaviour
Use a redirect checker or command-line request to inspect the complete chain, status code, Location header, final URL, and response time. Look for an unnecessary sequence such as old HTTP to old HTTPS, then to new HTTP, then to new HTTPS. The goal is normally one direct hop from each old entry point to the final canonical URL. See the guide to redirect performance testing for a repeatable audit approach.
Common mistakes
- Changing nameservers without copying the zone: this can make the website, email, verification records, or subdomains disappear.
- Redirecting only the homepage: deep links, search results, bookmarks, and campaign URLs may then fail or lose relevance.
- Forgetting HTTPS on the old domain: users may receive a certificate error before the forwarding rule is reached.
- Mixing canonicalisation rules: conflicting HTTP, HTTPS, www, and non-www rules can create a redirect loop. Check rule order across the DNS, CDN, web server, and application layers.
- Using a temporary redirect for a permanent move: select the status code that matches the intended duration and document the decision.
- Testing only in one browser: cached redirects can conceal a configuration change. Test with a clean session, command-line tools, and more than one network where practical. The redirect caching guide explains why results can differ.
- Leaving the old domain unprotected: keep ownership, renewal, DNS, and certificate arrangements under control for as long as the redirect is needed.
When to revisit
Review this setup before every domain consolidation, rebrand, ownership transfer, hosting change, or renewal audit. Recheck it before seasonal campaigns if printed materials, QR codes, adverts, or tracked links use the old domain. Also revisit the configuration when a DNS provider, registrar, hosting platform, certificate workflow, CDN, or redirect rule changes.
Keep a short redirect record containing the canonical destination, responsible account, certificate coverage, DNS zone owner, email dependencies, test URLs, and date of the last successful check. At each review:
- Run representative HTTP and HTTPS requests for old and new hostname variants.
- Confirm a 301 reaches the correct final URL without a loop or unnecessary chain.
- Check a selection of deep paths and query-string URLs.
- Send or receive a test email if the domain remains part of your mail setup.
- Compare the live DNS records with the documented zone.
- Record any provider-interface or certificate changes for the next review.
A domain redirect is complete only when web traffic, HTTPS, DNS dependencies, and email have all been tested. Treat the checklist as a change-control step, not a one-time forwarding switch.