--- title: "Run a site migration as a product launch so organic traffic survives" description: "Scope migration SEO as user stories, plan sprints from discovery to launch, set launch gates and recovery metrics, and brief stakeholders." canonical: "https://scalewithsearch.com/articles/site-migration-seo-product-managers" date: "2026-03-20" modified: "2026-09-25" --- ## Site navigation - [Scale With Search](https://scalewithsearch.com/) - Real estate - Real estate - [Real estate](https://scalewithsearch.com/for/real-estate) - Work - Start here - [Send your brief](https://scalewithsearch.com/work#send-your-brief) - [Prepare your six-question brief](https://scalewithsearch.com/work#prepare-your-six-question-brief) - Build - [Site build, content library with SEO, signal desk](https://scalewithsearch.com/work) - For your business - Trades and home services - [Auto body and collision shops](https://scalewithsearch.com/for/auto-body-and-collision-shops) - [Foundation and home repair contractors](https://scalewithsearch.com/for/foundation-and-home-repair) - [Garage door and fencing contractors](https://scalewithsearch.com/for/garage-door-and-fencing-contractors) - [HVAC contractors](https://scalewithsearch.com/for/hvac-contractors) - [Janitorial and commercial cleaning companies](https://scalewithsearch.com/for/janitorial-and-commercial-cleaning) - [Locksmiths](https://scalewithsearch.com/for/locksmiths) - [Moving companies](https://scalewithsearch.com/for/moving-companies) - [Pest control companies](https://scalewithsearch.com/for/pest-control-companies) - [Plumbing and electrical contractors](https://scalewithsearch.com/for/plumbing-and-electrical-contractors) - [Restoration and water or fire damage companies](https://scalewithsearch.com/for/restoration-and-water-fire-damage) - [Roofing companies](https://scalewithsearch.com/for/roofing-companies) - [Towing companies](https://scalewithsearch.com/for/towing-companies) - [Tree services and landscaping companies](https://scalewithsearch.com/for/tree-services-and-landscaping) - [Solar installers](https://scalewithsearch.com/for/solar-installation) - [General contractors](https://scalewithsearch.com/for/general-contractors-and-construction) - [Paving, concrete, and flooring contractors](https://scalewithsearch.com/for/paving) - Practices and professional services - [Bookkeeping and tax practices](https://scalewithsearch.com/for/bookkeeping-and-tax-practices) - [Dental practices](https://scalewithsearch.com/for/dental-practices) - [Family and criminal defense law firms](https://scalewithsearch.com/for/family-and-criminal-defense-law-firms) - [Med spas and aesthetics practices](https://scalewithsearch.com/for/med-spas-and-aesthetics) - [Personal injury law firms](https://scalewithsearch.com/for/personal-injury-law-firms) - [Veterinary clinics](https://scalewithsearch.com/for/veterinary-clinics) - [Gyms and fitness studios](https://scalewithsearch.com/for/fitness) - [Therapy and outpatient health practices](https://scalewithsearch.com/for/therapy-and-outpatient-health) - [Medical billing companies](https://scalewithsearch.com/for/medical-billing) - [Insurance agencies](https://scalewithsearch.com/for/insurance-agencies) - [Financial advisors](https://scalewithsearch.com/for/financial-advisors) - [Property management companies](https://scalewithsearch.com/for/property-management) - [Recruiting and staffing agencies](https://scalewithsearch.com/for/recruiting-and-staffing) - [Architects and interior designers](https://scalewithsearch.com/for/architects-and-interior-designers) - [Logistics and supply chain companies](https://scalewithsearch.com/for/logistics-and-supply-chain) - Agencies, MSPs, and manufacturing - [IT and managed service providers](https://scalewithsearch.com/for/it-and-managed-service-providers) - [Machine shops and precision manufacturers](https://scalewithsearch.com/for/machine-shops-and-precision-manufacturing) - [Marketing agencies and freelancers](https://scalewithsearch.com/for/marketing-agencies-and-freelancers) - [SEO agencies and consultants](https://scalewithsearch.com/for/seo-agencies-and-consultants) - [Small manufacturers and fabricators](https://scalewithsearch.com/for/small-manufacturers-and-fabricators) - Restaurants, shops, studios, and nonprofits - [Restaurants and hospitality businesses](https://scalewithsearch.com/for/restaurants-and-hospitality) - [Retail stores and ecommerce sellers](https://scalewithsearch.com/for/retail-and-ecommerce) - [Photographers, event planners, and travel agents](https://scalewithsearch.com/for/photographers) - [Churches and nonprofits](https://scalewithsearch.com/for/churches-and-nonprofits) - [All industries](https://scalewithsearch.com/for/) - Learn - For your office - [Office job guides](https://scalewithsearch.com/guides/) - [Browser calculators](https://scalewithsearch.com/tools/) - Start here - [How it works](https://scalewithsearch.com/how-it-works) - [Free Starter Kit](https://scalewithsearch.com/kit/business-memory-starter-kit.zip) - [Synthetic specimen](https://scalewithsearch.com/specimen/working-session-specimen.zip) - Guides - [The Complete Guide to Business Memory for AI Agents](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [The Complete Small-Business Guide to AI Agent Governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [The Complete Guide to Leaving Vendor AI Memory](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - Articles by cluster - [Business memory](https://scalewithsearch.com/articles/business-memory-for-ai-agents-guide) - [Agent governance](https://scalewithsearch.com/articles/ai-agent-governance-guide-small-business) - [Migration and ownership](https://scalewithsearch.com/articles/leaving-vendor-ai-memory-guide) - For machines - [llms.txt](https://scalewithsearch.com/llms.txt) - [llms-full.txt](https://scalewithsearch.com/llms-full.txt) - [Machine view](https://scalewithsearch.com/?view=machine) - Company - Evidence - [Proof](https://scalewithsearch.com/proof) - Company - [About](https://scalewithsearch.com/about) # Run a site migration as a product launch so organic traffic survives. Your quarterly roadmap includes a platform migration. Engineering estimates eight weeks. Your SEO manager mentioned "redirect mapping" once, and you assumed engineering would handle it. By day 3 after launch, traffic is down 65%, and your CEO asks why organic revenue fell. A migration is a product launch where the stake is retention, not acquisition. Existing organic traffic is the baseline, and your job is to keep it. Product managers (PMs) who treat a migration as an engineering-only project find out too late that nobody scoped, tested, or validated the SEO requirements. This guide treats the migration as a product initiative: requirements, sprint planning, launch criteria, and post-launch monitoring. The [migration SEO guide](/articles/site-migration-seo-guide) covers the SEO method by migration type. This article covers how you run it. ## Own the outcome, not only the process A common belief is that "the SEO team handles SEO." In practice, the SEO team names the requirements, and engineering implements them. You coordinate, prioritize, and validate. Without PM ownership, requirements fall through the cracks. The typical failure runs like this: 1. The SEO team delivers a redirect map of 5,000 URLs. 2. Engineering says, "We will handle it." 3. Engineering implements 80% of the redirects and deprioritizes the edge cases. 4. The edge cases include the small share of pages that bring most of the traffic. 5. The site launches, and traffic collapses. Your job is to make sure that the redirect map is complete, tested, deployed correctly, and validated after launch. ## Write the SEO requirements as user stories (sprints -4 to -2) Put each SEO requirement into the backlog as a story with acceptance criteria that engineering can estimate and accept. The [SEO user stories guide](/articles/seo-user-stories-engineering) covers the format in depth. **Story 1: redirect mapping.** ```text As a search engine crawler, I need each old URL to redirect to its equivalent new URL with a 301, so that rankings and indexing move to the new structure. ``` - [ ] Each URL in the current sitemap has a mapped destination. - [ ] Priority pages (the top 20% by traffic) have one-to-one matches. - [ ] No redirect chains: old URL to new URL in one hop. - [ ] Redirects are 301 (permanent), not 302 (temporary). - [ ] The SEO team reviewed and approved the map. The story is done when a spreadsheet lists old URL, new URL, and priority (P0, P1, or P2). Each P0 and P1 URL must also pass on staging. Engineering must also confirm that all redirects fit the timeline. For 5,000+ redirects, expect two to three sprints, depending on whether they go in the server configuration or the application. **Story 2: content parity.** ```text As a user, I need the same content, features, and information on the new site, so that I can complete my tasks as before. ``` - [ ] The top 100 pages by organic sessions have equivalent content. - [ ] Title tags and meta descriptions are kept, or changed on purpose. - [ ] Images, videos, and other media are moved or replaced. - [ ] Internal linking is intact, with no orphan pages. - [ ] Forms, calls to action, and conversion paths work. The story is done when a content audit compares old and new pages by URL, old word count, new word count, and change. QA must confirm the top 20 pages, and the SEO team must approve parity. **Story 3: technical SEO configuration.** ```text As a search engine crawler, I need sitemaps, robots.txt, canonicals, and schema configured correctly, so that I can crawl, index, and rank the new site. ``` - [ ] The XML sitemap lists the new URLs and is submitted in Google Search Console. - [ ] robots.txt allows crawling of each indexable page. - [ ] Canonical tags reference each page's own URL. - [ ] JSON-LD schema is kept from the old site. - [ ] No `noindex` tags on indexable pages. - [ ] Pages pass a mobile test in Lighthouse. Google retired its Mobile-Friendly Test in December 2023. - [ ] HTTPS is enforced, if it applies. The story is done when staging passes the SEO team's pre-launch checklist. Search Console must be set up for the new domain or structure, and analytics tracking must pass a test. Developers can use the [developer's migration checklist](/articles/site-migration-seo-checklist) as the test plan. ## Plan the sprints | Sprint | Deliverables | Who does what | Your checkpoint question | |---|---|---|---| | -4: discovery and baseline | A full crawl export; the top 200 pages by organic traffic for 12 months; pages with 5+ referring domains; a draft redirect map | SEO runs crawls and drafts the map. You mark high-risk pages (top traffic and top links). Engineering confirms feasibility. | Is the inventory complete, including old campaigns and forgotten subdirectories? | | -3: final redirect map | Each URL mapped; P0, P1, and P2 priorities; the implementation method | SEO resolves edge cases such as removed and merged pages. You protect P0 and P1 if scope must shrink. Engineering implements on staging. | Does the map cover URL parameters, pagination, and filter combinations? | | -2: staging and QA | Staging live with redirects; a manual check of the top 50 pages; the pre-launch checklist complete | Engineering deploys. SEO crawls and validates. QA tests forms, checkout, and user flows. You own the checklist and block launch on critical issues. | Does testing cover mobile, browsers, and URL patterns? Is staging a true copy of production? | | -1: launch readiness | A deployment plan with timeline and rollback; a monitoring dashboard for Search Console, GA4, and rank tracking; a communication plan | Engineering prepares the deploy and confirms rollback. SEO sets up monitoring and a triage plan. You set the timing and confirm that each team is ready. | Is there a rollback plan? Do stakeholders expect a 10 to 20% dip in week 1? | | 0: launch week | Redirects live with the new site; real-time monitoring | A daily standup on days 1 to 5 reviews the page indexing report, GA4 organic traffic against baseline, server log 404s, and the top 20 keywords. | Are redirects live, is the site indexable, and is analytics tracking? | If traffic is down more than 30% by day 3 and does not settle, check three things at once. Test 20 to 30 old URLs by hand to confirm that redirects are live. Look for `noindex` tags and robots.txt blocks. Confirm that GA4 and Search Console data still flow. Do not launch on a Friday afternoon. Issues that surface over the weekend cost three days of recovery time. ## Set the metrics before launch Agree on the metrics and thresholds before launch. Otherwise, the team argues about whether a number is normal instead of comparing it with a benchmark. The ranges below are planning estimates. ### Leading indicators, days 1 to 7 | Metric | How to measure | Target | Red flag | |---|---|---|---| | Redirect success rate | Test 100 random old URLs for a 301 to the right new URL. | 98% or more | Under 90% | | New indexing errors | Search Console page indexing report: new 404s, server errors, and noindexed pages | Under 50 in the first 7 days | Over 500, which points to a systemic problem | | Crawl activity | Search Console, Settings, then Crawl stats | Often up 20 to 50% in days 1 to 3 as Google follows redirects | Crawling falls, or shows many 404 and 500 responses | ### Lagging indicators, days 7 to 90 | Metric | How to measure | Expected path | Red flag | |---|---|---|---| | Organic traffic | GA4 traffic acquisition report, organic search sessions | Down 10 to 30% in days 1 to 7, 85 to 95% of baseline by day 14, 95 to 100% by day 30, then growth | Under 80% of baseline at day 30 | | Indexed pages | Search Console page indexing report | Within 10% of the pre-migration count by day 30 | Down more than 30% with no recovery by day 30 | | Keyword rankings | Top 50 keywords each week in Ahrefs, Semrush, or Moz | Moves of 3 to 5 positions in weeks 1 to 4, settled by weeks 6 to 8 | Top-10 keywords out of the top 20 with no recovery in 60 days | ## Triage and stabilize after launch **Week 1: respond.** Hold a morning standup on overnight metrics: Search Console errors, GA4 traffic, and server logs. Add redirects for new 404s. Answer support tickets about broken links and missing pages. Rank the fixes, because 404s are not equal. A 404 on a page with 5,000 backlinks is critical. A 404 on a 2019 post with no traffic can wait. Expect 50 to 200 missed redirects from edge cases, broken images from CDN misconfiguration, and forms that do not submit. If traffic is down more than 40% by day 5, escalate to the executive team. The cause is likely major: a sitewide `noindex`, a robots.txt block, or a redirect misconfiguration. **Weeks 2 to 4: stabilize.** Recrawl the full site with Screaming Frog each week and compare indexed pages with the baseline. Expect to find orphan pages, redirect chains that the migration added, and content that did not move. Update stakeholders on recovery, fixed issues, and open risks. Own the story. At 85% of baseline in week 2, say: "We are on track for full recovery by week 4. The remaining issues are in the backlog, in priority order." **Months 2 and 3: validate.** Review with the SEO lead and the engineering lead each month. Check four things. Traffic is at 95% of baseline or more, and the top 20 keywords are back in position. Indexed pages are within 10%, and organic conversion rate is back to baseline. If all four recovered, the migration succeeded; document the lessons. If metrics are still under 90% of baseline, investigate further. Likely causes are URL changes that were not redirected properly, lost content, or a technical regression such as slower pages or broken schema. If traffic has not recovered after 90 days, run a post-mortem. Common causes are a URL structure so different that Google treats the site as new, weaker content on migrated pages, and unresolved technical problems. ## Build safety nets **Phased migration.** Move one section at a time. For example, move `/blog` (200 pages) in week 1, `/products` (500 pages) in week 3, and `/resources` (100 pages) in week 5. A failure in one phase does not touch the others. The cost is a longer timeline and a mixed experience while sections sit on different platforms. Use phases for sites of 5,000+ pages and in risk-averse organizations. Also use them for high-risk moves, such as a domain and platform change together. **A rollback plan.** Be able to revert within hours. Keep the old site live on an internal URL. Configure DNS or the CDN for an instant switch back, and make the redirect rules easy to turn off. Set the trigger during planning, such as traffic down more than 50% by day 3 with no clear fix. Get executive agreement before launch. **Parallel running.** Run old and new sites at the same time for one to two weeks, and shift users gradually. Send 10% in week 1, 50% in week 2, and 100% in week 3. Small-scale exposure catches issues early. It needs a load balancer or CDN routing and strong engineering. Keep crawlers on one consistent version during the shift, with canonicals that point to the final URLs. Google then does not see two competing sites. Use this for critical, high-revenue sites and for sites with weak test coverage. ## Keep stakeholders informed Use four messages. The [SEO communication templates](/articles/seo-communication-templates-by-role) give more formats by audience. **Two weeks before launch, to executives, marketing, and support:** "We move [old site] to [new platform or domain] on [date]. Expected downtime: [none or minimal]. Expect a temporary traffic dip of 10 to 20% in week 1, with recovery by week 3. We tested on staging, and we will monitor closely after launch." This message sets expectations for the week-1 dip. **On launch day, to internal teams:** "The migration went live at [time]. Monitoring is in progress, and early metrics look good. Report any broken links or missing pages to [PM or SEO lead]." Support teams often find broken links before engineering does. **At the end of week 1, to executives:** "Traffic is at [X]% of baseline, inside the expected range of 80 to 90%. We fixed [Y] issues, and [Z] are in progress. Full recovery is on track for week 3." This shows control. **At the month-1 retrospective, to executives and the team:** "The migration is complete, and traffic is at [X]% of baseline. Here is what went well and what we will change next time." Compare the result with the traffic that an unplanned migration would have lost. That comparison builds the case for SEO scope in the next migration. ## Avoid six PM mistakes - **An engineering-only project.** You delegate, engineering does not know the SEO requirements, and the launch fails. - **SEO work outside the sprint plan.** If redirect mapping and testing are not in Jira, engineering deprioritizes them, and the site launches without redirects. - **A Friday launch.** Weekend issues cost three days. - **No agreed metrics.** The team debates what is normal instead of comparing results with benchmarks. - **Ignored edge cases.** "We will redirect the top 80%" skips long-tail pages that carry major links or conversions. - **No rollback plan.** Traffic collapses, and nobody can revert fast. ## Answer common PM questions **How much engineering time should SEO get?** About 20 to 30% of the total migration effort. On an eight-week migration, plan 1.5 to 2.5 weeks for redirects, testing, and configuration. **Should an agency run the migration?** An agency can audit and advise, but your engineers still implement. An agency helps when your team lacks SEO expertise. It does not replace planning. **What if engineering says redirects are not feasible?** Push back. Redirects are always feasible; the question is cost and complexity. Ask what the alternative is. There is none, so redirects are non-negotiable. **Can redirects come after launch?** No. Even 24 hours without redirects lets Google crawl 404s and drop pages. Redirects added later bring the pages back more slowly, and some rankings can take months to return. **What if the new platform limits redirects?** Some hosted platforms limit the number or the patterns of redirect rules. Check the limits before you choose the platform. Workarounds are redirects at a CDN such as Cloudflare, or a different platform. Accepting the traffic loss is the last option. **How do you convince executives to delay launch for SEO work?** Quantify the risk. Compare the engineering cost of a two-week delay with six months of organic revenue lost to a 60% drop. Present both numbers from your own analytics and finance data. **When should you migrate?** In a low-traffic period. Ecommerce avoids the fourth quarter, and B2B avoids the end of a quarter. A dip hurts less from a lower baseline. The [SEO guide for product managers](/articles/seo-for-product-managers) covers how to fit this work into the wider roadmap. ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```