# SEO Migration Services: Checklist and 90-Day Plan **URL:** https://mettevo.com/blog/article/seo-migration-services **Published:** 2026-10-22 **Updated:** 2026-10-22 **Author:** Oleg Silin **Category:** Blog | Mettevo > Get expert SEO migration services from Mettevo Digital Agency. Protect rankings, preserve organic traffic, and ensure a smooth website migration without SEO losses. ![SEO Migration Services](https://stage.mettevo.com/wp-content/uploads/2026/10/SEO_specialist_moving_WWW_logo_20261022173443.jpg) --- SEO migration services are the search work attached to a site move: mapping ranking URLs to new destinations, testing redirects before launch and monitoring recovery for 90 days. [Google's site-move documentation](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) expects ranking fluctuations, and medium-sized sites can need “a few weeks or more” for new URLs to replace old ones, so honest providers sell controls, not zero loss. ## **TL;DR** - An SEO migration is the search layer inside a site move, delivered in three phases: pre-launch, launch and 90 days of monitoring. - Google says redirecting many old URLs to one irrelevant destination, such as the home page, might be treated as a soft 404 error. - Mettevo scopes the work for small sites, mid-market and and for enterprise. - [Google expects ranking fluctuations](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes), so treat a zero-loss promise as a sales line and ask for dated reports to day 90. - On [mettevo.com](http://mettevo.com) in September 2026, [four of 247 pages carried 87% of one week's clicks](https://mettevo.com/blog/article/how-to-redesign-website-without-losing-seo), so hand-review the top of the redirect map. ## **What is an SEO migration, and what should it include?** An SEO migration is the set of search controls that keeps a site's rankings, backlinks and crawl access intact while its platform, domain, protocol or URLs change. A provider inventories ranking URLs, maps each to a destination, tests the result on a private staging copy, supervises launch and tracks recovery against a baseline. Phase Work Evidence to ask for Pre-launch Baseline export, URL inventory, tiered redirect map, staging crawl. Inventory with clicks and links per URL, second-reviewed map, crawl report. Launch Redirect test, removal of test blocks, sitemap submission, go or no-go. Signed checklist, redirect test log with status and hop count. Post-launch Indexing, crawl and traffic checks by URL group, fixes. Dated reports at days 1, 7, 14, 28, 56 and 90, with a fix list. ### **What is the difference between a site migration and an SEO migration?** A site migration is the engineering project that moves a site to a new platform, host, domain or design, and site migration services deliver it. An SEO migration is the search layer inside that project: the inventory, redirect map, indexing controls and monitoring that let Google follow the move. You can buy it alone or inside a rebuild quote. ## **Which migration type are you running, and what breaks by default?** Google documents [moves that change URLs](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) separately from moves that do not, such as a hosting change. The table covers six types. Type What changes What breaks by default Platform swap Content management system or store platform. Shopify redirects only from broken URLs and refuses sources starting with /shop, the base many WooCommerce stores use ([Shopify redirect help](https://help.shopify.com/en/manual/online-store/menus-and-links/url-redirect), [our WordPress to Shopify guide](https://mettevo.com/blog/article/wordpress-to-shopify-migration)). A WordPress site with “Discourage search engines from indexing this site” ticked outputs a noindex,nofollow tag ([WordPress Reading settings](https://wordpress.org/documentation/article/settings-reading-screen/)). Domain change Host name, so every URL. Redirects stop at the home page. Google asks for a Change of Address in Search Console, with both properties owned. HTTPS (Hypertext Transfer Protocol Secure) Protocol. Mixed content, canonicals still on http and expired or mismatched certificates URL restructure Paths and slugs. Pattern rules that over-match, redirects stacked on older redirects, and internal links still pointing at old URLs, which Google says to replace ([site-move guide](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes)). Site consolidation Several sites or sections become one. Many old URLs sent to one unrelated page, which might be treated as a soft 404. A consolidated page on the same topic is a valid target ([site-move guide](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes)). Headless rebuild Rendering and delivery, for example a WordPress back end with a Next.js front end. Google discovers links only in anchor elements with an href attribute ([JavaScript SEO basics](https://developers.google.com/search/docs/crawling-indexing/javascript/javascript-seo-basics)). A noindex tag in the initial source may make Google skip rendering, so a script that removes it may never run. A temporary redirect status where a permanent one was meant does not signal the new URL as canonical ([redirects guide](https://developers.google.com/search/docs/crawling-indexing/301-redirects)). ## **How do you avoid losing SEO during a site migration?** You avoid avoidable loss by controlling what Google can see: which URLs exist, where old ones point, what crawlers may index and what the new pages say. This 15-point website migration SEO checklist covers all four. 1. **Baseline.** Export [16 months of Search Console data](https://developers.google.com/search/docs/monitor-debug/debugging-search-traffic-drops) by page and query, plus analytics landing pages. 2. **Inventory.** Merge a live crawl, the sitemap, Search Console pages, analytics landing pages and backlink targets. 3. **Tiers.** Tier 1: URLs with clicks or external links. Tier 2: other indexed URLs with impressions. Tier 3: the rest. 4. **Hand-mapped top slice.** Every Tier 1 and 2 URL gets a specific destination, second-reviewed, never the home page. 5. **Tail rules.** Pattern rules cover Tier 3; URLs with no successor return 404 or join a consolidated page. 6. **Redirect mechanics.** One server-side permanent hop (301 or 308) from every old URL variant. 7. **Platform limits.** Check caps and source rules, such as [Shopify's 100,000-redirect cap outside Plus](https://help.shopify.com/en/manual/online-store/menus-and-links/url-redirect) and its broken-URLs-only rule. 8. **Staging crawl.** Compare status codes, titles, H1s, canonicals and internal links with the live inventory. 9. **Rendering check.** Compare page source with the rendered page; missing pages must return a real 404 status. 10. **Redirect test.** Run the whole map on staging; every target returns 200 in one hop. 11. **Directive audit.** List every noindex rule, robots.txt block and indexing toggle used in development, each with an owner. 12. **On-page parity.** Titles, descriptions, headings, hreflang annotations and structured data match on Tier 1 and 2 pages. 13. **Final-URL links.** Internal links, canonicals and the new sitemap point only at final 200 URLs. 14. **Accounts.** Own Search Console properties for old and new hosts, preferably domain properties, and carry over verification files. 15. **Go or no-go.** Written pass criteria, a named launch owner and a rollback trigger, agreed before cutover. ## **What did we find when we audited our own site first?** We ran two small measurements on mettevo.com, a WordPress and Next.js site, before writing this guide. Neither is a benchmark. Measurement Method and date Result Shopify handle collisions Sitemap fetched September 14, 2026, each URL reduced to its last path segment ([our WordPress to Shopify guide](https://mettevo.com/blog/article/wordpress-to-shopify-migration)). 416 URLs; 2 collisions: /niches/ui-ux-design with /web-design/ui-ux-design, and /niches/web-development with /web-development; 10 archive URLs with no Shopify equivalent. Click concentration Search Console Performance report, seven days to September 28, 2026 ([our redesign SEO guide](https://mettevo.com/blog/article/how-to-redesign-website-without-losing-seo)). 247 pages with impressions; 11 with clicks; 4 pages took 87% of clicks. Four of 247 pages, 1.6%, carried 87% of the clicks. A failed redirect on those four URLs would put 87% of that week's clicks at risk, against 13% for all other pages combined. So we hand-map the top slice, cover the long tail with pattern rules and sort the map by clicks, not by folder. The collisions show why a mapping test belongs before design approval: each pair of pages wanted the same Shopify handle, and a person must decide which keeps it. Both come from one agency site, not a store, so the /shop collision that hits WooCommerce stores did not apply. One week of clicks is a small sample, and neither measurement shows traffic before and after a migration. ### **How long does an SEO migration take?** An SEO migration runs from the first inventory to day 90 after launch. Mettevo's [web development page](https://mettevo.com/web-development) lists builds at 4 to 8 weeks for a corporate website and 6 to 12 for an ecommerce store, and the SEO work overlaps them. Add 13 weeks of monitoring and an ecommerce project spans roughly 19 to 25 weeks. ## **What should you ask an SEO migration provider before signing?** [Google's guide to hiring an SEO](https://developers.google.com/search/docs/fundamentals/do-i-need-seo) suggests asking about expected results, how success is measured and whether the provider shares every change. These seven questions adapt that list. 1. **Who reviews the redirect map, and can I see a redacted one?** Good answer: a named second reviewer and a real map with clicks per URL. 2. **What do you crawl on staging, and what fails the launch?** Good answer: raw and rendered crawls, with written pass criteria. 3. **How do you rank URLs for hand review?** Good answer: by clicks and backlinks, not by folder. 4. **Who can ship a redirect fix on day two?** Good answer: a named engineer with server access and a same-day target. 5. **What will you report, and against which baseline?** Good answer: dated reports per URL group, against baseline and last year. 6. **What do you promise?** Good answer: deliverables and dates. Bad answer: a traffic number. 7. **What is out of scope, and who owns it?** Good answer: named owners for content changes, hosting and analytics. ### **Which red flags should end the conversation?** - **A zero-traffic-loss guarantee.** Google expects ranking fluctuations and says, “No one can guarantee a #1 ranking on Google.” I treat one as a reason to walk away. - **No redirect map review.** Unchecked pattern rules from one person decide where your ranking URLs land. - **No staging crawl.** You meet the new site's errors in production, with Google watching. - **No post-launch monitoring plan.** If reporting stops at launch, nobody owns days 2 to 90. ## **What does the 90-day post-migration recovery plan look like?** Google says medium-sized sites can need “a few weeks or more” before new URLs replace old ones in results. We judge recovery per URL group against the pre-launch baseline, with a tolerance agreed before launch, and compare with the same dates last year because seasonality is a listed cause of traffic drops. Window Cadence What to check Day 0 to 1 Hourly, then end of day. Old-URL sample returns one permanent hop to a 200 page; robots.txt and noindex clear; sitemap submitted; Crawl Stats host status clean. Days 2 to 14 Daily. Page indexing report: Not found (404), Soft 404, Page with redirect and URL marked ‘noindex’; 404s on URLs that had clicks. Days 15 to 56 Weekly. Clicks by URL group (product pages, blog posts) against baseline; sitemap submitted versus indexed; Core Web Vitals report once its 28-day window reflects the new site, around day 35. Day 57 onward Monthly, with the day 90 report. 28-day windows against baseline and last year; leftover 404s and chains. The Change of Address tool acts for 180 days, but Google advises keeping redirects generally at least a year. Retire one only when server logs show no meaningful requests. ## **FAQ** ### **Can any provider guarantee zero traffic loss in a migration?** No. Google expects ranking fluctuations while it recrawls and reindexes a moved site, and says, “No one can guarantee a #1 ranking on Google.” A provider can guarantee process instead: a second-reviewed redirect map, a staging crawl, a launch checklist and dated reports for 90 days. ### **Should you change domain, platform and URLs at the same time?** Avoid it. Google advises planning changes “one after the other, not everything at the same time.” Combined launches make it hard to tell which change caused a drop. Small and medium sites should move all URLs at once, and large sites can move one section at a time. ### **Do you need the Change of Address tool for an HTTPS or www move?** No. The tool for a move to HTTPS is not needed, because Google will figure out the changes. Handle www and non-www moves with canonical tags or redirects instead. Use the tool for a move between domains or subdomains, once you own both properties and the 301 redirects are live.