What to check before changing your domain name

Start with the reason for the change

A domain change should solve a clear business problem. The current name may no longer fit the offer, may be difficult to spell, may restrict expansion or may be confused with another organisation. Write the reason down and define what success would look like. If the only problem is an outdated website, changing the domain may add risk without fixing the real issue.

Separate the brand decision from the web implementation. A new name affects signs, proposals, social profiles, packaging, email signatures and customer expectations. The website is one part of that transition. Decide who approves the name, which audiences need to understand it and whether the business will use both names for a period.

Ask whether the new name will still make sense if the offer, location or ownership changes. A domain is a long-term customer reference, so a small improvement in clarity should be weighed against the cost of changing every public touchpoint.

Check the new domain before committing

Confirm that the desired domain is available through a reputable registrar and that the business can become the registered owner. Check spelling, pronunciation, hyphens, common misspellings and meanings in relevant languages. Search for similar names and investigate whether the name could create legal or marketplace confusion before investing in design and promotion.

Review the extension, renewal price, transfer rules and privacy options. A short domain is not automatically a good domain if customers cannot remember or type it. Consider sensible variations and protect important alternatives when the risk justifies the cost. Record the account, renewal date and recovery details under business control.

Check whether the new name is easy to hear over the phone and distinguish from similar businesses. A domain that looks good in a design file may still create repeated corrections in conversations, invoices and support messages.

Audit the old domain and URLs

List the old domain’s important pages, subdomains, downloads, campaign links and email-related records. Use analytics, Search Console and link data to find URLs that attract valuable visitors or references. Include pages that are not linked from the main navigation. An old address may continue receiving traffic long after the rebrand has been announced.

Map each old URL to the most relevant new destination. Do not send every page to the homepage. Plan permanent redirects, update internal links and check canonical, sitemap and robots settings. A domain change with identical page paths is simpler than a domain and URL restructure at the same time, so avoid combining changes unless there is a strong reason.

Look for old URLs in printed material, partner websites, email campaigns and saved customer documents. These references are easy to overlook because they may not appear in analytics until someone follows them after the change.

Plan email and connected services

Changing a website domain does not automatically move business email. Create the new mailboxes and aliases, configure authentication and test sending and receiving before changing public addresses. Decide how long old addresses will forward and tell customers which address should be used in future. Protect continuity for invoices, support and account recovery.

Make a list of services that use the old domain: analytics, Search Console, advertising, social profiles, booking tools, payment providers, newsletters, CRM systems and login integrations. Update them deliberately and record who owns each account. A hidden verification record or callback URL can stop a connected service even when the website itself appears to work.

Keep a written owner for each integration and ask them to confirm the update. This avoids a situation where everyone assumes someone else changed a verification setting or account callback.

Prepare content and customer communication

Update the website’s name, logos, contact details, downloads, legal pages, social links and calls to action. Explain the relationship between old and new names where customers might hesitate. Keep important references searchable during the transition and make the new domain visible in email signatures, invoices and customer messages.

Communicate more than once. Tell existing customers what is changing, when it happens and what they need to do. Keep the message specific and avoid creating urgency that does not exist. A clear transition page can reassure visitors who arrive through an old link or receive a message from a new address.

Use a transition message that answers the practical question customers have: is this still the same business, and what should I use now? Reassurance is more useful than simply displaying a new logo.

Test, launch and monitor the change

Before launch, test representative old URLs, redirects, forms, payments, bookings, downloads, email delivery and analytics. Check mobile and keyboard use. Confirm that the new domain has the correct security certificate and that temporary indexing blocks are removed when the site is ready. Record the switch time and keep the old domain active for planned redirects.

After launch, monitor Search Console, analytics, enquiries, email delivery, brand mentions and support questions. Look for crawl errors, missing pages, traffic drops and customers using the wrong address. Fix high-impact issues first and keep an owner responsible for the follow-up. A successful domain change is a managed transition, not just the purchase of a new name.

Compare performance over several weeks and record what was changed. This creates a learning record for future brand or platform work and prevents normal launch variation from causing unnecessary reversals.

Sources

• Site moves and migrations · Google Search Central

Frequently asked

Will changing a domain automatically damage search rankings?

No, but it creates migration risk. Correct redirects, consistent content, verified properties, updated links and monitoring help search systems understand the change.

Should the old domain be cancelled immediately?

Usually not. Keep control of the old domain while redirects, old links and customer habits still matter. Review traffic and references before deciding whether it can be released.

Do I need a new email address when changing domains?

If the public email uses the old domain, you should plan new addresses, forwarding, authentication and a transition period. Website and email changes should be coordinated but tested separately.