How to Redesign a Website Without Losing Important Pages or Search Traffic

A redesign is a chance to make your website clearer, faster and easier to use. It is also a moment when useful pages can disappear, URLs can change and search engines can struggle to understand what has moved. A careful website redesign checklist for SEO helps you improve the site while protecting the work your existing pages already do.

This matters to small organisations as much as large ones. A local accountant might rely on a service page that brings in enquiries; a maker might have a how-to article that attracts search visitors. Neither page should vanish simply because the new design has a different navigation or content structure.

The aim is not to freeze the old site in place. It is to make deliberate decisions about what stays, what changes and how visitors and search engines reach the right destination.

1. Find out which pages matter before changing anything

Start by making an inventory of the current website. Include every page you can find, not only the pages in the main navigation. Older articles, downloadable resources, product pages and campaign landing pages may still receive visits or links.

Build a page inventory from more than one source

Use your site’s content management system, a crawl of the live site, your XML sitemap and analytics or search data. Each source has gaps: a page may be unlinked, missing from the sitemap or too old to show much recent traffic. Comparing sources makes it less likely that an important URL will be overlooked.

For each URL, record its page title, purpose, current status and intended future action. Add available evidence such as organic visits, search impressions, enquiries, sales or links from other sites. You do not need perfect data. A simple spreadsheet is enough to make decisions visible.

If you are unsure which older pages still deserve a place, work through this guide to auditing an old website before approving the new structure.

Decide what to keep, improve, combine or retire

Give each page a clear outcome:

• Keep: the page is still accurate and useful, so retain its URL and content.
• Improve: the subject remains valuable, but the information, layout or call to action needs work.
• Combine: two or more pages overlap and can become one stronger, more complete page.
• Retire: the page is obsolete and has no useful replacement or ongoing purpose.

For example, a home-renovation business might have separate pages for “kitchen fitting” and “kitchen installation” that answer much the same need. Combining them can make sense if the resulting page covers both clearly. But don’t merge unrelated services just to reduce the page count. A visitor searching for bathroom renovation should still land on a page about bathrooms.

2. Plan the new structure and URLs

Once you know which content is staying, plan where it will live. A sitemap is a list or diagram of the pages and their relationships; it helps you check that visitors can find important information without reproducing every detail of the old navigation.

Plan the structure around what customers need to do and understand. A small business might group its pages under Services, About, Case Studies and Contact, while keeping specific service pages easy to reach. For a step-by-step approach, see how to plan a small-business website sitemap.

Keep existing URLs where there is no good reason to change them

If a page is staying and its current address is clear, keeping that URL avoids unnecessary disruption. A redesign does not require a new URL for every page. Changing addresses just to make them look more uniform adds migration work and creates more opportunities for mistakes.

Sometimes a URL should change: perhaps the old address is confusing, the page is moving to a new section, or several pages are being combined. Record the old and new URL whenever you make that decision. Google’s guidance on moving a site with URL changes also recommends planning and testing redirects rather than treating the launch as a purely visual update.

3. Create a redirect map for changed and retired pages

A redirect automatically sends someone from an old URL to a new one. For a permanent move, use a server-side permanent redirect, usually a 301 or 308. This helps visitors who use an old bookmark or follow an old link, and gives search engines a clear signal that a page has moved.

Make a redirect map with at least two columns: old URL and new destination. Add a note for pages that will intentionally return a not-found response because there is no relevant replacement. Review the map with the person building the site; don’t leave it as a spreadsheet that nobody implements.

Match each old page to the closest relevant destination

Imagine a garden designer is replacing an old page at /services/garden-design/ with a new page at /garden-design/. A direct redirect from the old address to the new service page is sensible. If an old article about choosing plants has been retired, sending it to the homepage is unlikely to help. Redirect it to a genuinely related guide if one exists; otherwise, a clear 404 or 410 response may be more honest.

Avoid redirect chains, where one old address redirects to a second address and then a third. Point each old URL directly to its final destination. Also avoid sending a large batch of unrelated pages to one catch-all page. A redirect should preserve the visitor’s intent, not merely prevent an error message.

Google explains that redirects are one of the signals it uses to understand a URL move, and that permanent redirects do not cause PageRank loss in Google Search. That does not guarantee unchanged rankings: content, relevance and other site changes still matter. See Google’s documentation on redirects and Search for the technical detail.

4. Protect the content and signals that make pages useful

When a page is redesigned, its text often gets rewritten to fit a new layout. That can be a good improvement, but make sure the new version still answers the questions and needs that made the page useful. Retain important facts, service details, product specifications and relevant terminology. Improve thin or outdated copy, but don’t remove meaningful information simply to make the page shorter.

