Guide
Website migration checklist: change platform without losing rankings
What to do before, during and after a platform move so search engines and visitors find everything where they expect it.
Short answer: To change website platform without losing rankings, list every URL on the current site, record current rankings and traffic, give each changed URL a permanent 301 redirect to its closest equivalent, and keep titles, content and structured data the same. Test on staging, resubmit your sitemap at launch, then monitor errors, rankings and backlinks for eight to twelve weeks.
Updated 25 September 2026 · 7 min read
Why do website migrations lose rankings?
A website migration is any significant change to a site's platform, domain, URL structure or design. Search engines have spent years learning where your pages are and what they are about. A migration asks them to relearn it. If pages vanish, move without redirects or lose their content, the rankings those pages earned go with them.
Most ranking losses after a migration trace back to a few avoidable mistakes: missing redirects, changed URLs, thinner content, and the new site accidentally blocking search engines.
What is the full migration checklist?
Inventory every URL
Crawl the current site and export pages from Search Console and analytics, so you have a complete list of URLs that get traffic, rankings or links.
Benchmark performance
Record rankings, organic traffic, conversions and top landing pages before you change anything.
Map redirects one to one
Give every old URL that is changing a permanent 301 redirect to its closest equivalent on the new site.
Carry over on-page SEO
Keep titles, meta descriptions, headings, content, structured data, canonical tags and hreflang for each page.
Test on staging
Crawl the new site before launch to check redirects, internal links, status codes and tracking, while keeping staging out of search results.
Launch and resubmit
Switch over, remove any noindex left from staging, submit the new XML sitemap and use Search Console's Change of Address tool if the domain changed.
Monitor for eight to twelve weeks
Watch for 404 errors, redirect chains, ranking drops and lost backlinks, and fix issues as they appear.
How do you build a redirect map?
A redirect map is a spreadsheet with every old URL in one column and its new destination in the next. Build it from the combined inventory, not just the current navigation, because old campaign pages and blog posts often hold backlinks that nobody remembers.
- Redirect each page to its closest equivalent, not everything to the home page.
- Avoid chains: an old URL should go straight to its final destination in one hop.
- Keep query strings intact where campaigns depend on them, so UTM parameters survive the redirect.
- Let genuinely removed pages return a 404 or 410 rather than redirecting them somewhere irrelevant.
Which on-page elements must you keep?
| Element | Why it matters |
|---|---|
| Title and meta description | What searchers see in results, and a strong relevance signal |
| Headings and body content | What the page is actually about; thinner content often ranks lower |
| Canonical tags | Tell search engines which URL is the main version of a page |
| Hreflang tags | Point search engines to the right language or country version |
| Structured data | Supports rich results and helps machines understand the page |
| Internal links | Spread authority and help crawlers find every page |
| Image alt text | Accessibility, and image search relevance |
A canonical URL is the preferred address for a page when several addresses show similar content. Hreflang is an HTML attribute that tells search engines which language or region a page is for. Both are easy to lose in a template change; see the glossary for more terms.
What should you test before launch?
Crawl the staging site and the redirect map together. Every old URL should return a single 301 to a page that returns 200. Check that internal links point to new URLs directly rather than through redirects, that the XML sitemap lists only live, indexable pages, and that analytics, consent and form-to-CRM connections work. Keep staging out of search results with password protection or noindex, and make a note to remove that noindex on launch day.
What should you watch after launch?
Expect some fluctuation for a few weeks. Check Search Console for crawl errors and indexing issues, watch rankings for your benchmark keywords, and track organic traffic and conversions against the pre-launch baseline. Look out for backlinks that now land on errors, and ask the linking sites to update where it matters. If the forms moved too, confirm leads still arrive with their source, as covered in how to connect website forms to your CRM.
Where uForge fits
If you are moving to uForge, each change is built and previewed before it goes live, and technical SEO audits check crawlability, blocked pages and thin landing pages. Rank-drop and lost-backlink alerts, based on data from a third-party SEO data provider, help you spot problems after launch. See the uForge website builder and SEO, social and ads.