Skip to content
Case studies

See what a real audit finds.

Real businesses, real fixes. Every number on this page comes from an audit that actually ran.

Featured · Digital Presence Audit · nocodelabs.io · Oct 28 to 29, 2026

We ran the full audit on ourselves. It found 16 problems.

The same audit a client buys, run on our own business and published as a redacted sample. The site itself scored well. Outside it, buyers who don’t already know our name can’t find us yet.

The numbers

Findings
16

Each with evidence and a fix.

High severity
9

Costing us customers now.

Medium and low
7

Worth fixing, less urgent.

Strengths
2

The site itself is fast and clean.

Areas checked
10

From identity to backlinks and profiles.

Data used
Public

No logins, nothing private.

What it found

  • HighOur own site gave search engines and AI the wrong location for the business.Open
  • HighOur name collides with a generic phrase and with other companies.Open
  • HighA key profile link on every page was broken.Open
  • HighToo little outside proof: reviews, listings and links.Open
  • HighAI engines don't recommend us when an owner asks who to hire.Open
  • MediumOur product's name isn't what buyers search for.Open

Statuses update here as each fix ships. The sample report shows every finding, with the specifics redacted.

Report length depends on the business: more sites, profiles and locations mean more findings. This sample is one website and one business.

Where it started · Audit-01 · nocodelabs.io · Sept 16, 2026

We ran the audit on ourselves first.

Before auditing anyone else, we ran the audit on our own site. This run used the engine as it stood on Sept 16; the audit clients get today checks more, including directory listings and reviews.

Baseline scores

Controlled
89.8/100

Signals we own: site, content, structure.

Earned signals (AI authority assessment)
40.0/100

Audit-01 ran on our earlier v1 pipeline, where an AI model assessed authority. Today's DPS audit scores Earned from measured reviews, listings and citations with a fixed, published rule: no AI writes or adjusts any number.

Earned is low for a young company: authority takes time to build. That’s why the two scores stay separate.

What it found, and what the October audit measured

  • HighHomepage took 3.1 s to show its main content (LCP), vs 0.3 s on /pricing.Oct: still 3.1 s on mobile (lab)
  • MediumH1 rendering bugs on /audit: a broken apostrophe and a run-on headline.Oct: fixed
  • Medium/beta had 246 words: too thin to rank.Oct: kept out of search
  • Medium/contact had 377 words and no trust details.Oct: 555 words
  • Medium/diagnostic had 461 words, with no inputs, outputs or example.Oct: 741 words
  • LowNo PageSpeed data for / or /audit.Oct: homepage 91 mobile, 99 desktop

Next scored run

Audit-02 · Scheduled Q4 2026

The next scored run repeats audit-01’s Controlled and Earned scores. When it runs, the before-and-after numbers post here, whether they went up or not.

Read the full audit-01 case study →

More coming

More case studies as client audits complete.

We’re auditing a small group of local service businesses now. Their case studies publish here once the work is done and they’ve said yes to sharing it. We don’t publish examples we made up.

Your turn

See what an audit finds on your site.

The same audit we ran on ourselves: ranked findings with the evidence, and a fix list you can act on.