Free broken link workflow

Markdown Link Checker for READMEs, Docs, and Relative Paths

Use this tool for README files, docs folders, changelogs, knowledge-base articles, and any Markdown content where broken links make docs harder to trust or use.

FreeNo signupPrivate
OR

Good for

  • README and docs maintenance
  • GitHub and GitLab workflows
  • Content cleanup before publishing

What it does

Focused link checking for this workflow

Check and edit broken links in Markdown files, GitHub READMEs, GitLab docs, and other Git-based docs.

  • Checks pasted Markdown or a supported Markdown URL
  • Free to use, with no signup required
  • Validates external links, root-relative links, and repo-relative paths
  • Works with GitHub, GitLab, and similar docs pages

Why it matters

Fix the links that create real friction

Broken documentation links slow down onboarding, code review, support, and release work because readers cannot reach the referenced setup steps, files, or explanations.

  • ✓Checks relative paths as well as external URLs.
  • ✓Free to use, with no signup required.
  • ✓Your Markdown is processed for the check and not stored.

Workflow

How to use the results

Run the scan first, then work from the highest-risk links to the lower-priority cleanup items.

  1. Step 1

    Add Markdown content or URL

    Paste content directly or provide a repository URL for the Markdown file you want to validate.

  2. Step 2

    Review the broken targets

    Look for dead outbound URLs, wrong relative paths, broken heading anchors, and moved docs links.

  3. Step 3

    Fix and export

    Edit the broken targets in the live panel, verify replacements, then copy or download the cleaned Markdown.

FAQ

Can I use this for a private repo?

Yes, if you paste the Markdown content directly into the tool. That avoids relying on a public repository URL.

Does the tool resolve relative Markdown links?

Yes. Checking relative Markdown links is one of the main reasons to use this tool.

What Markdown links should I check before publishing?

Check external URLs, relative file paths, root-relative docs links, and heading anchors, especially after moving files or renaming sections.