Website migration is one of the few technical projects that can undo years of work on search visibility in just a few hours. Whether you are moving to a new platform, changing your domain, switching to HTTPS or doing a complete redesign, every change to your URL structure carries the risk that Google loses the connection between your old and new content. The good news is that losing rankings is not inevitable. It is almost always the result of gaps in planning, not of the migration itself. In this article we walk through an engineering approach that protects what you have built.
Why does migration put SEO rankings at risk?
Search rankings do not belong to your website as a whole, but to each individual URL. Over the years, Google has indexed hundreds or thousands of your pages, assigned them authority based on links and user behavior, and remembered which address matches which query. When a migration changes those addresses and you do not tell the search engine where the content went, this is what happens:
- Old addresses start returning a 404 error, so Google drops the pages from its index.
- Authority earned through external links is not passed on to the new addresses.
- The search engine temporarily loses trust in the site’s stability and crawls it less often.
- Users arriving from old links find empty pages and leave.
The result is a drop in organic traffic that can last for weeks. The goal of every serious migration is to make this transition invisible to both users and search engines.
Preparation before you touch anything
Most of a successful migration happens before a single file is moved. Without an accurate picture of the current state, you have nothing to compare the result against, and you do not know what you need to preserve.
A complete list of existing URLs
The first step is an inventory. You need a list of all addresses that are currently indexed and bring in traffic. Combine sources so nothing slips through:
- The XML sitemap as a starting point.
- Google Search Console for the pages that actually get clicks and impressions.
- A site crawler that simulates a search engine and uncovers every internal link.
- Analytics for the pages with the most traffic over the last twelve months.
Recording a baseline
Before the migration, record the key figures: organic traffic per page, rankings for your most important queries, the number of indexed pages and your backlink profile. Without this snapshot, you will not be able to tell normal fluctuations from a real problem caused by the migration later on.
Mapping old addresses to new ones
The heart of the whole process is the redirect map. It is a table that assigns each old address exactly one new, most relevant address. This is not a job done automatically with a single rule, at least not when the structure changes.
If you are thinking about a new or better website for your company, see how we approach website development for clients in Sarajevo and across Bosnia and Herzegovina.
| Old address | New address | Redirect type |
|---|---|---|
| /services.html | /services/ | 301 permanent |
| /blog?id=42 | /blog/site-migration/ | 301 permanent |
| /old-category/ | /new-category/ | 301 permanent |
A few rules that protect your rankings:
- Use only 301 (permanent) redirects for content that moves. Unlike a temporary 302, a 301 passes on authority.
- Send every old address directly to the final new one, never through a chain of several hops. Chains slow down crawling and lose some authority.
- Do not redirect everything to the homepage. If some content has no equivalent, find the closest topically related page.
- Content that is permanently removed with no replacement should return a 410 status, which clearly tells the search engine the page was removed on purpose.
Technical checks on the new website
Once the new version is ready, check the elements that directly affect how the search engine understands your content before going live. Ideally, this is tested in a staging environment closed to indexing.
- Titles and meta descriptions must remain present and meaningful on every page, because they are often lost when content is moved.
- Heading structure (H1, H2 and below) should keep a logical hierarchy.
- Canonical tags must point to the new addresses, not the old ones.
- Internal links should lead directly to the new addresses, not through redirects.
- The sitemap must contain only new, live addresses and be submitted through Search Console.
- Loading speed must not be worse than before, because it is a ranking factor. A redesign is an opportunity to make the site even faster.
Pay special attention that the new site is not accidentally left closed to search engines. A tag that blocks indexing, useful in a test environment, is the most common cause of catastrophic drops when someone forgets to remove it in production.
Launch day and the first few hours
Launching a migration should be treated as a controlled operation, not as flipping a switch. We recommend doing it during a period of lower traffic, with the team available to monitor.
- Activate all 301 redirects at the same time as the new version goes live.
- Manually test a sample of the most important old addresses and confirm they lead to the correct new ones.
- Submit the new sitemap and request a recrawl of key pages.
- Check that there are no unexpected 404 errors and that the server returns the correct status codes.
This part of the job requires development and SEO expertise at the same time, which is why migrations go best when they are led by a team that covers both areas. We describe our approach to projects like this as part of our services.
Monitoring results after the migration
A migration is not finished on launch day. The following weeks show whether everything went as planned. A slight drop of a few percent in the first days is normal while the search engine recrawls and understands the new structure. What to monitor:
- The coverage report in Search Console, where you look for spikes in errors and excluded pages.
- The number of indexed new addresses, which should grow as the old ones decline.
- Organic traffic and rankings compared with your baseline snapshot.
- Redirects that are still being triggered, because they show that external links still point to the old addresses.
If an important page loses its ranking, first check whether its redirect is correct and whether the new version kept the same content and keywords. The most common cause of a drop is thinner or altered content on the new page, not the migration itself.
Migrating without losing rankings is a matter of discipline, not luck. An accurate URL map, correct redirects and patient monitoring make the difference between an unnoticeable transition and months of recovery. If you are planning a redesign, a move to a new platform or a domain change, feel free to contact us so we can plan the process together before anything changes.

