Check Output Links
Check Output Links
Cleanup ⚡ tab → Project Analysis group
Scans your generated output for broken links — internal file links and external http(s) URLs — and creates a CSV report. Because it checks the built output rather than the source, it finds exactly what your readers would hit.
To check output links
- Build your target so there is output to scan.
- On the Cleanup ⚡ tab, in the Project Analysis group, click Check Output Links.
- Pick the output folder to scan (the picker starts at your project's output folder). All
.htm/.htmlfiles in it are scanned, sub-folders included. - Choose whether to also check external (http/https) links — this needs internet access and can take a while; choose No for offline use.
- A progress dialog shows the scan (you can cancel — a partial report is still produced).
What gets checked
- Links in
a href,img src,link href, andscript src. - Internal links are resolved against the files on disk; a missing file or folder is reported as Broken.
- External URLs are de-duplicated and checked politely (a few in parallel, 10-second timeout, redirects followed). Servers that block robots (HTTP 403/405/429) are reported as Warning rather than broken.
- Same-page
#fragments,mailto:,tel:,javascript:anddata:links are skipped.
The report
- If everything is fine you simply get "No broken links found!".
- Otherwise a CSV report opens automatically with columns Source File; Link; Type; Status; Detail — only broken and warning rows are listed. Header comment lines record the scope, file count, and whether external checking was on. You are offered to save a copy.
Notes
- The tool is read-only — nothing in your project or output is changed.
- For a source-level view of link health (broken xrefs, orphans and more), see Flare Diagnosis and Link Network Graph.
Was this page helpful?
Still stuck? Contact support