Beta. We read the public code of up to three pages and match it against 672 known AI tools. Chatbots are found on any platform; the other categories rely on WordPress plugin files. We cannot see AI running on a server, and some sites block us outright, so a quiet result means “nothing found in what we could read”, not “no AI here”. This is a different job to the plugin: it finds AI running on a site, and never inspects whether your images carry a disclosure.
What the check looks for.
We match your page’s public code against a registry of 672 AI tools. What we can see depends entirely on whether a tool leaves a trace on the page a visitor loads, so each category below says where it works. Two things are true of all of them: we cannot see AI running on a server, and a tool that only runs inside your admin leaves no trace on a public page.
01
Chatbots and assistants
Live chat widgets, support bots and AI assistants that answer your visitors on the page.
Where we can see it: Any platform. These load their own script, so this is the one category we find reliably.
02
Content AI
Writing, SEO and content-generation tools that produce or rewrite the text a visitor reads.
Where we can see it: WordPress only, and rarely. Most of these run only in wp-admin, and a tool that never touches the public page cannot be seen from outside.
03
Image generators
Plugins and services that create or edit images with AI, the ones a visible badge is built for.
Where we can see it: WordPress only. Recognised by their plugin files. A generator used elsewhere and uploaded by hand leaves nothing to find.
04
AI translation
Machine-translation tools that render your pages into other languages automatically.
Where we can see it: WordPress only. Recognised by their plugin files.
05
Audio generators
Voice and audio tools that synthesise speech or sound for your pages.
Where we can see it: WordPress only, and thinly covered: six tools in the registry today.
06
Video generators
Tools that generate or edit video with AI.
Where we can see it: WordPress only, and thinly covered: two tools in the registry today.
Two duties, two article numbers.
Your report groups every tool it finds by the part of EU AI Act Article 50 that may apply to it.
Article 50(1): tell visitors they are talking to AI
Chatbots and AI assistants must tell people they are not human.
Article 50(4): disclose AI-generated media
Where AI-generated or edited images, video or audio would pass as real people, places or events, the deployer discloses that it is artificial.
Everything else is reported without an article. Translation tools and other AI that makes no media carry no labelling duty of their own, so the report lists them and leaves the judgement to you.
Under Article 50, these may need a visible label. Read the full guide.
What this check does not do.
This tool reports the AI tools and services present on the scanned pages, grouped by the part of the law that may apply. It does not judge whether any specific image or message is AI, and it reads only public page code. Not legal advice.
Where it is weakest
Most of what this tool knows is WordPress-shaped. It recognises 672 AI systems, but only 30 of them leave a trace we can read on a site that is not WordPress: the widely used chat widgets, which load their own script. The rest, including every one of the 120 image generators, are recognised by the WordPress plugin they leave behind.
So on Squarespace, Wix, Webflow, Shopify or a static site, a generated image usually leaves nothing in the page for us to find. Finding none here is not evidence that there are none. If you publish AI images on one of those platforms, work from what you know you made, not from this result.