How to redesign a website without losing SEO

Decide whether the project is also a migration

List changes to URLs, domains, CMS, hosting, rendering, architecture, navigation, templates, content, analytics and consent. A visual refresh with stable HTML is a different risk profile from a headless rebuild and complete content restructure.

If several major systems will change, separate them where practical. Google recommends changing one major thing at a time when possible because combined changes make later diagnosis harder.

Record the search and commercial baseline

Identify the pages, queries and journeys that create value. Segment them by template and purpose. Capture traffic, conversions, visibility, indexation, internal links, rendered content, canonicals and structured information before the design decisions become expensive to reverse.

The baseline should also include known faults. A redesign is an opportunity to fix them, but the team needs to distinguish inherited problems from regressions introduced by the new site.

Give each design decision an acceptance test

The project brief should state what a successful redesign must preserve or improve. For a category template, that might mean retaining its useful product context, offering crawlable links to subcategories and showing the same core information in rendered output. For an article template, it might mean keeping author, date, main content and relevant onward journeys available without depending on an interaction.

Review a real prototype against these expectations before approving a component. A beautiful mock-up is not evidence that the published page will work. Give designers and developers a small set of representative pages, including long titles, sparse content, international variants and retired items, so the design system is tested against the site rather than only ideal examples.

Review information architecture before polishing screens

Navigation and page relationships communicate priority. Test whether important pages remain reachable through crawlable links, whether category structures still make sense and whether consolidation removes useful distinctions.

Map old and proposed URLs even if the team expects most paths to remain stable. This exposes pages that disappear, split or merge and creates time to choose relevant destinations rather than redirecting everything to a category or homepage at launch.

Protect the purpose and evidence of valuable pages

Copy reviews often focus on tone and word count. Search risk depends on whether the new page still satisfies the need that earned visibility. Compare headings, primary content, supporting detail, internal links, media and conversion routes on representative pages.

Do not retain weak content simply because it ranks, but make intentional trade-offs. If useful information will be removed, document why the new experience is better and how the missing need will be served elsewhere.

Test templates as systems

Review rendered HTML, metadata, canonical rules, robots directives, status codes, structured data, pagination, hreflang and internal links on staging. Include empty, error and edge states as well as ideal examples.

Client-side rendering can work, but important content and links need to be present reliably. Test with browser rendering and crawl tools rather than assuming that what appears visually will always be available to a crawler.

Make redirects and launch controls explicit

Every changed valuable URL needs a relevant permanent destination. Test chains, loops, parameters, case handling and alternate hostnames. Update internal links and sitemaps to use the final URLs directly.

Create an ordered launch plan with owners and stop conditions. Availability, robots controls, redirects, canonicals, analytics and priority journeys should be checked before broader visual defects. Run a rehearsal so the team knows how long the checks take and how decisions will be made.

If the redesign changes URLs, use the website migration SEO checklist for redirect mapping, rehearsal and post-launch verification.

Monitor patterns rather than one headline graph

Compare page groups, templates, query types and journeys with the baseline. Watch indexation, crawl behaviour, conversions and visibility together. A site can retain aggregate traffic while a commercially important section fails.

Some fluctuation is expected while search systems reprocess significant changes. Technical validation can confirm whether the implementation is correct now; traffic and ranking outcomes require a longer observation window.

Leave the team with a reusable redesign standard

Document the decisions, tests and final behaviour. The best outcome is not only a successful launch but a pattern the organisation can reuse for later templates, campaigns and platform changes.

SEO is most effective when it becomes part of design and engineering quality. That means requirements, examples and acceptance criteria early in delivery rather than a final audit after the important choices are locked.