Changing Your Business Domain: An SEO Checklist

Treat the move as a small project

A business may change its domain to match a new name, simplify its address, or bring several properties together. Colby Technologies has rebranded from Colby’s Tech Life. That business context makes domain planning relevant here, but this article is a migration checklist, not a claim that a particular move produced a ranking increase.

Write down what is changing: the domain, company name, page paths, design, hosting, or all of them. When possible, separate unrelated changes so a problem is easier to diagnose. Agree on who controls the old domain, new domain, hosting, DNS, and search properties before scheduling the launch.

For the broader decision about replacing a site, see whether your website needs a redesign. Here the focus is continuity between old and new addresses.

Build a URL map before launch day

Start with your sitemap, navigation, useful landing pages, linked downloads, and any additional URLs shown in search or analytics reports. Create a worksheet with the old address, new address, purpose, redirect expectation, and verification result. Do not assume every old page belongs on the new homepage.

Prioritize pages with existing links, inquiries, or useful content. Check images and downloadable documents customers may have bookmarked. Ask the owner to review the map while the old site is still available; it is harder to remember what disappeared after the switch.

Use permanent redirects and test the destination

Google recommends permanent server-side redirects for lasting URL changes; HTTP 301 and 308 are permanent status codes. Configure each old address to reach its intended new destination directly where practical. Avoid a chain through several previous versions.

Test the final response, not just whether the browser moves somewhere. A successful route ends at the correct, working page. Check for loops, missing paths, mixed domain versions, and links that quietly discard the useful part of the old address. A screenshot of the new homepage cannot validate a whole migration.

Keep control of the old domain and its redirect service. Google’s site-move guidance recommends retaining redirects for at least a year, and longer can help people following old links. Include renewals and redirect ownership in the handoff so the plan survives beyond launch week.

Align the site’s own references

Update internal links, canonical tags, structured data, social-sharing URLs, and the sitemap to the preferred new addresses. A canonical tag identifies the preferred version of a page; it does not forward a visitor who follows an old link. Both navigation and search signals need to agree with the move.

Check that production has no leftover staging restrictions. The live page should be accessible and indexable when that is intended. Verify the new sitemap actually served by the host, since an application-generated sitemap can differ from a file in the repository.

Google’s Change of Address tool is relevant for supported domain or subdomain moves after redirects are in place. It is not used for every hosting change or a move from HTTP to HTTPS. Verify the appropriate properties and follow the tool’s eligibility requirements. The Search Console guide covers the surrounding inspection workflow.

Check customer paths beyond search

Make a separate list for email links, public profiles, directory entries, QR codes, payment links, and form destinations. A website can load correctly while an inquiry still goes to an old or unmonitored address. Test a real customer path from an external link through submission and receipt.

Retain a dated copy of the pre-launch site and the mapping worksheet. Assign a person to handle unexpected missing URLs. If a problem appears, use the record to repair the route; do not make repeated unplanned changes that obscure what happened.

Monitor the move with a short issue log

Check priority redirects, destination availability, the live sitemap, and inquiry delivery immediately after launch. Then review search visibility and indexing over subsequent weeks. Record the affected URL, observed issue, correction, and next check. Changes in traffic need context, including seasonality and other edits made at the same time.

Colby Technologies can scope migration work alongside a website project or technical SEO improvements. Bring the old site, proposed domain, account-access list, and any URLs that must keep working. Those details make the handoff and verification much more concrete.