Broken link checker
Check and edit broken links in website pages, PDFs, Markdown files, GitHub READMEs, GitLab docs, and other Git-based docs.
Start with the checker that matches your content. You can review results for website pages, edit and export Markdown, and update supported links inside PDFs without rebuilding the whole file.
Each checker fits a different kind of source, so it is easier to start in the right place.
Website pages
A simple way to review the links on a page before a launch, after a migration, or during an SEO cleanup.
PDF files
Useful for brochures, reports, manuals, forms, and other PDFs that people still download and share.
Markdown, READMEs, and Git docs
Made for GitHub READMEs, GitLab docs, knowledge bases, changelogs, setup guides, and Git-based docs.
These are the teams and tasks this tool is most useful for.
Review broken internal and outbound links before they turn into dead ends on important pages.
Catch broken README, docs, and changelog links after files move, branches change, or repos get reorganized.
Check PDFs used for forms, applications, onboarding packs, policies, manuals, and other downloadable documents.
Helpful guides for the questions people usually hit when links break across websites, PDFs, and docs.
Case Study
A practical look at the link problems that show up most often on marketing sites, docs hubs, blogs, and resource libraries.
Development
The most common Markdown link mistakes in GitHub READMEs, and how to catch them before they confuse new users.
Technical SEO
A simple way to tell the difference between a truly broken page and a bot block so your team fixes the right issue first.
WordPress
A practical approach to fixing WordPress 404s without relying on heavy always-on crawler plugins.
Development
A straightforward process for reviewing Markdown links in GitHub and GitLab docs before they go live.
SEO Strategy
What broken links change for crawl efficiency, internal linking, and user trust, plus where to fix them first.
A practical look at the link problems that show up most often on marketing sites, docs hubs, blogs, and resource libraries.
The most common Markdown link mistakes in GitHub READMEs, and how to catch them before they confuse new users.
A simple way to tell the difference between a truly broken page and a bot block so your team fixes the right issue first.
A practical approach to fixing WordPress 404s without relying on heavy always-on crawler plugins.
A straightforward process for reviewing Markdown links in GitHub and GitLab docs before they go live.
What broken links change for crawl efficiency, internal linking, and user trust, plus where to fix them first.
Everything you need to know about link health, markdown fixes, Git workflows, SEO impact, and how to use our tools.
A broken link (also known as a dead link) is a hyperlink on a webpage that no longer works because the website is experiencing one or more issues. These usually result in a 404 Not Found error, but can also be caused by 410 (Gone), 500 (Server Error), or timeouts.
Broken links negatively impact both User Experience (UX) and Search Engine Optimization (SEO). They create 'dead ends' for visitors and signal to search engines that your site is poorly maintained, which can lead to lower rankings.
Yes. Paste your markdown content or a GitHub/GitLab URL and we validate external URLs plus relative paths, including root-relative markdown references.
Yes. After a markdown scan, use the live fix panel to edit broken targets, copy the updated markdown, or download a cleaned .md file.
Yes. For external PDF URLs, use the PDF repair panel to replace the link target, optionally update the visible link text, and download a patched PDF.
Yes. Use the PDF tab to scan a public PDF URL or upload a PDF file. We validate both external links and internal PDF destinations.
Absolutely. Search engines like Google crawl your site to understand its structure. Too many 404 errors waste 'crawl budget' and can decrease your site's perceived quality, ultimately hurting your rank.
We recommend a full scan at least once a month, or every time you make significant changes to your site's structure or move pages around.
Website pages, PDFs, and Markdown files each have their own checker, so you can jump straight into the right workflow.