I Built a Dead Link Checker That Runs in Your CI/CD Pipeline in Under a Second

Most dead link checkers are slow. They launch headless browsers, crawl pages for 30 seconds, and time out on large sites. That's fine for a one-off audit, but useless in a CI/CD pipeline where every second counts. I built one that checks a page in under a second. Here's how it works and how to add it to your deployment pipeline. The Problem You deploy a new version of your site. A link that worked yesterday now 404s because someone renamed a page. Your users find it before you do. Your SEO score drops. The standard fix is a dead link checker. But most: Take 30-60 seconds per page (browser-based crawling) Can't run in CI/CD without adding minutes to your build Don't check image sources, only anchor links Don't report redirect chains (which hurt performance) Quick Mode: Sub-Second Link Checking The Dead Link Checker API has a mode=quick parameter that skips the browser entirely. It fetches the HTML, parses every <a> and <img> tag, and checks each link concurrently with HEAD requests (fal