Markdown Link Rot Checker
Find missing heading anchors, unresolved Markdown references, repeated destinations and HTTP links in saved source. Download the local JSON evidence.
Trace Missing Markdown Anchors and References
Markdown Link Rot Checker: how to use it
- Paste or open Markdown. Choose CommonMark or GitHub Flavored Markdown.
- Choose whether to include images, flag HTTP or scheme-relative URLs, and skip leading YAML front matter. Select Check Markdown links.
- Review source locations, generated heading anchors and repeated destinations. Copy or download the JSON report.
Limits and notes
Accepts 160,000 UTF-16 code units and up to 2,000 link entries and heading anchors. The checker interprets saved source, ignores code examples and raw HTML, and uses GitHub-style heading IDs derived from parsed heading text. External and relative destinations are reported without contacting sites or opening other files.
How your privacy works →Markdown Link Rot Checker: common questions
How are repeated heading IDs handled?
The first parsed heading gets its usual slug. Another Start here heading can become start-here-1. The heading list in the report shows the IDs used for this check.
Why did an external link get a destination label?
External destination means the link was recognized in the saved Markdown. Its HTTP response remains unknown until someone checks the target separately.
Which unresolved references are reported?
The checker looks for explicit patterns such as [Guide][missing] or [Guide][] that stay as literal text. A single bracketed word can be ordinary prose.
Can I check a Markdown file that begins with a thematic break?
Clear Skip leading YAML front matter when a leading line of three dashes is a thematic break. That setting reads the source from the beginning as Markdown.