Will a website redesign hurt SEO?

It can if useful content, URLs, internal links, metadata, or technical signals disappear. Google also notes that significant site changes can produce temporary ranking fluctuation while pages are recrawled and reindexed. A complete inventory, relevant permanent redirects, live-site testing, and post-launch monitoring reduce avoidable losses.

Should every old URL redirect to the homepage?

No. Each old URL should redirect to the closest relevant new page. Google warns against sending many unrelated URLs to one destination because that can confuse visitors and may be treated as a soft 404. A retired page with no relevant replacement may be better served with a proper 404 or 410 response.

How long should redesign redirects stay live?

Google recommends keeping redirects as long as possible and generally for at least one year. Keeping useful redirects longer can still help people following old bookmarks or links. Update your internal links immediately so your own visitors do not pass through redirects.

When should I use Search Console Change of Address?

Use it for a move from one domain or subdomain to another after the new site and redirects are live. Google says not to use it for internal path changes or an HTTP to HTTPS move. Those changes still need correct redirects, canonicals, and sitemaps.

Who should own the SEO migration checklist?

One named release owner should coordinate the developer, SEO lead, analytics owner, content approver, and business contact. Every task needs an owner and a verification method. Shared responsibility without a named decision-maker is how noindex tags and broken forms survive launch day.

Website Redesign SEO Checklist

A redesign can improve the site without discarding the search visibility and lead tracking the old one already earned. Work through this interactive checklist before design, during the build, on staging, and after launch.

By Taylor Rupe

Co-Founder & CTO, B.S. Computer Science · Updated Aug 5, 2026

How to Use This Checklist

Check an item only after its result is visible in the relevant system. Crawl the redirects, trace a test form through the CRM, and confirm analytics events in a debug or realtime report.

Phase 1

Before Design Starts

Inventory the site before anyone changes its navigation, content, or URLs. This is where you find the assets a redesign must protect.

Export every crawlable URL on the current site. Use the XML sitemap, CMS, analytics, Search Console, and a crawler. No single source is complete on every site.

Record a pre-launch search and lead baseline. Save organic landing pages, queries, clicks, forms, calls, bookings, and sales so the new site can be compared fairly.

Classify each URL as keep, improve, consolidate, redirect, or remove. A design should follow the content decision. Do not delete a useful page only because it is absent from a mockup.

Create a one-to-one old URL to new URL map. Each valuable old page needs the closest relevant destination. Sending every old page to the homepage creates a poor user path.

Identify pages with external links and organic traffic. These pages have earned value. Give them extra review before changing the topic, URL, or primary content.

Inventory titles, headings, copy, media, downloads, canonicals, and structured data. The visible page is only part of the migration. Important search and accessibility details can disappear during a rebuild.

Document every lead and revenue event. List forms, phone calls, bookings, purchases, chat, CRM routing, and thank-you states before the tracking code moves.

Name a launch owner, rollback decision-maker, and monitoring window. A migration needs clear authority when a redirect, form, DNS record, or tracking event fails.

Start with the URLs that already matter

Google's current site-move guidance recommends using sitemaps, analytics, server logs, Search Console links, and the CMS to find old URLs. It also says to include embedded files such as images, videos, scripts, and styles in the plan when their locations change.

Phase 2

During the Build

Build the new page system around the approved URL map, search intent, and conversion paths. Resolve the SEO requirements before templates are locked.

Keep valuable URLs unchanged when there is no clear reason to move them. Fewer URL changes mean fewer redirects, fewer failure points, and an easier launch.

Give every indexable page a self-referencing canonical. The canonical should point to the final preferred URL, not the staging host or an old address.

Write a unique title, description, H1, and useful main content for each page. The redesign still needs to answer the query and help the visitor make a decision.

Update internal links to point directly to final URLs. Do not rely on redirects for your own navigation, breadcrumbs, body links, or footer links.

Carry over relevant structured data and validate the rendered output. Rebuild schema from current page facts. Do not copy markup that describes content the new page no longer shows.

