What Happens to SEO When You Redesign a Website?

Suppose an established roof-repair page moves from /roof-repair to /services/residential/roof-repair. There is nothing inherently wrong with the new URL. The risk is what happens to the old one.

If the old URL disappears and returns a 404, anyone following an old link reaches a dead end. Search engines also have to discover and evaluate a new address without a clear migration signal. A server-side permanent redirect can connect the old page to its new equivalent.

One URL is easy. Established sites may change dozens or hundreds at once, which is why migration planning needs to happen before launch day.

Start with an inventory of the existing site. Combine URLs from the current sitemap, analytics, Search Console, backlinks, internal crawls, and any important campaign or profile links. Then choose the closest new destination for every valuable old page.

The relationship should be relevant: old roof repair to new roof repair, old storm damage to new storm-damage repair. Sending every old URL to the homepage because it is convenient is not the same as preserving the experience. Google specifically advises against redirecting many old URLs to one irrelevant destination.

Google recommends server-side permanent redirects such as 301 or 308 where possible. Point each redirect directly to its final destination and avoid chains that add latency and make troubleshooting harder.

A migration can alter page titles, headings, written content, navigation, internal links, canonical tags, structured data, robots directives, image URLs, XML sitemaps, page speed, mobile usability, rendering, and the overall hierarchy.

Some individual changes may be minor. Changing all of them simultaneously makes a traffic decline much harder to diagnose. Record what performs before launch so the new build can make deliberate improvements instead of accidentally erasing the baseline.

An established company may have a forty-page site. A redesign proposal may reduce it to eight beautiful pages. Some of the removed pages, however, may have been responsible for search traffic, links, and leads even if they were not prominent in the navigation.

Before deleting or consolidating a page, check its organic traffic, keyword visibility, external links, internal links, conversions, historical value, and role in the site’s topical structure. Consolidation can be the right choice, but it should be an SEO decision—not an accidental side effect of simplifying the menu.

Staging sites are often intentionally blocked from search engines. That is sensible until those rules survive the production launch. Important pages can go live with noindex directives, robots restrictions, staging canonicals, broken structured data, or references to the wrong hostname.

Test the production site as a crawler and as a customer. Confirm status codes, redirects, canonicals, robots rules, sitemap URLs, images, forms, analytics, mobile layouts, and navigation. Google’s site-move guidance also recommends testing the new site thoroughly and monitoring both old and new URLs as the transition proceeds.

Redirects preserve paths from old URLs, but they should not become a permanent substitute for website maintenance. Update navigation, body copy, buttons, canonicals, hreflang references, and other internal links to point directly to the new destinations.

The XML sitemap should list the new canonical URLs you want search engines to discover. Old URLs that redirect or no longer exist generally should not remain in the current sitemap. Submit the updated sitemap in Search Console after launch.

Watch Search Console, analytics, rank tracking, server logs, and lead data over the following days and weeks. Look for 404s, unexpected noindex pages, canonical conflicts, sitemap problems, changes in indexed counts, and drops isolated to particular sections.

Some ranking fluctuation can occur while Google recrawls and reindexes changed URLs. The objective is not to panic at every daily movement. It is to catch preventable failures quickly and confirm that important old signals have a clear path to the new site.

Design, development, and SEO work best when they share the migration plan from the beginning. The right question is not whether the website should ever change. It is how to build a better website without throwing away what was already working.