How to Audit All Redirects on a Website (Step-by-Step)

Goals of a Website Redirect Audit

A site migration, domain rebranding, or URL structure cleanup can easily shatter years of accumulated SEO authority if redirects are mismanaged. The primary goal of a comprehensive redirect audit is to ensure that every historical URL cleanly transfers visitors and search engines to its exact 1:1 equivalent page.

During an audit, your technical checklist must verify that:

• Every legacy URL resolves in exactly 1 single HTTP 301 hop.
• There are no multi-hop redirect chains or circular loops.
• Temporary 302 redirects are not accidentally used for permanent URL moves.
• Client-side JavaScript redirects and meta refresh tags are identified and evaluated.
• No high-value inbound links land on broken 404 pages or irrelevantly redirected homepages (Soft 404s).

Step-by-Step Audit Workflow

Follow this 5-step technical sequence when performing a redirect audit:

Step 1: Extract All Historical Target URLs

Gather your complete list of legacy URLs from Google Search Console (Indexed Pages report), XML sitemaps, analytics data (top landing pages over the past 12 months), and backlink profiles (Ahrefs or Semrush).

Step 2: Construct a 1-to-1 URL Mapping Matrix

Pair each old URL with its exact destination equivalent. Avoid blanket redirects where hundreds of old blog posts are pointed to your root homepage — Google treats these as Soft 404 errors and drops their link equity.

Step 3: Run Batch HTTP Header Diagnostics

Crawl the original list of URLs and record the initial HTTP status code (301, 302, 307), total hop count, and final destination HTTP status code (must be 200 OK).

Step 4: Audit Headless DOM Navigation (JS / Meta Refresh)

Server-only crawlers miss client-side JavaScript redirects like window.location.href. Execute a Chrome DevTools Protocol (CDP) pass on suspect pages to catch post-render navigation.

Step 5: Verify Googlebot Indexation

Use Google Search Console URL Inspection to verify that Googlebot sees the updated 301 headers and assigns canonical status to the new destination URLs.

Common Migration & Redirect Errors

Avoid these three high-risk migration traps:

• The Homepage Catch-All Fallback: Redirecting broken 404 links en masse to example.com/ causes Googlebot to ignore the redirects entirely. Always redirect to the closest contextual category or product page.
• Accumulated Redirect Chains: Migration rules layered over old CMS plugins often produce 3-hop or 4-hop chains (e.g., http://old.com → https://old.com → https://new.com/page → https://new.com/page/). Collapse these into 1 direct hop.
• Protocol / Subdomain Mismatches: Forgetting to handle www-to-non-www or http-to-https redirects before applying page-level migrations adds unnecessary latency.

Recommended Free Audit Tools

Auditing URLs requiring multi-hop analysis or JavaScript rendering is easiest with specialized browser diagnostics.

Use our Redirect Chain Checker to inspect full HTTP header traces, spot 301/302 discrepancies, and catch hidden client-side redirects instantly.