Website migration SEO: relaunch your site without throwing away its search traffic
Website migration SEO is the inventory, redirect, testing and monitoring work that carries the search value of old pages over to new URLs when a site changes its domain, platform, URL structure or design.
Short answer
Virelth's website migration service protects the search value of your old URLs when you redesign, change domains or switch platforms. We decide the fate of every old URL, build a one-hop 301 redirect map, test before launch and monitor afterwards. It starts with a free preliminary analysis; temporary fluctuation is normal, so we never promise zero loss.
Key points
- Every old URL gets a written decision: it stays, moves to its new address in one hop, or is removed for a stated reason.
- Old URLs are never mass-redirected to the homepage; redirects are permanent, single-hop and chain-free.
- The new site is crawled on staging before launch, checking noindex, robots.txt, canonicals, hreflang and tracking tags.
- Google says to expect temporary ranking fluctuation during a move and to keep redirects generally for at least one year.
- If another agency or your own team builds the site, we can handle only the SEO side of the migration.
Who is website migration SEO for, and who is it not for?
A good fit
- Companies moving to a new CMS or e-commerce platform, for example away from WordPress or between store platforms
- Businesses changing their domain, merging two sites or moving from a subdomain to the main domain
- Teams restructuring URLs or adding new language versions to an existing site
- Companies whose redesign is built by another agency and who want an independent SEO check
- Sites that lost traffic after a migration and want to find out why
Not a good fit
- Projects that cannot give access to the old site's URL list or Search Console data before the move
- Teams that want to skip testing entirely to keep a launch date
- Anyone expecting a guarantee of zero traffic loss
What counts as a website migration?
If the URLs of your pages change, then as far as search engines are concerned, your site is moving. The cases we see most often:
- Platform change: moving from WordPress to another system, or from one store platform to another. URLs often change quietly in the process.
- Domain change: a rebrand, a move from a country domain to a generic one, or two sites merging into one.
- URL restructuring: reorganized category paths, or cleaning up URLs that contain dates or IDs.
- Adding languages: new language versions on a single-language site, each of which has to be connected correctly with hreflang.
- Redesign: even when URLs stay the same, changed titles, content and internal links can affect search visibility.
Several of these can happen at once, but each carries its own risk. Where possible, we discuss splitting a domain change and a platform change into separate steps instead of doing both on the same day.
Why do sites lose search traffic in a migration?
Most losses come from a handful of recurring mistakes:
- Forgotten URLs: only the pages in the menu get moved, while old blog posts or campaign pages that have brought traffic for years are missing from the list.
- Blanket homepage redirects: every old URL is sent to the homepage, so visitors never find what they came for and the old page’s value goes nowhere useful.
- Redirect chains: an old URL first goes to an intermediate address, then to the new one.
- Staging settings reaching production: a
noindextag or a robots.txt rule that blocks crawling goes live with the new site. - Lost tracking: analytics tags or conversion definitions are missing on the new site, so even when a drop is noticed, its cause cannot be measured.
What does Google’s migration guidance recommend?
Google’s site move guide asks you to map old URLs to new ones, use permanent server-side redirects such as 301 or 308 where possible, update your sitemaps with the new URLs and make sure Search Console verification keeps working after the move. For small and medium-sized sites it recommends moving all URLs at the same time, and it says plainly that visibility in Search may fluctuate temporarily during the move. Redirects should be kept for as long as possible, generally at least one year.
Our plan applies those steps to your site and ties each one to a written checklist.
What do we monitor in the weeks after launch?
A migration does not end on launch day. As Google recrawls the old URLs, it sees the redirects and indexes the new pages, and problems surface one by one. During monitoring we look at:
- The page indexing report in Search Console: are new URLs being indexed, and are old ones recognized as redirects?
- Not-found errors: old URLs that were missing from the inventory but have links from other sites usually show up here; valuable ones get a redirect.
- Clicks by page group: category, service and blog pages are tracked separately, because a stable total can hide a loss in one group.
- Conversions: are forms and sales measured with the same definitions as on the old site?
Every issue goes into the change log with its cause and fix, and the monitoring period is fixed in the written scope. If you are planning a redesign, building the migration plan into the design from the start is the least risky route; it is a standard checklist in our web design projects.
What do you get from our website migration service?
Free migration preliminary analysis
We review the planned change, the size of the old site and its search data, and list the biggest risks in priority order. Whether you continue is up to you.
URL inventory
One merged list of old URLs from a crawl, sitemaps, Search Console, Analytics and pages with external links, with the traffic and value of each.
Mapping decisions
For every old URL: keep, move in one hop, merge into another page, or remove with a stated reason. You approve the decisions.
301 redirect map
Server-ready redirect rules that are single-hop and chain-free. No blanket redirects to the homepage.
Staging audit
A crawl of the new site before launch: noindex and robots.txt, canonicals, hreflang, structured data, internal links, tracking tags and the consent banner.
Launch-day checklist
The steps to carry out and verify, in order, at launch, including spot checks of redirects and a rollback plan.
Search Console tasks
Verifying the new property, submitting updated sitemaps and, if the domain changes, using the Change of Address tool.
Post-launch monitoring and report
For the period set in the scope: 404 and redirect errors, indexing and search traffic by page group, with a fix list for every issue found.
How does a website migration project run?
You decide at the end of every stage; we do not move on without your approval.
Discovery and free preliminary analysis
Start, ideally while the new site is being designed
We look at what will change, the old site's URLs and its search data. With read access to Search Console, deciding which pages matter is based on real data.
Approval: You read the analysis and decide whether to continue.
Plan and quote
After the analysis
Based on the type of migration, the number of URLs and who implements what, we prepare a written scope and quote. The length of post-launch monitoring is written into the scope.
Approval: No work starts until you approve the scope and quote in writing.
Setup: inventory, map and testing
The weeks before launch
We build the URL inventory, the mapping decisions and the redirect map, crawl the new site on staging and close the issues we find together with your developers.
Approval: You approve the mapping decisions, especially the pages to be removed.
Launch day
Launch
Redirects go live, robots.txt and noindex settings are checked, sitemaps are submitted and redirects are spot-checked with sample URLs.
Approval: The go-live decision, and if needed the rollback decision, is yours.
Measure and fix
The weeks after launch
We monitor Search Console and Analytics, fix missing or broken redirects and report a before-and-after comparison by page group.
Approval: We review the closing report together and agree who takes over any open items.
How do we measure whether a migration worked?
Measurements come from your own accounts and our crawls, and each report says where every number comes from.
Redirect coverage
How many valuable old URLs reach the right target in one hop, verified by crawling.
Indexing
New URLs entering the index and old URLs dropping out, in Search Console.
Errors
404s, server errors and redirect errors, each with its fix status.
Organic clicks by page group
Compared with the period before the move, with seasonality, campaigns and other influences noted.
Conversions
Forms, calls or sales in GA4, measured with the same definitions on the old and the new site.
Migrating without a plan, with developers only, or with SEO support
| Criterion | No plan | Developers only | Working with Virelth |
|---|---|---|---|
| URL inventory | None; old URLs are forgotten | Often just the pages in the menu | Merged list from crawl, Search Console, Analytics and link data |
| Redirects | None, or everything to the homepage | Technically correct, but not prioritized by search value | Prioritized by value, single-hop and chain-free |
| Testing | Problems are found after launch | Functional testing; SEO settings can slip through | Staging is also crawled for SEO |
| After launch | Noticed when traffic drops | Fixed when someone reports an error | Regular monitoring for the period in the scope |
| Best fit | Very small sites with no search traffic | Redesigns with little search traffic and unchanged URLs | Sites that win inquiries or sales from search; we work alongside your developers |
What determines the price of a website migration?
A migration is a one-off project, priced on its real scope. The main factors are:
- Number of URLs on the old site and how many of them receive search traffic
- Type of migration: domain, platform, URL structure, merging sites or adding languages, or several at once
- Number of language versions
- Who implements the redirects, and whether we have server access
- Whether a staging environment exists
- Length of post-launch monitoring
- How much content needs merging or rewriting
Price: From $690 per project + VAT
The exact scope and price are set in a written quote after the free preliminary analysis.
Prices exclude VAT. The written quote states the exact amount; invoices are issued in Turkish lira (TRY) at the exchange rate of the invoice date.
What should you check before any migration, whoever you work with?
- Will you receive a written decision list covering every old URL?
- Does anyone suggest redirecting all old URLs to the homepage? Nobody should.
- Are redirects permanent (301 or 308) and single-hop?
- Is the new site crawled on staging before launch, with the results shared with you?
- Is it written for how many weeks, and with which reports, the site will be monitored after launch?
- Be careful if someone promises no traffic loss at all; Google says to expect temporary fluctuation during a move.
- Are the old and new Search Console properties verified under your own account?
What can we show you as proof?
We do not have a client case study approved for publication yet, and we do not use invented logos, reviews or numbers. We followed the same rules when we moved our own site: virelth.com went from its old WordPress site to a new static build and launched on 16 November 2026. Valuable old URLs kept their paths, and every other old URL was planned in a single redirect file. The build stops if a redirect target is not built, points to the homepage, creates a chain or shadows an existing page. An old URL whose new page is not ready yet either goes to a planned fallback page or returns not found until its target launches, and then switches to it automatically.
Frequently asked questions
Google says to expect temporary ranking fluctuation during a move. A complete inventory, single-hop redirects and pre-launch testing reduce the risk a great deal, but they cannot remove it. That is why we never promise zero loss; we commit in writing to what we will check and what we will monitor after launch.
According to Google, it can take a few weeks for most pages of a small to medium-sized site to move, and longer for large sites. It also depends on how often Google crawls your site. During that period we watch the indexing and error reports closely and add every problem we find to the fix list straight away.
Google recommends keeping redirects for as long as possible, generally at least one year. We recommend keeping them permanently: links from other sites and bookmarks keep using old URLs for years, and redirect rules cost almost nothing to keep on the server.
Both the old and the new domain must be verified in Search Console under your account. Once a 301 redirect from the old homepage to the new homepage is in place, you use the Change of Address tool; Google says its effect lasts 180 days. The tool is only for moves from one domain or subdomain to another.
Yes; every page whose URL changes needs a redirect and monitoring. Google's Change of Address tool is not used in these cases, though: it is meant for domain changes, not for HTTP to HTTPS or for moving pages within the same site. All the other steps are the same.
Google recommends moving all URLs at the same time for small and medium-sized sites, while very large sites may move one section at a time. We decide this with you during planning, based on the size of the site, your team's capacity and how you want to spread the risk.
Yes. We prepare the URL inventory, the mapping decisions, the redirect map and the test list, and work from the same task list as the developers. They implement, we test and monitor after launch. Who does what is spelled out in the written scope.
A migration is a one-off project. The number of URLs, the type of migration, language versions, who implements the redirects and the length of post-launch monitoring set the price. We start with a free preliminary analysis, then send a written scope and quote; nothing starts before you approve it.
You do. Search Console, Analytics and hosting accounts are in your name; we are added with only the permissions we need. The URL inventory, redirect map, test reports and change log are handed over to you, and when the work ends you simply remove our access.
Your request has reached us
We will review your request and get back to you through the channel you chose.
We will review it and get back to you.
Your request could not be sent. Please check your details and try again, or write to us at info@virelth.com.