A site migration SEO checklist helps protect organic traffic when you change domains, platforms, URL structures or hosting. The essentials are straightforward: record your current performance, map existing URLs to their replacements, preserve important content and test crawlability before launch.
However, no responsible SEO team can guarantee zero traffic loss. Search engines need time to process changes, and some fluctuations are normal. Your goal is to prevent avoidable losses, detect problems quickly and maintain the signals that already support your rankings.
1. Define the migration and capture your baseline
Start by documenting exactly what will change. Moving hosting while retaining every URL is different from replacing a domain, redesigning templates and rewriting content simultaneously. Where practical, separate major changes so that performance problems are easier to diagnose.
Assign one person to approve launch readiness, with named owners for development, analytics, SEO and content. Schedule the release when developers can monitor it, rather than immediately before a weekend or public holiday.
Record what you cannot afford to lose
- Organic performance: export at least 8 to 12 weeks of clicks, impressions, sessions and conversions. Include year-on-year comparisons where seasonality matters.
- Landing pages: identify URLs responsible for the most organic leads, sales and assisted journeys.
- Search visibility: record important queries, ranking landing pages and performance by country and device.
- Technical state: save a crawl containing status codes, titles, headings, canonicals, indexability and internal links.
- Measurement: record analytics settings, consent configuration and key events such as purchases or submitted enquiries.
For an Islamabad business serving Pakistan and the UAE, separate those markets in your reporting. Stable traffic from Pakistan could otherwise hide a decline in valuable UAE enquiries.
2. Build a complete URL inventory and redirect map
Your site migration SEO checklist should cover more than the URLs in your current sitemap. Combine crawl data, XML sitemaps, analytics landing pages, Google Search Console exports and backlink destination reports. Include old campaign pages and downloadable files that still receive visits or links.
Create a mapping sheet with five fields: existing URL, destination URL, intended response, business priority and test result. Every valuable existing URL needs a deliberate outcome.
- Keep unchanged URLs: where the address and page remain valid, retain a normal 200 response.
- Redirect moved pages: use a server-side 301 or 308 redirect to the closest equivalent page.
- Handle merged content: redirect only when the destination genuinely satisfies the old page's purpose.
- Remove obsolete pages: return 404 or 410 when there is no relevant replacement.
For example, an old Lahore delivery page should lead directly to the new Lahore delivery page, not the homepage. Redirecting unrelated URLs to a generic destination can confuse visitors and may be treated as a soft 404.
Test redirects in bulk. Each old URL should reach its final destination in one hop, with no loops. Check HTTPS, www and non-www variants, trailing slashes and meaningful query parameters. Keep redirects for at least a year, and preferably longer where old links remain active.
3. Protect content, indexing signals and tracking
Keep the search intent and useful information of successful pages intact. A visually attractive replacement can still underperform if it removes product specifications, service details, FAQs or location information that previously answered search queries.
For priority pages, compare the old and new versions side by side. Check the title, main heading, body content, images, structured data and internal links. Avoid changing every title during the move unless there is a documented reason.
- Canonicals: confirm indexable pages reference the correct production URLs, not staging addresses or redirected pages.
- Internal links: update navigation, breadcrumbs and contextual links to final destinations.
- Hreflang: if used, update regional alternatives and verify reciprocal references.
- Structured data: validate markup and ensure it matches visible content.
- Rendering: check that important text and links remain accessible when the new platform relies on JavaScript.
- Tracking: test real purchase or enquiry journeys and check for missing or duplicate events.
If your checkout serves multiple markets, verify that orders report the correct PKR, USD, GBP or AED values. An apparent revenue decline may be a tracking or currency configuration problem rather than lost search demand.
4. Test staging and use a launch gate
Protect staging with authentication or suitable access restrictions. A robots.txt block alone is not a reliable way to keep staging URLs out of search results. If you also use noindex directives, document exactly how they will be removed from production.
Run the site migration SEO checklist against a production-like build. Test all priority pages and redirect mappings, then sample every template, including products, categories, articles, location pages and filtered listings.
Minimum launch approval checks
- Priority pages return 200 and contain their expected content.
- Redirects are implemented and tested on the intended server configuration.
- Production pages will not inherit staging authentication or noindex directives.
- Robots.txt permits crawling of pages and resources needed for rendering.
- XML sitemaps contain canonical, indexable production URLs only.
- Mobile navigation, forms, checkout and analytics work.
- HTTPS certificates, DNS settings, backups and recovery procedures are ready.
For a domain change, verify the relevant Google Search Console properties and plan to use its Change of Address tool where supported. This complements redirects rather than replacing them.
Agree on recovery triggers before launch, such as widespread server errors, inaccessible priority pages or broken checkout. Do not reverse a migration solely because rankings fluctuate briefly. A technical SEO review is especially valuable when developers are changing URL rules or rendering technology.
5. Monitor launch day and the following weeks
Immediately after deployment, crawl the live website and retest the old URL list. Check robots.txt, canonical tags, redirect responses, analytics and server errors before announcing completion. Submit the new sitemap through Search Console.
Use a clear monitoring schedule:
- First 24 hours: check availability, priority landing pages, redirects, conversions and unexpected indexing restrictions.
- First week: review organic landing pages, crawl failures and Search Console reports daily, allowing for reporting delays.
- Weeks 2 to 6: compare performance by page group, market and device against your baseline.
- After stabilisation: retain redirect checks and investigate valuable old URLs still receiving requests.
Diagnose patterns rather than reacting to one headline number. Falling impressions across a section may indicate indexing or content problems. Stable clicks but fewer recorded leads suggest a form, tracking or conversion issue. Server logs can help confirm whether crawlers encounter errors.
For budgeting, separate one-off migration preparation from ongoing SEO packages. A small brochure site and a multilingual shop need different levels of URL mapping, testing and post-launch support.
Frequently asked questions
Can a migration guarantee zero organic traffic loss?
No. A site migration SEO checklist reduces preventable mistakes, but cannot control search engine processing or demand changes. Measure success through preserved accessibility, visibility and conversions.
How long should migration monitoring continue?
Monitor closely for at least 4 to 6 weeks, extending this for large websites or domain changes. There is no fixed recovery deadline, and unresolved technical problems should not simply be left to settle.
Do unchanged URLs need redirects after a hosting move?
No, provided the addresses remain identical and serve the intended pages successfully. Focus on availability, HTTPS, performance, crawl access and accidental configuration changes.
Planning a migration? Request a free SEO analysis from SEOISB, part of HA Technologies in Blue Area, Islamabad, to identify technical risks and prioritise your next steps.