Website audit app for Mac

Find what’s broken before your client does.

Damdit audits the sites you build in a real browser, right on your Mac. Broken links, accessibility, SEO, speed and the CMS behind it, each issue with the page, the element and what was found. When it couldn’t check something, it says so.

Download for Mac See an issue up close

Free for 14 days, no card needed
Apple silicon, macOS 14 or later
One subscription covers 2 Macs

Damdit Overview for Northwind Studio: health score, next steps, issues by severity and audit coverage. — Damdit after an audit of Northwind Studio, a demo website: the score, what to fix first and what the audit couldn’t check.

Runs on your MacA desktop app. Audits run on your computer, not in a cloud.
Client sites stay privateNothing about the sites you audit reaches Damdit.
No tracking in the appNo analytics, no ad pixels, no usage profile.
Read-onlyIt never edits or publishes a website.

What it finds

One audit. The whole website.

Damdit opens up to 500 pages in Chromium for the deep checks, then reads the rest of the site, up to 5,000 addresses, for links, titles and descriptions.

Everything Damdit checks

How it works

From an address to a fix list in one audit.

Add the website
Production, staging or your dev server on localhost. Each keeps its own history.
Review the plan
Damdit shows the pages it found before it starts. You start the audit when it looks right.
Fix with evidence
What to fix first, where and why. The next audit shows what’s resolved and what came back.

Evidence

Each issue starts with the fix.

Open an issue and Damdit tells you what to do first, grouped by cause. Then the evidence, one example at a time: the page, the element and what was measured.

The fix, by cause: 9 of the 12 slow elements share one cause: the cookie banner. Fix that first and most of the issue is gone.
Where it is: Every page and element it affects, in one list you can sort.
The evidence: What Damdit measured on each page, with the element to copy into your code.

Largest Contentful Paint is slowHigh

Performance · 12 elements on 11 pages

Still detected in the audit of Nov 10, as in every audit since Oct 14 · See history

Open ▾

How to fix

9 of 12

The cookie consent banner is the largest elementLoad the consent script early, or accept the value: visitors who answered the banner don’t see it again.

3 of 12

A hero or card image, or text, is the largest elementReview the main content path, server response, hero media, fonts and render-blocking resources.

Where · 11 pages, measured by PageSpeed lab runs on phone and desktop · See all in Pages

EvidencePagesWhy it mattersHistoryTechnical

Example 1 of 12 · northwind.example/ · phone lab runNext example ›

LCP element

Measured LCP: 4.8 s
Needed: 2.5 s or less
Largest element: Cookie consent banner text
Third-party: Cookie consent

Example from the demo website Northwind Studio.

Coverage

A page it couldn’t check never counts as passed.

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.

Couldn’t check is 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.

Questions only a person can answer go to Needs review and don’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.

“The decision to mark timeouts and incomplete coverage as inconclusive rather than silently passing is excellent audit hygiene. Pairing rendered-DOM checks with offline evidence and history makes the client report more defensible.”

A developer on Reddit, in Damdit’s launch thread

History

Prove what changed.

Run another audit after the work. 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. Damdit audits in the background and tells you when an issue is new or comes back.

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.

Private by design

Your client’s website is not our data.

Cloud audit tools crawl your client’s site from their servers and keep the results there. Damdit runs on your Mac. Projects, addresses, evidence and reports stay on your computer.

Audits stay on your Mac.

Damdit’s servers know your email address, your computers and your subscription. Nothing about the websites you audit.

No tracking in the app.

No analytics SDK, no advertising pixels, no usage profile. The app doesn’t phone home with what you click.

Diagnostics only if you say yes.

Damdit asks once and sends nothing until you agree. This is everything one audit sends:

What stays where

One audit’s diagnosticsPOST /v1/audit-events

{
  "schema_version": 3,
  "app_version": "1.2.1",
  "os_family": "macos",
  "os_major": 26,
  "audit_hour_utc": "2026-11-12T09:00:00Z",
  "overall_score": 87,
  "used_module_count": 13,
  "issue_count": 24,
  "issues_by_severity": {
    "critical": 0, "high": 3, "medium": 12, "low": 9
  },
  "issues_by_category": {
    "accessibility": 9, "seo_indexability": 7,
    "links_security": 8
  },
  "delivery_id": "8d0c…"
}

No website address, no page, no account, no device ID. The delivery ID only stops a resend from being counted twice and is forgotten after 7 days. The server keeps daily totals.

How it compares

Built for the person who hands the site over.

Desktop crawlers are made for SEO specialists, cloud suites for marketing teams. Damdit is for the people who build the site and have to stand behind it.

Damdit or Screaming Frog?

Feature	Damdit	Desktop SEO crawlers	Cloud SEO suites
Runs on your computer	Yes	Yes	No
Client sites stay off third-party servers	Yes	Yes	No
Pages rendered in a real browser	Always, up to 500	Optional setting	Varies
Coverage: what couldn’t be checked	On every audit	Varies	Varies
Reports for client, developer and AI	Built in	Exports	Varies
Webflow CMS checks	Built in	No	No
Price	€9.99 a month, billed yearly	Licence per user	Monthly, often per project

General categories as of November 2026; individual tools differ.

Who it’s for

For people who build websites for others.

Freelancers and studios

Check before handover, show the client what changed after the work, and send a report you don’t need to rewrite.

Developers and their AI

Audit localhost while you build. Claude Code, Cursor and Codex read the audit through MCP or the damdit command, and a new audit confirms the fix.

Webflow builders

The CMS behind the site, too: references, drafts, required fields and class names left over before handover.

Damdit for Webflow

Who builds it

“I’ve built websites for clients since 2013. Before a handover I want to know what’s broken, with proof, and what I haven’t checked. Damdit is that audit.”

Tony BurešMaker of Damdit, web designer and developer

Building websites since 2013
Made in Brno, Czech Republic
Support answered by Tony himself

More about Tony

rules in every audit: 247
pages opened in a real browser: 500
addresses checked for links: 5,000
audits stored on our servers: 0

Pricing

One plan. The full app.

Free for 14 days with every feature, no card needed. One subscription covers 2 Macs.

Start free trial See pricing

Yearly: €9.99 / month; €119.88 billed yearly; / year; for the first year, then a year
Monthly: €12.99 / month; Cancel any time

Excluding VAT. VAT for your country is added at checkout.

FAQ

Questions people ask first.

More about rendering, coverage and the damdit command.

How Damdit audits

Does it run JavaScript?

Yes. Up to 500 pages load in Chromium, and the title, description, robots and canonical are read from the rendered page, not the raw HTML.

How much of a website does it check?

Up to 500 pages in a real browser for the deep checks, then the rest of the site, up to 5,000 addresses, for links, redirects, titles and descriptions. Anything past the limits is listed in Coverage as not checked.

Will Damdit change my website?

No. Damdit only reads the website. 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 person, and they go to Needs review.

What does Damdit know about me?

Your email address, your computers and your subscription, for the licence. Nothing about the websites you audit. Anonymous diagnostics are off until you turn them on.

Can it audit staging behind a password?

Not yet. A site behind a password is reported as password-protected and its pages aren’t checked. Your local dev server works: add it as the project’s local address.

Can I use the results with my own AI?

Yes. Claude Code, Codex, Cursor or Claude Desktop can run audits and read the findings through the damdit command or MCP, on your computer. You can turn this off in Settings. Your AI tool’s own terms apply to what you share with it.

Windows or Linux?

Mac first. Windows and Linux later.

Know what needs fixing. Prove what changed.

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

Download for Mac See pricing