Skip to main content
+1 (307) 310-6766hi@hoopinteractive.comSoftware, AI and marketing, one team
Server racks with cables in a data centre
Digital MarketingNov 20, 20269 min read

Site Migration Checklist

Every site migration shares five core SEO checks, but each type of move (redesign, CMS or platform change, ecommerce replatform, HTTPS, URL changes, subdomain moves, merged sites and domain changes) breaks something different. This checklist covers the extra steps for each.

S

Sahar

Content Writer

A site migration checklist has to match the move you are making. A redesign on the same platform, a switch from WordPress to Shopify, a move to HTTPS and a merger of two websites all carry risk, but they break different things. This guide starts with the site migration SEO checks every type shares, then gives the extra steps for each kind of move, so you can pick the sections you need. It complements our phase-by-phase website migration checklist, which explains when each task happens.

Need this done right?

Hoop builds the strategy, design and development behind sites like this one, talk to us about yours.

Start Your Project

The Site Migration SEO Checklist Every Type Shares

Whatever you are changing, every SEO site migration needs these five checks. They are the core of any site migration SEO checklist; the sections below add to them, never replace them.

  1. URL inventory: every URL with traffic, links or rankings, from a crawl, the sitemap, analytics and backlink data.
  2. Redirect map: each old URL mapped to its closest new page with a single permanent redirect.
  3. Staging crawl: the new site crawled before launch for content, titles, canonicals, indexing settings and internal links.
  4. Benchmark: traffic, rankings, Search Console data and indexed pages saved before anything changes.
  5. Search Console monitoring: indexing, errors and performance checked daily after launch, then weekly.

If you are not sure which type of move you are making, our explainer on what website migration is describes each one.

Redesign: The Website Redesign SEO Checklist

A redesign is the migration most people underestimate, because URLs often stay the same. But rankings depend on more than URLs: the content on the page, its headings, the internal links pointing to it and how fast it loads all change in a redesign. Use this website redesign SEO checklist:

  • Protect the content that ranks. For your top pages by organic traffic, compare old and new versions. Designers often shorten copy; if a page loses the sections that answered its main query, its rankings follow.
  • Keep the heading structure meaningful, with one H1 that still contains the page's main topic.
  • Check navigation and internal links. A new menu that drops a category, or a footer that loses links, changes how authority flows through the site.
  • Keep titles and meta descriptions unless you are deliberately improving them.
  • Measure speed on the new templates. Large hero images, video backgrounds and animation libraries are common causes of slower pages after a redesign.
  • Keep structured data on the templates that had it.
  • Check images: new file names and paths need alt text, and images with search traffic need redirects.

If the redesign is part of a rebuild, our website redesign team plans these checks into the design phase rather than after it.

Finally, re-test forms and calls to action on the redesigned templates, since layout changes often move or break them.

CMS or Platform Migration

A CMS or platform move changes how pages are generated, which usually changes URL patterns, templates and the way metadata is set. This CMS migration checklist covers the extra steps; it doubles as a platform migration checklist for any move between systems.

  • Document the URL pattern of every content type on the old and new platforms (pages, posts, categories, tags, authors, media) and map each.
  • List what plugins or modules did on the old site (titles, meta descriptions, canonicals, sitemaps, schema, redirects) and make sure the new platform does each job.
  • Migrate existing redirect rules from the old system, flattening any chains.
  • Decide what happens to archive, tag and author pages; many have little value and can be consolidated.
  • Check that media URLs and embedded files still resolve.

Moving to or from WordPress

A WordPress migration checklist adds a few specifics. WordPress builds URLs from its permalink setting, so match the old structure where you can, or map each post and page if you change it. Much of WordPress SEO is handled by plugins, so when moving away, recreate titles, meta descriptions, canonicals and schema in the new system; when moving to WordPress, choose one SEO plugin and configure it before importing content. Watch for category and tag base paths, attachment pages and old date-based URLs. Our WordPress development team handles moves in both directions.

Headless and JavaScript frameworks

