LINK-V
LINK-V · Article

How to Redesign Your Website Without Losing Search Traffic

November 19, 2026

A redesign can change the pages people find through search. Record what matters, decide where old addresses should lead and check the public result. Careful preparation reduces avoidable mistakes, but traffic retention is never guaranteed.


How to Redesign Your Website Without Losing Search Traffic

Before approving a website redesign, identify the pages that bring useful visitors, keep suitable addresses and content, and record where any changed pages will go. Check that plan before launch and check the public website afterward. This reduces avoidable mistakes. It cannot guarantee that search traffic will stay the same.

Which pages do people find through search?

Start with the current website while you can still inspect it. Ask for a list of important search landing pages, the pages visitors arrive on from search results. Include pages that lead to enquiries, purchases or other useful tasks, as well as popular articles. A quiet page answering a specific buying question may deserve protection too.

Use Search Console’s Performance report to look at pages, search queries, clicks and impressions over a suitable date range. Compare similar periods and account for seasonal demand. Search clicks tell you about visits from Google; your analytics and business records help show what those visitors did next.

Keep a baseline: the old addresses, what each important page helps someone do, its relevant content, response and key page fields. Save the evidence before the old website disappears. Agree who can approve a content removal or address change, and who investigates a technical difference.

Grace WebCompare compares your old and new website’s URL responses, redirect destinations, titles, descriptions, H1 headings and canonical paths. You can compare live, local or staging sites and rescan an individual URL after a correction. Use the differences to guide a review; a person still decides what should change.

Compare your old and new website

What should happen to each old address?

Give every important old URL a deliberate outcome. A new design alone is no reason to rename a useful address. Where the page genuinely moves, map its old address to the most relevant replacement. The list should explain the decision well enough that someone can test it.

Keep the address

A useful service page stays at /services/repairs/. The rebuilt page should still answer the relevant questions and be reachable at that address.

Move to a relevant replacement

An old repair guide becomes part of a fuller maintenance guide. Record that destination and check that the old address permanently redirects there.

Remove without a replacement

An expired offer has no useful equivalent. Agree its removal and let the address report that the page is gone. Sending it to an unrelated homepage can confuse the visitor.

These are hypothetical examples. On your website, several older pages may sensibly combine into one useful replacement. Review the content and reader’s purpose before approving that choice. Avoid sending every removed page to the homepage simply to make the old links appear to work.

Google’s guidance for site moves with URL changes explains URL mapping, permanent redirects and the related search checks. Apply its move steps where addresses actually change. A redesign keeping the same addresses does not need Google’s Change of Address tool.

What evidence should you see before approving launch?

Ask the team to compare important old pages with their intended replacements. Can a visitor still find the answer, product information, document or image they came for? A page can return successfully and still have lost the useful part of its content. Review that meaning alongside the technical comparison.

For a retained address, check that the expected page loads successfully. For a moved address, follow the old link and confirm it redirects directly to the relevant new page. Check important internal links, navigation and links within articles so they lead to the intended destinations.

Review page titles, main headings and descriptions against the approved content. They can change as part of a better page, but unexplained omissions deserve attention. Ask the team to verify canonical addresses, which identify the preferred version of a page, and indexing settings. A noindex instruction tells search engines to leave a page out of their index. It is useful in some situations and a serious mistake on a page meant to attract search visitors.

Keeping every URL unchanged still leaves work to check. A rebuild can alter content, internal links, canonical addresses or indexing settings without changing an address. In particular, restrictions used on a staging site must be reviewed before the public launch.

Where relevant, include sitemap addresses and language-version annotations in that review. Have the team record intentional differences and unresolved faults. Grace WebCompare can help reveal differences in its supported page fields; the team fixes the website and separately reviews content meaning, visual design and visitor tasks.

If the project also replaces the publishing system, our guide to moving from WordPress to a custom website covers that wider decision. If the aim is simply to change the hosting provider, first consider moving a website without rebuilding it.

What needs checking again on launch day?

Repeat the important checks on the public website. A successful staging test does not prove that live redirects, indexing settings or configuration are correct. Follow old search landing-page addresses, test their expected destinations and complete the main visitor tasks.

Name the person who investigates broken important routes and the person who decides how to handle a serious launch fault. Agree how they can be reached and what evidence they need. Our guide to planning a website update and recovery explains the separate questions around launch, live data and recovery.

What should you watch after the redesign?

Keep the old-to-new page map available after launch. Compare important landing pages and search queries using consistent filters and comparable dates. Alongside clicks and impressions, check errors, redirects, indexing and the journeys that lead to enquiries or sales. When an address changes, review its replacement as well as the old address.

Google warns that search rankings may fluctuate during a site move while it recrawls and processes the website. A decline deserves investigation, but it does not identify the cause by itself. Check for specific faults such as a missing page, an irrelevant redirect or an indexing restriction. Also consider content changes and seasonal demand rather than assuming every change is a redirect problem.

Agree who reviews the results and when they report back. Keep unresolved issues assigned until someone verifies the correction. There is no universal date by which traffic must recover, and a clean comparison cannot promise future rankings. The useful approval decision is whether important pages have an agreed destination, the checks support that decision and someone owns the follow-up.

Questions about redesigns and search traffic

Do we need redirects if our URLs stay the same?

A redesign alone does not require migration redirects for addresses that remain unchanged. Check that those addresses still serve the intended content, with working links, appropriate canonical addresses and the intended indexing settings.

Can we guarantee that search traffic will stay the same?

No. Search results can change, and Google warns of fluctuations during site moves. A baseline, deliberate page mapping and verified launch checks reduce avoidable errors without guaranteeing traffic, rankings or sales.

What should we check after launch?

Follow important old addresses to their expected pages, check errors and indexing, and compare old and replacement landing pages in Search Console over comparable periods. Check whether visitors can complete the business tasks that matter, and assign someone to investigate differences.

Does a website comparison decide which content to keep?

It can show supported technical and page-field differences. A person needs to decide whether a change is intentional and whether the replacement answers the visitor’s question. Review content, design and important tasks alongside the comparison.

LINK-V LINK-V