Check page titles and meta descriptions too. A title is the clickable heading that can appear in search results; a meta description is a short summary that may be used as the result snippet. Neither should be treated as a guaranteed ranking lever, but clear, accurate wording helps people understand the page. Keep titles specific to each page rather than copying one template across the whole site.

Also check internal links, canonical tags and structured data where applicable. Internal links should point to the new destinations, not keep sending visitors through redirects. A canonical tag indicates which URL should be treated as the preferred version when similar or duplicate pages exist. If you use one, make sure it points to the correct live URL, not a staging address or the old site.

5. Test the new site before launch

Build and review the new site on a private staging address, but make sure search engines are not invited to index it. Staging sites are often protected by a password or a “noindex” instruction. Before launch, agree who will remove that protection and how you will confirm it has been removed. A well-built site can remain invisible in search if the live version accidentally inherits a noindex setting.

Use a pre-launch checklist

• Check that every important old URL has a planned outcome: unchanged, redirected, or intentionally retired.
• Test the redirect map, including trailing slashes, uppercase or lowercase variations where relevant, and old URLs with query strings if those are in use.
• Check that pages return the expected status: live pages should generally return 200, moved pages should redirect, and missing pages should not falsely appear successful.
• Review the navigation, footer and in-content links on desktop and mobile.
• Confirm that page titles, headings, canonical tags and any structured data use the intended live information.
• Check that forms, telephone links, email links, checkout or booking steps work.
• Verify that the live XML sitemap contains the preferred, indexable URLs, not redirects or staging addresses.

Google’s sitemap guidance describes how sitemaps can help search engines discover URLs. A sitemap is a discovery aid, not a substitute for working internal links or correct redirects.

For practical checks beyond search, use the small-business website launch checklist to review forms, usability and other essentials before the new site goes live.

6. Launch in a controlled way

Choose a launch window when someone can check the site afterwards. For a small website, that might mean a weekday morning rather than late on Friday. Keep a copy of the old URL inventory and redirect map somewhere the team can reach them.

At launch, remove staging restrictions, publish the redirects, update internal links and submit or refresh the sitemap in Google Search Console. Use its URL Inspection tool to check a few high-priority pages, especially the homepage, key service pages and any page whose address changed. Google documents the tool in its Search Console URL Inspection help.

Don’t change domains, URLs, design, content and analytics configuration all at once unless there is a clear reason. When several large changes happen together, diagnosing a problem becomes harder. If the project allows it, keep changes focused and record the date and scope of the launch.

7. Monitor the site after launch

A launch is the start of the checking period, not the end of the project. In the first few days, crawl the live site and look for broken links, unexpected 404s, redirect loops, blocked pages and missing metadata. Check a sample of redirects manually and make sure they land on the page a visitor would reasonably expect.

Then review Search Console and analytics over the following weeks. Look for indexing issues, clicks and impressions on important pages, landing-page visits and completed enquiries or sales. Compare like with like where possible, allowing for normal changes in demand and seasonality. A single day’s movement is not enough to diagnose the cause of a change.

If an important page has lost visibility, check the basics first: is it indexable, does it return the right status, is its canonical correct, and does the redirect point to a relevant page? Then review whether its content still meets the searcher’s need and whether useful internal links point to it. Fix specific problems rather than making broad changes in response to an unexplained dip.

Frequently asked questions

Will a website redesign automatically hurt SEO?

No. A redesign can preserve or improve search visibility if important content, URLs and technical signals are handled carefully. Risk comes from avoidable changes such as deleting useful pages, breaking redirects or leaving the new site blocked from indexing.

Do I need to redirect every old URL?

No. Redirect URLs that have moved to a relevant replacement. If a page has no suitable successor, it can return a proper 404 or 410 status. Do not redirect unrelated pages to the homepage simply to avoid not-found responses.

How long should I keep redirects in place?

Keep permanent redirects for as long as you can, particularly when old pages may still be bookmarked or linked from other websites. Removing them too soon can make old links fail for visitors and search engines.

Should I change page URLs during a redesign?

Only when there is a useful reason, such as improving a confusing structure or consolidating content. If a URL is already clear and the page is staying, retaining it usually makes the migration simpler.

What should I check if search traffic drops after launch?

Check that the site is indexable, redirects work, key pages return the right status and canonical tags point to the intended URLs. Then review Search Console for affected pages and queries. Compare performance over a sensible period and investigate page by page before making further changes.