Websites & SEO
Find broken links and redirect chains on a page
Paste a page URL or upload a list of links. Up to 100 links are checked, and you see the status of each one and every redirect step on the way to it.
- URL / CSV / HTML
- Up to 100 links
Three public targets with bounded redirect evidence
- Only targets actually checked are billed
- Private and reserved addresses are blocked
- Transient failures are labelled unknown
result.json · findings.csv · checked-targets.csv · http-evidence.csv · read-me.txt
One clear job, from source to download
- 1
Add the source
Supported formats and limits are visible before the upload.
- 2
Confirm the settings
Review the exact source, options, units and access before processing.
- 3
Inspect and download
Check the preview and warnings, then unlock the complete package.
Check up to 100 links and every redirect step
Where the links come from
You give the tool a page URL or upload a list of links as CSV or HTML. It can check every link on one page, only the links on the same host, or your own list. One job covers up to 100 links. Targets must be publicly reachable. Private and internal network addresses are refused, so you cannot point the checker at an internal staging server.
The result files and how to read them
You get a package of CSV files and a short read-me. checked-targets.csv lists what was actually requested. http-evidence.csv records each redirect hop with its status and a timestamp. findings.csv holds the links that need attention. A timeout, rate limit or blocked request does not prove a link is dead, so those are marked unknown rather than broken. Recheck unknown links before you remove or change them.
Hop limit and what you decide afterwards
You set how many links to check and the maximum number of redirect hops to follow. A chain that runs past your hop limit is recorded as unresolved and is not followed further. The tool reports what it observed and does not change anything on your site. Which redirects to shorten, which links to fix and which unknown results to test again remains your decision.
Questions before you run it
Where do the links come from, a page or my own list?
You pick one source: every link on a single page, only the same-host links on that page, or a URL list you upload. An HTML file works as the link source too.
How many links and redirect hops does one run cover?
Up to 100 targets per job, and each redirect chain is followed to the hop ceiling you set. A chain that keeps going past that ceiling is recorded as unresolved rather than followed silently.
Why is a link reported as unknown instead of broken?
Timeouts, rate limiting and blocked requests do not prove a link is dead, so they are labelled unknown. Only a status the checker actually observed is written as a result.
Can I check links on an internal staging server?
No. Private, loopback and reserved addresses are refused so the checker cannot be aimed at internal infrastructure. Targets have to be publicly reachable.
What evidence do I get for a redirect chain?
http-evidence.csv records each hop with its status and timestamp, checked-targets.csv lists what was actually requested, and findings.csv holds the flagged items. Together they show why a link was classified the way it was.