Pick your industry, then tick the certificates you hold
Choose your sector and we’ll open the recognised Icelandic certifications for it. Tick the ones you actually hold — any claim they prove turns green instead of red when you scan. (No certificate? That’s fine — you can still make honest, specific claims.)
Paste your green copy
What’s risky — and which rule flags it
Each finding carries a § rule chip — the specific framework that governs that word. Everything is also caught by Icelandic Act 57/2005 and the EU ECGT.
Next, check whether your live page actually shows these credentials to Google and AI — then we’ll rewrite everything.
Is your page findable by AI & Google?
Enter your page’s web address and we’ll fetch it, or paste the HTML source for full privacy. Either way we check the signals AI search & Google use to extract, verify and cite your credentials.
“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.”
We fetch the public page through a fetch proxy to read its code — only the address is sent, and it also lets us check robots.txt & llms.txt. Want full privacy? Paste the source instead — that never leaves your browser.
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.
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.
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.
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.