A website redesign can improve credibility, performance, accessibility and conversions. It can also damage years of organic search visibility when the migration is treated as a last-minute technical task.

The risk does not come from changing colors or typography. It comes from changing the signals search engines already use to understand the website: URLs, page content, internal links, headings, metadata, structured data and site architecture.

The safest approach is to treat every redesign as an SEO migration, even when the domain name stays the same.

This checklist explains what to protect before launch, what to test on the new site and what to monitor after the change goes live.

Why Website Redesigns Lose Organic Traffic

Search engines build an understanding of a website over time. Individual URLs earn rankings, backlinks and behavioral history. Internal links show which pages are important. Page titles, headings and body content establish relevance.

A redesign can interrupt those signals when a team:

• Deletes useful pages without replacements

• Changes URLs without redirects

• Redirects every old page to the homepage

• Removes content that supported rankings

• Replaces specific service pages with one generic page

• Changes navigation and leaves important pages orphaned

• Launches with accidental noindex directives

• Forgets canonical tags or structured data

• Allows staging URLs to be indexed

• Ships a slower, JavaScript-heavy experience

A short period of ranking fluctuation can occur after a substantial migration. A severe or lasting decline usually points to a preventable implementation problem.

Google publishes separate guidance for site moves with URL changes and infrastructure changes that keep the same URLs. Use the path that matches the project.

Phase 1: Document What Already Works

Do not redesign from memory. Create a baseline before changing the site.

If the baseline reveals crawl, indexation, canonical or performance problems, use a technical SEO audit checklist to separate existing issues from problems introduced by the redesign.

Crawl the Current Website

Export a complete list of crawlable URLs and record:

• HTTP status code

• Page title

• Meta description

• H1 heading

• Canonical URL

• Indexability

• Internal links

• Image alternative text

• Structured data

• Word count or content length

This crawl becomes the migration inventory. Without it, pages are easy to forget and redirects are difficult to verify.

Export Search and Analytics Data

Use Google Search Console and your analytics platform to identify:

• Pages receiving organic clicks

• Pages receiving search impressions

• Queries driving qualified traffic

• Pages generating form submissions or calls

• Top landing pages

• Seasonal pages

• Pages with strong engagement

Do not judge a page only by total traffic. A low-volume service page may produce more revenue than a popular informational post.

Identify Backlinks and Offline URLs

Record pages that have earned links from other websites. Also note URLs used in printed materials, email campaigns, QR codes, paid ads, social profiles and partner directories.

Those URLs may need to remain in place or redirect permanently to the most relevant new destination.

Phase 2: Decide Which URLs Must Change

The lowest-risk URL change is the one you do not make.

If an existing URL is concise, accurate and ranking well, keep it. A new design does not require a new address for every page.

Change a URL when there is a clear reason, such as:

• Consolidating duplicate pages

• Replacing an outdated information architecture

• Removing meaningless parameters

• Correcting a misleading slug

• Combining domains or subdomains

• Moving from HTTP to HTTPS

Avoid changing URLs only to insert an extra keyword. The migration risk and operational cost may outweigh any theoretical benefit.

Create a One-to-One Redirect Map

Every changed or retired URL should have a documented outcome:

• Keep the same URL

• Permanently redirect to a closely matching page

• Consolidate into a stronger related page

• Return a true 404 or 410 when no replacement exists

Use server-side permanent redirects, normally 301 or 308. Map each old page to the most relevant new page. Do not redirect every removed URL to the homepage; that creates a poor user experience and gives search engines little evidence that the destination is an equivalent replacement.

Avoid redirect chains such as old URL → temporary URL → final URL. Point the original address directly to the final destination.

Phase 3: Preserve the Signals on Important Pages

A redesign should improve content, but it should not erase the reason a page ranks.

For every high-value page, compare the old and new versions.

Retain Search-Relevant Content

Preserve or thoughtfully improve:

• The page's primary topic

• Useful service details

• Location information

• Frequently asked questions

• Proof of experience

• Original images and examples

• Important headings

• Calls to action

Replacing 1,000 words of useful, specific content with a 100-word brand statement may make the design feel cleaner while making the page less useful to customers and search engines.

Good editorial design does not require thin content. It requires better hierarchy.

Migrate Titles and Descriptions Deliberately

Each page needs a unique, descriptive title. Google notes that page titles can influence the title link displayed in search results, while page content and meta descriptions can influence the snippet.

Do not let the new CMS create dozens of titles such as “Service | Company Name.” Carry forward useful titles, then improve them where the search intent or offer has changed.

Preserve Canonicals and Structured Data

Canonical tags should point to the preferred live URL. Structured data should accurately describe content visible on the page and use the current URL.

Validate applicable Organization, LocalBusiness, Article, Breadcrumb, Product or other markup before launch. Do not copy old structured data blindly if the content or business information has changed.

