If a bot talks to your customers, they have the right to know.

From 2 August 2026 the EU AI Act requires that people are told when they interact with an AI system and when they see AI-generated content. The free scan reads your homepage the way a crawler sees it and reports which transparency signals are visible and which are not.

The scan reports observed facts: found or not found. It never issues a compliance verdict; findings are inputs for your own legal review.

Article 50 signal scanready

3 free scans per day.

What the law actually says

Providers shall ensure that AI systems intended to interact directly with natural persons are designed and developed in such a way that the natural persons concerned are informed that they are interacting with an AI system…
Regulation (EU) 2024/1689, Article 50(1), EUR-Lex

What the scan reads in your page source

Three signal families, matched in your page source. Every finding in the paid audit comes with the exact fragment it was matched on.

  1. 01Chat & support widgets25+ vendor fingerprints (Intercom, Crisp, Tidio, Smartsupp, Botpress and others) matched in the page source.
  2. 02AI disclosure wordingPhrases that tell a visitor they are talking to a bot. Matched in 7 languages.
  3. 03AI-image credentialsC2PA / IPTC provenance markers read from image bytes in the deep audit scan. CDNs often strip them, so “not found” never means “not AI”.

Known limits, stated up front

The free scan is static: it does not execute scripts or click consent banners, so widgets loaded after consent stay invisible to it; the audit's rendered scan covers those. We respect robots.txt and never bypass access controls. And no scan can read facts that live outside the page: who operates the bot, what your images depict, whether a human reviewed a text.

What we found on 248 SME homepages

had a chat or support widget on the homepage
1 in 10
widget sites had visible AI disclosure wording
1 of 24
of widgets were visible to a static scan; the rest loaded only after a consent click
83 %

Our own corpus run, July 2026. Observed counts from scanned homepages. No projections.

Start free. The audit ships in August.

Launch pricing: what you see is what early customers pay.

  • Free scan€0 Homepage signal scan with an on-screen readout. Available now, no account needed, just your email. · Run it above
  • Monitoring€29–49 /mo · at launchMonthly re-scan with change alerts: new widgets, disappeared disclosures. · At launch
  • Agency€149–249 /mo · at launchMulti-site scanning and client-ready readouts for web agencies. · At launch

Full audit (pre-order)

€99 one-time, launch price

Deep rendered scan (after-consent widgets), AI-image credentials, page-by-page findings with evidence and a fix list. Ships in August 2026.

Pre-order is an email reservation; you pay nothing today.

Straight answers

When do these rules start to apply?

Article 50 transparency obligations apply from 2 August 2026. Breaching them can cost up to €15 million or 3 % of worldwide annual turnover, whichever is higher (Article 99(4)); for SMEs the lower of the two amounts applies (Article 99(6)).

Is this legal advice?

No. The scan reports what is technically visible on your pages: found or not found. Whether your specific setup meets Article 50 is a legal judgement for you and your advisers.

Does a clean readout mean my site passes?

No scan can tell you that. Some obligations depend on facts no crawler can see: who operates the bot, what your images depict, whether a human reviewed a published text. We show the signals; you and your advisers decide.

What does the free scan see, and what does it miss?

It reads your homepage's static source: widget fingerprints and disclosure wording. It cannot execute scripts or click consent banners, so after-consent widgets stay invisible to it; the audit's deep rendered scan covers those, plus AI-image credentials.

Who is behind Klaroscan?

Klaroscan is built and operated by Aivikta, Lithuania (EU), the same engine that powers our AI-visibility audits. EU-based, GDPR-first: scans store a hashed IP, never the raw address.