/

Updated 18 November 2026

Where to Place AI Disclosures on Your Website (With Examples)

AI Disclosure: This content includes AI-generated text.

Short answer: put an AI disclosure where the visitor meets the AI content, before or at the moment they see it. Under Article 50(5) of the EU AI Act, a required disclosure must be clear and distinguishable, given at the latest at first interaction or exposure, and accessible. A notice in your footer, terms or privacy policy fails all three for most content.

This guide goes through each type of content on a typical WordPress site and shows where the label belongs, with patterns that work on real themes.

First: do you need a disclosure at all?

Placement only matters for content that legally needs a label. For a typical website that means three things since 2 August 2026:

  • chatbots and other AI that talks to visitors (Article 50(1)),
  • deepfake images, audio and video (Article 50(4)),
  • AI-generated text published to inform the public on matters of public interest, unless a person reviewed it and someone holds editorial responsibility (Article 50(4)).

Product descriptions, marketing copy and stylised illustrations usually don’t need one. Our Article 50 test for websites walks through the decision piece by piece. You can still label voluntarily, and the placement advice below applies to voluntary labels too.

The three rules behind every placement

  1. Clear and distinguishable. The label must stand out from the surrounding content. Same-size grey text that blends into a byline is weak. A short, visually separate line is strong.
  2. At first exposure. The visitor should see the label before or as they consume the content, not after scrolling through it or on a separate page.
  3. Accessible. A screen reader must be able to read it. Labels that exist only as pixels inside an image, or only on mouse hover, fail this.

Where to place the disclosure, by content type

Content Best placement Avoid
Chatbot In the first message and the widget header Only in the privacy policy
Article or blog post Directly under the title, before the first paragraph Only at the end of the post
AI image (deepfake) Visible badge on the image plus text in the caption or alt text Only in image metadata or a hover tooltip
Video On screen at the start, ideally persistent while it plays, plus text near the player A line in the video description only
Audio or podcast Spoken notice at the start, plus text next to the player Show notes only
Archive and listing pages Small label in the post card or excerpt Nothing until the click
RSS feed and newsletter A line at the top of the item Assuming the site label travels with the content

Chatbots

The first thing the bot says should make clear it’s an AI: “Hi, I’m the Acme AI assistant.” Put “AI assistant” in the widget header as well, so people who don’t read the greeting still see it. Full wording examples are in our guide to chatbot compliance under the EU AI Act.

Articles and blog posts

Place the notice between the title and the first paragraph. That is the moment of first exposure, and readers who only read the opening still see it. Keep it short: “This article was written with AI and has not been reviewed by an editor.” If you rely on the human review exemption instead, you don’t need a label for the text, but it helps trust to say who reviewed it.

Images

For images that need a label, use a small visible badge in a corner of the image (“AI-generated”) and repeat it in text, in the caption or alt text, so screen readers get it too. Don’t rely on the invisible C2PA or IPTC metadata your image tool may embed. The Commission is clear that deployers can’t rely on the provider’s machine-readable marking to meet their own disclosure duty, because visitors can’t see it.

Video and audio

Show the disclosure on screen when the video starts and keep a persistent marker if the content is a realistic deepfake. For audio, say it at the start. Repeat it in text next to the player for people who scroll past or use assistive tech.

Listings, feeds and social previews

Many visitors meet your content on your blog listing, in an RSS reader or in a newsletter before they open the post. If a post needs a label, add a short marker to its card or excerpt, and to the top of feed and email items. A label that only appears on the single post page arrives after first exposure for these readers.

Using the official EU icons

The Commission has published a common set of icons for labelling AI-generated and manipulated content, and the Code of Practice on transparency of AI-generated content recommends them. They are optional. Pair the icon with a few words of text, because an icon alone isn’t readable by screen readers unless it has a text alternative, and many visitors won’t recognise it yet.

Placement mistakes that look compliant but aren’t

  • Footer-only notices such as “Some content on this site may be AI-generated”. It’s not specific, not at first exposure, and almost nobody reads it.
  • Disclosure on a separate “AI policy” page. Useful as background, but it doesn’t replace a label on the content itself.
  • Hover-only tooltips. They don’t work on mobile or with keyboard navigation.
  • Labels that can be closed and never return on content where the label is legally required. A dismissible banner is fine for a voluntary label. For a required one, keep at least a small persistent marker.
  • Labels inside the image file only. Not accessible, and lost when the image is cropped or shared.

Will a label hurt engagement?

Usually far less than people fear, and a clear label is better than a reader discovering it later. We cover the evidence and design patterns in how AI disclosures affect user experience. The short version: keep it short, specific and calm, not a red warning box.

Placing disclosures in WordPress

You can hand-code notices into your theme, but that gets messy across post types, page builders and feeds. The free EU AI Act Ready plugin lets you set a disclosure level per post and then places the notice for you: a banner before or after the content, labels in excerpts and RSS, badges on AI images including Elementor and Bricks background images, and notices for common chat widgets. It runs on your own server and needs no account. If you’re starting from zero, run a quick AI audit of your website first so you know which pages need a label at all.

Frequently asked questions

Is a disclosure at the end of an article enough?

For a required label, no. Article 50(5) asks for the information at the latest at first exposure. A reader meets the text at the top, so that’s where the label belongs.

Can the label be a small icon?

An icon is fine if it’s clearly visible and has a text alternative. Icon plus a few words is the safest combination.

Do I need to label every image on a page if one is AI-generated?

No. Label the specific image that needs it. A page-wide “this page contains AI images” notice is vaguer and less useful than a badge on the actual image.

Does the disclosure need to be in the visitor’s language?

The AI Act doesn’t spell this out, but a label people can’t understand is hard to call clear. Use the language of the page it appears on.