Website Redesign Seo Audit

Don't have time to read this? Schedule a 30-minute call and we will walk you through exactly how this applies to your business. Book a call

Key Takeaways

• A redesign SEO audit is not one audit. It is three: pre-redesign baseline, pre-launch staging review, and post-launch verification.
• The pre-redesign audit is the most overlooked. You cannot protect what you have not documented.
• Staging audits catch configuration errors before they go live. Fixing a noindex tag in staging takes five minutes. Fixing it after two weeks live costs rankings you cannot recover.
• The post-launch audit closes the loop: it confirms that what the redirect map said would happen actually happened.

Most redesign teams treat SEO as something to fix if traffic drops after launch. That approach is expensive.

The right time to audit is before the redesign begins, again in staging, and again in the first 30 days after launch. Each audit catches a different category of problem at the point when it is cheapest to fix.

Here is what each audit covers.

Audit 1: Pre-Redesign Baseline

Run this audit before any design or development work begins. Its purpose is to document exactly what SEO performance the current site has, so the redesign can be built to protect it.

What to Capture

Traffic and rankings:

• Organic sessions by page from Google Analytics (trailing 90 days)
• Keyword rankings for top 50 terms from Search Console Performance
• Pages with most impressions, not just most clicks
• Click-through rates by page for high-impression, low-click opportunities

URL inventory:

• Full crawl of the current site using Screaming Frog or Sitebulb
• Every URL returning a 200 status code
• Existing redirect rules (301s already in place from prior redesigns)
• Pages already returning 404 that could be cleaned up

Authority signals:

• Pages with external backlinks (export from Ahrefs, Semrush, or Moz)
• Pages with the most internal links pointing to them
• Pages appearing in any active ad campaign landing destinations

On-page elements:

• Meta titles and descriptions for every indexed page
• H1 tags for every indexed page
• Structured data / schema markup in use
• Canonical tag configuration

Store all exports outside the current CMS. These files become your recovery baseline if anything goes wrong after launch.

Audit 2: Pre-Launch Staging Review

Run this audit on the staging environment, before the new site goes live. This is where configuration errors are caught.

Technical Checks

Crawlability:

• [ ] robots.txt allows crawling (not set to Disallow: / from development config)
• [ ] No site-wide noindex meta tag is present in the template
• [ ] Priority pages pass URL Inspection and return "URL is on Google"

Redirects:

• [ ] Full redirect map is implemented in staging
• [ ] Every old URL in the map returns 301 (not 302, not 404, not 200)
• [ ] No redirect passes through an intermediate URL (no chains)
• [ ] Homepage redirect is not being used as a catch-all for unmapped URLs

Canonical tags:

• [ ] Canonical tags point to the live domain, not the staging domain
• [ ] Every page has a self-referencing canonical
• [ ] Parameterized URLs (filter, sort, tracking) have canonicals pointing to the clean base URL

Meta data:

• [ ] All meta titles from the baseline audit are present on equivalent new pages
• [ ] All meta descriptions from the baseline audit are present
• [ ] No page has a blank or auto-generated title tag

Structured data:

• [ ] All schema markup from the current site is replicated on equivalent new pages
• [ ] No schema errors appear in Google's Rich Results Test

Performance Checks

Test on mobile, not just desktop. Google uses mobile-first indexing.

Content Checks

• [ ] No priority pages have had body content significantly reduced
• [ ] Heading hierarchy is correct (one H1 per page, logical H2/H3 structure)
• [ ] Internal links throughout the site point to final destination URLs, not redirects
• [ ] XML sitemap is complete and contains only indexable pages

Audit 3: Post-Launch Verification

Run this audit in two passes: the first within 48 hours of launch, the second at the 30-day mark.

48-Hour Post-Launch Check

Search Console:

• Submit the updated XML sitemap immediately after launch
• Check Coverage report for 404 errors within the first 24 hours
• Request indexing on the five highest-priority pages via URL Inspection

Live site spot check:

• View page source on three different page types: a standard page, a blog post, and a service or product page
• Confirm canonical tags point to live domain
• Confirm no noindex tags are present
• Confirm redirect chains are not active on the live server

Warning: CMS caching layers sometimes serve staging configurations on the live domain for the first few hours after launch. Clear all caches and verify again 6 hours post-launch.

Analytics:

• Confirm Google Analytics is firing on all pages (check in real-time view)
• Verify goal and conversion tracking is intact
• Check that filter configurations are not double-counting sessions

30-Day Post-Launch Audit

Indexed page count:

Compare the indexed page count in Search Console Coverage to the pre-launch baseline. A count significantly lower than the old site's indexed pages requires investigation.

Redirect performance:

• Pull a Screaming Frog crawl of the live site
• Check for any new 404 errors not in the original redirect map
• Add missing redirects for any discovered gaps

Rankings comparison:

• Compare keyword rankings for your top 50 terms to the pre-redesign baseline
• For any term that dropped more than 5 positions, identify the associated page and run URL Inspection
• Check whether that page's content, canonical tag, or internal link volume changed

Backlink audit:

High-value backlinks from external domains may point to old URLs that are now redirecting. While 301 redirects pass most equity, direct links to the new URL pass more.

After 30 days, export the top backlinked old URLs that are now redirecting. Contact the linking domains to request a direct link update to the new URL.

Webflow Development Services

Webflow Experts On-Demand

Whether you're starting fresh or need a full revamp—we create fast, modern Webflow sites built for growth.

Let's talk

When to Hire an SEO Consultant for the Audit

For sites under 200 pages with a straightforward URL structure, the audits above can be executed internally with Screaming Frog and Search Console.

For sites with more than 500 pages, complex redirect histories from multiple prior migrations, or significant organic traffic to protect, an external SEO audit before launch is worth the investment. The cost of the audit is typically a small fraction of the revenue at risk if the redesign damages rankings.

The full SEO process for website redesigns provides the broader framework this audit sits within.

For teams deciding whether to manage the audit internally or bring in outside help, the website redesign SEO consultant guide covers when external expertise changes the outcome.

Pro tip: Save all three audit exports — pre-redesign, pre-launch staging, and post-launch 30-day — in a shared folder with dates in the file names. If an SEO issue surfaces six months after launch, these files tell you whether the problem originated in the redesign or developed afterward.

Not sure whether your audit covered everything? LOW/CODE Agency is a leading AI product team for SMBs and startups. We run pre-launch SEO audits as part of every website project and have protected rankings for clients including Medtronic, Zapier, and Sotheby's.

The SEO checklist for website redesigns gives you the condensed version of this process if you need a quick reference before your launch date.

Website projects start at $10,000+. Let's talk