Short answer: if your agency builds or maintains client websites, the EU AI Act gives you two jobs. First, make sure each client site discloses its chatbots, deepfake images and public-interest AI text under Article 50. Second, make sure your own team has enough AI literacy under Article 4. This page is a repeatable checklist you can run on every client site, with a handover note you can copy.
Checked on 18 November 2026. For the wider picture of agency responsibilities, read what agencies must do under the EU AI Act. This page is the practical audit.
Whose duty is it: the agency’s or the client’s?
- The client is usually the deployer. The site runs under the client’s name and serves the client’s visitors, so labelling deepfakes and AI text on that site is the client’s legal duty under Article 50(4).
- You can become a provider. If you build a custom AI chatbot or AI feature and deliver it to clients under your agency’s name, the Commission’s guidelines may treat you as the provider, with the Article 50(1) and 50(2) duties that come with it.
- You are the deployer for your own use. AI tools your team uses to make client content are deployed by you, which is where Article 4 AI literacy applies.
- Contracts decide who does the work. The law decides who is responsible; your contract decides who sets up the labels. Write it down.
The client site checklist
Run this on each site at launch, at every maintenance cycle, and whenever an AI tool is added.
| # | Check | Rule | Pass when |
|---|---|---|---|
| 1 | List all AI tools on the site: plugins, chat widgets, scripts, AI search, translation | Art. 50 overall | Inventory saved with date |
| 2 | Chatbot shows an AI notice before the first message | Art. 50(1), 50(5) | Visible on desktop and mobile in a private window |
| 3 | Realistic AI images, video and audio carry a visible label | Art. 50(4) | Every deepfake candidate labelled where it appears |
| 4 | Public-interest AI text is disclosed, or human editorial review is documented | Art. 50(4) | Decision recorded per content type |
| 5 | Notices are readable, accessible and in the site’s language | Art. 50(5) | Screen reader and contrast check done |
| 6 | Image optimisation does not strip AI provenance on purpose | Art. 50(2) support | One resized image checked |
| 7 | Custom AI features you built have their own disclosure and marking | Art. 50(1), 50(2) | Provider role assessed in writing |
| 8 | Client knows who updates labels for new content | Contract | Named person in the handover note |
Helpful guides for each step: auditing a site for AI usage (1), chatbot disclosure wording (2), labelling AI images in WordPress (3), disclosing AI-generated content (4) and where to place disclosures (5).
Your own team: Article 4 AI literacy
Article 4 has applied since 2 February 2025. Providers and deployers must take measures to ensure, to their best extent, a sufficient level of AI literacy among staff who use AI systems on their behalf. In practice an agency should be able to show:
- a list of AI tools the team uses and what for,
- a short internal policy on what may and may not be done with them (client data, images of real people, fact-checking),
- a record of who has been briefed or trained, and when.
One page and a 30-minute team session is a reasonable start for a small agency.
Handover note you can copy
AI transparency on [site], checked [date] by [agency]. AI tools found: [list]. Chatbot notice: [in place / not applicable]. AI images labelled: [number] in [locations]. AI text: [disclosed / reviewed by named editor / not public-interest]. Responsible for labelling new content: [name]. Next check: [date]. This note documents technical measures and is not legal advice.
Doing this across many WordPress sites
The free EU AI Act Ready plugin. On each site it lists detected AI systems, scans the media library for likely AI images, adds image, content and chatbot notices, tracks Article 4 literacy, and exports a printable compliance report you can attach to the handover note. There is no licence key, so it costs nothing to install on every client site. Setup takes about 15 minutes with the setup guide. If you are choosing between tools, see the plugin comparison.
FAQ
Can the client fine us if a label is missing?
Regulators fine the party with the legal duty, usually the client as deployer. Whether the client can then claim against you depends on your contract. Agree scope in writing.
Do we need to check sites launched before August 2026?
Yes, for chatbots and for content published or changed since 2 August 2026. Older images do not need retroactive labels according to the Commission’s guidelines.
Is a high-risk assessment needed for a normal website?
Rarely. Marketing sites, shops and blogs do not usually fall under the high-risk rules. See understanding high-risk AI systems.
Sources
- AI Act, Article 50, AI Act Service Desk, European Commission
- AI Act, Article 4, AI Act Service Desk, European Commission
- Commission guidelines on Article 50 transparency obligations
This guide is general information, not legal advice. Written by the EU AI Act Ready team, 18 November 2026.