EU AI Act for WordPress Sites: Does Your Chatbot Need a Disclosure?

The short version

From 2 August 2026, if your site uses an AI system that interacts directly with visitors — a chatbot, an AI-powered live chat, a virtual assistant — EU AI Act Article 50 requires you to clearly inform visitors they are talking to AI, before or at the first interaction. This applies regardless of where your site or business is hosted or registered, as long as EU visitors can reach it.

You have roughly six weeks left.

Which WordPress AI features this actually covers

WordPress sites typically have AI touching the visitor experience in one of a few common ways:

• AI live chat plugins (Tidio, Tawk.to with AI add-ons, Chaport, Smartsupp, WPBot, and similar) — if the plugin's AI feature responds directly to visitor messages, this is almost always in scope. The plugin developer is not responsible for your disclosure; you are, as the site owner deploying it.
• Jetpack AI Assistant or similar AI writing tools used to help draft pages, posts, or product descriptions — this is content generation, not direct visitor interaction, and falls under a different part of Article 50 (machine-readable marking, with a longer transition window) rather than the chatbot disclosure rule.
• WooCommerce AI product description or recommendation tools — typically out of scope for the chatbot rule unless they involve a conversational interface visitors interact with directly.
• AI-powered support ticket systems with auto-reply features — in scope if AI-generated replies are sent to visitors without clear labeling as AI.

A common misconception worth correcting directly: installing a third-party AI chat plugin does not shift the compliance obligation to that plugin's developer. The obligation sits with whoever deploys the system toward end users — that's the site owner, not the plugin author.

What the disclosure actually needs to say

The requirement isn't complicated, but it is specific. The notice must be:

• Clear — not buried in a footer or privacy policy
• Timely — shown at or before the first interaction, not after several messages
• Distinguishable — visitors should actually notice it, not have to look for it

A line like "This chat is powered by AI" sitting quietly under a widget for the entire conversation, shown once and then gone, is unlikely to meet "timely" on its own. The disclosure should appear as the system's first message, before the visitor can type anything.

Where to actually add this in WordPress

For most AI chat plugins, this means adding the disclosure as the bot's configured opening or greeting message in the plugin's settings — nearly every chat plugin (Tidio, Tawk.to, Chaport, Smartsupp) has a "welcome message" or "bot greeting" field built for exactly this. For a custom-coded chat widget added directly to your theme, the disclosure text needs to render as the first message in the chat window before any visitor interaction.

For the hosted compliance badge specifically, the standard installation path is: Appearance → Theme Editor → footer.php → paste the snippet directly before the closing </body> tag, on every page where AI is active. The badge then appears within about 60 seconds.

What happens if a site doesn't have this

A visitor contacts their national competent authority. The chatbot ran without a disclosure. The authority opens a review and requests documented evidence that the required AI notice was shown to users — within a defined response window.

Without a logged record, there's nothing to produce. A timestamped record showing the disclosure was actually displayed — not just that the text exists somewhere — is what's asked for. Documented good-faith compliance is an important factor in fine calibration under Article 99.

Fines for Article 50 violations are calibrated under Article 99, up to 3% of global annual turnover or €15 million, whichever is higher — with lower effective exposure for small businesses based on turnover, and assessed case by case. Use the fine calculator on the Disclo homepage to see what 3% of your actual turnover looks like — for most small WordPress sites, it's a far smaller number than the headline figure suggests, but it's not zero.

The three things to actually do

1. Identify every AI touchpoint on your site — chat plugins, AI writing assistants, any AI-powered support tools.
2. Add a compliant first-interaction disclosure to each visitor-facing one — specific wording, shown before the visitor can type.
3. Keep a record that the disclosure was actually live and showing, not just that you added it once. A screenshot from launch day doesn't prove anything about October.

Get this handled in 15 minutes

The Disclo Compliance Kit includes ready-made disclosure text for chat widgets, a persistent chat label, and an AI transparency page template — in your language, based on official EU guidance, ready to paste into your WordPress theme or plugin settings today.

This is general guidance, not legal advice. Based on the official EU AI Act and the Article 50 draft guidelines published 8 May 2026. Consult a qualified EU technology lawyer for advice specific to your situation.