Broken Link Checker
Scan a local set of HTML files for broken relative/internal targets. External HTTP/HTTPS links are listed separately as unverified because this browser-only version does not bypass cross-origin restrictions.
Use the Broken Link Checker
Scan a local set of HTML files for broken relative/internal targets. External HTTP/HTTPS links are listed separately as unverified because this browser-only version does not bypass cross-origin restrictions.
Calculation, text generation and supported file processing happen locally in your browser; this batch does not require a new external processing service.
This browser-only version does not claim to crawl or verify the live public web. It checks supplied HTML/local files and clearly separates external URLs that still require live verification.
How to use it
Start with the realistic worked example, replace it with your own verified values or files, inspect the result, and check the stated assumptions and limitations before using the output.
How the Broken Link Checker works
Scan a local set of HTML files for broken relative/internal targets. External HTTP/HTTPS links are listed separately as unverified because this browser-only version does not bypass cross-origin restrictions. This page exposes the exact production relationship or documented process, the Build 0223 QA fixture and the boundaries that determine what the result means.
Calculation breakdown
ToolLott will explain the current inputs and displayed result here.
Local broken-link scan
For Broken Link Checker, ToolLott uses this production rule: Resolve relative href/src targets against the supplied local page set; external URLs are listed as unverified. The worked example is anchored to Build 0223 and the current explanation follows the user-entered values and displayed result.
Resolve relative href/src targets against the supplied local page set; external URLs are listed as unverifiedToolLott evaluates the documented relationship with the entered values before display formatting.
| Symbol / input | Meaning | Unit |
|---|---|---|
files | Local HTML files | user input |
maxFiles | Maximum HTML files | user input |
Step-by-step method
- Validate the required values, options and units shown on the page.
- Apply the documented local broken-link scan rule or inspection process.
- Compare the output with the Build 0223 verified example and review the page-specific assumptions before reuse.
Worked example
Owen, a digital marketer, is preparing a small static-site handover and wants to catch a relative link to a file that is absent before the site is deployed.
Example inputs
- Maximum HTML files: 100
Calculation / processing
Use the verified QA fixture: Maximum HTML files: 100.Apply the production local broken-link scan workflow exactly as described on this page.The production QA fixture reports: Local broken-link scan: up to 100 HTML files - external URLs listed as unverified.
The result is the verified Build 0223 output for this exact scenario. It should be interpreted with the displayed inputs, assumptions and limitations rather than as context-free advice.
Assumptions
- The calculation or inspection uses only the values/data explicitly supplied to this tool.
- Units, rates, source text and options are interpreted exactly as labelled; nothing external is inferred unless the page explicitly performs a supported lookup.
Limitations
- The output is limited to the documented formula, heuristic or supplied-data inspection and does not establish facts that the tool has not measured or fetched.
- For financial, engineering, career, academic or production decisions, verify the assumptions and any governing external requirements separately.
Common questions
What does the Broken Link Checker actually do?
Scan a local set of HTML files for broken relative/internal targets. External HTTP/HTTPS links are listed separately as unverified because this browser-only version does not bypass cross-origin restrictions. The methodology documents the production calculation or transformation rather than a generic description.
Does the worked example match the real ToolLott tool?
Yes. It is tied to the passed production QA fixture for Build 0223, including the expected summary.
What should I verify before relying on the output?
Check the entered values, stated assumptions, support boundaries and any authoritative sources linked on the page; independently review high-stakes use.
Methodology sources
This page uses basic mathematical or ToolLott implementation logic that does not require an external factual source. The worked result is still tied to the production tool and QA example.
Related ToolLott tools
A realistic way Owen could use this tool
Owen is a digital marketer.
Owen is preparing a small static-site handover and wants to catch a relative link to a file that is absent before the site is deployed.
Owen uploads index.html and about.html together. The fixture contains four relevant links in total: valid local navigation, a link to missing.html, and one external HTTPS URL. The tool resolves local filenames within the supplied set and deliberately leaves external URLs marked as unverified.
The scan finds exactly 1 broken internal target (missing.html), 1 external URL that still needs a live check, and 4 inspected link targets overall. Owen can fix the missing local page before deployment instead of discovering the dead link after handover.
Fictional scenario using realistic example data. For Ready tools, the worked result is tied to the tested example shown in the tool. Replace the figures with your own inputs and independently verify important professional, financial, legal, health or safety decisions.
What this checker is for
Use it to check broken link using the inputs you provide.
It sits within ToolLott’s SEO Tools collection, where you can also create meta tags, robots.txt, XML sitemaps and schema markup, and check redirects, links, backlinks and keyword density.