Why Redirect Auditing Matters

Even a single misconfigured redirect can silently harm your site's performance — slowing page loads, bleeding link equity, or blocking search engines from indexing your content. Regular redirect audits help you catch and fix these issues before they compound.

This guide walks you through a practical audit workflow using free, accessible tools.

Step 1: Check Individual URLs with cURL

cURL is a command-line tool available on macOS, Linux, and Windows (via WSL or Git Bash). It lets you inspect the exact HTTP headers a server returns — including redirect chains.

curl -I -L --max-redirs 10 https://example.com/old-page

The -I flag fetches headers only; -L tells cURL to follow redirects. You'll see each hop in the chain, including the status codes at each step.

Look for:

  • More than 2 hops in any redirect chain
  • Unexpected 302 codes where you expected 301
  • Final destination returning anything other than 200

Step 2: Use a Browser Extension

Browser extensions like Redirect Path (available for Chrome and Firefox) display the full redirect chain in your browser toolbar as you visit any page. This is ideal for quick spot-checks during day-to-day work.

What to look for:

  • Red indicators = 4xx errors (broken links)
  • Yellow indicators = 3xx redirects
  • Green = 200 OK (final destination healthy)

Step 3: Crawl Your Entire Site with Screaming Frog

Screaming Frog SEO Spider has a free tier that crawls up to 500 URLs. It's one of the most effective tools for finding redirect chains and loops across an entire site.

  1. Download and install Screaming Frog (free tier available)
  2. Enter your domain and start a crawl
  3. Navigate to Response Codes → filter by 3xx
  4. Use the Redirect Chains report to identify multi-hop chains
  5. Export the report to a spreadsheet for prioritization

Step 4: Check HTTP Headers with Online Tools

If you don't have access to a command line, several free web-based tools let you inspect HTTP headers and redirect paths:

  • httpstatus.io — Check redirect chains for multiple URLs at once
  • redirect-checker.org — Visual redirect chain display
  • Google Search Console → URL Inspection — Shows how Google actually resolves a URL, including redirects it follows

Step 5: Review Server Logs

Your web server logs (Apache, Nginx, or CDN logs) are the most authoritative source of redirect activity. Look for:

  • High volumes of 301/302 responses — may indicate unresolved old URLs still being linked internally
  • Crawl bot traffic on legacy URLs — Googlebot hitting redirected pages wastes crawl budget
  • Patterns of 404s following 301s — a redirect destination may have been deleted

Building a Redirect Audit Checklist

  1. ✅ All redirect chains resolved to a maximum of 1 hop
  2. ✅ No redirect loops detected
  3. ✅ All permanent moves use 301 (not 302)
  4. ✅ Final destinations return 200 OK
  5. ✅ Internal links updated to point directly to canonical URLs
  6. ✅ XML sitemap contains only canonical, non-redirecting URLs
  7. ✅ Robots.txt does not block crawling of redirect destinations

How Often Should You Audit?

For most websites, a thorough redirect audit every quarter is sufficient. After any major change — CMS migration, domain move, HTTPS upgrade, or large-scale content restructuring — run a full audit immediately before and within two weeks of the change going live.

Summary

Redirect auditing doesn't require expensive enterprise software. With cURL, Screaming Frog's free tier, and a browser extension, you have everything you need to keep your redirects clean, lean, and SEO-friendly.