Web design and technical SEOImplementation guide

How to redesign your website and protect SEO and inquiries

A new website can look better and lose what already worked. A redesign needs to preserve useful journeys, information and technical signals.

Sources reviewed on

Explore this topic on the map
KEY TAKEAWAY

Before launch, know which URLs exist, what value they provide and where they will go. Test forms and measurement as carefully as the design.

New typography, images and navigation can improve a website. They can also remove a page that generated inquiries, break a form or leave staging settings blocking indexing. Appearance is only one part of a successful launch.

No migration can guarantee every existing Google position. A planned process can reduce avoidable errors and make problems easier to detect quickly.

01 /

Separate redesign, URL changes and hosting changes

A redesign may retain every URL or change them. For URL changes, Google recommends mapping destinations, using relevant permanent redirects and updating signals such as canonicals, links and sitemaps. Redirecting everything to the homepage can create irrelevant destinations.

A hosting-only move is a different scenario with its own access and availability checks. Changing platforms does not automatically require renaming pages that already serve their purpose. Define what changes and why first.

Sources: Google Search Central: Site moves with URL changes · Google Search Central: Changing your hosting

02 /

Inventory commercial value as well as URLs

Collect URLs from the sitemap, internal links and known Search Console pages. Include campaign destinations, externally linked pages and pages generating inquiries, even when they are not the most visited. Review downloads and language versions too.

For each URL, record its purpose, current status and proposed destination. Keep, improve, combine or retire it for a defined reason. A removed page without an equivalent replacement should not redirect somewhere arbitrary merely to avoid a 404.

03 /

Design journeys before polishing components

Choose three buying tasks: understand an offer, find evidence and make contact. Complete each on mobile using the navigation, buttons and information available to a new visitor. Do not assume familiarity with the previous structure.

Keep important content understandable and accessible. An animation that obstructs reading, delays the next step or prevents contact needs adjustment. Include reduced-motion behavior and check contrast, focus and keyboard controls.

04 /

Build a launch test matrix

Our suggested matrix records the page or feature, expected behavior, observed result and owner. Include entry pages, languages, forms, tools, campaign links, the 404 page and applicable privacy notices.

For forms, test required fields, error messages, confirmation and actual receipt at the authorized destination. Use clearly identified test data and coordinate submissions so they are not mistaken for leads. A thank-you screen does not prove the team received the inquiry.

05 /

Review technical signals in the release version

Check HTTP status codes, robots rules, staging blocks, canonicals, relevant hreflang, titles, descriptions and headings. Validate structured data against what the page actually shows. Review alternative text according to each image’s purpose instead of filling it with keywords.

Test important old URLs and their final destinations when redirects are involved. Avoid unnecessary chains. The sitemap should reflect published, indexable pages; inclusion does not compel Google to index a URL. Preserve real publication dates and update modification dates when substantive changes occur.

06 /

Observe the launch against a baseline

Before launch, record inquiries, important pages and available measurement. Afterward, review errors, form receipt, discovery and indexing, comparing periods in context. A single day’s traffic cannot distinguish a fault from ordinary variation.

Keep a recoverable version and concrete rollback criteria for critical failures. A broken form requires immediate action; a ranking fluctuation calls for diagnosis rather than simultaneous changes without evidence.

  • Old URLs have a documented decision and relevant destination where appropriate.
  • The published environment allows intended user and crawler access.
  • Contact, forms and tools have been checked end to end.
  • Mobile and desktop retain readable, usable journeys.
  • Post-launch monitoring and a recovery path are in place.

REFERENCES

Sources and review

Source documentation consulted on October 7, 2026. Platforms and features may change; check the official source before implementation. The English adaptation retains the source review date of the original article.

  1. Site moves with URL changes Google Search Central
  2. Changing your hosting Google Search Central

This guide provides general guidance. It does not guarantee search rankings or replace a review of your business, locations and data.

FROM INSIGHT TO ACTION

Take a practical next step.

All insights

Want a new website without an improvised launch?

We can review your current structure, buying journeys and launch risks before defining the redesign.

Request a free audit