/

Updated 18 November 2026

How to Audit Your Website for AI Usage (EU AI Act Checklist)

AI Disclosure: This content includes AI-generated text.

Short answer: a website AI audit is a list of every place AI touches your site, with a decision next to each one: does the EU AI Act require a disclosure, and if so, is it in place? For a small business site it takes about an hour. You end up with a record you can show an authority, a client or your own team, and usually only two or three items that actually need fixing.

This guide gives you the steps, what to look for in each area, and a template you can copy.

Why bother with an audit?

Since 2 August 2026, Article 50 of the EU AI Act requires websites to disclose chatbots, deepfakes and unreviewed AI-written text on public-interest topics. You can’t meet those rules if you don’t know where AI is used, and most site owners underestimate it. AI hides in plugins, widgets, theme features, translation tools and content written months ago by someone who has since left. An audit also gives you something the law values: a documented, reasoned decision for each item, including the ones you concluded need no label.

Step 1: list the AI on your site

Go through these sources one by one. Write down everything, even if you think it’s harmless.

Visitor-facing features

  • Chatbots, live chat with AI replies, voice assistants
  • AI search, “ask our docs” boxes, product finders
  • Product recommendations, “you may also like”, personalised content blocks
  • Dynamic or personalised pricing
  • AI-powered forms: quote calculators, eligibility checkers, CV screening
  • Automatic translation of pages

Content

  • Blog posts, guides and news written or substantially rewritten with AI
  • Product and category descriptions
  • AI-generated or AI-edited images, including featured images and backgrounds
  • AI voiceovers, avatars, video presenters
  • Social posts and newsletters generated from your site content

Behind the scenes

  • WordPress plugins with AI features (SEO assistants, writing tools, image generators, auto-posting)
  • Spam filtering, fraud detection and moderation
  • Analytics with AI insights or session analysis
  • Third-party scripts loaded by your theme or tag manager

Practical shortcuts: check your plugin list for anything mentioning AI, GPT, OpenAI, assistant or generate; ask everyone who publishes on the site which tools they use; and open your tag manager to see every third-party script that loads.

Step 2: classify each item

For each entry, answer three questions.

  1. What’s your role? You’re usually a deployer (you use the tool). If you built your own AI system and run it under your name, you may be its provider. Read are you responsible for third-party AI tools if this is unclear.
  2. Does an Article 50 rule apply? Use this quick test:
    • People interact with it (chat, voice)? Disclose that it’s an AI.
    • Realistic image, audio or video that could pass as real? Disclose it as a deepfake.
    • Text on a public-interest topic (law, health, finance, politics, consumer safety) that no qualified person reviewed? Disclose it, or review it properly and keep a record.
    • None of the above? No AI Act label required. Other laws may still apply.
  3. Do other rules apply? Personal data means GDPR (privacy notice, legal basis, processor contract). Personalised prices and ranked recommendations bring consumer-law transparency duties. Automated decisions about people bring GDPR Article 22.

Our overview of the AI transparency rules every website must follow explains each rule in more detail.

Step 3: check what’s already in place

For every item that needs a disclosure, look at the live site as a visitor would, on desktop and mobile:

  • Is the notice visible before or at the moment people meet the AI content?
  • Is it clear and specific, not a vague footer line?
  • Can a screen reader read it?
  • Does it still appear on archive pages, in feeds and in the mobile layout?

Where to place AI disclosures has good and bad examples by content type.

Step 4: fix and document

Fix the gaps, then record the decision for every item, including the ones that need nothing. This template is enough for most sites:

Item Tool / vendor Role Rule Decision Evidence Checked
Support chatbot Tidio Deployer Art. 50(1) Greeting says “AI assistant” Screenshot 18 Nov 2026
Blog: tax change explainer ChatGPT draft Deployer Art. 50(4) text Reviewed by our accountant, no label Review note with name and date 18 Nov 2026
Hero image, team page Midjourney Deployer Art. 50(4) deepfake Replaced with real photo Old file archived 18 Nov 2026
Product descriptions AI writing plugin Deployer None Not public interest, no label Reasoning noted 18 Nov 2026

Step 5: keep it current

  • Re-run the audit every three to six months, and whenever you add a plugin, widget or new content workflow.
  • Add “does this use AI?” to your publishing checklist so new content is classified as it’s published.
  • Make sure the people who publish know the rules. Since February 2025, Article 4 has required organisations to support the AI literacy of staff using AI.

Common findings

When we look at small business sites, the same issues come up again and again:

  • A chatbot with a human name and no AI mention.
  • Photoreal AI “people” on team, testimonial or about pages.
  • Old AI-written articles on legal or health topics that nobody checked.
  • Auto-posting plugins publishing near-duplicate AI content, which is also an SEO problem.
  • A privacy policy that doesn’t mention the chatbot vendor.

Doing it in WordPress

The free EU AI Act Ready plugin turns most of this into settings. Each post gets a disclosure level (no AI, AI-assisted, AI-generated, or AI-generated and human-reviewed), visitors see a notice only where one is needed, AI images get labels, common chat widgets get an AI notice, and you can export a report of every decision as your audit record. It runs on your server with no account. If you work for clients, our guide on what agencies must do under the EU AI Act shows how to turn the audit into a handover document.

Frequently asked questions

Is an AI audit legally required?

Not as such for most websites. But you need to know where AI is used to meet the Article 50 duties, and a documented audit is the simplest way to show you took them seriously.

How long should I keep the audit record?

The AI Act doesn’t set a period for deployers of ordinary websites. Keep it for as long as the content and features are live, plus a reasonable period afterwards, and keep older versions when you update it.

Do I need to list AI tools I only use internally?

For Article 50, only AI that visitors interact with or whose output they see matters. For Article 4 AI literacy and for GDPR, internal tools count too, so include them in a separate section.

What if I can’t tell whether old content was AI-written?

Treat public-interest articles of unknown origin as unreviewed: either review them now and record it, or add a label. Our guide on disclosing AI-generated content explains the review standard.