Website audit app for Mac

Know what needs fixing. Prove what changed.

Damdit loads the sites you build in a real browser, checks up to 500 pages and backs every issue with evidence. When a page times out or a check can’t run, you see that too. Never a quiet pass.

  • Free for 14 days, no card needed
  • Apple silicon, macOS 14 or later
  • One subscription covers 2 computers
  • Windows and Linux later
Damdit Overview for Northwind Studio: health score, next steps, issues by severity and audit coverage.
Damdit with a demo website, Northwind Studio, after its sixth audit: the score, what to fix first, and what the audit could not check.
  • Rendered in ChromiumYour JavaScript runs before anything is checked.

  • No quiet passesA page it couldn’t check is listed as not checked.

  • Evidence on every issueThe pages, the element, what was found.

  • Stays on your MacAudits never go to a Damdit server.

Coverage

A missing result is not a clean result.

Plenty of audit tools treat a page that timed out like a page that passed. You hand over a clean report and find out later it wasn’t clean. Damdit keeps the two apart.

Coverage on every audit.

Pages checked out of pages planned, and which areas weren’t measured. “Speed not measured: PageSpeed is off” is part of the result.

Couldn’t check, not passed.

A timeout, a website that blocks Damdit or a check that couldn’t run is reported as exactly that.

A person decides what a rule can’t.

Whether some text is placeholder goes to Needs review. It doesn’t touch the score.

Coverage

Coverage limited

12pages audited · 13 addresses found

Audited 12Not audited 1

  • MeasuredURL Health, SEO, Security and 7 more areas

  • Not measuredTracking · Content · Class Hygiene

  • Real-user experienceNot connected

Example: the demo website Northwind Studio after its sixth audit.

Evidence

Every issue shows its evidence.

One issue per rule, with every page it affects. A label missing from a shared footer shows up as one issue on 200 pages, not 200 separate findings.

The issue
What’s wrong, how serious it is and where it appears.
The evidence
What Damdit observed on each page, down to the element.
The fix
What to change, and what the result should look like.
One issue in Damdit: This URL returns an HTTP error, high severity, with how to fix it, what happened and the evidence: observed HTTP 404, expected a successful page response.
$ damdit check http://localhost:4321 --format textLocal check of http://localhost:4321 (saved nowhere)Score: 93Issues: 3  findings: 15  critical 1, high 0, medium 2, low 0Coverage: complete  [critical] A form field has no usable label — 12 findings on 12 pages  [medium] The page has no meta description — 1 finding on 1 page  [medium] The page has no working social preview image — 2 findings on 2 pagesNot applicable here: security headers, HTTPS, robots.txt,the sitemap and PageSpeed need the live host.

Environments

Catch it on localhost. Confirm it on production.

Give a project up to three addresses: production, staging and your local dev server. Each keeps its own audits, history and issues, so a messy staging run never touches production’s numbers.

Production
northwind.example
Staging
staging.northwind.example
Local
localhost:4321
  • On localhost, checks only the live host can answer, like security headers, robots.txt or the sitemap, read “not applicable”, not “passed”.
  • No project needed for a quick look: damdit check audits your dev server and saves nothing.
  • Not yet: Staging behind basic auth or a password page can’t be audited yet. Damdit doesn’t log in.

History

Prove what changed.

Run another audit after your changes. History shows what’s new, what’s resolved, what came back and what’s still there, audit by audit.

Or put a website on a schedule: daily, weekly or monthly. Audits run in the background with the window closed and tell you when an issue is new or comes back. Your Mac needs to be on and you need to be logged in.

Damdit History for Northwind Studio: the health score across six audits, every audit run, and what changed since the previous audit, such as 2 resolved issues.

For your AI tools

Fix it with your AI. Prove it with Damdit.

Claude Code, Cursor, Claude Desktop and Codex read your audits through MCP or the damdit command. Answers come from the audit, with the issue IDs behind them.

  1. Ask what changed or what to fix first.
  2. Fix in your code. Damdit never edits the website.
  3. Verify with a new audit that shows it Resolved.