Moving to a headless CMS or a JavaScript framework changes how pages render. Make sure titles, meta descriptions, canonicals, headings, body content and internal links are present in the HTML the server sends, not only after scripts run, and check rendered pages with Search Console's URL Inspection tool. Client-side routing must produce real, crawlable links and real URLs, with correct status codes for missing pages.

When we moved BeesApp, a retail-tech platform in Saudi Arabia, from a patchwork of PHP, Django and Vue to one Next.js, Flutter and FastAPI architecture, with the data migrated, load times fell by 74%; see the BeesApp case study.

Whatever the platform, run at least one full rehearsal: migrate a copy of the content, crawl the result and compare it with the old site before the real cut-over. Rehearsals surface mapping gaps, encoding problems and missing fields while there is still time to fix them calmly.

Ecommerce Replatforming: Shopify and Other Store Moves

An ecommerce site migration has more URLs, more templates and more data than most sites, and every product page can be a source of revenue. This ecommerce migration checklist, which doubles as a Shopify migration checklist, covers what stores need beyond the core checks:

  • Product URLs: every product mapped, including discontinued products that still have links or traffic (redirect them to the closest product or category).
  • Category and collection URLs: mapped one to one, including subcategories.
  • Variant URLs: decide how size and colour variants are addressed and canonicalised on the new platform.
  • Filter and search URLs: decide which faceted pages should be indexable; most should not.
  • Product content: descriptions, specifications, images and alt text carried over in full.
  • Reviews: migrated with their dates, and still marked up with structured data where eligible.
  • Structured data: product, price and availability markup present on the new templates.
  • Customer accounts and orders: migrated and tested; plan password resets if needed.
  • Feeds: shopping and marketplace feeds pointed at the new URLs before ads resume.

WordPress (WooCommerce) to Shopify migration

A WordPress to Shopify migration has one particular trap: Shopify uses fixed path prefixes. Products live under products/, collections under collections/, pages under pages/ and blog posts under blogs/ followed by the blog's name. WooCommerce URLs such as product/ or shop/ cannot usually be reproduced, so every product, category, page and post needs a redirect. Shopify has a built-in URL redirect feature that supports bulk import, documented in Shopify's help centre. Map the redirects in a spreadsheet, import them, then test them in bulk after launch. Our Shopify development and Shopify SEO teams run this kind of move together.

An example product URL map

Fictional URLs, to show the shape of the mapping.

Old URL (example)New URL (example)Note
shop/blue-mugproducts/blue-mugSame product, new prefix
product-category/mugscollections/mugsCategory becomes a collection
product-category/mugs/ceramiccollections/ceramic-mugsSubcategory flattened
shop/old-green-mug (discontinued, has links)collections/mugsClosest relevant page
shop/test-product (no traffic or links)None (removed)Allowed to return 404

Mapping in a table like this, then importing it, is far safer than relying on a platform's automatic redirects, which rarely cover categories, discontinued products and old campaign URLs.

HTTP to HTTPS Migration

An HTTP to HTTPS migration is technically simple but easy to do partially. Google treats a protocol change as a site move with URL changes, as its site-move documentation explains. For HTTPS migration SEO:

  • Install a valid certificate that covers every hostname you use, with and without www.
  • Permanently redirect every HTTP URL to its HTTPS equivalent, usually with one server rule.
  • Fix mixed content: images, scripts and stylesheets still loaded over HTTP.
  • Update canonicals, internal links, sitemaps and hreflang to HTTPS.
  • Add the HTTPS version to Search Console if you use URL-prefix properties, or use a domain property that covers both.
  • Consider HSTS once everything works, so browsers always use HTTPS.

URL Structure Changes

Changing folders or slugs, such as moving from services/web-design to web-design, or shortening long post slugs, is worth doing only when the new structure is clearly better for users and search, because every changed URL carries some risk. If you do it:

  • Map every changed URL one to one; never send a whole folder to one page.
  • Update internal links to the new URLs instead of relying on redirects.
  • Decide on one format for trailing slashes and letter case, and redirect the others.
  • Change structure once, not in several rounds, so search engines only process one move.

