Practical guide · last reviewed August 2026
The short version
01
Article 50 asks you to inform the person. Informing them in a language they do not read is not informing them.
02
Set your WordPress site language. The badge, the disclosure box and the chatbot notice follow it.
03
22 of the 24 official EU languages are included, free, with no language packs to buy.
“Clear and distinguishable” is about the reader, not the file.
Article 50 of Regulation (EU) 2024/1689 asks deployers to disclose AI-generated or AI-manipulated content in a way that is clear and distinguishable at the latest at the point of first interaction. The Act does not contain a sentence saying “translate your badge”. It does not need to. A disclosure exists to inform a person, and a label the person cannot read has not informed anyone.
This is worth taking seriously if you sell across borders. A German customer on a German storefront who sees an English word floating over a product photo has been shown a mark, not given information. The same logic already applies to your returns policy and your cookie notice; there is no reason AI disclosure would be the exception.
Where it matters most
Cross-border WooCommerce, multilingual sites, and any EU business whose customers are not English speakers.
What we are not claiming
That translation alone makes you compliant, or that the Act names a list of languages. It does not. This is about the disclosure doing its job.
The parts a visitor sees, not just the parts you see.
Plenty of plugins translate their settings screens and stop there. That is backwards: the settings are read by one person who chose to install the thing, and the badge is read by everyone who visits.
The badge on the image
A German page renders KI-generiert, a Polish one Wygenerowane przez AI, a Swedish one AI-genererad.
The disclosure box
The explanation shown when someone clicks the badge, including the sentence naming which type of AI involvement applies.
The chatbot notice
The Article 50(1) line telling visitors they are talking to an AI, in the language of the page they are on.
The admin dashboard
Every screen, the media library column, and the Article 4 readiness checklist, for whoever maintains the site.
Taken from the law, not translated from ours.
Regulation (EU) 2024/1689 exists in all 24 official languages, and each version is equally authentic. So the legally load-bearing phrases are not translated out of English: they are taken from the Act’s own text in that language. “Artificially generated” becomes künstlich erzeugt in German and généré artificiellement in French because that is what the Regulation says there.
This also means being careful in the other direction. The French text reserves manipulé for the deepfake case, so using it for an ordinary AI-edited photo would claim more about your image than the law does. An earlier draft of our French did exactly that, and a review pass caught it.
Every language was then read again, string by string, hunting for translations that are grammatically perfect and mean the wrong thing. That review changed 128 strings. Some were embarrassing: the badge shape called “pill” had become the word for a medicine tablet in two languages, and the French word for a chat widget is also the word for a cat.
Every official EU language WordPress supports.
Bulgarian, Croatian, Czech, Danish, Dutch, English, Estonian, Finnish, French, German, Greek, Hungarian, Italian, Latvian, Lithuanian, Polish, Portuguese, Romanian, Slovak, Slovenian, Spanish and Swedish.
Irish and Maltese are the two official EU languages WordPress itself does not ship a translation set for, so they are not included. When WordPress adds them, we will.
There is nothing to configure.
Set Settings › General › Site Language to the language your visitors read.
WordPress installs that language pack. The plugin’s translations are already bundled, so nothing else downloads.
Flag an image as usual. The badge renders in that language on the front end.
On a multilingual site the disclosure follows whatever locale WordPress has resolved for the request, so a page served in Dutch shows the Dutch wording. Individual users can also set their own admin language in their profile without changing what visitors see.
Related guides
Each one stands on its own, in plain English, with the exact steps for a WordPress site.
The lawThe EU AI Act and WordPress (Article 50)
Who Article 50 covers, the 2 August 2026 deadline, the penalties, and exactly what a WordPress site owner must do, in plain English.
Read guide
The how-toHow to label AI images in WordPress
A step-by-step walkthrough: install the plugin, flag an image from the Media Library, and get the badge, embedded metadata and JSON-LD automatically.
Read guide
The metadataWhat IPTC DigitalSourceType actually is
The machine-readable tag behind “AI-generated”: what the IPTC DigitalSourceType vocabulary means, the values AIM Transparency writes for AI and human provenance alike, and why it future-proofs your images.
The shopDisclose AI product images in WooCommerce.
Selling with AI product photos? Put the “AI Generated” badge across your shop grid, your categories and the single-product gallery, free, plus embedded provenance, on any theme. Compliance and buyer trust, in one move.
Read guide
Written textHow to disclose AI-written text in WordPress
The half of Article 50(4) nobody quotes. Whether the text duty reaches your site at all, how to record it per post, and why human review on its own is not the exemption.
Read guide
ChatbotsHow to disclose an AI chatbot on WordPress
Article 50(1) is the other half of the law: if visitors interact with an AI, you have to tell them. Where the notice belongs, and how to find widgets already running.
Read guide
For developersShow an AI disclosure automatically with WordPress hooks
One filter, one condition, one call to do_shortcode. Copy-paste recipes for categories, custom fields, WooCommerce and block themes.
Read guide
The releaseWhat WordPress 7.1 changes for AI image provenance
7.1 can rebuild your images in the browser before they ever reach your server. What that does to provenance written inside the file, what we measured against the release candidate, and the one line that turns it off.
Read guide