♞Websites
Website Redesign Without Losing SEO: Redirects, URL Mapping, Content and Launch Checks
Short answer: To redesign a website without losing SEO, benchmark your current traffic, keep URLs where you can, and map every old URL that changes to its closest new equivalent with a permanent 301 redirect. Keep the content and page titles that rank, update internal links, remove any noindex tags at launch, submit a new sitemap and monitor Search Console closely.
A redesign should make a site better for visitors and for search. Yet many businesses see traffic fall after launch, and it is almost never because the new design is worse. It is because pages that ranked were deleted, URLs changed without redirects, or a setting left over from development told Google to stay away.
Every one of those problems is preventable with planning. This is the process we follow on our website redesign projects, based on Google’s own guidance for moving sites and changing URLs. It works for a ten-page brochure site and for a shop with thousands of products; only the size of the spreadsheet changes.
Why websites lose rankings after a redesign
Search engines rank individual URLs. When a URL disappears without a redirect, the history attached to it, including links from other sites, effectively disappears too. The most common causes of a post-launch drop are:
- Changed URLs with no redirects, so old links and search results lead to error pages.
- Removed or thinned content, often because a designer wanted shorter pages and cut the text that was ranking.
- Changed titles and headings that no longer match what people search for.
- Leftover development settings, such as a sitewide noindex tag or a robots.txt file that blocks crawling.
- Broken internal links and navigation that buries important pages several clicks deep.
- Slower pages because the new design added heavy images, video or scripts.
A short dip while Google recrawls is normal, and Google says to expect ranking fluctuations during a move. A sustained drop usually points to one of the problems above.
Before you start: benchmark everything
You cannot protect what you have not measured. Before any design work, capture a snapshot of the current site.
- Search Console Performance: export clicks, impressions and positions by page and by query for at least the last 12 months. Search Console keeps 16 months of data, so do this before it rolls off.
- Top pages: list the pages that bring the most search clicks, enquiries and sales. These are your protected pages.
- Pages with backlinks: use the Links report in Search Console to find pages other sites link to.
- A full crawl: run a crawler over the old site to list every URL, title, meta description, H1, status code and canonical tag.
- Sitemaps and analytics: save the current XML sitemap and note conversion rates so you can compare after launch.
If you are still deciding whether a redesign is the right move, our article on the signs a website needs a redesign will help.
SEO is one strand of a wider project plan. Our website redesign checklist covers the rest, from content and design to testing, so the SEO steps here slot into a timeline rather than being squeezed in the week before launch.
Build a URL map
The URL map is the most important document in an SEO-safe redesign. It is a spreadsheet listing every old URL and exactly what happens to it. The best outcome is simple: if a URL does not need to change, do not change it. Where it must change, Google’s guidance is to decide where each old URL should redirect to, starting with the pages from your sitemaps, analytics and links report.
| Old page | What to do | Status code |
|---|---|---|
| Same page, same URL | Keep the URL; no redirect needed | 200 |
| Same page, new URL | Redirect old to new, one to one | 301 or 308 |
| Several pages merged | Redirect each old URL to the merged page | 301 or 308 |
| Page removed, close equivalent exists | Redirect to the closest relevant page | 301 or 308 |
| Page removed, no equivalent | Let it return not found or gone | 404 or 410 |
| Temporary change, page returning | Use a temporary redirect | 302 or 307 |
Do not redirect large numbers of old pages to the homepage. Google may treat a redirect to an unrelated page as a soft 404, which passes nothing useful and confuses visitors. Remember images and PDFs too: if an image or document attracts search traffic or links and its URL changes, it needs a redirect as well.
Protect the content that ranks
Design changes how content is presented. It should not quietly delete the content that earns traffic. For every protected page in your benchmark:
- Keep the substance. Restyle and restructure the text, but keep the topics, answers and detail that match what people searched for. Improve it if you can; do not cut it to fit a template.
- Keep or improve titles and H1s. If a page ranks for a phrase, the title tag and main heading should still include it.
- Carry over meta descriptions, image alt text and structured data such as product, review or FAQ markup that the old site used.
- Keep important pages close to the homepage in the navigation, and keep the internal links that pointed to them.
- Make sure text is real text, not baked into images, and that key content does not depend on scripts that might not render.
Planning the new page structure is part of the same exercise. Our guide to the essential pages for a small business website is a useful check that nothing important is missing.
Set up redirects the right way
Google recommends server-side permanent redirects, HTTP 301 or 308, for content that has moved for good. They tell Google the new URL should replace the old one in results. A few rules make them work properly:
- Redirect straight to the final URL. Avoid chains such as old page to interim page to new page. If chains are unavoidable, Google suggests keeping them short, ideally no more than three hops.
- Update internal links so menus, buttons and in-text links point directly to the new URLs instead of relying on redirects.
- Add self-referencing canonical tags on each new page, and update any hreflang tags if you run several language or country versions.
- Keep redirects for at least a year, as Google advises. In practice we leave them in place indefinitely; old links on other sites never stop sending visitors.
- Test before launch. Run your old URL list through a crawler or redirect checker on the staging site and confirm every row returns the planned status code.
From our projects: we add a column to the URL map for the tested result and do not launch until every protected page shows a single 301 hop to the right destination. It turns launch day from guesswork into a checklist.
Launch day and the weeks after
Launch day
- Remove noindex tags and any password protection used during development.
- Check robots.txt allows crawling of everything you want indexed.
- Confirm every version of the domain (www and non-www, HTTP and HTTPS) redirects to one preferred version.
- Submit the new XML sitemap in Search Console and inspect your most important URLs with the URL Inspection tool.
- Check analytics, conversion tracking, forms and checkout on the live site.
- If the domain itself has changed, use the Change of Address tool in Search Console. It is not needed for URL changes on the same domain or for moving to HTTPS.
After launch
Watch Search Console daily for the first two weeks, then weekly. Check the Page indexing report for new errors, compare clicks and impressions for your protected pages against the benchmark, and fix any 404s that should have been redirected. Google notes that a medium-sized site can take a few weeks or longer to settle. Check speed too, because a heavier design can undo good SEO work; our guide to making a small business website faster covers the fixes.
Google’s tools and report names change over time. Follow the current Search Central documentation on site moves and redirects for the latest steps.
Checklist: website redesign without losing SEO
- Search Console and analytics data exported and saved before work starts.
- Protected pages identified: top search pages, top converting pages and pages with backlinks.
- Full crawl of the old site saved with titles, headings and status codes.
- URL map completed for every old URL, including images and documents that get traffic.
- URLs kept the same wherever there is no strong reason to change them.
- Ranking content, titles, H1s, alt text and structured data carried over or improved.
- Server-side 301 or 308 redirects set one to one, with no chains and no mass homepage redirects.
- Internal links, canonicals and hreflang updated to the new URLs.
- Noindex and staging protection removed and robots.txt checked at launch.
- New sitemap submitted and key URLs inspected in Search Console.
- Redirects kept for at least a year and performance compared with the benchmark weekly.
Questions
Will a website redesign affect my SEO?
It can, positively or negatively. A redesign that keeps URLs or redirects them properly, preserves ranking content and loads quickly often improves search performance. Problems usually come from changed URLs without redirects, removed content, altered titles or development settings such as noindex being left on after launch.
How long does it take to recover rankings after a redesign?
Google says to expect some ranking fluctuation while it recrawls and reindexes the site, and that a medium-sized site can take a few weeks or longer to settle. If traffic to important pages is still well below your benchmark after that, check redirects, indexing and content changes for those pages.
Should I keep the same URLs when redesigning my website?
Yes, wherever you can. Keeping URLs removes the biggest source of risk in a redesign, because nothing needs redirecting and existing links keep working. Change URLs only for a clear benefit, such as fixing a confusing structure, and then map each old URL to its new equivalent with a permanent redirect.
How long should I keep 301 redirects after a redesign?
Google recommends keeping redirects in place for at least one year so its systems can transfer signals to the new URLs. Many sites keep them indefinitely, because links on other websites, bookmarks and old emails can keep sending visitors to old addresses for years.
Do I need the Change of Address tool after a redesign?
Only if you move to a new domain or subdomain. The Change of Address tool in Search Console tells Google the whole site has moved. It is not needed when URLs change on the same domain, when you move from HTTP to HTTPS, or when you switch between www and non-www versions.