SEO Analysis

Single-Page Broken Link Checker

Run a limited check of three distinct link destinations from one public page and distinguish HTTP errors from unverified links.

Remote public website analysis · No account required

Inspect a public website

Analyze URL sends the submitted URL, including its query parameters, to the WebToolspire API. The API checks public DNS and requests the target without your browser cookies or authorization. Do not submit secret URLs.

One URL, an eight-second server deadline, and at most five redirects. Remote HTML is limited to 128 KiB; JavaScript is not executed.

Limited check of three unique destinations from the first 60 source links. Each target has a 1.2-second deadline and at most two redirects. Unchecked or inconclusive links remain unverified. Results arrive together after the bounded check.

Add your input, then run the tool to see results.
WORK WITH CONFIDENCE

Understand your results

For maintainers spot-checking destinations linked from one page.

This limited single-page check extracts the first 60 anchor or area links and requests at most three distinct HTTP(S) destinations in source order. Every hop goes through the existing URL, public DNS and redirect validation. GET response bodies are cancelled after headers. Unchecked links, blocked requests and timeouts remain unverified.

How to use this tool

  1. Enter a public source page URL.
  2. Run the bounded analysis and wait for the combined result.
  3. Filter HTTP errors separately from redirects, timeouts and unverified rows, then export the CSV.

What the observations mean

HTTP error means a status was actually returned to the Worker. Redirect and successful responses are observations. Timeouts and security blocks do not establish a broken destination.

Worked example

Spot-check a page with links to a missing resource and an access-controlled area.

<a href="/missing/">Old guide</a> <a href="/account/">Account</a>

A returned 404 is an observed HTTP error. A 403 or a timeout is unverified. Only eligible destinations within the budget are requested.

Limits and processing

One source, at most three distinct target URLs, sequential checks, two redirects per target, 45 total outgoing requests including DNS, and an eight-second source/report deadline. No full-site crawling or streaming progress.

Common problems and practical fixes

The target times out
The per-destination deadline is 1.2 seconds. Verify manually or rerun later.
A link remains unverified
It may be outside the three-target budget, duplicated, non-HTTP(S), blocked or beyond the deadline.
The page has more links
Only 60 source links are reported, with later links omitted and unverified.

Best practices

Use the report as a spot check and confirm an error in its publishing context before removing a link.

Practical tips

  • Start with a small representative page.
  • Check access-denied responses in a browser before treating them as broken.
A LITTLE MORE CLARITY

Frequently asked questions

Practical answers for using the Single-Page Broken Link Checker.

Does this crawl the whole site?

No. It never recursively reads a destination or discovers more links.

Why are most links unverified?

The Free-plan version checks at most three unique destinations and has strict deadline and redirect budgets.

Is a 403 response a broken link?

It can reflect access control or bot protection. The checker labels access-restricted responses unverified.