- Crawl and save the old site before anything changes.
- Map every old URL to its best new equivalent and redirect with 301s.
- Test the new site on staging: redirects, indexing, internal links and structured data.
- Monitor Search Console daily for the first weeks after launch.
Types of migration
A migration is any big change to how search engines find your pages: a redesign, a move to a new platform (for example WordPress to Shopify), a new URL structure, moving from HTTP to HTTPS, or a new domain. The bigger the change, the higher the risk.
Before the migration
- Benchmark. Export performance data from Search Console and Analytics: top pages, top queries, conversions.
- Crawl the old site. Save a full list of URLs, titles, meta descriptions, headings, canonical tags and structured data.
- Collect all known URLs. Combine the crawl with Search Console, Analytics, your XML sitemap and backlink data, so pages that are linked from other sites are not forgotten.
- Map URLs. Match every old URL to the most relevant new URL. Avoid redirecting everything to the homepage.
- Keep what works. Carry over content, titles and internal links from pages that perform well.
On the staging site
- Block the staging site from indexing with password protection, not just a noindex tag that might be copied to production.
- Test that every mapped redirect returns a single 301 to the right page, with no chains or loops.
- Check that important pages are indexable: no stray noindex tags, correct canonical tags, a working robots.txt.
- Confirm structured data, hreflang (for multilingual sites) and internal links are in place.
- Test mobile layout and page speed on key templates.
Launch day
- Put the redirects live at the same moment as the new site.
- Remove staging protection and check that robots.txt allows crawling.
- Submit the new XML sitemap in Search Console.
- For a domain change, use the Change of Address tool in Search Console.
- Crawl the live site and spot-check the most important old URLs.
How to build a redirect map
A redirect map is a spreadsheet with two main columns: the old URL and the new URL it should point to. Add columns for the page’s organic traffic, number of linking websites and notes. Work through it in order of importance, so the pages that bring traffic and links get the most careful matching.
- Match each old page to the closest equivalent in content, not just in name.
- If a page is being removed with no equivalent, redirect to the most relevant parent category or service page.
- Only let pages return a 404 or 410 if they have no traffic, links or value.
- Update internal links on the new site to point directly to the new URLs, not through redirects.
Content risks during redesigns
Designers often simplify pages during a redesign, removing text that was helping rankings. Before launch, compare word counts, headings and key sections on your top pages. If a page that ranks well loses most of its content, expect it to lose rankings too.
Platform-specific checks
Each platform has its own quirks. Shopify adds fixed URL paths such as /products/ and /collections/, WordPress plugins can add or remove trailing slashes and duplicate archive pages, and JavaScript-heavy frameworks may need server-side rendering so search engines see your content. Check how your new platform handles URLs, canonical tags, pagination and XML sitemaps before you build the redirect map.
After launch
Watch the Pages (indexing) report and the Performance report daily for the first two weeks, then weekly. Fix 404 errors for old URLs you missed, update important backlinks to point to the new URLs where you can, and keep redirects in place for at least a year, ideally permanently. A small, temporary dip is normal; a large or lasting drop means something needs attention.
We plan and test migrations as part of our technical SEO service, and we can review your plan before launch with a website audit.
