A website migration is a business change, not a file copy. Domains, platforms, templates, hosting and URL structures can all change at once, and every one of them can affect how search engines crawl, index and rank the site. Most migration losses are avoidable, but they are usually caused by the same handful of omissions: no baseline, no URL map, redirects that point to the wrong place and nobody watching the first month.
This checklist is for the owner or marketing lead who has to sign off the migration. It assumes a site with real organic traffic, not a brochure that nobody visits. Work through it in order, and keep evidence for each item.
Know which migration you are doing
- Domain change: a new domain or a move between www and non-www.
- Platform change: for example, a move from one CMS or ecommerce platform to another.
- Redesign: the platform stays but templates, navigation and content structure change.
- Protocol or hosting change: HTTP to HTTPS, a new host or a CDN.
- Combination: several of the above at once, which is the highest-risk case.
Write down which one applies. It determines the checks that matter and the people who must be in the room.
Step 1: Build the baseline
Before anyone changes a setting, export the current state. Without a baseline you cannot tell whether a drop after launch is a migration problem or normal seasonality.
- Export every indexable URL from the sitemap and from a full crawl.
- Record the status code, canonical, title, meta description, H1 and main heading structure for each URL.
- Record organic landing pages, sessions, conversions and revenue for the last 12 months.
- Export backlinks and the top linked pages.
- Record Core Web Vitals and page speed for the main templates.
- Save the current robots.txt, sitemap files, hreflang tags and structured data.
Keep the baseline in a spreadsheet that the whole team can read. It becomes the acceptance test for the migration.
Step 2: Build the URL map
Every old URL needs a decision: keep it, redirect it, or retire it. A one-to-one map is the only reliable approach.
- Keep the same URL wherever the new platform allows it.
- Redirect changed URLs with a single 301 hop to the closest equivalent page.
- Do not redirect thousands of unrelated pages to the home page. Search engines treat that as a soft 404.
- Preserve query strings where they change content, such as filters or pagination.
- Redirect both the www and non-www versions, and both HTTP and HTTPS, in one hop.
- Map images, PDFs and other files that receive traffic or links.
Assign an owner to the URL map and a reviewer who did not build it. The reviewer's job is to open a sample of fifty redirects and confirm the destination is genuinely equivalent.
Step 3: Control staging and indexing
- Protect staging with authentication or a separate hostname that is not indexed.
- Do not rely on a robots.txt block alone if the staging site contains content you do not want copied.
- Check that the production site does not inherit the staging
noindextag or password protection. - Keep the production robots.txt permissive except for genuine admin or search pages.
- Confirm the new site returns the correct canonical host and protocol.
This is one of the most common and most expensive mistakes. A launch that copies the staging configuration can remove the entire site from search results within days.
Step 4: Protect content and templates
- Carry over titles, descriptions, H1s and internal links. A redesign is not a reason to rewrite every page.
- Keep the same content on the same topic at the same URL where possible.
- Preserve structured data for products, articles, local business and breadcrumbs.
- Check that navigation and footer links point to the new URLs, not the old ones.
- Keep image alt text and file names where they still make sense.
- Remove or redirect thin, duplicate and outdated pages deliberately.
Step 5: Prepare the launch
- Lower the DNS time-to-live at least 24 to 48 hours before the switch.
- Install and test the SSL certificate on the new host.
- Test forms, checkout, payment gateways and order confirmation emails.
- Check the 404 page and the search page.
- Verify analytics and tag manager fire on the new templates.
- Prepare the new sitemap and submit it after launch.
- For a domain change, use the search engine change-of-address tool where available.
- Schedule the launch for a quiet business period, not a Friday afternoon or a campaign week.
Step 6: Watch the first 30 days
Launch day is the start of the work, not the end. Check these items daily for the first week and weekly after that:
- Crawl the site and list every 404, 500 and redirect chain.
- Compare the number of indexed pages with the baseline.
- Check organic sessions and conversions by landing page.
- Review server logs for crawl errors and blocked resources.
- Check Core Web Vitals on the main templates.
- Confirm sitemaps are accepted and the old URLs resolve correctly.
- Watch for duplicate versions of the site on www, non-www, HTTP and HTTPS.
Keep redirects in place for at least a year, and ideally permanently. Old links, bookmarks and partner references do not disappear on launch day.
Verification and evidence
- Percentage of baseline URLs that return a 200 or a single 301 to a relevant page.
- Number of 404s and redirect chains found in the post-launch crawl.
- Indexed page count compared with the baseline.
- Organic sessions and conversion rate by template.
- Core Web Vitals pass rate for the main templates.
- Analytics coverage: page views, events and conversions on the new site.
Owner: marketing lead for content and analytics, technical lead for redirects, DNS and hosting. Evidence: baseline export, URL map, crawl reports and a signed launch checklist.
Common mistakes
- Redirecting everything to the home page.
- Launching without a crawl baseline.
- Leaving the staging
noindextag in production. - Forgetting internal links, images and PDFs.
- Changing URLs and content at the same time without a reason.
- Ignoring mobile performance and checkout during testing.
- Letting the old domain expire after a migration.
Where this fits
If you need help planning the technical side, start with Managed Technology & Cybersecurity. The pricing page explains how we scope infrastructure work. For the maintenance side after launch, read the website malware prevention checklist.
Sources
- Google Search Central, "Site moves with URL changes", accessed 17 November 2026.
- Google Search Central, "Redirects and Google Search", accessed 17 November 2026.
- Google Search Central, "Build and submit a sitemap", accessed 17 November 2026.
- web.dev, "Web Vitals", accessed 17 November 2026.
Responses (0)
No comments yet. Add the first one below.
Leave a response
Your email address will not be published. Required fields are marked *.