# Site Migration SEO Guide: 301 Redirect Maps, Change of Address and Monitoring

Author: Fatih Emin Çakıroğlu (https://fatihemincakiroglu.com)
Source: https://fatihemincakiroglu.com/en/guides/site-tasima-seo
Published: 2026-10-18
Updated: 2026-10-18

A site migration is any project that changes a website's domain, platform (CMS or e-commerce system) or URL structure. To visitors it may look like a redesign; to a search engine, thousands of addresses are moving at once. For Google to carry the signals of old URLs over to new ones, you have to state clearly where every old URL now lives.

The pattern I see most often: teams focus on the launch date, redirects get pushed to the final week, and the search for answers starts only once organic traffic drops. This guide covers the steps in order: inventory, the 301 redirect map, Search Console's Change of Address tool, canonical/hreflang/sitemap updates and post-migration monitoring.

> Short answer: for an SEO-safe site migration, redirect every old URL to its closest equivalent new URL with a single 301, and update canonicals, hreflang, sitemaps and internal links to the new addresses. Use Search Console's Change of Address tool only when the domain changes, and monitor indexing, crawl errors and performance data for weeks after launch.

## Types of site migration: how risky is each change?

The key question that defines risk is whether URLs change. If they stay the same, no redirects are needed; if they change, every change means a redirect rule.

| Migration type | Example | Do URLs change? | Change of Address tool |
| --- | --- | --- | --- |
| Domain change | oldbrand.com → newbrand.com | Yes | Yes, use it |
| Protocol change | http:// → https:// | Yes (protocol) | No |
| Platform/CMS change (same domain) | WordPress → Shopify | Usually yes | No |
| URL structure change | /product.php?id=12 → /products/blue-shirt | Yes | No |
| Redesign | Same URLs, new template | No | No |
| Hosting/server change | Same domain, new server | No | No |

Even when URLs stay put, a new template can break title tags, internal links, structured data or speed, so I recommend a pre-launch [technical SEO audit](https://fatihemincakiroglu.com/en/guides/teknik-seo) for every migration.

## Before the move: URL inventory and benchmark data

A redirect map is only as good as the URL list behind it. The sitemap alone is not enough; pages missing from it often still earn traffic or backlinks.

- Crawl the current site and export every reachable URL.
- Export pages with traffic from the Search Console Performance report and landing pages from GA4.
- List pages with backlinks; they should be prioritised in the map.
- Add image, PDF and other file URLs to the inventory.
- Record current positions for key queries, clicks per page and Core Web Vitals values.

Without this benchmark you cannot answer “did we drop, and by how much?” after launch. The [SEO reporting guide](https://fatihemincakiroglu.com/en/guides/seo-raporlama) explains which metrics to keep, and the [Core Web Vitals thresholds](https://fatihemincakiroglu.com/en/blog/core-web-vitals-2025) give you a reference point for speed.

Keep staging behind a password or noindex, and confirm those blocks are removed at go-live; a forgotten noindex or robots.txt block is one of the costliest migration mistakes.

## How do you build a 301 redirect map?

A 301 redirect map is a table pairing every old URL with its new URL. Permanent moves use 301 (or 308); 302 and 307 signal a temporary move.

- [ ] Map one to one: each old page should go to the closest new page in terms of content.
- [ ] Avoid chains: redirect A → C in a single hop instead of A → B → C.
- [ ] Do not send every old URL to the homepage; Google may treat that as a soft 404.
- [ ] Return 404 or 410 for content that genuinely has no equivalent.
- [ ] Cover parameterised URLs, trailing slashes and uppercase/lowercase variants in your rules.
- [ ] Keep redirects in place for at least a year, longer if you can.

For a domain change where the path structure stays the same, a single general rule may be enough. A simple example for .htaccess on an Apache server:

```
RewriteEngine On
RewriteCond %{HTTP_HOST} ^(www\.)?oldbrand\.com$ [NC]
RewriteRule ^(.*)$ https://www.newbrand.com/$1 [R=301,L]
```

If the URL structure changes too, you need to define the map's rows individually at server or platform level. Category, product and filter URLs need separate handling, as covered in the [e-commerce SEO guide](https://fatihemincakiroglu.com/en/guides/e-ticaret-seo).

## When should you use the Search Console Change of Address tool?

The Change of Address tool in Search Console is designed for domain changes only. It is not used for moving from HTTP to HTTPS or for platform or URL structure changes within the same domain; in those cases 301 redirects and an updated sitemap are what you need.

Before using the tool, make sure that:

- Both the old and the new domain are verified in Search Console under the same account.
- Pages on the old domain 301 redirect to their equivalents on the new domain; the tool checks this on a few sample URLs.
- You start the request from the old domain's property and select the new domain as the destination.
- The old domain's robots.txt does not block Googlebot; a redirect on a blocked URL cannot be seen.

The tool is an extra signal about the move, not a migration method on its own; the 301 redirects do the real work.

## How do you update canonicals, hreflang, sitemaps and internal links?

Redirects connect old addresses to new ones, but every on-site signal must also point to the new addresses. Conflicting signals make it harder for Google to pick the main URL.

### Canonical and hreflang

Each page's canonical tag should point to its own absolute URL on the new domain; canonicals still pointing to the old domain are a frequent error. On multilingual sites, hreflang annotations must list the new URLs of every language version, be reciprocal, and include an updated x-default where one exists.

### Sitemaps and internal links

The new XML sitemap should list only new, canonical URLs returning a 200 status code, submitted to the new Search Console property. Temporarily keeping a sitemap of the old URLs can help Google discover the redirects faster. Update internal links to point straight at the new URLs rather than through redirects.

The url and @id fields in structured data are easy to miss; the [schema structured data guide](https://fatihemincakiroglu.com/en/guides/schema-yapisal-veri) explains how to set them up. Also update the website address in Google Business Profile, your social profiles and ad destination URLs; for local businesses this step belongs alongside the [local SEO guide](https://fatihemincakiroglu.com/en/guides/yerel-seo).

## Post-migration monitoring: the first days and weeks

A migration does not end on launch day. Ranking fluctuations are normal while Google crawls and indexes the new URLs; what matters is catching a lasting problem early.

- [ ] Day one: test the URLs in your map with a crawler and verify status codes, chains and destinations.
- [ ] Day one: confirm the live site has no noindex, robots.txt block or canonical error.
- [ ] Week one: watch the Page indexing report and Crawl stats in Search Console.
- [ ] Week one: review the 404 and 5xx responses Googlebot receives in your server logs.
- [ ] Following weeks: monitor Performance data for both the old and the new property and compare it with your benchmark.
- [ ] Following weeks: compare landing page and conversion data in GA4 against the previous period.

My list of free [SEO tools](https://fatihemincakiroglu.com/en/tools) covers several options for these checks. If a drop in specific page groups becomes persistent, check redirect destinations first, then differences in content and internal linking.

## The site migration mistakes I see most often

- Changing the domain, platform, URL structure and content all at once, which makes it impossible to isolate the cause when something goes wrong.
- Removing redirects a few months after launch, or letting the old domain registration lapse.
- Leaving image and PDF URLs out of the map.
- Migrating only the main language on a multilingual site and leaving the other languages' hreflang links broken.
- Measuring the migration only by looking at total traffic.

If you are planning a large or multilingual migration, involving [SEO consulting](https://fatihemincakiroglu.com/en/seo-consulting) from the start prevents mistakes that are hard to undo. If you would like to review your migration plan together, you can [book a free intro call](https://fatihemincakiroglu.com/en/book-a-call).

## Frequently Asked Questions

### How long does it take for rankings to recover after a site migration?

There is no fixed timeframe; it depends on site size, crawl frequency and redirect accuracy. Google notes that most pages of a medium-sized site can take a few weeks to move in its index, and larger sites longer. If there is no recovery as the weeks pass, look for a technical problem.

### How long should I keep the old domain?

Redirects should stay in place for at least a year, so the old domain must stay active at least that long. In practice I recommend renewing it indefinitely; if it lapses, the redirects and backlink value are lost and the domain can end up in someone else's hands.

### Should I migrate all at once or in sections?

On large sites, moving one section first lets you catch problems at a small scale; it takes longer but spreads the risk. For small and medium-sized sites, a well-prepared single switchover is usually easier to manage.

### What happens if I used 302 redirects by mistake?

A 302 signals a temporary move; for a permanent change the right choice is 301 or 308. Google may treat long-standing redirects differently over time, but rather than relying on that uncertainty, switching the rules to 301 straight away is the clearest path.

### Should I ask sites to update important backlinks?

301 redirects pass the value of links to old URLs on to the new addresses, so you do not need to change every link. Asking the owners of your few most valuable links to update them still reduces dependence on redirects.

### Should I rewrite content during the migration?

Ideally, no. Changing content, titles and internal linking during the move makes it hard to isolate the cause when performance shifts. Finish the migration, let the data settle, then improve content in a later phase.

---
Please attribute as: "Fatih Emin Çakıroğlu (fatihemincakiroglu.com)". Original: https://fatihemincakiroglu.com/en/guides/site-tasima-seo