--- title: "Protect your rankings through a domain, platform, HTTPS, or URL migration" description: "Plan, launch, and recover a site migration by type (domain, platform, HTTPS, or URL structure), with recovery targets and a diagnosis list." canonical: "https://scalewithsearch.com/articles/site-migration-seo-guide" date: "2026-03-20" modified: "2026-10-02" --- ## 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) # Protect your rankings through a domain, platform, HTTPS, or URL migration. Your agency recommended a new CMS. The redesign launched on Friday. On Monday morning, organic traffic is down 60%. Google Search Console shows 4,000 404 errors, and the old URLs redirect to the home page instead of to equivalent new pages. Recovery can now take 6 to 12 months. Migrations destroy rankings when a team treats them as IT projects instead of SEO projects. The new platform works; the URLs, redirects, and content structure do not. Google cannot match old pages to new ones, reads the migration as mass deletion, and drops pages from its index. This guide covers four migration types: domain changes, platform changes, HTTP to HTTPS, and URL structure changes. The method is the same for each. Preserve the URL mapping, keep content parity, redirect correctly, and monitor closely. Developers can run each step as a pass or fail test with the [developer's migration checklist](/articles/site-migration-seo-checklist). ## Choose the migration branch before planning | Change | What should remain stable | Evidence needed when recovery fails | |---|---|---| | Platform | URLs, reader tasks, primary content, tracking definitions | Old/new rendered HTML, response headers, forms, performance traces, and indexing directives | | Domain | Page-to-page task match and content | Full old/new map, domain-property verification, redirect headers, final canonicals, crawl logs | | URL structure | Content and page relationships | Every historical URL’s mapped final response, internal-link graph, canonical and sitemap comparisons | | Content consolidation | Useful substance and the intended reader task | Before/after sections, query intent review, survivor rationale, one-hop redirects, link updates | | HTTP to HTTPS | Host and path equivalents | Protocol redirects, certificates, mixed-content checks, HTTPS canonicals and sitemap | Combine branches only when the release requires it. A CMS switch with unchanged URLs first needs rendering and directive checks. A domain move first needs verified page mappings and property scope. A consolidation needs content and intent evidence even when every redirect works. [Google’s site-move documentation](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes) explains URL mapping and move monitoring. ## Plan 2 to 4 weeks before launch ### Crawl the existing site Inventory each URL, the current structure, and the baseline metrics. Use Screaming Frog, Sitebulb, or the Semrush Site Audit. Export these fields for each URL: - The URL, including URLs that do not return 200. - The title tag, meta description, and H1. - The word count. - The count of internal links to the page. - The response code (200, 301, 404, 500). - The canonical tag and any `noindex` tag. This export becomes the source for the redirect map. A URL missing from it does not get a redirect. On a mid-size site, expect 10,000 to 15,000 or more rows. ### Find the pages that cannot break Export organic landing pages from GA4 for the last 12 months and sort them by sessions. Take the top 20%, and cross-reference them with conversion data to see which pages bring leads or sales. Tag them "priority 1" in the redirect map. If the home page and 50 blog posts bring 80% of organic traffic, those pages are non-negotiable, and the other 500 matter less. That triage decides where effort goes when the timeline is tight. ### Export backlinks Export target URLs, referring domains, their domain rating, and anchor text from Ahrefs, Semrush, or Majestic. Sort by the number of referring domains. A page with 50 linking domains that loses its redirect wastes more value than 100 pages with no links. ### Map old URLs to new URLs Map each old URL to its equivalent new URL, one to one. Decide the new URL structure with the developers first. For example: ```text Old URL: domain.com/blog/2024/01/email-marketing-tips New URL: domain.com/blog/email-marketing-tips ``` Handle three edge cases: - **A page removed entirely:** redirect it to the most relevant existing page. If nothing is relevant, return 410. Do not redirect it to the home page, which Google can treat as a soft 404. - **Several old pages merged into one:** redirect each old URL to the merged page. - **New pages with no old equivalent:** these need no redirect. Every URL in the crawl export gets a mapping, with no exceptions. Mark pages that you deliberately do not redirect as "410 intentionally" or "noindex". ### Stand up a staging site Build a staging site, such as `staging.domain.com`, with the same content and structure as production and all redirects in place. Block it from indexing with a `noindex` header or password protection. Most migration disasters surface after launch because nobody tested staging properly. ### Use the release checklist on staging Run the developer’s migration checklist for mapping, final status, self-canonical, indexing directives, content parity, and rollback evidence. Assign an owner to each check. Save the output before launch, then repeat the response and rendering checks on production. Keep URL, platform, content, and tracking changes separate where possible. When they must ship together, record each in the change log. Otherwise a later decline has several plausible causes and no clear test. ## Launch with the evidence ready Deploy the new site and its redirect configuration together. Have the developer verify old URLs through to their final responses, and have the content owner inspect priority pages. The release checklist carries the full pass/fail procedure. Submit the new sitemap through the verified production property. The [XML sitemap guide](/articles/xml-sitemap-best-practices-developers) covers generation. Watch request failures and server logs for immediate faults. Use finalized search data for later ranking comparisons, since it does not provide a real-time release check. ## Recover in weeks 1 to 12 ### Week 1: triage Each day, read the page indexing report for new errors and add redirects for any new 404s. Watch organic traffic, which usually settles within 3 to 7 days. Check the top 20 keywords: small moves are normal, and drops of 50% or more signal a problem. As a planning range, traffic can fall 10 to 30% in days 1 to 3 while Google recrawls. It recovers to 85 to 100% of baseline by days 4 to 7, and it settles or grows in week 2. Three red flags need action. Traffic is down more than 40% with no recovery by day 7. Indexed pages are down more than 30%. Top keywords fall out of the top 20. If you see one, work through these checks: 1. Confirm that each priority page redirects correctly. 2. Search the new site for stray `noindex` tags. 3. Confirm that canonicals point to the new URLs, not the old ones. 4. Confirm that robots.txt does not block the new site. ### Month 1: full audit Crawl the new site with Screaming Frog and compare it with the pre-migration crawl: - **Indexed pages:** within 10% of the pre-migration count in the page indexing report. - **404 errors:** investigate each "Not found" URL with a traffic or link history. - **Redirect chains:** the migration must not add new ones. - **Orphan pages:** pages with no internal links are common after migrations. - **Content parity:** the top 20 pages keep their word count within 10%. Fix in this order. First, add redirects for 404s that have links or traffic. Then collapse redirect chains, and add internal links to orphans. ### Months 2 and 3: refine Track keyword positions each week in Ahrefs or Semrush. Most keywords return to their pre-migration positions, or better, within 60 to 90 days. For pages that have not recovered, request indexing again with the URL Inspection tool. Ask high-authority sites that still link to old URLs to update their links. Google has said that 301 redirects pass full ranking signals, so this is not about a loss per hop. Direct links remove the dependency on the redirect and save a hop for users. ## Adjust for your migration type ### Domain change A domain change, such as `domain-old.com` to `domain-new.com`, adds four steps: - Implement 301 redirects at the server or edge, not only canonical tags. - Use the Change of Address tool in Search Console after you verify both domains. - Keep the old domain registered and its redirects live for at least 12 months, and longer if possible. Do not let it expire. - Update your Google Business Profile, social profiles, and email signatures. Watch brand search. If people still search for the old brand name, rankings can dip until recognition shifts. The [SEO during a rebrand guide](/articles/seo-during-rebrand-executives) covers the brand side. Expect 90 to 180 days for full recovery, because signals move to the new domain over time, not at once. ### Platform change A platform change, such as WordPress to Webflow or Shopify to a custom build, adds these steps: - Keep the URL structure if you can; that is the easiest path. - If the structure changes, rely on the redirect map. - Confirm that the new CMS produces clean HTML without render-blocking problems. - Re-implement schema markup, which often gets lost in a CMS change. - Test form submissions and checkout. A broken conversion path costs more than a ranking dip. The common pitfall is a new CMS that generates URLs differently, such as WooCommerce product URLs against custom URLs. Developers must either match the old structure or map every URL. ### HTTP to HTTPS A protocol change adds five steps: - Redirect each `http://` URL to its `https://` equivalent with a 301. - Update internal links to `https://`; do not rely on redirects alone. - Update canonical tags to the `https://` versions. - Resubmit the sitemap with `https://` URLs. - Add the `https://` property in Search Console, or use a domain property that covers both. This is the simplest migration, and it rarely causes ranking drops when done correctly. Google announced HTTPS as a light ranking signal in August 2014. ### URL structure change Common restructures remove dates (`/blog/2024/01/15/post` to `/blog/post`), flatten hierarchy (`/category/subcategory/post` to `/blog/post`), or replace parameters (`/products?id=123` to `/products/item-name`). Map and redirect every old URL. Update internal links to the new structure, so that the site depends less on redirects. Submit the new sitemap. The risk is high if the map is incomplete, because each missing redirect is a 404 and lost traffic. For multilingual sites of any type, map each language version separately. After launch, confirm that hreflang points to the new URLs. The [hreflang implementation guide](/articles/hreflang-implementation-guide) covers the tags. ## Measure success on six metrics | Metric | Source | Target | |---|---|---| | Indexed pages | Search Console page indexing report | Within 5 to 10% of the pre-migration count within 30 days | | Organic traffic | GA4 | 95 to 100% of baseline within 60 days; a 10 to 20% dip in weeks 1 and 2 is acceptable if it recovers by weeks 4 to 6 | | Keyword rankings | Ahrefs or Semrush | Top 20 keywords within 2 positions of their pre-migration rank within 90 days | | Referring domains | Ahrefs or Semrush | Stable; a sudden drop points to broken redirects | | Core Web Vitals | Search Console or PageSpeed Insights | Same or better LCP, INP, and CLS. INP replaced First Input Delay as a Core Web Vital in March 2024. | | Organic conversion rate | GA4 | Within 5 to 10% of baseline | The migration succeeds when all six metrics recover within 90 days. If any metric is still more than 20% below baseline at day 90, the migration left SEO issues unresolved. ## Diagnose a migration that does not recover Work through eight checks in order: 1. **Redirects are live.** Test 50 to 100 old URLs with a bulk redirect checker. 2. **No stray noindex.** Search the new site's source for ``. This is a common cause of post-migration collapse. 3. **The right Search Console property.** Confirm that you added and monitor the new domain or protocol. 4. **robots.txt.** Open `domain.com/robots.txt` and confirm that it does not block important pages. 5. **Canonicals.** Confirm that they point to new URLs, not old ones. 6. **Structure.** Crawl the new site for orphan pages, broken links, and structural issues. 7. **HTTPS.** If you moved to HTTPS, confirm that each page loads over HTTPS without mixed content warnings. 8. **Content parity.** Compare word counts and section headings with the old pages. If the release checks pass, return to the branch table. A platform move can still lose important rendered content. A domain move can have an incomplete historical map. Consolidation can weaken the surviving task. Compare the affected pages and queries with those branch-specific records before deciding that time alone will fix the decline. Use the site’s observed crawl and indexing progress, not a promised 30-to-90-day recovery. Google’s move guidance describes temporary fluctuations and varying processing times. A rollback changes the site again, so use the documented trigger and release owner. Do not assume that reverting always doubles recovery time. ## Answer common migration questions **How long does recovery take?** Usually 30 to 90 days. An HTTPS move or a small URL change recovers faster. A domain, platform, and structure change at the same time can take 90 to 180 days. **When should you migrate?** In a low-traffic season, if your traffic is seasonal. Ecommerce sites avoid the fourth quarter. The dip hurts less from a lower baseline. **Can you migrate in phases?** Yes. Move `/blog` first, then `/products`, then the other sections. Each phase gets its own redirect map and monitoring. Phases reduce risk. **What if you cannot map every URL?** First map the top 20% of pages by traffic, pages with backlinks, and pages in the top 20. For the rest, redirect to the most relevant category page. Where no relevant page exists, return 410 rather than a home page redirect. **Why not 302 redirects?** A 302 tells Google the move is temporary, so it can keep the old URL in its index longer. A 301 tells Google the move is permanent and to show the new URL. Use 301. **Can JavaScript redirects replace server redirects?** No. Google sees a JavaScript redirect only after rendering, which is slower and less reliable. Use server-side 301 redirects in `.htaccess`, Nginx, or application code. The [migration guide for product managers](/articles/site-migration-seo-product-managers) shows how to put this plan into sprints, launch criteria, and stakeholder updates. ---- ```text .|########||. .|########||. .|########||. |##||. .||##|. |##||. .||##|. |##||. .||##|. |#|. .|#|. |#|. .|#|. |#|. .|#|. |#| |#| |#| |#| |#| |#| .#| |#. .#| |#. .#| |#. .#. .#| .#. .#| .#. .#| |#. .#| |#. .#| |#. .#| |# ...... #| |# ...... #| |# ...... #| .# ||#########| #| .# ||#########| #| .# ||#########| #| .#. |######||######|. .#. .#. |######||######|. .#. .#. |######||######|. .#. #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# #. .##|###|##|#|######| .# || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || || |##|#||||||||||||#||#| || # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. # |#||||||||||||||||||||#| #. || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # # .#||||||||||||||||||||||||#| # || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || || ....|||#||||||##|#|||#|#||##||||....|. || #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# #. . ....|# ....#||| ||| .#||| ....#. .# # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. # . ||||#| .#####|| . .#| .#||| ||||# #. .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || .| ||||| #. |#|||||. || #. |#||. .||||| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || || |.... #. ....|#. |. ...|. ....|| || #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# #. .||||||##||||||##||####|||||||#||||||#| .# # .||####|###########################|. # # .||####|###########################|. # # .||####|###########################|. # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#||||||.#.|| # |. ..# #| #|||||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||||| .. |# ## |#| ...#|#|||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#|||#|# .# .#| #| ##|.#..#|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # .#||||||############|######|||||#| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # # |...||#||||||#||||#|#||||||#|||||#||| |.| # #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# #. .. ||||# .|||##|. |#| .|| || .|||#. #| # .# || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || | ...|| ...##| | #| .|. |. ##### .. .| || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || || ||||| || ||||#| . |. |. |#. ||||| |#| || || .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. .# |.....#|....|#.||||.|||##.|#|....||.#||.#. #. #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# #.|||||||#############################| ||| .# || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || || ##||#||#||||||#||#||#||#||##. || # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # # .#|||||||||#||#|||||||||||#| # || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || || |#||||||||||||||||||||||#| || .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. .# |#||||||||||||||||||||#| #. || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || || |#||||||||||||||||||#| || #. .######|#|#########| .# #. .######|#|#########| .# #. .######|#|#########| .# .#. |#####||||#####| .#. .#. |#####||||#####| .#. .#. |#####||||#####| .#. |# ||########|| #. |# ||########|| #. |# ||########|| #. |# ...... #| |# ...... #| |# ...... #| |#. .#| |#. .#| |#. .#| |#. .#. |#. .#. |#. .#. .#| |#. .#| |#. .#| |#. |#| |#| |#| |#| |#| |#| .|#|. .|#|. .|#|. .|#|. .|#|. .|#|. |##||. .||##| |##||. .||##| |##||. .||##| .||########||. .||########||. .||########||. Scale With Search 2026 [scalewithsearch.com](https://scalewithsearch.com) ```