How Damdit works with AI tools
Claude CodeMCP · damdit

I fixed the footer contrast. Did it work?

damdit · run_audit, compare_issue_history

Yes. The new audit of Oct 13 no longer detects Text contrast is below the required minimum on any of the 12 pages. It’s Resolved. iss_7c1f

But one issue came back: A form field has no usable label, on 12 pages. The newsletter form in the footer lost its label again.

Reports

Reports you can send as they are.

The same findings, written for whoever reads them. PDF, HTML or Markdown, and PDF and HTML carry the project’s logo.

For your client.

Plain language: the score, the top priorities, what changed and what an automated audit can’t confirm.

For your developer.

Every issue, the affected pages, the evidence and how to fix it.

For your AI.

A JSON package an agent can work from.

Damdit documents the issues. You decide how to address them.

For Webflow builders

It reads your Webflow CMS, too.

Connect a site token with read access and Damdit checks what a crawler can’t see: a published post pointing to a draft author, a reference to the wrong collection, a required field left empty. Leftover class names like div-block-47 land on the review list before handover.

Damdit for Webflow

Privacy first

Your websites are your business. Not ours.

Damdit is built to know as little about you as it can. It doesn’t track you, and it sends no diagnostics unless you say yes.

Read the Privacy Policy

Your audits stay on your computer.

Projects, website addresses, evidence, reports and access keys never go to a Damdit server. Optional modules talk to Webflow and Google directly. Your Damdit account only knows your email address, your computers and your subscription.

No tracking.

This website has no cookies, advertising pixels or cross-site tracking. Page views are counted by our own cookieless statistics, without storing IP addresses. Sign-in and account emails have no open or click tracking.

Anonymous numbers, only if you say yes.

Damdit asks once and sends nothing until you agree. With diagnostics on, it shares a few numbers after an audit, like the score and how many issues of each severity it found. Never a website address, page content or which issues. Change your mind any time in Settings.

Read-only. Made in the EU.

Audits never edit or publish your website. Damdit is built in the Czech Republic, and your account data and its backups are stored with European providers in the EU.

FAQ

A few things worth knowing.

Does it run JavaScript?

Yes. Every page loads in Chromium, and the title, meta description, robots and canonical are read from the rendered page, not the raw HTML. If a page redirects on the client side after load, Damdit gives it a few seconds to settle.

How many pages does an audit check?

Up to 500 pages, plus up to 500 link checks. Pages beyond the limit are listed in coverage as not checked.

Can it audit staging behind a password?

Not yet. A site behind basic auth or a password page shows up as password-protected, and its pages aren’t checked. Your local dev server works: add it as the project’s local address.

Does it run in CI?

Not yet. The damdit command runs on your Mac alongside the app, so it fits scripts and coding agents, not CI runners.

Will Damdit change my website?

No. Damdit inspects your website and records findings. It doesn’t edit or publish anything.

Does it find every issue?

No automated audit can. Damdit shows what it checked, where coverage was limited, and what couldn’t be checked. Some questions still need a manual review.

Does it work offline?

Running an audit requires access to the website and any connected services. Your saved audit history and reports remain available locally.

Can I use the results with my own AI?

Yes. Export structured audit data, or let your AI tools work with Damdit directly. The app includes a command-line tool and an MCP server, so tools such as Claude Code, Codex, Cursor, or Claude Desktop can run audits and read findings on your computer. You can turn this off in Settings. Damdit doesn’t send your audit data anywhere; your AI tool’s own terms apply to what you share with it.

What does it cost?

€12.99 a month, or €119.88 a year (€9.99 a month) when you pay yearly, excluding VAT, after a 14-day free trial. VAT for your country is added at checkout. One plan with the full app. See pricing

Your next website audit starts here.

Know what needs fixing. Prove what changed. Free for 14 days, no card needed.