To move a store or company site to a new platform without losing rankings, keep every URL that still works, send each URL that changes to its exact new equivalent with a single permanent (301 or 308) redirect, and carry titles, descriptions, canonical tags, hreflang and structured data over unchanged. Then submit the new sitemap, watch 404s daily, and expect some ranking movement: Google says a medium-sized site can take a few weeks or more before the new URLs replace the old ones in results, and larger sites take longer.
The checklist below follows Google Search Central's site-move documentation (last updated August 2026) and adds the practical detail a replatforming project needs.
First, decide what kind of move this is
Google treats two situations differently, and your checklist depends on which one you are in:
Same URLs, new infrastructure. If every public address stays identical and only the hosting, CDN or platform behind it changes, follow Google's hosting-change guide: copy and test the site, lower your DNS TTL at least a week in advance, remove temporary crawl blocks, then switch DNS. Google notes it is normal to see a temporary drop in crawl rate right after launch, followed by a steady increase over the next few days.
URLs change. Most replatforming projects land here, because each platform has its own URL patterns (for example /product.php?id=12 becoming /products/blue-lamp). This is a site move with URL changes, and redirects become the core of the project.
Google also advises changing one thing at a time. If you plan a new domain, a new platform and a new design, its guidance is to do them one after the other rather than all at once, so that if traffic moves you can tell why. If you must bundle changes, at least keep the URLs stable wherever the new platform allows it.
Step 1: Build a complete URL inventory
You cannot redirect what you have not listed. Pull URLs from several sources and merge them, because each one misses something:
Your current XML sitemaps.
Search Console performance data, for pages that earn impressions and clicks.
Server logs and analytics, for URLs visited recently (pick a window long enough to cover seasonal pages).
Search Console's links report, for pages other sites link to.
A full export from the old platform: products, categories, content pages, blog posts, and filtered or paginated URLs that are indexed.
Files and media: images, videos, PDFs and other downloads. Google specifically reminds you that these can get search traffic and links too.
For each URL, record the status code, title, meta description, canonical, hreflang set, structured data types and organic traffic. That snapshot becomes your before-and-after test.
Step 2: Map every old URL to one final destination
Create a mapping table: old URL, new URL, redirect type, and a note on why. Rules that keep the map clean:
Keep URLs identical where you can. The best redirect is no redirect.
Redirect like to like. A product goes to the same product, a category to its equivalent category. Google warns against sending many old URLs to one irrelevant page such as the home page; that confuses users and can be treated as a soft 404. Redirecting several old pages to one page that genuinely consolidates their content is fine.
Use server-side permanent redirects. Google recommends HTTP 301 or 308, and its redirects documentation explains that permanent redirects signal the target should be the canonical URL shown in results. Google also states that 301 and other permanent redirects do not cause a loss of PageRank.
One hop, no chains. Googlebot can follow up to 10 hops, but Google advises redirecting straight to the final destination and, if a chain is unavoidable, keeping it to ideally no more than 3 and fewer than 5. Chains appear quietly when old redirects from a previous migration point to URLs that are now redirecting again, so re-point those legacy rules to the new final URLs too.
Let dead content die properly. Pages you are deliberately not carrying over should return 404 or 410 on the new site, not a redirect to something unrelated.
Step 3: Carry on-page SEO across unchanged
Rankings are tied to what a page says as well as where it lives. During the build, check that the new platform reproduces:
Titles and meta descriptions, page by page. Template defaults often overwrite hand-written titles during import, so compare old and new values for every URL, not a sample.
Headings and body content, including category descriptions that are easy to lose.
Canonical tags. Google asks for a self-referencing rel="canonical" on each new URL, pointing at the new address, never the old one.
hreflang. On multilingual or multi-country sites, update every alternate annotation to the new URLs, in both directions.
Structured data for products, prices, availability, breadcrumbs, organization and FAQs, validated on templates before launch.
Internal links, rewritten to point directly at new URLs instead of relying on redirects.
Page speed. A new platform is a good moment to measure it; see our guide to Core Web Vitals for stores.
Step 4: Prepare Search Console and the launch environment
Verify all variants of the old and new sites (www and non-www, HTTP and HTTPS) and make sure your verification method survives the move.
If you uploaded a disavow file for the old site, Google recommends uploading it again on the new site's property.
Prepare two sitemaps: one with the old URLs and one with the new URLs.
Staging sites are often blocked with robots.txt or noindex. List exactly what must be removed at launch; forgotten blocks are one of the most common mistakes Google lists.
Check server capacity. Google notes it will crawl the new site more heavily than usual after a migration, because redirected crawls of the old site land on the new one.
If your traffic is seasonal or dips on certain weekdays, schedule the switch for a quiet period.
Step 5: Launch day
Turn on the redirects and remove temporary crawl blocks.
Test the redirect map in bulk with a crawler or script: every old URL should return one 301 or 308 to a 200 page. Spot-check important URLs with Search Console's URL Inspection tool.
Submit the new sitemap. Submitting the old-URL sitemap as well helps you watch the old URLs drop out; Google says redirect warnings on that old sitemap are expected.
Update high-value external links, social profiles and ad campaigns so they point at the new URLs.
When to use Change of Address
Search Console's Change of Address tool is only for moving from one domain or subdomain to another, for example example.com to example.net. Google says not to use it for HTTP to HTTPS moves, switching between www and non-www, moving pages within the same domain, or changing hosting without URL changes. A replatforming project that keeps the same domain therefore does not need it. If you are also changing domain, submit it for every verified variant of the old domain once redirects are live; Google says the tool's effects continue for 180 days.
After launch: monitor 404s and what to expect
The first weeks decide whether the move holds its rankings. Check daily at first:
404 log and crawl errors. Any old URL returning 404 that had traffic or links is a missing redirect. Google says redirecting to wrong, non-existent URLs is one of the mistakes it sees most often.
Search Console indexing and sitemap reports. Indexed old URLs should fall while new ones rise.
Performance by page. Compare clicks and impressions for your top pages against the inventory snapshot, and investigate any page that falls sharply.
Server logs for Googlebot activity and unexpected error codes.
Expect fluctuation. Google calls temporary changes in visibility during a move normal and says rankings settle over time, with small to medium sites typically taking a few weeks for most pages to move. Keep redirects for as long as possible: Google's site-move guide says generally at least 1 year, and suggests considering keeping them indefinitely for users. Organic search is usually too valuable to risk on a shortcut here; see why SEO drives organic traffic.
Decision questions before you sign off
Does every URL with traffic, links or a sitemap entry have a mapped destination or a deliberate 404/410?
Does any redirect take more than one hop?
Do titles, descriptions, canonicals, hreflang and structured data match the old site, URL by URL?
Have all robots.txt and noindex blocks from staging been removed?
Who reviews the 404 log each day for the first month?
If you are still choosing a platform, add these to your shortlist questions; our guide to choosing an e-commerce platform covers the rest.
How CIQRA handles a migration
CIQRA migrations run in five steps: inventory, transfer, design, a password-protected preview you sign off, and go-live. Old URLs stay exactly as they were or are 301-redirected, old URLs can be bulk-imported into the redirect manager, and every 404 is logged. Per-language XML sitemaps, hreflang and canonical tags are generated automatically. In one multilingual company-site migration, preview-environment measurements in September 2026 compared the SEO titles of 4,633 URLs with the old system and found zero differences, with 2,548 redirect records carried over across 26 languages.
Sources
Google Search Central: How to move a site (site moves with URL changes) (updated 2026)
Google Search Central: Changing your hosting (site moves with no URL changes) (updated 2025)
Google Search Central: Redirects and Google Search (updated 2026)
Google Search Console Help: Change of Address tool (accessed 2026)