Map the complete site
Include pages, products, categories, images, files, campaigns, subdomains, HTTP and HTTPS, www and non-www variants, and high-value linked URLs.
How to Change Domains Without Losing SEO
Google-aligned domain migration
A domain change is a controlled site move, not one forwarding rule.
Google recommends preparing the new site, mapping old URLs to relevant new URLs, using direct server-side permanent redirects, updating internal signals, verifying properties, submitting Change of Address, and monitoring both domains.
- URL-to-URL map
- Direct 301 redirects
- Search Console
- Year-plus retention
Decision frame
Prepare the new domain and the old domain together.
The old domain must remain controlled so it can keep serving redirects, while the new domain must be clean, crawlable, secure, verified, and ready to receive every mapped destination.
Redirect to final destinations
Use server-side 301 or 308 redirects and avoid chains, loops, broad homepage routing, temporary forwarding, or path loss.
Expect movement and monitor
Google notes that rankings can fluctuate while URLs are recrawled and reindexed. Watch both properties, traffic, errors, and conversions.
Platform and operating capability
CMS Max can coordinate the website side of the move.
Domain ownership and DNS may stay with the organization registrar while CMS Max manages accepted website, certificate, redirect, canonical, sitemap, and content requirements.
URL inventory
Use CMS Max pages, ecommerce records, blog posts, sitemaps, analytics, and crawl evidence to build the migration map.
Redirect management
Use SEO Max for supported redirect records and coordinate registrar or server rules for complete domain-level coverage.
Canonical signals
Publish the new final URLs in canonicals, internal links, navigation, sitemaps, structured data, feeds, and campaign destinations.
HTTPS and hosts
Verify root and www behavior, certificates, HTTP-to-HTTPS redirects, preferred hostname, and all historical variants.
Content and analytics
Keep useful content equivalent and update analytics, tags, verification, forms, feeds, ads, integrations, and external profiles.
Monitoring
Review 404s, redirect chains, Search Console, analytics, orders, forms, email, subdomains, certificates, DNS, and support reports.
Implementation workflow
Move the domain through a rehearsed release plan.
Google advises changing one major thing at a time when practical and keeping redirects for at least a year.
- 01
Prepare
Audit domain ownership, renewal, MFA, DNS, email, certificates, subdomains, verification, current URLs, analytics, links, and risks.
- 02
Build the map
Assign each useful old URL to a relevant final new URL and identify intentional 404 or 410 outcomes.
- 03
Ready the new site
Test content, canonicals, robots rules, sitemaps, internal links, forms, commerce, analytics, certificates, and capacity.
- 04
Launch
Enable direct permanent redirects, verify all variants, inspect representative responses, submit Change of Address, and publish new sitemaps.
- 05
Monitor
Track crawl, indexing, traffic, rankings, links, errors, certificates, DNS, email, subdomains, conversion, and support until stable.
Practical reference
Keep the old domain as an active migration asset.
Renewal, DNS access, and redirect service on the old domain remain critical after the public launch.
- Redirect status
- 301 or 308 server-side permanent redirect where technically possible.
- Path behavior
- Preserve the requested path only when it maps to the correct relevant destination.
- Search Console
- Verify old and new variants, submit Change of Address for domain moves, and monitor indexing.
- Retention
- Keep redirects at least one year; longer can continue helping users and old links.
- Rollback
- Document DNS, website, certificate, email, and redirect recovery access before cutover.
Evidence and next steps
Use current product and primary-source guidance.
Features, provider requirements, plans, policies, interfaces, and search guidance can change. Verify the live CMS Max implementation and current official source before release.
Frequently asked questions
Make the practical decisions before launch.
Use each answer to identify configuration, evidence, testing, monitoring, and ownership.
Will rankings remain exactly the same?
No one can guarantee that. Google says temporary fluctuation can occur while the old and new URLs are crawled and indexed.
Should all old pages redirect to the new homepage?
No. Use relevant URL-to-URL mappings. Irrelevant bulk redirects can confuse users and may be treated as soft 404s.
Should the old domain be allowed to expire?
No. Keep durable ownership, renewal, security, DNS, and redirect control for the migration period and preferably longer.
Does Change of Address replace redirects?
No. It supplements a correctly implemented domain move; permanent redirects and updated site signals are still required.
How long should redirects stay active?
Google recommends at least one year and notes that keeping them longer can continue helping users.
Move the domain with every signal and dependency accounted for.
CMS Max can build the URL map, redirect plan, DNS checklist, Search Console process, verification suite, cutover runbook, monitoring, and rollback evidence.