
Website Redesign SEO: Keep Your Traffic and Rankings
Website redesign SEO comes down to one question: will the page addresses change? If they will, Google treats the launch as a site move. Map each old address to its new page, add permanent redirects, update sitemaps and canonical tags, clear any staging blocks, and expect rankings to wobble while Google recrawls.
Smarter Revolution is a US team that builds AI into a company's real workflows and then runs it for them, including Website Modernization for companies on a dated site. This guide is for owners and marketing leads planning a rebuild who want a clear checklist to hold their web team to. We do not promise rankings or traffic after any move, and nothing here is legal advice.
Is a website redesign a site move in Google's eyes?
It depends on the addresses, not the look. Google's guide to site moves and migrations covers changing the URLs of existing pages, whether that means a new domain, a switch from HTTP to HTTPS, or new paths on the same domain. A redesign that keeps every address exactly as it was is a different case. Google points changes that keep the URLs but switch infrastructure, such as a new hosting provider or a content delivery network, to a separate guide on changing your hosting, which says it applies "only for migrations that don't affect the user-visible URL." If the redesign comes with a new content system, check whether it builds page paths in its own pattern, adds or drops a trailing slash, or renames the blog section. Before any design work starts, export the full list of current addresses and compare it with what the new build produces. If even one important address differs, plan the launch as a site move.
What should you do before the new site goes live?
Build the map first. Google's site move guide calls mapping old URLs to new ones important and suggests where to find them: your sitemaps, your server logs or analytics, the Links report in Search Console, and your content system's own export.
- One row per old address. Each row names the new page that best matches it. Where there is no real match, write that down too.
- Plan the robots rules and noindex tags for launch day. If your developers hid the staging build from search engines, Google's guide asks you to write out the launch robots.txt file ahead of time, along with the list of pages whose noindex tags must come off.
- Update the new site to match the map. Google's guide says each new page should carry a canonical tag pointing to itself, internal links should use the new addresses, and the sitemap should list the new addresses.
- Change one big thing at a time. Google's guide advises against moving domain, content system and layout all at once, and suggests doing them one after another. If your rebuild needs a new content system and a new design, ask your web team whether they can launch in two steps, and if not, how they will test each change on its own first.
- Pick all at once or in sections. On a small or medium site, Google's preference is one switch-over for the whole site instead of a staged, part-by-part move.
Which redirects should you use?
Google's guide recommends permanent server-side redirects where possible, naming 301 and 308. On the worry about losing link value, the same page says plainly: "Don't worry about link credit." Its reason, quoted: "301 and other permanent redirects don't cause a loss in PageRank."
- Point straight to the final page. Google's advice is one hop where you can manage it: each old address should lead directly to its new home, and if a chain cannot be avoided, keep it short.
- Do not send everything to the home page. Google cautions against it. Visitors who expected a specific page end up somewhere else, and Google says a mass redirect like that might be handled as a soft 404.
- Let removed pages say so. If a page is not coming across, Google's guide wants its old address to answer with a 404 or 410 status code.
- Keep the redirects in place. Google asks for a long run here: its guide says "generally at least 1 year," and longer if you can.
How long do rankings take to settle after a move?
There is no fixed date. Google's guide warns that positions can wobble for a while as Google crawls and indexes the rebuilt site again. On timing, its rough rule puts most pages of a small or medium site at a few weeks, with big sites needing more. Google also suggests timing a move for a period of lower traffic where you can. Agree with your team in advance what normal settling looks like so a dip in week one does not trigger a panic rollback.
Which migration mistakes does Google call common?
Google's site move guide lists the common mistakes, and they are worth turning into a launch-day checklist.
- Leftover blocks. The live site goes out still carrying a noindex tag or robots.txt rule that was put there for testing.
- Wrong redirects. Old addresses point to the wrong page, or to nothing.
- Other crawl errors. Errors beyond redirects can appear on the new site; Google's guide asks you to check Search Console's indexing data for a sudden rise.
- Too little server capacity. Expect heavier Googlebot traffic than usual after the move, Google says, so the host needs headroom.
- Stale sitemaps. The sitemap still lists the old addresses.
Does a redesign change how AI answers see your site?
It can, through the same basics. Google's page on AI features and your website names two conditions a page must meet before it can be considered as a supporting link in AI Overviews or AI Mode: it has to be indexed, and it has to qualify to show with a snippet in Google Search. The same page says no special markup or extra files are needed. Our reading, not a statement Google makes about migrations: a redesign that leaves a staging noindex or a robots block in place could take those pages out of AI Overviews too, not only out of the regular results. For the wider crawl checks, see our guide on how to get cited by ChatGPT, and for structuring content so AI answers can use it, our LLM Search Optimization service.
What should you monitor in the weeks after launch?
Watch the move, not just the new site. Google's guide calls Search Console "your friend" during a site move and its checklist includes the Sitemaps report: compare the number of new addresses you submitted with the number Google has indexed. Google also wants you tracking how visitor and crawler traffic shifts between the old addresses and the new ones.
- Daily for the first week. Spot-check a sample of old addresses from the map to confirm each lands on the right page.
- Weekly after that. Review new crawl errors, indexed counts from the new sitemap, and any page that has dropped out.
- Before you remove anything old. Confirm the redirects are still live, and check the timing in the redirect section above before taking any down.
If you want a quick outside view of your site before you plan the move, our free website authority check is a place to start.
How does Smarter Revolution handle a website rebuild?
Our Website Modernization service rebuilds a dated WordPress, Wix, Squarespace or GoDaddy site as a fast Next.js site, carries your content across with 301 redirects from the old addresses, and keeps running the site after launch. We do not promise rankings or traffic. Search engines decide those, and the steps in this guide reduce risk rather than remove it.
We start with a free 30-minute scoping call about your current site and what has to carry over. The scope then comes to you in writing. Timelines run in weeks, not quarters, counted from when we have the access and approvals we need. We charge one fixed price to build your system and one monthly fee to run and improve it, both agreed in writing before work starts.
To talk through a rebuild plan and the address map, book a call.
Frequently asked questions
Do 301 redirects lose link value?
Not according to Google. Its site move guide says "301 and other permanent redirects don't cause a loss in PageRank," so link value is not a reason to avoid them.
How long should we keep the old redirects?
Google's guide asks for as long as you can manage, and puts it at "generally at least 1 year." Our advice: if in doubt, leave them up longer.
Should we change domain, content system and layout at the same time?
Google advises against it. Its guide suggests making those changes one after another, for example moving to the new domain first and changing the layout later.
Do we need to tell Google about a new domain?
Only if the domain or subdomain changes. Google's guide says to use the Change of Address tool in Search Console then, and that it is not needed for HTTP to HTTPS moves or new paths.
What should happen to pages we delete?
Let them answer with a 404 or 410 status code, as Google's site move guide advises. Do not point all of them at the home page, which Google may treat as a soft 404.
The bottom line
Website redesign SEO is mostly planning: know whether addresses change, map every one, redirect each to its true match, clear staging blocks, and watch Search Console for weeks after launch. Google's own guides cover each step, and none of them promise a result.
Sources
- Google Search Central, "Site Moves and Migrations" (How to move a site), opened 30 October 2026: developers.google.com
- Google Search Central, "Changing your hosting", opened 30 October 2026: developers.google.com
- Google Search Central, "AI features and your website", opened 30 October 2026: developers.google.com
Mark Alouf
Smarter Revolution is a US team that builds AI into a company's real workflows and then runs it for them. We start with one workflow and add the next when you are ready.


