How to migrate a website without losing search visibility
A new design, platform or domain can put your search visibility at risk. From the URL inventory and 301 map to launch-day checks and the weeks that follow, these are the steps that make a migration safe.
Summarise this article with an AI tool
The tool opens in a new tab with a summary prompt that includes this article’s address.
To migrate a website without losing search visibility, list every important URL on the current site, map each old URL to its new equivalent with 301 redirects, check that content and headings survive on the new site, keep the staging site out of search indexes and watch Search Console closely in the weeks after launch.
Why is a migration an SEO risk?
A migration is an SEO risk because search engines know your site through its URLs. When a page's address changes, the links pointing to it, its position in search results and visitors' bookmarks only carry over to the new address through a correct redirect. Without one, visitors and crawlers hit a 404 error.
"Migration" is not a single operation. Each of these changes carries its own risk:
- Domain change: moving from oldcompany.com to newcompany.com
- Platform change: moving from a hosted platform to WordPress, or from WooCommerce to custom software
- URL structure change: /product/123 becoming /products/category/product-name
- Redesign and content changes: pages merged, removed or retitled
- Server change: a new host with the same domain and URLs
A server change is usually the lowest risk because URLs stay the same. Changing domain and platform at the same time carries the highest risk. Where possible, staging the changes makes problems easier to trace.
What should be prepared before the move?
The most important document is the URL inventory of the current site. It covers URLs in the sitemap, pages that receive traffic in Search Console, pages with external links and every reachable URL a crawler finds.
For each URL, record:
- The URL and page title
- Recent clicks and impressions
- Whether the page has external links
- Whether it will have an equivalent on the new site
This inventory is also your baseline. Keeping a copy of pre-migration traffic and ranking data lets you interpret changes correctly afterwards.
Which pages must be kept?
Pages that bring traffic, conversions or external links must be kept or redirected to their closest equivalent. If two pages are merged, the important information from both should appear on the new page. Pages with no visits and outdated content can be removed deliberately.
How do you build a 301 redirect map?
A 301 redirect map is a one-to-one table showing which new URL each old URL permanently redirects to. Google uses permanent redirects to understand a page's new location.
| Old URL | New URL | Note |
|---|---|---|
| /our-services/web | /services/web-design | Same content, new URL |
| /product.php?id=45 | /products/sample-product | Dynamic to readable URL |
| /campaign-2024 | /campaigns | Redirect to the current equivalent |
| /old-service | — | No equivalent: 410 or the related category |
Rules to follow:
- Redirect each old URL to its closest content match; sending everything to the home page weakens the signal.
- Avoid redirect chains. If A goes to B and B goes to C, point A straight to C.
- Use permanent (301 or 308) redirects, not temporary 302 redirects.
- Consolidate www and non-www, http and https versions onto one address.
- Include images, PDFs and important media files in the inventory.
Google's site move documentation explains how redirects are processed.
How do you check content parity?
Content parity means checking that new pages keep the information and signals of the old ones. Even with correct redirects, visibility can drop if the content becomes thinner.
Check:
- Page titles and meta descriptions
- H1 and subheading structure
- The scope of the main copy and key facts
- Internal links and menu structure
- Structured data such as Organization, Product and BreadcrumbList
- Canonical tags and hreflang on multilingual sites
- Image alt text
The most common redesign mistake is shortening explanatory copy on service pages to make them "look cleaner". Search engines and AI answer systems understand what a page is about from that copy.
How should the staging site be protected?
The staging site should be kept out of search indexes before launch. Password protection is the safest method. A noindex tag or a robots.txt block can also be used, but these settings must not be carried over to the live site. One of the most common launch-day mistakes is leaving the "discourage search engines" setting switched on.
What should be checked on launch day?
Launch-day checks confirm that redirects and technical settings work on the live site:
- Open a sample of inventory URLs and confirm they 301 to the right address.
- Make sure robots.txt does not block crawling and no pages still carry noindex.
- Generate the new sitemap and submit it in Search Console.
- Check that canonical tags point to the new domain and correct URLs.
- Test forms, payment and order flows.
- Confirm analytics and tag manager code run on the new site.
- Check that the SSL certificate is valid on every version of the domain.
When is the Search Console change of address tool used?
The change of address tool is only for domain changes. It is not needed when URLs change within the same domain or when only the platform or server changes. Before using it, both domains must be verified in Search Console and the 301 redirects must be live.
How should the schedule be planned?
Plan the launch for a quiet period when your team can respond. Campaign periods, season openings or trade-fair weeks are poor choices, because any error shows up exactly when traffic peaks.
A typical schedule:
- Record the inventory and baseline data
- Define the new URL structure and build the redirect map
- Check content parity and technical settings on staging
- Test redirects on staging
- Run the launch-day checklist
- Monitor on day one, week one and month one
If DNS records will change, lowering the TTL a few days in advance shortens propagation time. If email runs on the same domain, MX records need their own plan.
What about multilingual sites?
Each language version needs its own URL inventory and redirect map. An old Turkish URL should redirect to the new Turkish page and an old English URL to the new English page. Redirects that mix languages confuse both users and crawlers. hreflang tags must point to the new URLs, each language pair must reference the other and x-default must point to the right page.
How long should you monitor after launch?
Monitor for at least several weeks, and for a few months on large sites. Crawling new URLs and transferring signals takes time, and temporary fluctuations are normal.
Watch:
- Indexing reports and 404 errors in Search Console
- Clicks and impressions compared with the baseline
- Requests to old URLs in server logs
- Whether key pages appear in results with their new URL
- Unexpected drops in conversions such as forms or orders
When a missed URL appears, add it to the redirect map and recheck it. Keep redirects in place for as long as possible, ideally permanently.
Who should run the migration?
The safest approach is one plan, with one person responsible for the inventory, the redirects and post-launch monitoring. If design, development and content are handled by different people, the redirect map should be their shared document.
Karınca Bilişim runs website migrations with an inventory, a 301 map and a launch-day checklist. When a migration comes with a redesign, we bring technical SEO checks to the start of the project. You can describe your planned change through the quote form.
Frequently asked questions
Is a traffic drop after migration normal?
Short-term fluctuation is common while search engines process the new URLs. Large, lasting drops usually come from missing redirects, lost content or crawl settings left blocked. Comparing with the pre-migration baseline is the fastest way to find the cause.
Is it enough to redirect all old URLs to the home page?
No. Mass redirects to the home page are often treated like missing pages. Each URL should redirect to its closest content equivalent.
How long should redirects stay in place?
Ideally permanently. Links from other sites and saved bookmarks can keep sending requests to old URLs for years.
Does changing server affect SEO?
If the domain and URLs stay the same, the effect is usually limited. The new server's speed, downtime and SSL configuration can still affect users and crawling, so include these checks in your hosting and domain management plan.