Phase 4: Rebuild the Internal-Link System

Navigation is an SEO decision as well as a user-experience decision.

Important pages should be reachable through ordinary crawlable links. Google recommends standard anchor elements with href attributes and descriptive anchor text. Script-only click handlers may not provide the same reliable crawl path.

Review:

• Main navigation

• Footer navigation

• Breadcrumbs

• Service-page cross-links

• Links within articles

• Related case studies

• Calls to action

• Pagination

Update all internal links to point directly to final URLs instead of relying on redirects. Every page you want indexed should receive at least one meaningful internal link.

Phase 5: Protect the Staging Website

A staging environment should not compete with the live site.

Use authentication or another reliable access restriction. A noindex directive can provide additional protection, but do not rely on robots.txt alone to hide staging content. Google explains that a URL blocked by robots.txt can still appear in search results when other pages link to it.

Before launch, confirm that:

• Staging authentication will not carry into production

• Production pages do not contain noindex

• Production robots.txt permits appropriate crawling

• Canonicals use the live domain

• XML sitemaps use live URLs

• Analytics and conversion tracking use production settings

Accidental production noindex directives are among the most damaging and avoidable migration mistakes.

Phase 6: Test the New Site Before Launch

Run a complete crawl of the staging site and compare it with the migration inventory.

Test:

• All planned redirects

• Page status codes

• Canonical tags

• Titles and descriptions

• Heading structure

• Internal links

• XML sitemaps

• Structured data

• Image paths and alternative text

• Mobile layouts

• Forms and conversion tracking

• Analytics events

• Keyboard navigation

• Screen-reader fundamentals

• Core Web Vitals

Google's current Core Web Vitals thresholds for a good experience are Largest Contentful Paint within 2.5 seconds, Interaction to Next Paint of 200 milliseconds or less, and Cumulative Layout Shift of 0.1 or less at the 75th percentile of visits.

Performance is not merely a score. Test the real devices and connections customers use, especially the mobile experience.

Launch-Day SEO Checklist

When the new site goes live:

1. Verify that important pages return a 200 status.

2. Test a sample from every redirect pattern.

3. Confirm old URLs resolve to the correct new pages.

4. Remove staging-only noindex directives and access restrictions.

5. Verify the production robots.txt file.

6. Publish the updated XML sitemap.

7. Submit the sitemap in Google Search Console.

8. Inspect the homepage and several priority pages.

9. Confirm canonical URLs use HTTPS and the preferred hostname.

10. Test contact forms, phone links and conversion tracking.

11. Check analytics for live traffic.

12. Crawl the production site and resolve critical errors.

Keep the old crawl, redirect map and launch crawl together. They create an audit trail for troubleshooting.

What to Monitor During the First 90 Days

A migration is not complete when the homepage loads.

Monitor weekly at first, then continue at a reasonable cadence:

• Organic clicks and impressions

• Indexed-page counts

• Crawl errors

• Pages excluded from indexing

• 404 responses

• Redirect chains and loops

• Core Web Vitals

• Rankings for priority queries

• Organic leads and revenue

• Server logs for unusual crawler behavior

Compare page groups, not only total traffic. A decline isolated to a service category often points to missing content, internal links or redirect problems within that section.

Avoid reversing every change after a few days. Search engines need time to recrawl and process a meaningful migration. Fix clear technical errors immediately, but use enough data to separate normal volatility from a structural issue.

Website Redesign SEO Mistakes to Avoid

Redirecting Everything to the Homepage

This frustrates visitors and does not preserve the context of the original page. Use the closest relevant destination.

Deleting Content for a Cleaner Design

Improve hierarchy and readability instead of removing useful information. Design and substance should support each other.

Changing the Domain and CMS at the Same Time Without a Plan

Multiple simultaneous changes make troubleshooting difficult. When possible, sequence major changes or create a detailed test and rollback plan.

Launching Without a Baseline

If you did not export traffic, rankings, conversions and crawl data before launch, you will have little evidence for diagnosing a decline.

Treating SEO as a Post-Launch Task

Redirect mapping, content decisions, architecture and performance belong in the project plan from the beginning. An SEO review two days before launch is too late to correct foundational decisions efficiently.

Redesign the Experience, Preserve the Equity

A successful redesign should make a website faster, clearer, more accessible and more effective without discarding the visibility it has already earned.

The essential sequence is straightforward:

1. Inventory the current website.

2. Identify the pages and signals that create value.

3. Keep strong URLs whenever possible.

4. Map every necessary change.

5. Preserve and improve useful content.

6. Test the migration before launch.

7. Monitor performance after launch.

Redkey Web Design combines custom web development with technical SEO so migration planning is part of the build, not an emergency task at the end. Explore our web design and development services and SEO services, or request a site audit before your next redesign.