Domain Redirects

We begin with an inventory of every domain and subdomain you own or have used, including old ones that still receive visits or backlinks. We note where each is registered, where its DNS is managed and what it currently shows. Then we decide the single canonical address: https, with or without www, on the main domain. Every other address must lead there in one step. Next we choose the redirect method. For whole domains, the best place is usually the web server or hosting control panel, using permanent redirects that keep the path and query string, so that old-domain.com/services/ leads to new-domain.com/services/ and not just the home page. Where the host allows only simple forwarding, we check that it keeps paths and uses the correct status code, since some registrar forwarding tools use temporary codes or frames. For extra domains with no old content, such as misspellings, we point them to the home page or a suitable landing page. DNS comes first: the old domain must resolve to a server that can answer, even if it hosts only the redirect; see domain DNS configuration. The old domain also needs a valid certificate, or visitors typing https will see a warning before the redirect happens; see SSL certificate installation. For a domain change, we prepare a map of important old pages to new ones, since structure often changes, and check it against the redirect rules; the page-level side is covered in redirect and 404 error management. We avoid chains, where one address redirects to another that redirects again, and loops, where rules point at each other, both of which slow visits and can break access. After implementation we test each address in several forms: http and https, with and without www, with deep paths and with parameters, using browser tools and command-line header checks. We confirm status codes, final destinations and speed. For search, we update sitemaps, tell Search Console about an address change where it applies and monitor indexing and errors; see Google Search Console. We update internal links, email signatures, ad destinations and analytics so they use the final address and not the redirect. We keep old domains renewed so the redirect does not lapse; see domain renewal coordination. We document every rule so future developers know why it exists. We cannot redirect domains that have expired and been re-registered by others, and we cannot control how long search engines take to settle, but correct domain redirects keep visitors, links and trust connected to your current address.