When a reference points outside the items Damdit looked at, it says so instead of guessing.
A published item that references an unpublished one, like a blog post pointing to an author that’s still a draft.
A reference to an item from the wrong collection.
A required field left empty, or a value of the wrong type.
A collection with nothing in it.
CMS templates with a fixed title or no meta description, and structured data fed by an empty field.
Tidy up before handover.
Leftover class names like div-block-47, long combo-class stacks and deep nesting land on the review list. Clean up what matters to you; the score doesn’t change. These come from the rendered page, so they work without a token too.
Is this the domain you think it is?
Damdit checks that the address you’re auditing is one of the site’s custom domains in Webflow.
Your token stays yours.
Damdit needs read access to Sites and CMS. The token goes from your Mac straight to the Webflow API, is kept in secure storage, and never reaches a Damdit server.
And the rest of the audit.
Accessibility, SEO, links, forms, security headers, reports for your client, history and your AI tools. All of it works with or without Webflow.
FAQ
Questions from Webflow builders.
Do I need Webflow to use Damdit?
No. Every audit starts with a URL. The Webflow module is optional.
Can Damdit change my Webflow site?
No. It only reads. It never edits, publishes or deletes anything.
Is Damdit made by Webflow?
No. Damdit is an independent app that uses the Webflow API.