How to Audit All Links on a Website Before a Redesign

Website redesigns cause more SEO damage than almost any other single event in a site’s lifecycle.

The same pattern follows everywhere: a marketing team spends months on a new design, launches to internal excitement, and then watches organic traffic drop 20-40% over the following weeks. The culprit is almost always the same - broken links, missing redirects, and pages that were quietly removed or restructured without a systematic plan.

A 2022 study by Ahrefs found that 66% of links pointing to websites return 404 errors within 10 years. Redesigns compress that attrition into a single day when done without a link audit. Years of accumulated backlink equity, carefully built internal linking structures, and indexed page authority can disappear in a single deployment.

This guide is the exact process used to prevent that from happening.

Why Redesigns Destroy SEO Equity

Understanding the mechanics of what goes wrong helps you know what to protect.

URL structure changes are the biggest risk. A redesign often comes with “cleaner” URL architecture - moving from /services/web-design/portfolio/ to /work/ feels cleaner, but it breaks every internal and external link built over years of the old structure. Each broken link is a severed channel for PageRank.

Content consolidation removes indexed pages. Redesigns frequently involve consolidating old blog categories, combining thin content pages, or removing outdated service pages. Each deleted page is an opportunity to either 301 redirect its equity to a surviving page or to simply lose it entirely.

Navigation restructuring severs crawl paths. When a new nav is built from scratch, old page structures that were in menus and footers disappear. Pages that were previously one click from the homepage may become four clicks deep - or orphaned entirely, reachable only through their direct URL.

Staging environments use different domains. Links built in staging (e.g., staging.yoursite.com/...) that carry over to production become broken internal links on the live site - a common oversight when redesigns are built on subdomains.

Step 1: Crawl and Export Your Current Site’s Full URL Inventory

Do this before any design work begins. You need a complete map of what exists today.

What to capture:

• Every URL that returns a 200 (OK) status
• Page title and meta description for each
• Organic traffic for the past 12 months (from Google Analytics or Search Console)
• Number of inbound backlinks per URL (from Ahrefs, Semrush, or GSC’s Links report)
• Number of internal links pointing to each URL

Tool options for the crawl:

• redcacti.com/tools/sitemap-audit - free, no login, gives full URL list with status codes
• Screaming Frog (free up to 500 URLs)
• Your registered redCacti account - exports full page list as CSV

From Google Search Console:

• Download Performance -> Pages data for 12 months of traffic per URL
• Download Links -> Top linked pages for backlink counts per URL

Merge these into a spreadsheet with these columns:

This spreadsheet is your source of truth for the entire redesign process. Everything after this step references it.

Step 2: Identify High-Value URLs That Must Be Preserved

Not all URLs are equal. Some carry years of accumulated backlinks and ranking signals. Losing them without a proper redirect is like closing a bank account with savings in it.

Flag any URL with:

• More than 100 organic clicks per month (from GSC)
• More than 5 referring domains linking to it (from your backlink data)
• A conversion history (check your analytics goal completions or events)
• A top-3 ranking for any target keyword

These URLs need one of three outcomes in the new design:

1. Preserved exactly - same URL, same or improved content. No redirect needed.
2. 301 redirected - URL changes, but a redirect is in place from old to new before launch.
3. Consolidated - page is merged into a new page, with a 301 redirect to the consolidation target.

There is no fourth option. A high-value URL that disappears without a redirect is a permanent loss of accumulated equity.

Escalate disagreements about deleted pages. Design teams often want to remove old, thin, or “off-brand” pages. SEO concerns should be part of that conversation - a page ranking #4 for a lucrative keyword is not a candidate for deletion without a plan.

Step 3: Create Your Redirect Map

A redirect map is a document that lists every URL that will change and where it should go. Build this before a single line of new code is deployed.

Format:

Rules for building the redirect map:

1. Every URL in your “Change” or “Delete” column needs a row in the redirect map unless it has zero traffic, zero backlinks, and zero internal links.

2. Map to the closest topically relevant destination. A deleted service page should redirect to the most relevant surviving service page - not to the homepage. Homepage redirects dilute equity and are a signal to Google that you couldn’t find a relevant destination.

3. Avoid redirect chains. If your current site already has a redirect (/A -> /B), and the new site changes /B to /C, your redirect map should add /A -> /C directly - not /A -> /B -> /C.

4. Handle pagination and filtered URLs. Redesigns often change pagination structures (/blog/page/2/) and filter parameters. These are easy to miss and should redirect to the parent page.

5. Include non-page URLs. PDFs, old media files, RSS feed paths, and sitemap URLs should all be mapped if they receive traffic or have external links.

Step 4: Audit Internal Links in the New Design on Staging

Before launch, crawl the staging version of the new site to find broken internal links. This step catches links that were accidentally built to old URL patterns during development.

Common staging broken links:

