To redesign a website without losing SEO, list every old URL, export your Search Console data and map each old URL to one new URL before you build. Keep the content and titles that already rank. On launch day, add permanent redirects, submit the new sitemap and test every old URL. Then compare Search Console with your baseline for several weeks.
Key takeaways
- Redirects: Google recommends permanent server-side redirects, such as 301 or 308, and says to keep them for at least 1 year.
- Baseline: export your Search Console data before the move. Search Console keeps data for the last 16 months only.
- Test site: block it with a password or noindex. Google says robots.txt does not keep a page out of Google.
- Languages: each language version must list itself and all others. Google ignores hreflang tags that do not point both ways.
- Expectations: Google says rankings move during a site move, and a medium-sized site can take a few weeks or more.
- Bottom line: the URL map decides the result. Build it before the design, and test every old URL on launch day.
Website redesign SEO: why traffic drops after a relaunch
Traffic drops after a redesign when Google cannot connect the old pages to the new ones. The usual causes are old URLs with no redirect, pages that ranked and were deleted, and a new site that still blocks Google from the test phase. Each cause is easy to check before launch, so most losses come from a missing list.
A redesign changes more than the look. It often brings a new platform, new URLs, a new domain or new languages. Each change sends Google a new set of signals. Google’s guide to site moves says to expect temporary changes in rankings during the move. For a medium-sized site, it says Google can take a few weeks or more to show the new URLs.
So the goal is a controlled move. Google should find every old page, follow it to its new page and see content that is the same or better. This is the base of every website and brand revamp we build.
Website migration SEO checklist by phase
A website migration has four phases: before the build, during the build, launch day and the weeks after. Each phase has one main task and one main check. The table gives the short version. The sections below explain each step, with the Google documentation behind it.
Print the table or copy it into your project plan. Each row needs one owner, and the launch-day row needs a person who tests the redirects on the day.
| Phase | What to do | What to check |
|---|---|---|
| Before the build | List every old URL, export Search Console and analytics data, and map each old URL to one new URL | Every URL with clicks or links has a target in the map |
| During the build | Keep or improve the content of each page, write titles, add structured data and hreflang, and block the test site | The test site has a password or noindex, and each page has a self-referencing canonical |
| Launch day | Turn on permanent redirects, remove the test blocks, submit the new sitemap and use Change of Address if the domain changes | Every old URL reaches its new page in one redirect, and the new page returns 200 |
| The weeks after | Read the Page indexing report and the 404 errors, and fix each one | Clicks and impressions per page against your baseline, week by week |
Before the redesign: URL inventory, baselines and the redirect map
Before anyone designs a page, make a full list of your current URLs and a record of how each one performs. Then decide where each old URL goes on the new site. Google’s site move guide calls this the URL mapping. It is the most important document of the whole project, because every redirect comes from it.
Use more than one source for the list. A crawler finds the pages that your menus and links reach. Your sitemap and server logs find pages that nothing links to. Google’s guide also points to the Links report in Search Console for pages with internal and external links.
Export your data early. Search Console keeps data for the last 16 months only. A copy from before the move lets you compare each page later.
- Crawl the old site and save every URL, title, description and status code.
- Add the URLs from your sitemap, your server logs and the Links report in Search Console.
- Export clicks and impressions per page and per query from Search Console, and landing pages from your analytics.
- Mark the pages that bring clicks, leads or links. They keep their content and get a redirect to the closest new page.
- Map each old URL to one new URL. Pages with no new home and no value can return 404 or 410.
During the build: content, titles, structured data and hreflang
During the build, each new page should carry the same or better content than the old page it replaces. Keep the topics and the words that rank, then improve the structure and the speed. A new design that deletes the text Google ranked will lose those rankings, however good it looks.
Titles and descriptions need the same care. Write them per page, keep the query that brought clicks at the start, and check how they look in results before launch. Our free Google results preview shows where a title gets cut.
The test site needs a block, or Google can index it next to your live site. Google says robots.txt is not a way to keep a page out of Google. A blocked URL can still appear if other pages link to it. Use a password or a noindex rule instead, and remember that noindex only works when robots.txt does not block the page.
- Content: the same or better text for every page in the URL map, with the same main topic.
- Canonicals: Google’s guide says each new URL should have a canonical tag that points to itself.
- Structured data: keep the schema the old site had, such as Organization, Product, FAQ or Article, on the new URLs.
- Languages: Google says each language version must list itself and all other versions. If two pages do not point to each other, Google ignores the tags.
- Internal links: point menus and text links to the new URLs, so each click reaches the page without a redirect.
Launch day: 301 redirects, the new sitemap and Change of Address
On launch day, turn on a permanent server-side redirect from each old URL to its new URL, remove the test blocks and submit the new sitemap. Then test every old URL from the map. Google recommends server-side redirects with the status codes 301 or 308, because they have the highest chance of being read correctly.
Keep each redirect to one hop. Google’s crawlers follow up to 10 redirect hops, but every extra hop is one more place where a move can fail. An old redirect from a past redesign should point straight to the newest URL.
If your domain changes, use the Change of Address tool in Search Console. You must own both properties with the same Google account. Google uses the tool only for domain and subdomain moves. It is not needed for a move from http to https or for new URLs on the same domain.
- Redirects: 301 or 308, server-side, from each old URL to one new URL.
- Test: request every old URL in the map and confirm it lands on a new page with a 200 status.
- Blocks: remove the password, the noindex rules and any test rules from robots.txt.
- Sitemap: submit the new sitemap in Search Console. It must use full URLs and stay under 50,000 URLs per file.
- Keep the redirects for as long as possible. Google’s guide says generally at least 1 year.
After launch: Search Console checks and AI search
After launch, check Search Console every few days for the first weeks. Look at the Page indexing report, the 404 errors and the Sitemaps report. Compare clicks and impressions per page with your baseline. Google says that, ideally, traffic on the old site falls while traffic on the new site rises.
Fix each 404 that has clicks or links with a new redirect. A 404 on a page you removed on purpose is fine. Google drops that URL from the index over time.
AI search depends on the same work. Google says there are no extra requirements to appear in AI Overviews or AI Mode. A page must be indexed and eligible to show with a snippet. AI features traffic is part of the Web search data in Search Console, so your baseline covers it.
After a move, also ask ChatGPT, Gemini and Perplexity the questions your buyers ask, and note which pages they cite. We do this check before every discovery call, as part of our SEO and AI search work.
Website migration case: RNJ Transport
RNJ Transport, a road freight forwarder from Klaipėda in Lithuania, replaced its WordPress site with a new Astro site in 11 languages. The first call and the first commit were on 19 October 2026. On 21 October 2026, the new site went live on the client’s domain. All 944 pages returned a 200 status.
RNJ Transport launch
Updated November 2026aimo
RNJ Transport’s new site went live in two days, every page working.
A road freight forwarder from Lithuania replaced a WordPress site in one language with a static Astro site.
- 944/944 pages returned 200 at launch
- 11 languages with hreflang
- 100 Lighthouse SEO score on mobile
- First call First call and first commit on 19 October 2026.
- Checks npm run verify checks copy, languages, titles, menus and the sitemap before each release.
- Domain switch The new site went live on the client’s domain on 21 October 2026.
Traffic results are not recorded yet. A Search Console review is planned.
The old site had the problems this checklist is for. The text was only in Lithuanian, but the pages were coded as US English. There was no hreflang, and the language switch linked to nothing. 9 of the 14 URLs in the sitemap were pages from the theme. The company ranked 8th for its own name, behind companies in the US and UK with the same name.
The new site has hreflang in the sitemap for every language, with English as the x-default. It has an llms.txt file and a Markdown copy of every page for AI tools. Before each release, a script called npm run verify checks the copy, the pages in each language, the titles, the menus and the sitemap. Lighthouse on mobile scored 97 for performance, 100 for accessibility, 96 for best practices and 100 for SEO on 19 October 2026.
We have no traffic results to share yet. A Search Console review is planned, and we will add the numbers to the RNJ Transport case when we have them. The same work fits other logistics and transport companies with sites in several languages.
A website redesign as the start of SEO and AI search
A redesign is the best moment to build for SEO and AI search, because every page, URL and template changes anyway. Adding structured data, hreflang and clean titles later means a second project on the same pages. That is why AI for Marketing Ops prefers new sites and revamps: the base is right from the first day.
Plan the new site around the questions your buyers ask. Each main question gets one page with a direct answer, so Google and AI tools can quote it. Keep the speed checks and the copy checks in a script, so each release passes the same tests.
We do not promise rankings, and no one can. What we can control is a move where Google finds every page, and a new site built for the searches your buyers make.
Common questions
How long does it take for traffic to recover after a website migration?
Google says rankings change for a while during a site move. For a medium-sized site, Google can take a few weeks or more to show the new URLs, and larger sites take longer. Compare each page with your baseline every week. A page that is still lower after that time usually has a redirect or content problem.
Should I use 301 or 308 redirects?
Both are permanent redirects, and Google treats both as a sign that the page has moved for good. Use the one your server or hosting supports. What matters more is that the redirect is server-side and goes from each old URL to one new URL in one hop.
How long should I keep the redirects?
Google’s site move guide says to keep redirects for as long as possible, generally at least 1 year. If you change domain, the Change of Address help page says at least 180 days, and longer if old URLs still get Google traffic. Keep the old domain registered so no one else can buy it.
Do I need the Change of Address tool?
Only when you move to a new domain or subdomain. Google says you do not need it for a move from http to https, for www to non-www, or for new URLs on the same domain. You must own the old and the new property in Search Console with the same Google account.
Should I move the whole site at once or in sections?
Google recommends moving all URLs of a small or medium site at the same time. Large sites can move in sections. Moving at once also means one launch day, one test of the redirect map and one baseline to compare with.
Does a website redesign affect AI search?
Yes, in the same way as classic search. Google says AI Overviews and AI Mode have no extra requirements: a page must be indexed and eligible to show with a snippet. A page that loses its redirect or its content in a redesign loses both. Check AI answers after launch as well as Search Console.
How long does a website and brand revamp take with AI for Marketing Ops?
Most revamp projects go live in 10 working days, from the start of work to the new site live on your domain. For RNJ Transport, the new site went live 2 days after the first call. Every project ends with documentation and a handover session.
Sources and checks (10)
- Google Search Central: site moves with URL changes
- Google Search Central: redirects and Google Search
- Google Search Central: HTTP status codes and network errors (redirect hops, 404 and 410)
- Search Console Help: Change of Address tool
- Google Search Central: tell Google about localized versions of your page
- Google Search Central: build and submit a sitemap
- Google Search Central: block search indexing with noindex
- Google Search Central: introduction to robots.txt
- Google Search Central: AI features and your website
- Google Analytics Help: Search Console keeps data for the last 16 months