How to redesign a website without losing SEO

A redesign does not lose rankings because the colours changed. Rankings fall when the launch quietly changes the things search engines had already learned: URLs, content, internal links, canonical tags, crawl access, structured data and page purpose.

The safest redesign treats the current website as a working system with evidence attached to it. Some pages are valuable even if nobody on the project likes how they look.

The rule that prevents most migration damage

Inventory first. Change second. Redirect third. Verify always.

Google's own migration guidance recommends changing one major thing at a time where practical. If you are changing the domain, CMS and visual design, separating those changes makes faults easier to diagnose. Google also recommends preparing a URL map, testing the new site, using server-side permanent redirects and monitoring both old and new URLs. Google site-move documentation

Before design begins: capture the evidence

Create a spreadsheet or database with every indexable URL. For each URL, record:

• current status code;
• canonical URL;
• title and meta description;
• H1 and core page topic;
• organic clicks and impressions;
• important queries;
• inbound links, where available;
• internal links pointing to the page;
• structured-data types;
• proposed destination on the new site;
• action: keep, improve, merge, redirect or retire.

Search Console is essential here, but it is not a complete crawler. Its performance report explains how clicks, impressions, click-through rate and average position are counted, including differences between page and property aggregation. Export both page and query data for at least the last 16 months if available so seasonality is visible. Google's metric definitions and performance-data guide

Also keep a copy of the old site's crawl, sitemap, analytics landing-page report and top linked pages. This is the baseline for launch QA.

Protect the pages that already work

Every existing URL needs an explicit decision.

Keep

If a page ranks, earns links and serves the same intent, keep its URL. A redesign is not a reason to make `/services/physiotherapy` become `/what-we-do/body-care/physio-vancouver`.

Improve

You can rewrite a weak page, but preserve the parts that explain its performance: topic coverage, proof, useful sections, headings, media and links. Improvement should be deliberate, not an automatic consequence of fitting text into a new layout.

Merge

When two pages genuinely serve the same purpose, combine the useful material and redirect both old URLs to the strongest relevant destination. Google warns against sending many unrelated URLs to the home page because those redirects can be treated as soft 404s.

Retire

If content has no replacement and no value, a real 404 or 410 can be more honest than an irrelevant redirect. First check traffic, backlinks and business use. "Nobody remembers this page" is not evidence.

Build the redirect map before launch

Use one-to-one, server-side permanent redirects from every changed old URL to the closest new equivalent. Avoid chains such as old A to old B to new C. Test the final destination directly.

Google recommends keeping redirects for as long as possible, generally at least one year, so its systems and users have time to transfer signals and update references. In practice, keeping valid legacy redirects indefinitely is often inexpensive. Google site-move documentation

The redirect map should include PDFs, images and campaign URLs when they have traffic or inbound links, not only HTML pages.

Keep the new site out of the index until it is ready

A staging site should require authentication or be blocked from public access. Do not rely only on `robots.txt` to hide confidential staging content. Before launch, check that no staging `noindex` tag, blocked resource, canonical URL or password protection ships to production.

This single mistake is common enough to deserve a launch owner and a signed check.

Preserve more than words

Search understanding comes from relationships as well as copy. Carry over:

• descriptive internal links;
• breadcrumbs and hierarchy;
• image alt text where it is useful and accurate;
• Organization, LocalBusiness, Service, Product, Article and other valid schema;
• author and update information;
• hreflang on multilingual sites;
• pagination and faceted-navigation rules;
• canonical tags;
• XML sitemaps;
• robots directives;
• Open Graph and social-sharing data.

Google's Search Essentials says helpful, reliable, people-first content and clear words in titles, headings, alt text and link text are among the practices with the greatest impact. Structured data and JavaScript also have their own eligibility requirements. Google Search Essentials

Test the site like a search engine and a customer

Before launch, crawl the staging site and check:

• no unintended 404s or 500s;
• no internal links to redirected URLs;
• one correct canonical per indexable page;
• no accidental `noindex`;
• mobile content matches desktop content;
• forms, calls and bookings record conversions;
• structured data validates and matches visible content;
• page titles and H1s are unique and purposeful;
• consent and analytics work as intended;
• key pages meet agreed performance and accessibility standards.

Google uses the mobile version of a page for indexing and ranking, so hiding important content or links on mobile is not a harmless design choice. Google mobile-first indexing guidance

Launch sequence

1. Take a final production crawl and analytics export.
2. Freeze content changes on the old site.
3. Deploy during a staffed, lower-risk window.
4. Remove staging restrictions on production.
5. Enable and test redirects.
6. Confirm canonical tags, robots directives and sitemap URLs.
7. Verify analytics and conversion events with real tests.
8. Submit the new sitemap in Search Console.
9. Use Change of Address only when the domain changes.
10. Inspect representative URLs and watch server logs, Search Console and analytics.

What to watch after launch

Do not judge the migration from one morning of rank checks. Watch trends by page type and query group.

• A sharp fall in indexed pages may point to crawl, canonical or `noindex` problems.
• Stable impressions with fewer clicks may reflect changed search presentation or weaker snippets.
• Lost impressions and position across migrated pages may point to redirect, content or internal-link changes.
• A single template failing points to a local technical defect.
• All channels falling, including direct and paid landing traffic, suggests a site or analytics problem rather than SEO alone.

Google notes that it must crawl old and new URLs to process a move and may crawl the new site more heavily for a period. Temporary movement is possible; unexplained sustained loss is not something to wait out without investigation.

The handoff document

At the end, the business should receive the URL inventory, redirect map, before-and-after crawl, analytics event list, Search Console notes, schema list and known-issue log. A redesign is not safely complete when the home page looks right. It is complete when the old demand reliably reaches the new experience and measurement proves it.

Source check

Migration requirements were verified against multiple current Google Search Central and Search Console documents on August 22, 2026. The checklist combines those requirements into an operating sequence. Google does not guarantee traffic preservation, and this article does not claim a redesign is risk-free.

Sources

• Google Search Central: site moves and URL changes
• Google Search Console: clicks, impressions and position
• Google Search Console: performance-report data
• Google Search Essentials
• Google: mobile-first indexing best practices
• Google: page experience