Check redirects from a SEMrush Site Audit

SEMrush Site Audit reports the source URL and final destination for redirect chains, temporary redirects, and loops but crawls only as SEMrushBot. This guide takes that export and adds hop-by-hop chain data, per-hop TLS, security headers, and Googlebot/Chrome comparison.

The workflow

1. Run a Site Audit in SEMrush. Go to Site Audit > Issues > Redirects. SEMrush reports redirect chains, temporary redirects, and redirect loops.
2. Export the affected URLs. Export the source URLs from the redirect issues report as CSV.
3. Batch check in Checkredirects.io. Paste or upload the URLs into the batch checker. Every URL is inspected concurrently with full chain details.
4. Review what SEMrush does not show. For each URL, Checkredirects.io shows every intermediate hop, per-hop timing (DNS, TCP, TLS, TTFB), TLS certificate details, security headers, and resolved IP addresses.
5. Compare user agents. SEMrush crawls as SEMrushBot. Use the user-agent comparison to see if Googlebot or Chrome gets a different redirect chain.
6. Set up monitoring. For critical URLs, create a monitor to check them on a schedule and get notified when redirect behavior changes.

What this catches that SEMrush misses

• Intermediate hops in redirect chains (SEMrush shows source and destination, not the middle)
• TLS certificate issues on redirect servers (expired certs, mismatched SANs)
• Security header gaps on 301/302 responses (HSTS missing on redirects)
• Bot-specific redirect behavior (Googlebot vs SEMrushBot vs real browsers)
• Timing bottlenecks (which hop in the chain is slowest)

Related guides

• Check redirects from an Ahrefs Site Audit
• Use Checkredirects.io with Screaming Frog
• How to bulk test 301 redirects

Run your SEMrush export through a batch check

Free plan includes 250 checks per month.

Sign up free