Is a URL change worth it?

Ask three questions before changing URLs. Will users understand the new structure better? Will it fix a real problem, such as duplicate paths, unreadable parameters or folders that no longer match your services? And can you map every changed URL properly? If the honest answer is that the new URLs are only slightly tidier, the safer choice is usually to keep the old ones and improve the pages instead.

Subdomain to Subfolder (and Back)

Moving a blog or shop between a subdomain such as blog.example.com and a subfolder such as example.com/blog is a common consolidation. It is a site move like any other: map and redirect every URL from the old location to the new one, update internal links and canonicals, add the content to the main sitemap, and keep both properties in Search Console so you can watch the old one empty and the new one fill. If the subdomain ran on a different platform, combine this with the platform checks above.

One practical detail is often missed: the subdomain's analytics, tag manager container and cookie settings may differ from the main site's. Bring them into line before the move, so reporting is continuous and consent works the same way across the merged site. Check that any separate sitemap for the subdomain is retired and its URLs appear in the main sitemap.

Merging Two Websites Into One

Merging two websites, after an acquisition or a rebrand, means deciding which pages survive. For each topic covered on both sites, keep the stronger page (more traffic, links and better content), fold the useful parts of the weaker one into it, and redirect the weaker URL to the survivor. Pages unique to the retired site move across with their own redirects. Keep the retired domain and its redirects live long-term, and ask the sites behind your most valuable backlinks to update them. Expect the merged site to take some time to settle in search while signals are consolidated.

Plan the content decisions before any redirects are written: list the topics on both sites, choose the surviving page for each, and agree what moves across from the retired page. Writers then merge content while developers prepare redirects, and the two lists meet on launch day.

Changing Your Domain

A domain change moves every URL at once and has its own steps, including Search Console's Change of Address tool. Our domain migration checklist covers it in full.

Which Checklist Do You Need?

Migration typeExtra risksSection
RedesignLost content, changed internal links, slower templatesRedesign
CMS or platformNew URL patterns, lost metadata, renderingCMS or platform migration
Ecommerce replatformProduct and category URLs, variants, reviews, feedsEcommerce replatforming
HTTP to HTTPSPartial redirects, mixed content, old canonicalsHTTP to HTTPS migration
URL structureMany changed URLs at onceURL structure changes
Subdomain or subfolderTwo properties, two sitemaps, internal linksSubdomain to subfolder
Merging sitesDuplicate topics, lost links from the retired siteMerging two websites
Domain changeEvery URL and link changesDomain migration checklist

Combined moves, such as a redesign on a new platform with a new domain, need every relevant section. The more you change at once, the more carefully you should test, and the more valuable an experienced second pair of eyes becomes.

Planning a site migration? Get a free SEO audit before you move. Our SEO migration services cover every type of move above, with the developers to build the new site in the same team.

“Every migration type breaks something different. The checklist has to match the move.”
Hoop Interactive

Key takeaways

  • 01Every type needs a URL inventory, a redirect map, a staging crawl, a benchmark and Search Console monitoring
  • 02Redesigns lose rankings through changed content and internal links even when URLs stay the same
  • 03Platform and ecommerce moves change URL patterns, so every product, category and post needs a mapped redirect
  • 04HTTPS, subdomain and merged-site moves each have their own traps, from mixed content to duplicate pages
S

Written by

Sahar

Content Writer

site migration checklistsite migration seoseo site migrationsite migration seo checklist
FAQ

Frequently Asked
Questions

Everything you need to know before booking a strategy call. Can't find your answer? Contact us directly.

Ask hoop

Usually replies in minutes

What is the riskiest type of site migration?

Domain changes and full replatforms that also change URLs. A domain change moves every URL and every link at once, and a replatform changes templates, URL patterns, rendering and data together. The more things change at the same time, the more places traffic can be lost, and the harder it is to tell which change caused a problem.

PEOPLE ALSO ASK

Swipe for 3 more questions →

Can't find your answer? Contact us directly.

Book a Free Call