Short answer: You can change a business website’s domain without treating Google visibility as an afterthought. The safest path is a planned one-to-one move: preserve each valuable page, permanently redirect each old URL to its closest new equivalent, update the new site’s internal links and sitemap, then monitor both properties in Google Search Console. A new domain is not a reason to wipe out your useful service, location, and resource pages.
A domain change can happen during a rebrand, an ownership change, or a move away from a platform that no longer fits. For a Quad Cities business, the practical risk is not the new name itself; it is losing the paths customers and search engines already use to find services, locations, and contact information.
Google’s current site-move guidance recommends mapping old URLs to their new destinations, using permanent server-side redirects where possible, updating internal links, and submitting the new sitemap. The Change of Address tool is for a domain or subdomain move after the new site is live and redirects are in place. It is not a substitute for the technical migration work.
First decide whether you are changing a domain or just changing a website
A full domain move means the public address changes, such as oldbusiness.com becoming newbusiness.com. A redesign on the same domain is different: URLs might still change, but the Change of Address tool is not the right step. In either case, the core discipline is the same: know what currently earns visibility and give every useful old URL a sensible destination.
Do not collapse everything to the new homepage. A visitor looking for an old roofing-service page should land on its matching roofing-service page, not a generic home screen. Google likewise recommends a URL map for more complex moves. A relevant one-to-one redirect is more useful than a broad catch-all.
A four-stage domain migration plan
Save a list of current URLs, top landing pages, titles, and Search Console signals.
Pair each valuable old URL with its closest live replacement before launch.
Launch the new domain, apply permanent redirects, and submit its sitemap.
Check redirects, index coverage, and high-value URLs while Google recrawls.
1. Build an inventory before anyone changes DNS
Start with the pages people already reach: core services, city or service-area pages, contact and booking pages, blog posts that earn visits, and pages linked from outside sites. Export a crawl if you have one, review Google Search Console’s Performance report, and note the pages that generate inquiries or calls in analytics. This becomes your migration ledger.
Keep the content that has a purpose. A rebrand is a good time to improve thin or obsolete pages, but removing a page that answers a real question without offering a relevant replacement creates a dead end for customers.
2. Make a one-to-one redirect map
Put the old URL, new URL, page purpose, and redirect test result in one shared sheet. Avoid redirect chains such as old page to interim page to final page. Google describes redirects as a strong canonicalization signal and recommends permanent server-side redirects when a URL has permanently moved.
- Map every indexable service, location, blog, and conversion URL that has an equivalent.
- Use a permanent server-side redirect for a permanent destination whenever possible.
- Send retired pages to the closest genuinely useful alternative, not automatically to the homepage.
- Test both common hostname variants, such as
wwwand non-www, if they existed.
3. Launch the new domain as a complete, crawlable site
Before switching traffic, verify that the new pages return successfully, can be crawled, and use the intended canonical URLs. Replace old-domain links in navigation, content, structured data, social profiles, paid listings, and email templates. Submit a sitemap containing the final new URLs—Google advises against putting redirecting URLs in a sitemap.
If the whole domain or subdomain changes, verify ownership of both old and new properties in Search Console, then use Change of Address after the redirects are live. Google notes that the tool checks ownership and samples redirects; it does not repair missing redirects or replace your URL map.
4. Watch the move instead of declaring victory on launch day
Googlebot needs to visit old and new URLs to understand a move, so plan for monitoring rather than a same-day verdict. Use URL Inspection on important pages, watch indexing and crawl reports, and revisit the redirect sheet when a high-value old URL produces a 404 or lands somewhere irrelevant. Keep the old domain and redirects available for at least a year; Google recommends that minimum for site moves.
Keep critical customer signals stable during the move
Keep the customer promise stable where you can: the service offering, primary location details, phone number, important page topics, and clear conversion paths. Large changes to brand, domain, platform, page structure, and copy at the same moment make it harder to isolate what went wrong. A staged migration lets your team improve the site while retaining a clear map from the old experience to the new one.
If you are moving from a site builder to a more flexible platform, read our guide on when to move from Wix to WordPress. If the real need is a stronger service-page structure—not a new domain—start with how to build a local service page that brings better leads.
Situations that merit migration help
Get technical and SEO support when the site has many indexed pages, several locations, ecommerce, a complex booking flow, or meaningful traffic from search. The migration is not the time to guess at redirect rules or change a URL structure in bulk without testing. QC Webworks can help local businesses scope a practical migration around the existing site, conversion paths, and search visibility. Talk with our team about a website migration plan.
Frequently asked questions
Will a new domain keep all of my Google rankings?
No one can guarantee that. A careful move gives Google clear, consistent signals about where each page went and reduces avoidable losses, but search results can change for many reasons. Measure important queries and landing pages before and after the move rather than promising a fixed outcome.
Should every old URL redirect to my new homepage?
No. Redirect a page to the closest equivalent page whenever one exists. A homepage redirect is appropriate only when it is genuinely the best remaining destination, such as for a retired page with no relevant replacement.
Do I need the Change of Address tool for a redesign?
Not if the domain stays the same. Use redirect mapping, canonicals, internal-link updates, and sitemap updates for URL changes within a site. Use Change of Address when moving a domain or subdomain after the new site and redirects are ready.
How long should I keep the old domain?
Keep ownership and redirects for at least one year. This gives search engines time to revisit old URLs and continues to help people arriving through old bookmarks or third-party links.
Can I move platforms and domains at the same time?
You can, but it raises the risk because several systems change at once. Preserve the URL map, test forms and tracking, and launch only after redirects and key pages are verified. If possible, avoid additional major content or navigation changes during the first migration phase.