Website Redesign Checklist: SEO Edition

Why Redesigns Are Dangerous for SEO

A website redesign is one of the highest-risk events in the lifecycle of your organic search traffic. We have seen businesses lose 40-60% of their organic traffic overnight because a redesign was treated as a purely visual project. Pages get deleted. URLs change without redirects. Internal linking structures collapse. Metadata disappears. The new site looks great and ranks for nothing.

This does not have to happen. A redesign executed with SEO as a first-class requirement can actually improve rankings, not just preserve them. But you need a checklist, and you need to follow it rigorously before, during, and after launch.

Pre-Redesign: Inventory and Baseline

Before anyone touches a wireframe, document exactly what you have and how it performs.

Crawl Your Current Site

Run a full crawl using Screaming Frog, Sitebulb, or a similar crawler. Export every URL on your current site along with:

• HTTP status code
• Page title and meta description
• H1 tag
• Word count
• Number of internal links pointing to each page
• Canonical tag value
• Indexation status (indexed vs. noindexed)

This crawl becomes your reference document. Every URL in this export needs to be accounted for in the new site structure, either by keeping it at the same URL, redirecting it, or deliberately retiring it (with a redirect to the closest relevant page).

Export Your Top-Performing Pages

Pull data from Google Search Console and Google Analytics to identify:

• Pages with the most organic traffic -- These are non-negotiable. They must survive the redesign at the same URL or with a 301 redirect.
• Pages ranking for target keywords -- Even if traffic is low, a page ranking position 8-15 is close to breaking through. Do not lose that progress.
• Pages with the most backlinks -- Use Ahrefs, Semrush, or Google Search Console's Links report. External links are hard to earn. Every page with quality backlinks needs a 301 redirect if its URL changes.
• Pages with the highest conversion rates -- A page that converts at 8% is valuable even if it only gets 50 visits/month. Protect it.

Document Your Current Technical Setup

Record your existing:

• Robots.txt configuration
• XML sitemap location and structure
• Structured data / schema markup
• Canonical tag patterns
• Hreflang tags (if multilingual)
• Internal linking patterns
• 301 redirect rules already in place

Redesigns frequently wipe these configurations. If they are not documented beforehand, they are forgotten.

During the Redesign: SEO Requirements

These items need to be built into the redesign project plan, not bolted on at the end.

URL Structure

Ideal: Keep existing URLs exactly as they are. Same paths, same slugs, same trailing slashes. This eliminates the single largest source of redesign-related traffic loss.

If URLs must change: Build a complete redirect map before development begins. Every old URL gets a 301 redirect to its new equivalent. No exceptions. Do not use 302 redirects -- they tell search engines the change is temporary, which delays passing link equity. A solid SEO strategy treats URL preservation as a hard constraint during any redesign.

Redirect Map

Create a spreadsheet with three columns: Old URL, New URL, and Status Code (301 for all permanent moves). Map every single page. Include:

• All service pages
• All blog posts
• All category and tag archive pages
• Landing pages
• PDF and document URLs that have external links
• Image URLs if they have been linked to or indexed

Test every redirect before launch. Automated testing tools like Screaming Frog can crawl your redirect map and verify each one resolves correctly.

Page Title and Meta Description Migration

Export all existing page titles and meta descriptions. During the redesign, ensure each page retains its optimized title and description. Content management system migrations frequently strip or reset metadata to defaults. Check every page individually.

Content Preservation

Every piece of content that exists on the current site should either:

1. Exist on the new site at the same or a better URL
2. Be redirected to a relevant page on the new site
3. Be deliberately retired because it has zero traffic, zero backlinks, and no keyword value

Option 3 should be rare. When in doubt, redirect rather than delete. A page with even one quality backlink is worth preserving as a redirect target.

Internal Linking Architecture

Redesigns often break internal linking in subtle ways. The old site might have sidebar links, footer links, or in-content links that do not carry over to the new design.

Check: Map out your current internal linking structure. Identify which pages link to which other pages. Ensure the new site replicates or improves these link paths. We have seen redesigns where the blog was completely delinked from service pages, severing the topical authority signals that were driving rankings.

Structured Data

If your current site uses schema markup (LocalBusiness, Article, FAQ, Product, etc.), document it and ensure the new site implements equivalent or improved structured data. Redesigns frequently drop structured data entirely because the development team was not aware it existed.

Image Optimization

A redesign is the perfect opportunity to fix image performance:

• Convert all images to WebP with JPEG/PNG fallbacks
• Implement responsive images with srcset
• Add descriptive alt text to every image
• Compress to the lowest acceptable quality (usually 75-85%)
• Set explicit width and height attributes to prevent layout shift

