Broken link checker
DeadLinkTool is a free link integrity toolkit for checking and fixing broken links in website pages, PDFs, Markdown files, GitHub READMEs, and GitLab 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 checker
Check broken links on a public page before a launch, after a migration, or during an SEO cleanup.
Internal links
Review same-domain links on a page so navigation, content links, and crawl paths stay clean.
Backlink checks
Open a page that links to you or a prospect page, then review dead outbound links that may need outreach or redirects.
GitHub and GitLab
Made for GitHub READMEs, GitLab docs, changelogs, setup guides, and Git-based documentation.
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.
Start from the wording that matches the cleanup job in front of you.
Check broken links, 404s, blocked URLs, and working links from a public website page.
Separate same-domain links from external links and focus on internal 404 cleanup.
Review backlink source pages and backlink prospects for dead outbound links.
Check README links, repo docs, GitLab pages, and Markdown paths that break after files move.
Paste Markdown or a supported repo URL, fix bad targets, and export clean Markdown.
Scan PDF links, validate internal destinations, and patch supported external PDF URLs.
Start with a focused guide when you already know the symptom you need to solve.
Prioritize internal 404s, update source links, and use redirects only when they help users.
Understand file moves, branch changes, renamed anchors, and export paths in Git docs.
Recover lost link value with relevant redirects, cleanup scans, and backlink source checks.
Map old URLs to useful replacements, clean internal links, and avoid redirect noise.
Separate access-control blocks from truly broken URLs before changing content.
Recover valuable external links with relevant redirects and focused outreach.
Clean product, collection, navigation, and campaign links without slowing the store.
Fix CMS slug changes, archived pages, and redirect gaps after Webflow publishes.
Find dead references on resource pages and qualify useful replacement opportunities.
Patch supported external PDF URLs when the PDF layout is still correct.
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.
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.
Use a GitHub README link checker to validate README links, relative paths, anchors, and external references before users hit dead docs.
A simple way to tell the difference between a truly broken page and a bot block so your team fixes the right issue first.
Learn why links show 403 Forbidden during scans, when a 403 is a false positive, and how to decide whether the link needs a fix.
A practical approach to fixing WordPress 404s without relying on heavy always-on crawler plugins.
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.