• Links to the old site’s URL structure that weren’t updated
• Hardcoded staging subdomain URLs (staging.yoursite.com/...) that will break on production
• Links to pages that were in the design but were cut from the final launch build
• Navigation or footer links that reference a page that hasn’t been built yet

Running the staging crawl:

If your staging site is publicly accessible (no login wall):

1. Run redCacti’s free audit tool against the staging URL
2. Note every 4xx error and its source page
3. Fix before launch

If your staging site is behind a login or IP restriction:

• Use Screaming Frog locally and point it at the staging URL (it can handle basic auth)
• Or temporarily whitelist your IP for the crawler

What to look for in the staging crawl report:

• Internal links to old URL patterns - these need to be updated to the new URL structure
• Links to staging domain - any staging.yoursite.com URLs in content need to become yoursite.com
• Broken navigation links - check header, footer, and any mega-menu links
• CMS template links - dynamic links in blog post templates, product cards, etc. that reference old slug patterns

Step 5: Verify All Redirects Are Working

A redirect map is only useful if the redirects are actually configured and working. Test them systematically before launch.

For each row in your redirect map:

1. Visit the old URL on the new site (or staging if redirects are configured there)
2. Confirm it redirects to the expected new URL
3. Confirm the final status code is 200 (not another redirect)
4. Confirm the redirect is 301 (not 302) - check with a browser devtools Network tab or a redirect checker tool

Checking redirect chains: A URL that redirects A -> B -> C instead of A -> C directly is a chain. Each hop costs PageRank. Use a redirect tracer (many are free online) or the curl command:

curl -I -L https://yoursite.com/old-page/

The -L flag follows all redirects and shows each hop with its status code. The final line should be HTTP/2 200 and there should be only one intermediate HTTP/2 301.

Common redirect failures to check:

• Redirect configured without the trailing slash, but links include the trailing slash (or vice versa)
• http:// URLs redirected but https:// versions not covered (or vice versa)
• www vs non-www mismatch
• Redirect loops - A -> B -> A - which make the URL unreachable

Step 6: Run a Post-Launch Audit Within 48 Hours

Even with a thorough pre-launch process, production environments behave differently from staging. Run a full crawl within 48 hours of launch.

Why production differs from staging:

• CDN and caching layers that aren’t present on staging can intercept or modify redirects
• SSL/TLS configuration may differ between environments
• Production database content may have links that weren’t in the staging data
• User-generated content, comments, or dynamic embeds may have broken links not in the static build

What to look for:

• Any 404 that wasn’t in your staging crawl - these are production-specific issues
• Redirect chains that weren’t visible on staging
• Pages returning 200 but showing error content (soft 404s)

Respond immediately to:

• Any high-value URL from your inventory that is returning 404 - this means a redirect was missed or failed
• Navigation links returning 404 - highest impact per fix

Step 7: Monitor the First 30 Days

The month after a redesign launch is the highest-risk period for emerging broken links. Some issues only appear when real users navigate the site in unexpected ways. Some are uncovered by Google’s crawler over time.

Set up weekly automated crawls with redCacti during this period. Any new 404 or broken link appearing in the weekly report during the first 30 days is likely a redesign artifact - fix these with priority.

Watch GSC for signals:

• Coverage report - new 404 errors appearing after launch
• Performance report - traffic drops on specific pages (can indicate a redirect that’s losing equity)
• Crawl stats - increase in 404 responses signals missed redirects at scale

Pre-Launch Checklist

Before design work begins:

• Crawl current site and export full URL inventory
• Pull 12-month traffic data per URL from Google Analytics / GSC
• Pull backlink data per URL from Ahrefs, Semrush, or GSC
• Flag high-value URLs (traffic > 100/mo or backlinks > 5)

During redesign:

• Build redirect map covering every URL that changes or is deleted
• Review redirect map for chains and homepage-dump redirects
• Include all non-page URLs (PDFs, feeds, old category pages)

Pre-launch (staging):

• Run broken link audit on staging environment
• Fix all broken internal links in new design
• Remove all staging-domain URLs from content
• Verify every redirect in redirect map resolves correctly
• Check for redirect chains (3+ hops)

Launch day:

• Confirm redirects are live on production
• Run immediate spot-check of top 10 high-value URLs

Post-launch:

• Full-site crawl within 48 hours
• Fix any new 404s not present on staging
• Set up weekly monitoring for 30 days
• Monitor GSC Coverage report for new 404 errors

A website redesign without a link audit is an SEO liability. The process above is thorough, but it front-loads the work: a URL inventory before design starts means every subsequent decision is made with the SEO cost clearly visible.

The single highest-return action in this guide is building the redirect map before launch. Every other step serves that document.

Start your pre-redesign link audit ->

Run a free crawl of your current site to get your full URL inventory - the first step in any redesign link audit.

Also in this series: How to Find Broken Links on Your Website · How to Fix a 404 Error Without Losing SEO Equity