A new website should bring more traffic, not less. Yet many redesigns and platform changes lose a large share of their search traffic in the weeks after launch, and some never get it back.
It’s rarely the new design that causes the drop. It’s what gets lost along the way: old URLs that now return errors, pages that were quietly removed, titles and content that changed, or a staging setting left switched on. The good news is that almost every migration loss is preventable. This guide walks through how to plan, launch and monitor a website migration so your rankings come with you.
What counts as a website migration?
In SEO terms, a migration is any change that affects how search engines find, crawl or understand your site. Some are much riskier than others:
| Type of change | Example | SEO risk |
|---|---|---|
| Design only | New look, same URLs and content | Low |
| Platform change | WordPress to a custom Next.js site, or Wix to WordPress | Medium to high |
| URL structure change | /services.php?id=4 becomes /services/web-design | High |
| Domain change | oldbrand.com to newbrand.com, or a country domain to .com | High |
| Merging sites | Combining several sites or language versions into one | High |
| Adding languages | Adding an Arabic version under /ar/ | Medium |
Many projects combine several of these at once, such as a new platform, new URLs and new content. Each extra change multiplies the risk, so it’s worth asking whether everything really needs to change at the same time. If you’re still deciding whether a rebuild is necessary, see our guide to the signs your website needs a redesign.
Why sites lose traffic after a migration
- Missing redirects: old URLs return 404 errors, so search engines drop them and backlinks stop counting
- Removed or thinned content: pages that ranked are deleted or cut down to fit the new design
- Changed titles and headings: the words that matched searchers’ queries disappear
- Staging settings left on: a noindex tag or a robots.txt block copied from the test site to the live one
- Broken internal links: menus and content still pointing to old URLs, wasting crawl budget
- Slower pages: a heavier design that hurts Core Web Vitals
- Lost structured data, hreflang or canonical tags: features that helped the old site rank, forgotten in the rebuild
Search engines don’t rank your website. They rank your pages. Every page you lose without a redirect is ranking you throw away.
Before launch: plan and prepare
1. Benchmark your current performance
Export at least 12 months of data before anything changes: organic traffic and conversions by page from Google Analytics 4, and queries, clicks and impressions by page from Google Search Console. Note your rankings for your most important keywords. Without a baseline, you can’t tell whether the migration worked.
2. Crawl and inventory every URL
Use a crawler such as Screaming Frog or Sitebulb to list every URL on the current site, then add URLs from your XML sitemap, Search Console and analytics, plus pages with backlinks from tools like Ahrefs or Semrush. Some valuable URLs, such as old campaign pages, PDFs and images, won’t be linked from your menus at all.
3. Decide what happens to each page
For each URL, decide whether to keep it (same URL), move it (new URL with a redirect), merge it into another page, or remove it. Be careful with removals. A page with traffic, rankings or backlinks should usually be kept or redirected to its closest equivalent, not deleted.
4. Build a redirect map
The redirect map is the most important document in any migration: a spreadsheet listing every old URL and the new URL it should point to.
- Use 301 (permanent) redirects, not 302s or JavaScript redirects
- Redirect each old page to its most relevant new page, not everything to the homepage. Google treats mass redirects to the homepage as soft 404s
- Avoid redirect chains (A to B to C). Point every old URL straight to its final destination
- Include variations: with and without trailing slashes, uppercase letters, http and www versions
- Update existing redirects from previous redesigns so they point to the new URLs directly
5. Protect content, metadata and structured data
Carry over the title tags, meta descriptions, headings and body content of pages that rank well, or improve them deliberately rather than by accident. Keep image alt text, structured data, canonical tags and, for bilingual sites, hreflang tags that link each English page to its Arabic version. Our guide to multilingual SEO in the Middle East covers hreflang in detail.
6. Test on a protected staging site
Build and test the new site on a staging server that search engines can’t reach. Password protection is safer than a noindex tag, because noindex tags have a habit of reaching the live site. Then crawl the staging site, test the redirect map, and compare page speed with the old site.
Launch day checklist
- Remove staging protection, and check there’s no noindex tag and that robots.txt allows crawling
- Deploy redirects and test a sample of old URLs, including your top 50 pages by traffic
- Check canonical tags point to the new live URLs, not staging
- Submit the new XML sitemap in Google Search Console and Bing Webmaster Tools
- For a domain change, verify both domains and use Search Console’s Change of Address tool
- Check analytics, tag manager and conversion tracking are firing on the new site
- Test forms, checkout and other key journeys end to end
After launch: monitor and fix
Some fluctuation in rankings is normal for a few weeks while search engines recrawl your site. Large sites can take longer to settle. During that period:
- Check Search Console daily for the first two weeks for crawl errors, 404s and indexing problems
- Compare traffic and rankings for key pages against your benchmark, page by page
- Fix any missing redirects as soon as they appear
- Ask the sites with your most valuable backlinks to update their links to the new URLs
- Keep redirects in place for at least a year, and ideally permanently
Common migration mistakes
- Launching on a Friday or just before a campaign or busy season
- Redirecting everything to the homepage
- Deleting blog posts or pages because they “look old”
- Forgetting images, PDFs and other files that have their own rankings and backlinks
- Changing domain, platform, URLs and content all at once without a plan
- Switching off the old hosting before confirming everything works
Website migration checklist
- 12 months of analytics and Search Console data exported as a benchmark
- Full URL inventory from crawls, sitemaps, analytics and backlink tools
- A decision for every URL: keep, move, merge or remove
- A complete 301 redirect map with no chains
- Titles, content, structured data, canonicals and hreflang carried over
- New site tested on a password-protected staging server
- Noindex and robots.txt checked on launch day
- New sitemap submitted and Change of Address used for domain moves
- Daily monitoring for the first two weeks, then weekly for three months
A migration is one of the riskiest moments in a website’s life, but it’s also a chance to fix old problems, improve speed and structure, and come out stronger. With a careful plan, your new site should keep the rankings you’ve earned and build on them.
Planning a redesign or moving to a new platform? We’ll help you protect the search traffic you’ve built.
Talk to our team →

