# The SEO Site Migration Checklist for 2026 (Download PDF + Excel) Source: https://piperocket.digital/checklists/seo-site-migration-checklist/ Author: Kamaraj Mathiarasan (Kim), Co-Founder, PipeRocket Digital Published: 2026-07-04 Last updated: 2026-07-04 A site migration is any change that affects your URLs or infrastructure: a redesign, a replatform, a domain change, an HTTP-to-HTTPS move, or a restructure. Done carelessly, it is the fastest way to lose rankings you spent years building. This is the checklist we run to protect organic traffic through a migration at PipeRocket Digital. It is interactive. Tick each item as you complete it, your progress saves in your browser, and you can download the whole thing as a PDF to share with developers and stakeholders. ## How to use this checklist Work it in three phases: plan before you touch anything, execute carefully at launch, and monitor closely afterward. Most migration disasters trace back to a skipped step in the planning phase, especially an incomplete URL-to-URL redirect map. ## The SEO Site Migration Checklist for 2026 Protect your rankings through a redesign, replatform, or domain change. Work it before, during, and after launch. Tick items off as you go. Your progress saves automatically, and you can download the whole thing as a PDF. ### 1. Plan before you touch anything - [ ] Define the migration type (domain, CMS, design, HTTP to HTTPS, restructure) - [ ] Benchmark current rankings, traffic, top pages, and backlinks as a baseline - [ ] Crawl the live site to capture a complete URL inventory - [ ] Set a rollback plan and a low-traffic launch window ### 2. Map URLs & redirects - [ ] Create a 1:1 old-URL to new-URL mapping for every indexed page - [ ] Write 301 (permanent) redirects, never 302, for every changed URL - [ ] Avoid redirect chains: point old URLs straight to the final destination - [ ] Preserve or update internal links to the new URLs ### 3. Preserve on-page & content - [ ] Keep or improve titles, meta, headings, and body content on migrated pages - [ ] Migrate or recreate structured data on the new pages - [ ] Carry over canonical tags and hreflang correctly - [ ] Do not drop pages that earn traffic or links without a redirect plan ### 4. Prepare staging - [ ] Build and QA on a staging site that is blocked from indexing (noindex or auth) - [ ] Verify robots.txt and remove the staging noindex before launch - [ ] Test the redirect map on staging before go-live ### 5. Launch day - [ ] Deploy redirects at the moment of cutover - [ ] Confirm the new site is crawlable and not accidentally noindexed - [ ] Submit the new XML sitemap in Search Console - [ ] Use the Change of Address tool for domain moves ### 6. Post-launch monitoring - [ ] Watch Search Console coverage, crawl stats, and rankings daily for the first weeks - [ ] Fix any 404s and broken redirects as they surface - [ ] Compare traffic and rankings against the pre-migration baseline - [ ] Update or reclaim external backlinks pointing to old URLs where possible ## Plan before you touch anything Start by defining exactly what is changing (domain, CMS, design, protocol, or structure), because the type of migration determines the risks. Benchmark current rankings, traffic, top pages, and backlinks so you can prove the migration did not cost you later. Crawl the live site for a complete URL inventory, and agree a rollback plan and a low-traffic launch window before any work begins. ## Map every URL and redirect This is the step that makes or breaks a migration. Create a 1:1 mapping from every old indexed URL to its new destination, and write 301 (permanent) redirects, never 302s. Avoid redirect chains by pointing old URLs straight to the final destination, and update internal links to the new URLs rather than relying on redirects. ## Preserve on-page and content Rankings live in your content, so keep or improve titles, meta, headings, and body copy on migrated pages. Migrate or recreate structured data, carry canonical tags and hreflang across correctly, and never quietly drop a page that earns traffic or links without a redirect plan. ## Build and QA on staging Build the new site on a staging environment that is blocked from indexing (via noindex or authentication), and test the redirect map there before go-live. The most common own-goal is launching with the staging noindex still in place, so verify robots.txt and remove the block at launch. ## Launch and monitor Deploy the redirects at the moment of cutover, confirm the new site is crawlable and not noindexed, submit the new sitemap, and use the Change of Address tool for domain moves. Then watch Search Console coverage, crawl stats, and rankings daily for the first few weeks, fix 404s and broken redirects as they surface, and compare against your pre-migration baseline. ## Go deeper This is one of the focused lists in our [marketing checklists hub](https://piperocket.digital/checklists/). Pair it with the [technical SEO checklist](https://piperocket.digital/checklists/technical-seo-checklist/) for the crawl and indexing details, and the [complete SEO checklist](https://piperocket.digital/checklists/seo-checklist/) for the bigger picture. Launching a brand-new site instead of migrating one? Use the [new website SEO checklist](https://piperocket.digital/checklists/new-website-seo-checklist/) instead. ## How we use this at PipeRocket Digital We treat migrations as the highest-risk moment in a site’s life and run this checklist end to end. The redirect map and the post-launch monitoring window are where we spend the most time. If you have a migration coming up, [talk to us](https://piperocket.digital/contact-us/) before you launch, not after. ## Frequently Asked Questions ### What is an SEO site migration? An SEO site migration is any significant change to a website that can affect its search visibility: moving to a new domain, changing CMS or platform, redesigning, switching to HTTPS, or restructuring URLs. The goal of migration SEO is to make the change without losing rankings, traffic, or link equity. ### Why do rankings drop after a migration? Almost always because of broken or missing redirects, changed URLs with no 1:1 mapping, dropped pages, a staging noindex left in place at launch, or lost on-page content. A complete redirect map and careful QA prevent the large majority of migration traffic losses. ### Should I use 301 or 302 redirects for a migration? Use 301 (permanent) redirects for a migration. A 301 tells search engines the move is permanent and passes ranking signals to the new URL. A 302 is temporary and can prevent those signals from transferring, so it is the wrong choice for a migration. ### How long does it take to recover after a site migration? If the migration is done well, you may see only a brief dip and recovery within a few weeks. Larger or messier migrations can take one to three months to stabilise. Close monitoring in the first weeks, and fast fixes for any 404s or redirect errors, shortens the recovery. ### What is the most important step in a site migration? The 1:1 URL redirect map. Every old indexed URL must 301 to its correct new destination without chains. Get that right and preserve your on-page content, and most other issues are recoverable; get it wrong and you lose rankings and link equity that are hard to win back.