SEO Audit Before Redesign Example for Growing Sites

A redesign can make a site look sharper and convert better, then quietly erase years of organic search equity. This SEO audit before redesign example shows what a practical pre-launch audit looks like when the goal is not just a prettier website, but a safer growth project.

Picture a 250-page ecommerce brand preparing to move from an aging theme to a faster, more flexible storefront. The new design has cleaner navigation, better product photography, and fewer template variations. Good news for customers. The risk is that category URLs are changing, old collection pages are being removed, and product copy is being shortened to fit the new layout.

None of those decisions is automatically wrong. But each one can affect the pages Google ranks, the queries that bring in buyers, and the links that still send authority to the site. A pre-redesign SEO audit turns those unknowns into a clear launch plan.

Why an audit comes before design approval

Too many teams treat SEO as a QA item for the week before launch. By then, the wireframes are approved, the templates are built, and the developer is trying to finish a long punch list. The choices with the biggest search impact - URL structure, navigation, page types, content modules, and indexation rules - are expensive to change at that stage.

A pre-redesign audit gives marketing, design, and engineering the same baseline. It identifies which pages earn traffic, which templates create technical problems, and which elements must survive the move. It also separates genuine risk from harmless noise. A page with no traffic, no links, and no business purpose may be a good candidate for removal. A low-traffic category page that drives high-margin leads is not.

The audit is not an argument against redesigning. It is the evidence needed to redesign without guessing.

SEO audit before redesign example: the starting snapshot

For our ecommerce example, the team begins by crawling the current site and connecting Google Search Console, Google Analytics 4, PageSpeed Insights, and Chrome UX Report data. Crawl data explains what the site is built like. Google data explains what users and search engines are actually seeing. You need both.

The initial findings look like this:

• 186 indexable URLs, including 42 category pages and 118 product pages
• 31 pages with organic clicks in the past 90 days, generating 78% of search traffic
• 14 URLs with valuable external backlinks, including three discontinued product pages
• 19 broken internal links and 27 redirect chains
• Slow mobile performance on category templates, largely caused by oversized images and third-party scripts
• Duplicate title tags across filtered collection pages

This is not a report card. It is a migration inventory. The team now knows that only a portion of the site carries most of its organic value, but it also knows that several apparently obsolete URLs cannot simply disappear.

A smart audit adds business context here. Compare organic landing pages against conversions, revenue, leads, or assisted conversions where the data is available. A page ranking in position eight may deserve more attention than a page ranking in position two if it introduces visitors to a product line with a higher average order value.

Build a keep, improve, redirect, or retire map

Every current URL should receive a decision before the new site is built. For lean teams, four labels keep the work simple: keep, improve, redirect, or retire.

Keep means the URL, purpose, and core content should remain largely intact. This is common for top-performing product categories, evergreen resources, and pages with strong backlinks. Improve means the page stays, but the redesign fixes an obvious weakness such as thin copy, missing internal links, slow loading, or poor heading structure.

Redirect means the old URL has a clear, relevant replacement. In the example, an old `/outdoor-furniture/` collection is being consolidated into `/patio-furniture/`. That is a sensible one-to-one 301 redirect because the shopper intent remains close. Redirecting it to the homepage would be easier, but less useful to customers and less convincing to search engines.

Retire is reserved for URLs with no suitable replacement and no meaningful search, link, or commercial value. A discontinued item with no traffic may return a true 410 status, or a 404 if that better matches the site’s standard handling. The right choice depends on the situation. What matters is avoiding lazy redirects that send every removed page to a broad category or the homepage.

Put this map in a shared spreadsheet or project board with the old URL, new URL, decision, owner, status code, and notes. It becomes the single source of truth for developers and marketers during launch.

Audit the templates, not only individual pages

A redesign changes systems. Looking only at the top 20 landing pages misses the problems that can repeat across hundreds of URLs.

In this example, the new product page template removes the visible product description from above the fold and loads some content only after a customer interaction. The design may be attractive, but the team needs to confirm the text is present in the rendered HTML and remains accessible to crawlers. If the content is essential to ranking, hiding it behind an interaction is a trade-off worth testing, not a decision to make on taste alone.

The category template creates a different issue. The old site has a short descriptive introduction, subcategory links, and an FAQ section. The proposed version has only a product grid and a large hero image. Removing repetitive copy can improve usability. Removing the only text that explains the category’s relevance can weaken the page. The answer may be a concise, well-designed content block rather than restoring a wall of text.

Check every planned template for one clear H1, sensible heading order, crawlable internal links, canonical tags, indexation directives, structured data, image alt text where it adds context, and mobile performance. Also inspect faceted navigation. Filter URLs can create thousands of near-duplicate pages if parameters are indexable without a deliberate strategy.

Protect internal links and structured data

Navigation changes are a frequent redesign blind spot. A new menu often prioritizes a smaller set of commercial categories, which can be good for shoppers. But if it strands former hub pages or removes links to profitable subcategories, rankings can slip even when redirects are perfect.

Map the internal linking paths to high-value pages. In our example, six best-selling subcategories lose their links from the main menu. The fix is not necessarily putting everything back in the header. The team adds prominent links from relevant parent categories, buying guides, and a revised footer. The pages remain easy to reach in a few clicks, and the navigation stays clean.

Structured data deserves the same care. Product pages may need valid product, offer, and review markup. Organization and breadcrumb markup can support clearer entity signals and search presentation. A redesign is a good time to correct invalid schema, but do not add markup just because a template can support it. The code must reflect visible, accurate page content.

Test the staging site like it is already live

A staging environment is where the migration plan meets reality. Crawl it before launch and compare it against the current-site inventory. Are every planned destination URL available? Are canonical tags pointing to the production domain? Is the noindex tag present only where intended? Are images, scripts, and CSS accessible? Does the mobile version include the same meaningful content and links?

Then test redirects in bulk. A handful of manual checks is not enough when dozens or hundreds of URLs are changing. Review old-to-new mappings for loops, chains, 302s where permanent 301s are intended, irrelevant destinations, and URLs that return errors.

This is also the right point to measure performance. A new site can look lighter while loading more scripts, larger images, or font files. Test key templates on mobile connections, especially category and product pages where organic visitors begin their purchase journey. Core Web Vitals are not a substitute for good content and site architecture, but slow, jumpy pages create a customer problem and can limit search performance.

Launch with owners, monitoring, and a short response window

A successful migration needs named owners. Marketing owns content continuity and business priorities. Engineering owns redirects, tags, rendering, and performance. Whoever manages analytics verifies tracking. If no one owns a check, it is likely to be skipped.

After launch, submit the updated sitemap, validate key pages in Search Console, and watch crawl errors, indexation, traffic, rankings, conversions, and page speed daily for the first week. Expect some movement. Google needs time to process substantial changes, and minor ranking volatility does not always signal a failure.

What deserves immediate attention is a sharp drop in indexed pages, widespread 404s, canonical errors, blocked resources, a major fall in organic conversions, or top landing pages disappearing from results. Keep the old crawl, redirect map, and pre-launch benchmarks handy so the team can diagnose a change quickly instead of debating what the site used to do.

For teams that need the evidence without a dense agency deck, WhatSEO.ai can turn crawl findings and real Google data into a prioritized, implementation-ready task list. The point is not to create more SEO work. It is to give the people building the site a clear answer before launch day.

A redesign should leave customers with a better experience and your team with fewer surprises. Audit the site while its current search value is still visible, then make every design decision with that value in view.