Key takeaways
- Google's site-move guide asks you to keep redirects for "at least 1 year". The Search Console help stops at 180 days: go with the longer one.
- Blocking a staging site in robots.txt does not stop it being indexed. A password does.
- A redesign that keeps every URL still changes the content Google evaluates, and can move rankings.
- The redirect map, Search Console, analytics, the domains and DNS access should stay with the company paying for the site, not with the agency.
Why do websites lose rankings after a redesign or migration?
Rankings drop when Google cannot connect old URLs to new ones, when a staging block reaches the live site, or when new templates change the content. Good website migration SEO makes the dip smaller and shorter. Nobody can honestly promise there will be no dip at all.
Google says so in its guide to site moves with URL changes, last updated on 20 August 2026. On a small or medium-sized site, most pages take "a few weeks" to move, and rankings fluctuate in the meantime. Large sites take longer, depending on server speed and the number of URLs.
This guide is written for the person who commissions and pays for the new site. That matters more when the agency works from another country, in a second language and sometimes a different time zone. What you leave out of the contract is hard to put back in after launch.
The Google pages linked here were checked on 11 November 2026. We are a Spanish agency and build redesigns and migrations as part of our web development service, so this is also the checklist we hold ourselves to.
Website migration SEO: which kind of move are you making?
Changing hosting and changing domain carry very different risks. Google's rule is to change one thing at a time. Its own example: if you are moving domain, changing CMS and redesigning, do it in stages, the domain first and the design later.
| Type of change | Risk (our view) | What Google asks for | What usually breaks |
|---|---|---|---|
| New hosting or CDN, same URLs | Low | Test on a temporary hostname and lower the DNS TTL at least a week ahead | A firewall that locks Googlebot out |
| Redesign, same URLs | Medium | No special tool | Titles, copy and internal links the new templates no longer carry |
| New URLs on the same domain | Medium to high | A URL map and permanent redirects, one by one | Unredirected URLs and redirects to the homepage |
| New domain, or country domains merged into one | High | Redirects, the Change of Address tool and keeping the old domain | www and non-www variants nobody redirects |
| Everything at once | Highest | Do it in stages | Knowing which change caused the drop |
The help page for the Change of Address tool is blunt about the last row. Combine a move with a redesign of content and URLs and you will "probably" lose traffic while Google reassesses the pages. John Mueller of Google advised in 2020 spacing the changes out to see the effect of each, as Search Engine Roundtable reported.
Merging several country domains into one site is common in Europe, and it counts as a domain move for every one of them. Each old domain needs its own redirects and its own Search Console property, so a .de, a .fr and a .nl mean three moves to plan.
What if I only change the design and keep the URLs?
The risk falls, but it does not disappear. Mueller put it simply in April 2021, in a post quoted by Search Engine Roundtable: if you change design, you generally change the content. Headings, titles, images, internal links, accessibility and speed all count.
A common failure is a new template that quietly drops category copy or footer links. Compare old and new page by page before you approve the build, starting with the title, the H1 and the links on each template.
What should you demand from the agency before you sign?
Ask for five written deliverables in the quote: a URL inventory, a redirect map you keep, a password-protected staging site, a launch plan and post-launch monitoring with dates. Search Console, analytics, the domains and DNS access should be in your company's name from day one, whichever country the agency works from.
Google's own page Do you need an SEO? says a redesign is a great time to hire one, and the earlier the better. Its suggested questions include experience with international sites, and whether the provider will share every change it makes to your site and explain why.
- A URL inventory with clicks per page, exported from Search Console, plus the list of sites linking to you.
- A redirect map in a spreadsheet, listing old URL, new URL and response code. You receive it before launch and it belongs to you.
- A password-protected staging site, never one hidden only by robots.txt.
- A launch date chosen around your traffic in every market, with a written rollback plan.
- At least three months of monitoring included, with the name of the person doing it.
- Who keeps the redirects running for at least a year, and on which server.
When the agency is abroad, add three practical points. Agree the working language for launch day and who is on call in your time zone. If the agency will touch form data or customer records, Article 28 of the GDPR requires a written processing agreement. And keep the domain registrar account yourself, because redirects, DNS changes and Search Console verification all depend on it.
Walk away from anyone who guarantees you will lose no rankings. Google warns against providers who promise a top position or claim a special relationship with it. Our guide on how to choose a digital marketing agency covers the other red flags, and how much a website costs shows what a build with a Spanish agency includes.
How do 301 redirects work, and how long should you keep them?
Each old URL is redirected on the server, with a 301 or a 308, straight to its closest new equivalent with no intermediate hops. Google asks you to keep them "for as long as possible, generally at least 1 year". The Search Console help settles for at least 180 days, which is how long its Change of Address tool runs.
301 or 302?
Google's documentation on redirects, updated on 14 April 2026, separates permanent redirects (301 and 308) from temporary ones (302, 303 and 307). Permanent ones tell Google which URL to show. Temporary ones do not, which slows a move down. A JavaScript redirect is a last resort, because Google may miss it if rendering fails.
The idea that every 301 leaks part of a page's strength still circulates. Gary Illyes of Google wrote in July 2016 that 30x redirects no longer lose PageRank, as Search Engine Roundtable reported. It is an old statement rather than a guarantee, but it disposes of the percentage that gets repeated without a source.
Three mistakes that turn a move into a drop
The first is chains. Googlebot follows up to 10 hops, yet Google recommends going straight to the final destination and, failing that, ideally keeping to 3 or fewer. The second is sending lots of old URLs to the homepage, which Google may treat as soft 404s. Redirecting several pages to one that merges their content is fine.
The third is redirecting pages that no longer exist to anything at all. If a page goes and has no equivalent, it should return a 404 or a 410, which Google reads more clearly than a forced redirect.
180 days or a year?
Google gives two timeframes on two different pages. The Change of Address help asks you to keep redirects for at least 180 days. That is how long the tool forwards signals and prioritises the new site, after which Google no longer links the two. The site-move guide asks for at least a year, and suggests keeping them indefinitely for users.
Insist on a year as the minimum, and keep them while old URLs still get visits. Google also recommends renewing the old domain for at least a year so nobody buys it for malicious use. If hosting changes too, write down who runs the server that answers with the 301s. Cancel the old hosting and the redirects go with it.
How to keep the staging site out of Google
Put the staging site behind a password. Blocking it in robots.txt is advice repeated in many guides, and it does not do the job. Google states that a URL disallowed in robots.txt can still be indexed if other sites link to it, and show up without a description.
Pairing the block with a noindex tag fails too. Google explains on its page about blocking indexing that if a page is not crawled, the noindex is never seen. A password keeps out anyone unauthorised, and keeps the site out of Google as a side effect.
The opposite mistake is just as serious. The site goes live still carrying the staging Disallow: / or noindex, and Google's site-move guide specifically says to remove those blocks at launch. Ask the agency to have the production robots.txt ready, together with the list of pages that need the noindex removed.
Multilingual sites, hreflang and consent: the European part of a migration
Most European sites run in more than one language, and that doubles what can break. When URLs change, the hreflang annotations must point to the new URLs. Google's guide to localised versions also requires the links between versions to go both ways, so one language version left on old URLs can break the set.
Canonical tags should point to each page's own new URL, and internal links should too, without leaning on redirects. Structured data is easy to lose when templates change. Check that the new templates keep the markup types described in our guide to structured data for AI search.
Measurement is the part nobody owns. If the analytics tag, the consent banner and Consent Mode v2 are missing from the new site on day one, you lose the data to compare before and after. A banner that fires tags before the visitor chooses can create a GDPR problem in every EU market at once. Test both on staging, in each language.
Launch day: a website migration SEO checklist
Launch is prepared on staging and executed in a few hours. This is the order Google's guide follows, with what to check at each step.
- Pick the quietest period for traffic, by season or day of the week, across all your markets. Google recommends it because fewer people are affected and Googlebot gets more server capacity.
- Switch on the server redirects and remove the staging password, noindex and robots.txt block.
- Test a sample of old URLs with the URL Inspection tool in Search Console, and the rest with a crawler or script if there are many.
- Submit the sitemap with the new URLs. If Search Console warns that URLs in the old sitemap redirect, that is expected.
- Use the Change of Address tool only for a domain or subdomain move, and submit it for every verified variant of the old domain.
- Notify Bing and other engines through IndexNow, including redirected URLs and those returning 404 or 410.
- Ask sites that link to you to update their links, and update your own profiles.
Check the Change of Address requirements the week before. You must own both properties in Search Console, and the old homepage must redirect to the new one. The property has to cover the whole domain, with no path (example.com works, example.com/blog does not). The tool does not cover HTTPS moves or dropping www.
Peak seasons and public holidays differ from one country to the next, so a quiet week in one market can be the busiest in another. According to the IndexNow FAQ, submissions are shared between Bing, Yandex, Naver, Seznam.cz, Yep and Amazon. Google is not on that list, and relies on the sitemap and, for a new domain, the Change of Address tool.
How long does Google take, and what is normal after launch?
On a small or medium-sized site, Google takes a few weeks to move most pages, and rankings fluctuate meanwhile. Redirect warnings for the old sitemap are expected, and so is a dip in crawling just after a server change. Pages dropping out of the index, or a decline that keeps going, point to a fault.
| What you see | Reading | What to do |
|---|---|---|
| Rankings moving up and down in the first weeks | Normal, Google is reassessing | Wait and review by template |
| Warnings that the old sitemap redirects | Normal | Ignore them or retire that sitemap |
| Pages excluded by noindex or blocked by robots.txt | Fault | Remove the staging block |
| Many old URLs flagged as soft 404 | Fault from redirecting to the homepage | Redirect to the equivalent page or return a 404 |
| 5xx errors that do not go away | Server fault | Fix them before anything else |
| Canonicals pointing at old URLs | Template fault | Self-referencing canonical on the new URL |
Server errors do damage fastest. Google crawls more slowly when it gets 5xx errors, and eventually drops URLs from the index if the error persists. Before blaming the migration for a fall, rule out seasonality. Google's guide to debugging traffic drops suggests looking at 16 months in the Performance report and comparing year on year.
Template speed counts as well. The Core Web Vitals thresholds on web.dev are 2.5 s for LCP, 200 ms for INP and 0.1 for CLS, worth measuring on staging before launch. We cover their effect on sales in Core Web Vitals and conversion. A drop that fits none of the above calls for an SEO review with your Search Console data.
Does a migration affect AI search visibility?
Yes, through the same route. Google's page on AI features in Search says normal SEO best practice applies to AI Overviews and AI Mode, with no additional requirements. The weak spot is often a default robots.txt on the new platform that blocks crawlers you used to allow. Compare old and new line by line, and see whether your website is ready for AI search for the other checks.
Where to start
Before asking for quotes, export from Search Console the pages with clicks over the last 16 months and the list of sites linking to you. That tells you what you cannot afford to lose. Ask for the redirect map as a deliverable in your name, and for the contract to state who keeps the redirects running for at least a year. If you want us to quote, our starting rates are on the pricing page, and you can request a scoped proposal through contact, in English.
Frequently asked questions
How long should you keep 301 redirects after a migration?
At least a year, according to Google's site-move guide, and longer while old URLs still get visits. The Search Console help asks for at least 180 days, which is how long its Change of Address tool runs. Keep renewing the old domain for at least a year as well.
Does a website redesign affect SEO if the URLs stay the same?
It can, although the risk is lower than when URLs change. Google treats a redesign as a change of content: headings, titles, internal links, images and speed. Compare the old and new site template by template before launch.
Do I need to tell Google that my website has moved?
For a domain move, yes, through the Change of Address tool in Search Console once the redirects are live. If only URLs change within the same domain, the redirects and a new sitemap are enough. The tool does not cover moving to HTTPS or dropping www.
Is it normal for traffic to drop after a website migration?
A few weeks of fluctuation is normal, and Google describes it in its site-move guide. If pages drop out of the index or the decline continues after that, check noindex, robots.txt, redirects to the homepage, 5xx errors and canonicals.
Should I change domain and redesign at the same time?
Better not. Google recommends changing one thing at a time, the domain first and the design later. If you do both together, it warns you will probably lose traffic while it reassesses the pages, and you will not know which change caused it.



