How to redesign a website without losing search visibility

A website redesign does not have to cost you search visibility, but it will if you treat it purely as a design project. Every important URL must either stay the same or redirect permanently to its closest new equivalent, content that performs must be carried over, and indexing settings must be checked before and after launch. Even then, expect some temporary movement in rankings.

Why redesigns lose search visibility

Search visibility describes how often and how prominently your pages appear in Google's results. It is tied to URLs, their content and the links pointing to them, and a redesign often changes all three. Common causes of losses:

• Changed URLs without redirects. If an old address stops working, visitors and Google hit an error page, and the signals that URL had earned are lost.
• Removed content. Pages or sections that seemed unimportant in the design phase are sometimes the ones ranking for valuable searches.
• New internal linking. A simplified navigation can bury important pages or cut them off completely.
• A "noindex" left over from staging. Noindex tells search engines not to include a page in their results. It belongs on the test version, never on the live site.
• Slower pages. Larger images, extra scripts and animations can make the new site slower than the old one, especially on mobile.
• Changed titles and headings. They tell search engines what a page is about. Rewriting them for style alone can weaken the match with what people search for.

All of these are avoidable when SEO is part of the project from the start, not an afterthought.

Before launch: inventory what you have

You cannot protect what you have not recorded. Before anything changes, take stock of the current site, and agree early on who is responsible for redirects and SEO checks.

Crawl and list every URL

A crawler is a tool that follows the links on your site like a search engine and records every address it finds. Combine its results with your XML sitemap, a page export from your content management system and the landing pages in your analytics, including linked PDFs. The result is one complete list of old URLs.

Export Search Console data

Google Search Console shows which pages appear in search results and get clicks, and for which queries. Export top pages and queries for the longest period available to capture seasonal patterns. This is your baseline, and it shows which pages deserve the most care.

Record backlinks

Backlinks are links from other websites to yours. The Links report in Search Console lists your most-linked pages; dedicated SEO tools can add detail. A page with external links should never end in an error after the relaunch.

Decide what happens to each URL

Then decide the future of every old URL:

Removing a page is legitimate, but it should be deliberate. If a page has traffic or backlinks and a reasonable successor exists, redirect it.

Build a 1:1 redirect map

A redirect map is a simple table: old URL on the left, new URL on the right, one row for every old URL that still matters. It is usually the most important document of a relaunch.

For site moves with URL changes, Google recommends permanent server-side redirects, meaning the HTTP status codes 301 or 308. A permanent redirect tells Google that the new address should replace the old one in search results; temporary redirects (302 or 307) do not send that signal. Details are in Google's documentation on site moves with URL changes and on redirects and Google Search.

A few rules keep the map clean:

• Redirect to the closest relevant page. A product page should point to the new version of that product, not to a general overview.
• Do not redirect everything to the homepage. Google may treat mass redirects to an unrelated page as a "soft 404", meaning an error rather than a move, and visitors lose the context they came for.
• Avoid redirect chains. Each old URL should reach its final destination in one step, including redirects left over from earlier relaunches.
• Update internal links. Links within your own site should point straight to the new URLs instead of relying on redirects.

Carry over what already works

A redesign is a good opportunity to improve content, but build on what performs instead of replacing it blindly. If you rewrite pages that rank well, the new version should answer the same questions at least as well.

On every important page of the new site, check:

• Page titles and meta descriptions. Keep proven titles or change them deliberately, not by accident through a new template.
• Headings. One clear main heading per page, with a logical structure below it.
• Internal links. Important pages stay reachable within a few clicks, from the navigation and from related content.
• Canonical tags. A canonical tag tells search engines which URL is the preferred version of a page. Each must point to the final production URL, never to the old site or staging.
• Hreflang for multilingual sites. Hreflang annotations tell Google which version of a page is meant for which language. Each version must reference itself and all others with full URLs, and the references must be reciprocal. See Google's guide to localized versions of your pages.
• XML sitemap. The new sitemap should list only final, indexable URLs and be submitted in Search Console after launch.
• Speed. Test the new templates on a phone and a mobile connection before launch.

Much of this is decided during the build itself, which is why we treat web design and development and SEO as one project rather than two.

Staging, domain changes and launch day

Protect the staging environment

A staging environment is the test copy where the new site is built and reviewed. Protect it with a password and, if needed, noindex so it stays out of search results, then remove both from the production site on launch day. A forgotten noindex or a blocking robots.txt file on the live site is one of the most avoidable causes of lost visibility.

If the domain changes as well

With a new domain, the redirects must be configured on the old domain itself, at the server or hosting level. Every old address, including the variants with and without "www" and "https", should forward to its specific counterpart on the new domain. The old domain therefore has to stay registered and active.

Once the redirects are live, report the move with the Change of Address tool in Search Console, which requires verified ownership of both properties. The tool is meant for moves from one domain or subdomain to another, not for a switch from HTTP to HTTPS. Keep the old domain and its redirects for at least a year; Google recommends keeping redirects for as long as possible.

If possible, do not change domain, URL structure and design all at once. Fewer simultaneous changes make problems easier to trace.

Launch checklist

• Redirect map tested: each old URL returns one 301 or 308 to the correct target
• Noindex and password protection removed; robots.txt does not block important pages
• Canonical tags point to final production URLs
• Hreflang complete and reciprocal (multilingual sites)
• Titles, meta descriptions and headings in place on key pages
• New XML sitemap live and submitted in Search Console
• Search Console set up for the new site (and the old domain, if it changed)
• Analytics and conversion tracking working
• Forms, contact details and 404 page working
• Fresh crawl shows no unexpected errors or redirect chains

After launch: monitor, fix and be patient

The first weeks after launch decide whether small problems stay small. Check the Page indexing and Sitemaps reports in Search Console regularly, and compare clicks and impressions of your key pages with your baseline. Crawl the live site again and add missing redirects for any old URLs that return errors. If you have server logs, they show which URLs Googlebot requests and which errors it encounters.

Expect temporary fluctuations. Google itself notes that rankings can move while a site is recrawled and reindexed, and that a medium-sized site can take a few weeks or more for most pages to move. Nobody can guarantee rankings after a relaunch. Careful preparation removes the avoidable risks, so the new site is judged on its quality rather than on technical mistakes.

In short

A redesign that protects search visibility starts with an inventory, not with a mockup. Record what performs today, give every important URL a clear future, redirect permanently and precisely, and check your indexing settings twice. If you are planning a relaunch, our SEO service covers migrations from the first inventory to post-launch monitoring. Get in touch to talk through your plans.