Before launch and handover

Audit it before it goes live. And before you hand it over.

Give a project its production, staging and local addresses. Damdit audits each one on its own, opens a staging site that’s locked before launch, and keeps the checks only a person can do on the list until they’re done.

  • Localhost, staging and production
  • Staging behind a password or a hosting lock
  • Free for 14 days, no card needed
  • Apple silicon, macOS 14 or later

Test enquiry reaches HubSpot

Needs reviewHandover check · Staging

How to fix

Send the contact form once and confirm the enquiry arrives. Mark it done, and the client report says so.

Project
Northwind Studio
Address
staging.northwind.example
Access
Vercel protection bypass
Listed in
Needs review · client and developer reports
Example from the demo website Northwind Studio.

The last week before launch is when things slip.

Content goes in, redirects change, someone adds a script. The audit you ran two weeks ago no longer describes the site you’re about to hand over.

From localhost to handover

  1. Audit localhost while you build.Checks only the live host can answer, like security headers, read “not applicable”, not “passed”. damdit check audits your dev server without a project.

  2. Audit staging, even when it’s locked.Add HTTP Basic credentials, a Vercel protection bypass or a Cloudflare Access service token. Damdit sends it only to that website.

  3. Keep the checks a person must do.“Test enquiry reaches HubSpot” stays in Needs review and in the reports until someone marks it done.

  4. Audit production after launch.Each address keeps its own history, so you compare production with production and staging with staging.

What it catches before launch

  • Broken links

    Across the whole site, and the links to other websites.

  • Missing titles and descriptions

    And the share image that a social network won’t show.

  • Accessibility

    Contrast, labels, names and headings, with the element to fix.

  • Canonicals that point away

    A canonical to another domain, a redirect or a page that asks not to be indexed.

  • Oversized images

    Images larger than they’re shown, and images without dimensions.

  • Webflow CMS

    Published items pointing to drafts, wrong references and empty required fields.

Where it stops

Where it stops.

  • Damdit opens locked sites only with access that unlocks viewing. It never signs in to accounts, members areas or a CMS admin.
  • A Webflow site password isn’t supported yet.
  • PageSpeed Insights runs on Google’s servers and can’t open a locked site, so speed isn’t measured there.
Is it safe to give Damdit my staging password?

It’s stored in your Mac’s secure storage and sent only to that website’s address, never to other sites or to Google. Use access that only unlocks viewing.

Does a staging audit change my production score?

No. Production, staging and local each keep their own audits, history and issues.

Can I give the client a report?

Yes. The client report explains the score, the top priorities, what changed and what an automated audit can’t confirm, in plain language.

Does it work with my agency’s workflow?

Damdit runs on your Mac. Your coding agent can read the audit through MCP or the damdit command, and audits can run on a schedule.

Hand over a site you’ve checked.

Run your pre-launch audit on Damdit. Free for 14 days, no card needed.