Green Claims → Findability Studio — compliant AND findable, in one pass

Step 1 · Paste

Paste your green copy

Product description, web copy, label, or social caption

High risk — remove or rework Needs proof — make specific

Step 1 · Result — compliance

What’s risky under the ECGT

Next, check whether your live page actually shows these credentials to Google and AI — then we’ll rewrite everything.

Step 2 · Check your live page

Is your page findable by AI & Google?

Paste your product page’s HTML source (in your browser: right-click → View Page Source → select all → copy). This checks the signals AI search and Google use to extract, verify and cite your credentials. Runs entirely in your browser.

★ How to say this to a client — honestly

“Google says structured data isn’t a direct ranking factor, and no special schema is required for AI Overviews. What changed in 2026 is that schema became an AI trust & entity-verification signal: structured data makes your real credentials easier for AI and Google to extract, verify and cite — correlated with more citations, not a guarantee. We only mark up genuine, specific credentials, which is exactly what the ECGT requires. One fix, two wins.”

Your page’s HTML source (not a web address — the actual source code)

Beyond schema — other ways to be found

Answer the buyer’s exact question in text. A short “Is this cup compostable? Yes — certified EN 13432…” Q&A (with FAQ schema) is what answer engines lift.
Link out to the certifier / official registry. A link to your FSC or Vakinn listing (plus sameAs) lets a machine confirm you’re real — the entity-trust signal.
One canonical “Our materials & claims” page. One stable URL per claim beats the same words scattered across the site.
Put claims in text, never baked into product images. A claim inside a photo is invisible to crawlers.
Be specific. Vague claims aren’t cited and aren’t compliant — specificity serves both.
Claim your entity. Google Business Profile + consistent name/details across the web help AI recognise the brand.

Now fix the wording and generate the machine-readable version — including the schema this check said was missing.

Step 3 · Rewrite + machine-readable schema

Your corrected, machine-readable version

A · Your copy, rewritten to comply

Each risky phrase swapped for a specific, provable one. Bracketed […] parts are where your real fact or certificate number goes.

B · The same real credentials, made machine-readable (JSON-LD)

Paste this into your product page’s <head>. It’s the Certification markup Google & AI use to verify and cite a claim — barely used yet, so it’s a real edge.

Starter schema — fill the brackets from your actual certificates

C · Proof to hold on file before you publish

A rewrite is only safe once the evidence exists. These are the documents each kept claim needs.

Why this is one job, not two: the schema only works on genuine, specific credentials — the exact same thing the ECGT now demands. Fix the wording and you’ve also made it findable. One fix, two wins.

This is the taste. A full audit looks like this.

The studio shows the pattern on one block of text. A real engagement reviews every channel, matches each claim to your actual certificates, writes the drop-in copy, and delivers a branded dossier + the search-optimised proof page.

↓ Example — not a live scan

⚠️ This is a claims-hygiene helper, not legal advice. It flags common risk patterns under Directive (EU) 2024/825 (ECGT) and related packaging/consumer rules and points to the standards typically used to substantiate them; it does not certify legal compliance. For high-stakes claims, confirm with a qualified specialist or lawyer.