Preserve useful image, video, and PDF URLs when practical. Embedded files can receive links and search visits too. Include changed asset URLs in the migration plan.

Reserve space for images, embeds, banners, and consent tools. Stable dimensions reduce unexpected layout movement and make the page easier to use.

Implement analytics and business-specific key events in the new templates. Measure the lead form, phone call, booking, or purchase that matters, not only page views.

Phase 3

Before Launch on Staging

Treat staging as a release candidate. Crawl it, test it, and compare it with the old site while both are still available.

Protect staging from public indexing and write down how that protection will be removed. Authentication is preferable when available. If noindex or robots rules are used, they must be part of the launch removal list.

Crawl the rendered staging site. Check status codes, indexability, titles, headings, canonicals, internal links, image alternatives, and structured data at scale.

Test the complete redirect file against the approved URL map. Every old URL should reach the relevant final URL in one hop when possible.

Confirm canonicals, hreflang, sitemaps, and robots rules use the final host. Staging domains and temporary blocks often survive in copied configuration.

Test forms, phone links, bookings, purchases, email delivery, and CRM routing. A successful browser message is not enough. Confirm the lead reaches the system and person who must act on it.

Verify Analytics and ad conversion events in debug and realtime reports. Confirm each event fires once, carries the expected details, and is attributed to the correct destination.

Test on physical phones, with keyboards, across browsers, and with reduced-motion enabled. Automated checks will not catch every focus, overflow, tap-target, readability, or interaction problem.

Run performance tests on representative page types. Test the homepage, service pages, articles, location pages, product pages, and any template with heavy media or scripts.

Phase 4

Launch Day and After

Launch is the start of migration monitoring. Check the live site immediately, then watch search and lead data while crawlers process the changes.

Take a recoverable backup and confirm the rollback plan before the release. Know which version, database, DNS settings, and configuration can be restored if a critical issue appears.

Remove staging authentication, noindex tags, and temporary robots blocks from the live site. Inspect rendered live pages. Do not assume an environment setting changed correctly.

Activate server-side permanent redirects and test high-value URLs first. Google recommends permanent server-side redirects such as 301 or 308 when possible.

Crawl the live site and compare it with the staging crawl. Look for new errors caused by production settings, hostnames, paths, caching, or deployment differences.

Submit the final sitemap in Search Console. The sitemap should contain canonical, indexable, final URLs that return successful responses.

Use Search Console Change of Address only for a domain or subdomain move. It is not for internal path changes or an HTTP to HTTPS move. Redirects and updated sitemaps still matter.

Confirm live forms, calls, bookings, purchases, and analytics events. Run real test leads and trace them through the inbox, CRM, call system, or payment flow.

Monitor crawl errors, index coverage, organic landing pages, and leads after launch. Expect some search fluctuation, but investigate missing pages, error spikes, lost conversion events, and irrelevant redirects.

Keep permanent redirects live for at least one year, and longer for users when practical. Google recommends keeping them as long as possible so signals and old links can move to the new URLs.

Temporary movement is not the same as a failed migration

Google says significant site changes can produce temporary ranking fluctuation while the new URLs are crawled and indexed. That is why the baseline and monitoring plan matter. Watch page-level search and lead data, then fix specific failures instead of reacting to one daily total.

What a Redesign Should Preserve

Herb Stomp already had a real Portland storefront, an established catalog, a long operating history, customer reviews, and educational content. The redesign job was to build a stronger shopping experience without treating those assets as disposable.

Herb Stomp ecommerce homepage before its redesign — Before: the existing store, catalog, and content still had business value.

Herb Stomp custom ecommerce homepage after its redesign — After: a new custom store with the content and commerce paths rebuilt together.

Read the Herb Stomp case study for the project details. If your own redesign involves organic traffic, our SEO audit service can create the baseline and migration map before development starts.

Planning a redesign?

Send us the current site before the new page map is final. We can inventory the search assets, design the migration plan, and build the new site around the business outcomes it needs to keep.

Discuss your redesign See web design services