Launch Day: Verification Checklist

This is the critical window. Run through these checks immediately after the new site goes live.

Immediate Checks (First Hour)

• [ ] All 301 redirects are functioning correctly
• [ ] Robots.txt is not blocking crawlers (check for leftover staging environment rules like Disallow: /)
• [ ] XML sitemap is accessible and contains all new URLs
• [ ] Homepage loads correctly on mobile and desktop
• [ ] HTTPS is enforced with no mixed content warnings
• [ ] Google Search Console is verified on the new site
• [ ] Google Analytics / GA4 tracking code is firing on all pages

First Day Checks

• [ ] Submit updated XML sitemap in Google Search Console
• [ ] Request indexing for your most important pages
• [ ] Run a full site crawl and compare against your pre-redesign crawl
• [ ] Verify all page titles and meta descriptions are correct
• [ ] Check structured data using Google's Rich Results Test on key pages
• [ ] Test site speed on mobile and desktop via PageSpeed Insights
• [ ] Verify canonical tags point to the correct URLs
• [ ] Check that internal links point to live pages (no 404s, no redirect chains)

First Week Monitoring

• [ ] Monitor Google Search Console for crawl errors daily
• [ ] Watch the Index Coverage report for sudden drops in indexed pages
• [ ] Track organic traffic in analytics, comparing day-over-day and week-over-week
• [ ] Check rankings for your top 20 target keywords
• [ ] Review server logs for unusual crawl patterns or high error rates
• [ ] Test all forms, CTAs, and conversion paths

Post-Launch: Recovery and Optimization

Even a well-executed redesign typically sees a temporary traffic fluctuation. Google needs time to recrawl, reassess, and reindex your pages. Here is what to expect and what to do about it.

Weeks 1-2: The Dip

It is normal to see a 10-20% dip in organic traffic in the first two weeks as Google processes changes. This is not cause for panic if your redirects are working and your content is intact. It is cause for panic if the dip exceeds 30% or persists beyond three weeks.

Weeks 2-4: Recovery

Traffic should begin stabilizing and returning to pre-redesign levels. If specific pages are not recovering, check:

• Is the redirect working correctly?
• Has the content changed significantly?
• Did the page lose internal links in the new structure?
• Are there new technical issues (slow load time, render-blocking resources, missing metadata)?

Month 2+: Growth

If the redesign improved site speed, mobile experience, content quality, and internal linking, you should see rankings and traffic begin exceeding pre-redesign levels. This is where a redesign pays off -- not on launch day, but in the months following when improved technical performance compounds with existing content authority.

Real-World Example: What Happens When You Get It Right

When we redesigned the site for Birdtail Waterfowl, SEO was embedded in the project from day one. We mapped every existing URL, preserved all content with keyword value, implemented proper 301 redirects for changed paths, and built the new site with clean HTML, fast load times, and structured data on every page. The result was not a traffic dip -- it was immediate improvement because the technical foundation was dramatically better.

Common Mistakes That Destroy Rankings

These are the errors we see most frequently on redesigns that come to us for recovery:

1. No redirect map. Old URLs return 404s. Google drops them from the index. Backlink equity vanishes.
2. Robots.txt blocking the entire site. A staging environment robots.txt (Disallow: /) goes live with the production site. Google deindexes everything within days.
3. Content consolidation without redirects. Five old pages get merged into one new page, but only one of the five old URLs redirects to the new one. The other four return 404s.
4. Changing URL structure unnecessarily. Renaming /services/search-engine-optimization/ to /services/seo/ might feel cleaner but costs you established URL authority for zero user benefit.
5. Dropping metadata. The CMS migration resets all page titles to the site name and clears meta descriptions. Nobody checks until rankings drop.
6. Killing page speed. The old site loaded in 2 seconds. The new site, with its heavy JavaScript framework, video backgrounds, and unoptimized images, loads in 7 seconds. Beautiful. Slow. Invisible in search results.

The Checklist, Summarized

Before redesign: Full crawl, performance baseline, backlink inventory, redirect map, content audit.

During redesign: URL preservation, redirect implementation, metadata migration, internal link architecture, structured data, image optimization.

Launch day: Redirect verification, robots.txt check, sitemap submission, analytics confirmation, speed test.

Post-launch: Daily monitoring for two weeks, weekly monitoring for two months, ongoing optimization.

A redesign should be an upgrade to your search performance, not a setback. Treating SEO and web design as a single integrated discipline -- rather than handing a finished design to an SEO team for review -- is the difference between a redesign that grows your business and one that costs you a year of recovery.