Skip to content

Green claims triage for agencies

Compliance triage across a roster, without a platform

If you audit green claims for other people, the bottleneck is rarely the judgement — it is finding every place a claim appears before you can judge it. That part is mechanical, and this does it in 7-20 seconds per site (3 real shops, 2026-08-30).

Workflow

Four steps that survive contact with a real client list

01

Triage the roster

Run the scanner across each client's highest-traffic pages. Ten pages per site is enough to tell a shop with a wording problem from one with a structural one — which is the only distinction that matters when you are deciding where to spend the retainer. The limit is 5 site scans an hour from one address, so a long roster is a job you spread across the day.

02

Separate the two kinds of finding

Vague adjectives are a copy fix an editor can do in an afternoon. Offset-based neutrality claims and self-made badges are not — they need the underlying practice to change, and someone senior has to agree to that.

03

Rewrite against the evidence you can get

Every finding ships with a rewrite pattern, but the pattern needs a fact: a licence number, a percentage, a verifier. Collecting those from the client is usually the long pole, so start it before the copy work.

04

Re-scan and keep the delta

The second scan is what you show the client. Nothing here is stored, so export or screenshot the first report before you start changing things.

Who it fits

Four practices, one shared bottleneck

Sustainability consultancies

You already do the substantiation work. This handles the mechanical sweep so the billable hours go to judgement rather than to searching product pages for the word "eco".

E-commerce and DTC agencies

Your copywriters are producing claims weekly. A pre-publish check catches the ones that would have to be pulled later, when pulling them is expensive and visible.

PR and communications

Campaign lines carry the highest-risk wording and the shortest review cycle. Checking a headline takes about 396 milliseconds.

Legal and compliance practices

The findings cite the provision, so the output slots into an existing advice format rather than needing translation first.

Be straight with clients

The conversation this tool is for

The uncomfortable finding is rarely the vague adjective. It is the carbon-neutral badge the client has spent three years and real money building a brand around, which Annex I to Directive 2005/29/EC point 4c disposes of in a sentence.

Having the provision on screen next to their own copy changes that conversation. It stops being your opinion about their marketing and starts being a fact about their exposure — and it moves the discussion to what they can substantiate instead of what they would like to say.

The 92 entries in the lexicon each carry a rewrite pattern for exactly that reason. “You cannot say this” ends a meeting badly; “here is what you can say, and here is what you need in order to say it” gives everyone a next step.

Common questions

Is there a multi-client dashboard?
Not today. This build has no accounts, which means no workspaces and no saved rosters. The pricing page sketches what that would look like; it is honest about the fact that it does not exist yet. Pricing
Can I white-label the report?
Not yet. What you can do is export the page — the report is plain HTML with no external dependencies, so printing to PDF from the browser produces a clean document.
Can I scan a prospect's site before pitching?
Yes, and it is one of the more useful things you can do with it. The scanner only reads public pages, at browsing speed. A findings summary is a considerably better opener than a generic capability deck.
How do I explain a false positive to a client?
Directly. Matching is deterministic and cannot read intent, so a glossary entry flags the same way a product claim does. A review model then marks the obvious commentary — its verdict is printed next to the finding, which stays in the report either way, because that call is worth checking. Every finding shows the sentence it came from, which usually settles the question in one look.
Is there an API?
The endpoints exist — POST /api/scan, /api/check-copy, /api/check-image — but there is no API documentation: the request shape is what the tools on this site send, visible in your browser's network tab. There are no keys, and the rate limits are per address (5 site scans an hour, 30 text checks, 10 images). Treat it as usable for a spike, not for production.

Run it on your largest client first

Ten pages, 7-20 seconds, no account.