Using Checkredirects.io with Screaming Frog
Screaming Frog returns the final status code and destination for each redirect but does not expose intermediate hops, per-hop TLS, security headers, or how different user-agents see the URL. This guide pipes a Screaming Frog export through a batch check to fill those gaps.
What Screaming Frog shows vs what Checkredirects.io adds
Screaming Frog reports the final status code and destination URL. It does not show you the intermediate hops, how long each hop takes, what TLS certificate each server presents, or whether Googlebot sees a different redirect than Chrome.
Checkredirects.io fills these gaps. You get the full chain hop by hop, with timing breakdown (DNS, TCP, TLS, TTFB), certificate details (subject, issuer, SANs, expiry), security headers (HSTS, CSP, X-Frame-Options), and the ability to compare how different bots see the same URL.
Step 1: Export URLs from Screaming Frog
Crawl your site in Screaming Frog. Go to Bulk Export > Response Codes > Redirected URLs (3xx). Export as CSV. This gives you every URL that redirects.
Alternatively, export all URLs and filter to the ones you want to audit.
Step 2: Batch check in Checkredirects.io
Go to the Batch Checker and paste the URLs from your export, or upload the CSV directly. The batch checker processes all URLs concurrently and gives you filterable, sortable results.
Or use the API directly:
curl -X POST https://api.checkredirects.io/v1/batch \
-H "Authorization: Bearer httpnd_your_key" \
-H "Content-Type: application/json" \
-d '{urls": ["https://example.com/page1", "https://example.com/page2"]}'Step 3: Compare user agents
For URLs where you suspect cloaking or bot-specific behavior, use the User-Agent Comparison tool. Select the SEO Essentials pack (Googlebot Desktop, Googlebot Mobile, Bingbot, Chrome, Safari) and check if the redirect behavior differs.
This catches common issues like: Googlebot gets a 200 while Chrome gets a 301, or mobile Googlebot lands on a different page than desktop.
Step 4: Export and merge
Export your Checkredirects.io results to CSV or Google Sheets. Merge with your Screaming Frog data by matching on the original URL column. Now you have Screaming Frog's crawl data enriched with per-hop chain details, TLS info, and security headers.
When to use this workflow
- After a site migration, to verify redirect chains are clean
- During a technical SEO audit, to check for security header gaps
- When investigating user-agent cloaking or bot-specific redirects
- Before a replatforming, to baseline current redirect behavior
Related guides
- Check redirects from an Ahrefs Site Audit
- Check redirects from SEMrush Site Audit
- Site migration redirect checklist
Run a Screaming Frog export through a batch check
Free plan includes 250 checks per month.