Bulk URL Checker
A free bulk URL checker that tests up to 100 URLs at once and reports their HTTP status codes, full redirect chains, response times, and plain-English flags for common SEO and performance issues. Accepts pasted URL lists, CSV uploads (auto-detects URL columns), and sitemap URLs. Every fetch runs server-side with SSRF protection on every redirect hop. Built for site relaunches, migration audits, and anyone who's tired of checking URLs one at a time.
How a bulk redirect checker works — and why it matters
What a redirect chain is, why multiple hops hurt performance, and how to fix them.
Before a site relaunch or domain migration, someone needs to confirm that every old URL either still works or correctly redirects to its new location. Doing this one URL at a time with a free online checker is a multi-hour chore — and the paid tools that do it in bulk (Ahrefs, SEMrush, Screaming Frog) cap their free tiers specifically to push you toward a subscription.
What is a redirect chain?
When a web server receives a request for a URL that has moved, it returns a 3xx status code (like 301 Moved Permanently or 302 Found) along with a Location header pointing to the new URL. If that new URL also redirects, you get a chain: the browser follows hop after hop until it reaches a page that returns a 200 OK. Each hop is a full HTTP round-trip — a DNS lookup, a TLS handshake, an HTTP request, and an HTTP response — before the browser can even start loading the next one.
Why multiple hops hurt
- Latency: Each redirect adds roughly 100–300ms of server response time on top of the network round-trip. A chain of three redirects can add a full second of delay before the page even begins to load.
- Crawl budget: Search engine bots have a limited budget of pages they'll crawl per session. Wasting that budget on redirect hops means fewer real pages get indexed.
- Broken chains: If any hop in the chain returns an error or goes to a dead URL, every link pointing to the original URL is effectively broken — even if the final destination still exists.
- Security downgrades: A redirect that goes from HTTPS → HTTP → HTTPS is a security downgrade at the HTTP hop. Browsers may warn users, and the intermediate plaintext request is vulnerable to interception.
How to fix redirect chains
The simplest fix: update the original URL to point directly to the final destination, skipping every intermediate hop. If you can't update the source (e.g., the URL is in a third-party link you don't control), at least make sure every hop is a 301 (permanent) rather than a 302 (temporary), and that no hop downgrades from HTTPS to HTTP.
This tool makes that audit possible in bulk: paste up to 100 URLs, upload a CSV from a crawl report, or drop in a sitemap URL, and get a single table showing every chain, every status code, and plain-English flags for the issues worth fixing.
Frequently Asked Questions
Everything you need to know about ForgePlug's Bulk URL Checker
What does this tool check?
What counts as a redirect chain?
Why do redirect chains matter for SEO?
How does the sitemap input work?
Can I upload a CSV file?
What does 'SSRF protection' mean?
Why is there a 100-URL limit?
Does this tool store my URLs?
Tool Overview
A closer look at Bulk URL Checker — how it works, who it's for, and where it fits in your workflow.
Before a site relaunch or domain migration, someone has to confirm that every old URL either still works or correctly redirects to its new location. Doing this one URL at a time with a free online checker is a multi-hour chore — and the paid tools that do it in bulk (Ahrefs, SEMrush, Screaming Frog) cap their free tiers specifically to push you toward a subscription. ForgePlug's Bulk URL Checker is the free alternative: paste up to 100 URLs, upload a CSV crawl export, or drop in a sitemap URL, and get a single table showing every status code, every redirect chain, and plain-English flags for the issues worth fixing.
Every check runs server-side with full SSRF protection on every redirect hop — meaning a URL that 302s to 169.254.169.254 or localhost is caught and blocked, not followed. Results stream back in real time as they finish, so you see progress without waiting for the slowest server to respond. The tool follows redirects manually (not via fetch's automatic redirect-follow), capturing each hop's status code and Location header so you can see the exact path a browser would take.
The free tier caps each run at 100 URLs — enough for a thorough audit of a small-to-medium site. If you need to check hundreds or thousands of URLs at once, scheduled re-checks, or a branded client report, the paid plan will cover that. For now, this covers the gap that no free tool on the internet fills: bulk status checking without an account, without a watermark, and without a credit card.
Key Features
Everything you get with this tool, at a glance.
Bulk Status Check
Test up to 100 URLs at once for HTTP status codes, redirect chains, and response times.
Three Input Modes
Paste a URL list, upload any CSV (auto-detects URL columns), or enter a sitemap URL.
Full Redirect Chains
Follows every hop manually up to 20 deep, recording status codes and Location headers at each step.
SSRF Protection on Every Hop
Validates every redirect destination against private IP ranges — no internal address is ever followed.
Sitemap Parsing
Enter a sitemap URL and the tool extracts all loc entries as the list to check — no copy-paste needed.
Plain-English Flags
Every issue comes with a human-readable explanation and a concrete recommendation for fixing it.
Copy Report & CSV Export
Export results as a formatted text report or a properly escaped CSV for sharing with teammates.
Real-Time Progress
Results stream back as each URL finishes — no waiting for the whole batch to complete.
How to Use Bulk URL Checker
Get from zero to done in four quick steps — no account, no learning curve.
Add your URLs
Paste a list of URLs (one per line or comma-separated), upload a CSV file from a crawl tool, or enter a sitemap URL. The tool auto-detects URLs in any CSV column.
Click Check URLs
The server processes up to 100 URLs with a concurrency pool of 10, following redirects manually and applying SSRF protection on every hop.
Review the results table
Each row shows the URL, final status code, hop count, response time, and a plain-English flag. Click the arrow to expand and see the full redirect chain.
Export and share
Copy the report to your clipboard for a Slack message, or export as CSV to open in a spreadsheet and share with your team or client.
Practical Examples
Real input and output pairs so you know exactly what to expect.
Direct 200 OK
Input
https://example.com/about
Output
Status: 200 OK — no redirects, no issues. Direct response in 142ms.
Single redirect
Input
https://example.com/old-blog/post-1
Output
Status: 200 OK after 1 redirect hop — 301 from /old-blog/post-1 to /blog/post-1, then 200 OK. Flag: 1 redirect hop before reaching its destination.
Chain of three hops
Input
https://old.example.com/page
Output
Status: 200 OK after 3 hops — 301 → 302 → 301 → 200. Flag: 3 redirect hops — consider pointing this URL directly at the final destination to save load time.
404 after redirect
Input
https://example.com/deleted-page
Output
Status: 404 after 1 redirect hop — 301 to /missing, which returns 404. Flag: this page wasnt found. If the page moved, set up a redirect to the new URL.
SSRF blocked on redirect hop
Input
A URL that 302s to http://169.254.169.254/latest/meta-data/
Output
Status: Blocked — Redirect blocked: That URL resolves to a private or reserved address (169.254.169.254) and cant be checked.
Was this tool helpful?
Your feedback helps us improve Bulk URL Checker for everyone.
Share this tool