A website redesign can improve the way your business looks while breaking the routes customers use to find it. Protect your existing pages before changing their addresses.
Answer: Website redesign SEO means preserving valuable content, URLs, internal links, and search access while changing the site. Keep useful addresses where possible. When a page moves, permanently redirect its old URL to the closest relevant replacement and test the route before launch.
The launch review should cover more than the new homepage. It needs to account for the service page someone bookmarked, the case study linked in a proposal, and the article Google still sends people to.
Start with the pages that already matter
My view: a redesign should earn its changes. A cleaner navigation menu is useful. Renaming every address because the new site builder prefers a different folder structure is a separate decision, with separate consequences.
Before design approval, make an inventory of the existing site. Google’s site-move guidance recommends mapping old URLs to new ones. That applies when a redesign changes addresses, even if the domain stays the same.
Use more than the current menu to build the inventory. Pull together your crawl, sitemap, Search Console landing pages, analytics, and known links from other websites. Include PDFs and campaign landing pages when they still serve a purpose.
Then add business context. Which pages explain a profitable service? Which ones support sales conversations? Which case studies help a buyer trust you? A low-traffic page may still answer the question that gets a deal moving.
This is not an instruction to keep every old page forever. It is a way to avoid deleting useful work simply because nobody remembered it during the redesign meeting.
Build an old-to-new URL map before launch
The most useful redesign document may be a spreadsheet. Give every known URL a decision: keep it, move it, combine it with another page, or retire it.
Here is an illustrative example for a service business. These are hypothetical paths, not findings from a client audit.
| Existing page | Decision | Launch behavior |
|---|---|---|
| /commercial-cleaning/ | Keep the service and address | The refreshed page still loads at the same URL |
| /office-cleaning-faq/ | Combine useful answers into the service page | Redirect to /commercial-cleaning/ only if it now answers those questions |
| /case-study-riverside/ | Move into the new case-study section | Redirect directly to /case-studies/riverside/ |
| /expired-event/ | Retire, with no relevant replacement | Return an appropriate 404 or 410 rather than sending everyone home |
For permanent moves, Google recommends server-side permanent redirects where possible. Its redirect documentation identifies both 301 and 308 as permanent status codes. Your developer can choose the implementation that fits the hosting stack.
Do not change a useful URL merely to make it look newer. You can usually improve the copy, page layout, and conversion path without moving the address at all.
Where a move is justified, go straight to the final destination. A visitor should not bounce through several retired versions of the same site before reaching today’s service page.
The homepage is not a universal replacement
Imagine clicking a link promising a commercial-cleaning case study and landing on a homepage that says, “Welcome to our new website.” Technically, a page loaded. Practically, the work of finding the evidence has been handed back to you.
Google specifically warns against redirecting many old URLs to an irrelevant destination such as the homepage. It says those redirects can confuse users and may be treated as soft 404 errors.
That does not mean every old page needs a separate new page. Consolidation can be sensible. If several overlapping articles become one genuinely useful guide, redirecting them to that guide can preserve their purpose.
The test is relevance, not convenience. Does the destination satisfy the reason someone followed the original link?
Apply the same judgment to service pages. If the redesign removes a detailed explanation of a service and substitutes a vague paragraph on a general page, a redirect alone has not preserved the information buyers needed.
Test the customer route, not just the redirect
A redirect report is necessary. It is not the whole acceptance test.
Choose 10 commercially important old URLs as a first manual review set. That number is a practical starting point, not a Google requirement or a substitute for testing the full URL inventory.
- Open the old address directly. Do not start at the new homepage. Confirm that a moved page takes you to the intended replacement without a loop or unnecessary chain.
- Read the destination. Check that the service, answer, or evidence promised by the old link is still there.
- Try the next step. Submit a clearly labeled test inquiry with the team’s knowledge, use the booking route, or check the phone link. Confirm that the intended team receives the test.
- Inspect search access. Verify that important live pages are crawlable and indexable. Check for leftover staging restrictions, incorrect canonical URLs, and broken internal links.
Google’s site-move guidance calls for updated internal links, canonical annotations, and sitemaps. Links you control should point to the final addresses rather than relying on redirects indefinitely.
If the rebuild also changes the rendering technology, inspect the actual page content rather than assuming an attractive browser preview proves everything is accessible. Google’s JavaScript SEO documentation explains that crawling and rendering are separate steps and that not all bots can run JavaScript.
A WordPress-to-custom-app rebuild may be perfectly reasonable. It still needs a content-access test. Changing the platform is not permission to skip the buyer’s journey.
What this means for AI search
The direct evidence here is Google’s documentation about crawling, rendering, redirects, and site moves. It is not a promise that a specific redirect will retain a ChatGPT citation or win an AI recommendation.
The wider business implication is straightforward: your published pages are reference points. People and systems may encounter links to those pages outside your navigation. Preserving a relevant destination keeps those links useful when they are followed.
That is part of AI Findability, but it is also ordinary website stewardship. Clear service information, accessible evidence, and working routes matter whether the visitor starts with Google, an AI answer, an email, or a colleague’s saved link.
For more on the access side, see agent-ready websites. Do not confuse making information accessible with guaranteeing that a system will recommend it.
Expect a transition, then investigate specific problems
Google says a site move happens on a per-URL basis and can produce temporary ranking fluctuations while it recrawls and reindexes. Its guidance says small and medium sites can take a few weeks for most pages to move, with larger sites taking longer. That is guidance, not a guaranteed recovery deadline for your site.
Keep the URL map after launch. Use it to investigate unexpected errors, missing important pages, and drops in traffic to specific services. Check completed inquiries as well as visits. A working page with a broken form is still a business problem.
Google recommends keeping redirects for as long as possible, generally at least one year. It also says keeping them indefinitely can make sense for users. Do not remove them after a week simply because the launch team has moved on.
Record the launch date and major changes. If you simultaneously change the domain, platform, content, and navigation, diagnosing a decline becomes harder. Where practical, separate major changes so you can tell which decision caused which effect.
Make continuity part of the redesign brief
The brief should ask for an existing-page inventory, documented URL decisions, tested redirects, a search-access check, and a post-launch review. Put those deliverables beside the design approvals, not in a vague promise to “handle SEO later.”
A better-looking site should make the business easier to choose. It should not make existing customers and prospects learn how to find you again.
If a redesign is on your calendar, a Website Findability Audit can identify the pages and paths worth protecting before the build starts. Tell me what is changing and when you plan to launch. That is the right place to start.
Sources
This is an evergreen implementation guide, not a report of a new Google policy. Official documentation checked September 16, 2026. Examples and prioritization advice are editorial recommendations.