Broken link checker

Broken links across the whole site, with the page and the place.

Damdit follows the links on up to 5,000 addresses of your website and asks each link to another website once. A broken link on page 4,000 shows up like one on the home page, with every page that holds it and where it sits.

  • Up to 5,000 addresses in one audit
  • Links to other websites checked too
  • Free for 14 days, no card needed
  • Apple silicon, macOS 14 or later

This URL returns an HTTP error

High1 URL · linked from 214 pages

How to fix

Fix the link in the footer, or restore the page at this address. One fix covers all 214 pages.

Address
northwind.example/plans
Observed
HTTP 404
Linked from
214 pages, e.g. /, /about, /blog/launch
Where
Footer · link text “Pricing”
Example from the demo website Northwind Studio.

A broken link is rarely just one link.

It sits in a footer on 300 pages, or in an old post nobody opens any more. One tool lists it 300 times, another stops at its page limit and never sees it. You fix the one you found and the rest stay.

How Damdit checks links

  1. It reads the whole site.Up to 500 pages in Chromium for the deep checks, then the rest of the site over HTTP, up to 5,000 addresses.

  2. It groups by link, not by page.One issue per broken address, with every page that holds it and where: header, navigation, footer or content. One fix in the footer covers them all.

  3. It asks other websites once.Each external address once, up to 1,000. A site that refuses Damdit with 401, 403, 429 or bot protection reads “Couldn’t verify”, never broken.

  4. It says what it couldn’t reach.Pages past the limit, and links it couldn’t check, are listed in Coverage instead of quietly passing.

What it finds

  • Broken internal links

    Links to pages that answer 404, 410 or a server error.

  • Links to redirects

    Links that still point to an old address and take a detour.

  • Links that can’t work

    Empty links, links to localhost and mistyped addresses like hppts://.

  • Links to other websites

    External pages that are gone. Sites that refuse Damdit are kept apart.

  • Pages no link reaches

    Pages your sitemap or Webflow lists but no link leads to, when Damdit read the whole site.

  • Pages too deep

    Pages four or more clicks from the home page, with the click path to them.

  • A site with no real 404

    Damdit asks for an address that can’t exist and reports a site that answers with a page or a redirect.

  • Link texts that say nothing

    Links that only say “Read more” or “Click here”, in English, Czech, Slovak and German.

Where it stops

What it doesn’t do.

  • It checks up to 5,000 addresses in one audit. Anything past that is listed as not checked.
  • On the 500 pages it opens in Chromium, it reads links after scripts run. The rest of the site is read from the HTML.
  • It finds and documents broken links. It never edits your website.
Does it check links to other websites?

Yes. Each external address once, up to 1,000 per audit. A missing page is an issue; a site that refuses Damdit reads “Couldn’t verify”, so you can check it yourself.

Will it slow down or overload the website?

No. Damdit opens up to 500 pages in a browser and asks each other address once. It’s an audit, not a load test.

Can I check a site that isn’t live yet?

Yes. Audit your local dev server, or add a staging address to the project. Each keeps its own history.

How do I show the client what changed?

Run another audit after the fixes. History shows what’s resolved and what came back, and the client report says so in plain language.

Find the broken links before your client does.

Run Damdit on a site you know well. Free for 14 days, no card needed.