The EU AI Act and your AI-built website
If an AI wrote your marketing site, which parts of the AI Act reach you? The risk tiers, the Article 50 transparency rules, the deadlines and the myths.
Settle the GDPR side of your site
Your AI-built site on servers in Belgium, with built-in forms and analytics and a DPA on every paid plan. 14 days free, no card.
Somewhere between the AI Act being adopted and its transparency rules taking effect, a genre of advice emerged claiming that every AI-generated paragraph on the internet would soon need a warning label. If you used ChatGPT, Lovable or Bolt to build your company's website, that genre is aimed squarely at your anxiety. Most of it is wrong, and the parts that are right are narrower than they sound.
This piece separates what the regulation asks of someone publishing an AI-built marketing site from what it asks of the AI industry, gives the official dates, and ends with a checklist you can work through in an afternoon. One caveat before anything else: this is general information written by a hosting provider, not legal advice. If your situation involves regulated sectors, high-stakes content or real doubt, a lawyer who has read your specifics beats any blog post, including this one.
What the Act regulates, and what it does not
The AI Act is a product regulation for AI systems. It sorts them by risk: a short list of prohibited practices, a heavily regulated high-risk category covering things like biometric identification and AI in hiring or credit decisions, a transparency tier for systems that interact with people or generate content, and a minimal-risk remainder with no new obligations at all.
Notice what is absent from that list: websites. A static site is not an AI system, however it was written. The HTML your code generator produced is output, and the Act attaches obligations to systems and to the people who provide or deploy them, not to artifacts those systems leave behind. So the first-order answer for most readers is that your website as such is not what the AI Act regulates, in the same way a document is not regulated by rules about word processors.
Where you do appear in the Act's vocabulary is as a deployer: someone using an AI system professionally. The heavy deployer duties sit in the high-risk category, and building a marketing site with a chatbot's help does not put you there. What can reach a website publisher is one article in the transparency tier, so that is where the real analysis lives.
The timeline, with the official dates
The Act entered into force on 1 August 2024 and applies in stages. Some deadlines moved when the "AI Omnibus" amendment, proposed on 19 November 2025 and politically agreed on 7 May 2026, entered into force on 27 July 2026. The dates below follow the Commission's AI Act Service Desk, which already includes those amendments.
| Date | What applies |
|---|---|
| 1 August 2024 | The AI Act enters into force |
| 2 February 2025 | Definitions, the AI literacy rule and the first prohibited practices |
| 2 August 2025 | Obligations for providers of general-purpose AI models; national authorities and EU governance |
| 2 August 2026 | Most of the Act, including the Article 50 transparency rules; enforcement starts |
| 2 December 2026 | New prohibitions on AI that generates non-consensual sexual deepfakes or child sexual abuse material; transitional deadline for certain providers whose generative systems were on the market before 2 August 2026 to meet the Article 50(2) marking rule |
| 2 August 2027 | Each Member State should have at least one AI regulatory sandbox running |
| 2 December 2027 | High-risk rules for the sensitive use cases in Annex III |
| 2 August 2028 | High-risk rules for AI embedded in regulated products (Annex I) |
So the transparency rules are not a future worry any more: they have applied since 2 August 2026. Fines for breaching them are set in Article 99: up to EUR 15 million or, for a company, up to 3 percent of total worldwide annual turnover, whichever is higher. That number explains the volume of the commentary, if not always its accuracy.
Article 50: who must disclose what
Article 50 is the piece that touches AI-generated content, and it splits duties between two roles.
Providers carry the marking duty. Under Article 50(2), the companies behind systems that generate synthetic audio, images, video or text must make sure the outputs "are marked in a machine-readable format and detectable as artificially generated or manipulated." That engineering burden belongs to the toolmakers, not to you. You do not owe anyone watermarks on your HTML.
Providers of chat systems carry a notice duty. Article 50(1) says systems "intended to interact directly with natural persons" must be designed so people are informed they are dealing with an AI system, unless that is obvious.
Deployers carry two disclosure duties, both narrow. The first covers deepfakes: if you publish AI-generated or manipulated images, audio or video that resemble real people, places or events in a way that could pass as authentic, you must disclose that the content was generated or manipulated. For evidently artistic, satirical or fictional work, the duty shrinks to a disclosure that does not spoil the work. The second covers text, and its wording does the heavy lifting: disclosure is required for AI-generated text "published with the purpose of informing the public on matters of public interest", and the duty falls away "where the AI-generated content has undergone a process of human review or editorial control and where a natural or legal person holds editorial responsibility for the publication of the content."
Read that against a normal business website. Product descriptions, service pages, a company story and pricing copy are commercial communication, not reporting to the public on matters of public interest. And if a person at your company read and approved the pages before publishing, and the company stands behind them, you have human review and editorial responsibility anyway. The review is meant to be real: someone actually checking the content, not a spell-check and a shrug. For a typical AI-built marketing site, that reading points away from any labelling duty. The Commission's guidelines on Article 50 define "AI-generated text on matters of public interest" and give in-scope and out-of-scope examples, so check your own pages against them rather than against this paragraph.
There is also a practical tool now. The Commission's Code of Practice on Transparency of AI-generated Content is voluntary, but the Commission and the AI Board have confirmed it as an adequate way to show compliance with the marking and labelling rules, and the EU has published icons that deployers may use to label generated content.
The edge cases that are real
Narrow is not the same as empty. A few configurations genuinely trigger obligations:
- A chatbot on your site. People talking to an AI system must be able to know it, at the latest at their first interaction. If you embed a vendor's assistant, check that it identifies itself. If you build or brand your own, read the guidelines on who counts as the provider, because that duty may then be yours.
- Synthetic people presented as real. AI-generated testimonials with invented customers, or a generated video of a recognisable person saying things they never said, run into the deepfake disclosure duty, and into consumer protection law that predates the AI Act by decades.
- News-shaped content. If your content marketing crosses from promotion into informing the public on public-interest topics, health or finance being the classic examples, the text disclosure question becomes live, and the human-review exemption becomes worth documenting rather than assuming.
- AI features beyond the website. The moment your business deploys AI for decisions about people, you are in a different part of the Act entirely, and this post stops being relevant.
Also worth a line: the AI literacy rule in Article 4, in application since February 2025 and amended by the omnibus, asks providers and deployers to "take measures to support the development of AI literacy" of the staff who operate AI systems on their behalf. It "does not require providers or deployers to guarantee any specific level of AI literacy of any individual." For a small team publishing AI-built pages, that is less a compliance project than a reason to know roughly what this post covers.
A checklist for your AI-built site
Work through these in order. For most marketing sites, steps three to five end with nothing to label.
- List the AI that runs on the site, not the AI that built it. Generated pages and copy are output. A chat widget, an image generator or any other AI feature that visitors use live is an AI system with obligations attached.
- No live AI features? Skip step three; steps four and five still apply to what you publish.
- Chat assistant on the site. Make sure it says it is an AI before or at the first message, in a clear and accessible way, and check who the provider is.
- Generated images, audio or video of real-looking people, places or events. Label them as generated unless they are obviously artistic or fictional, and then still mention it in a way that does not spoil the work. Do not invent customers or testimonials.
- Text that informs the public on matters of public interest. Either have a named person review and approve it, and keep a dated record of that review, or disclose that it was AI-generated.
- AI literacy. Write down which AI tools your team uses, for what, and who reviews the output. One page is a fine start.
- The regulation that already applied. Check the forms, the analytics and every processor in the chain under the GDPR. The data sovereignty overview walks through the layers, and data residency for AI websites shows how to verify where each one sits.
- Where the site runs. If you are choosing a host anyway, the European alternatives to Vercel and Netlify compares ten options with sources.
The compliance surface you already had
Here is the practical irony: for a marketing site, the AI Act changes little, while the GDPR has governed it all along. The form collecting visitor emails, the analytics script logging IPs, the jurisdiction of every processor in the chain: all of that applies with full force regardless of who or what wrote the HTML. Publishers worried about European regulation get more protection per hour from auditing those layers than from rereading Article 50. The operational side, review before publishing and reversibility after, is in deploying AI-generated frontends to production in the EU.
Hosting choice is part of that older, more concrete compliance story. VibeDeploy runs AI-built sites on servers in Belgium operated by Tnet Comm.V, with a DPA on every paid plan, built-in forms and analytics, flat plans from 4 euro on the pricing page (prices include VAT where it applies), and deploy paths made for AI workflows, from a dragged-in folder at deploy localhost to production to guides for ChatGPT and Claude artifacts.
Interpretations will keep sharpening as authorities enforce the rules. But the shape is clear enough to retire the panic. Publish honestly, review what you publish, disclose your chatbot, fabricate no humans, and keep your data layers in order. The AI Act was written for systems that decide things about people. Your website, thankfully, mostly just says things.
Sources
Official EU pages, checked on 13 October 2026:
- European Commission: AI Act, regulatory framework and application dates
- AI Act Service Desk: Timeline for the implementation of the EU AI Act
- AI Act Service Desk: Article 50, transparency obligations
- AI Act Service Desk: Article 99, penalties
- AI Act Service Desk: Article 4, AI literacy
- European Commission: Guidelines on transparency obligations for providers and deployers of certain AI systems
- European Commission: Code of Practice on Transparency of AI-generated Content
Ship your AI-built site in minutes
VibeDeploy hosts your AI-built websites in the EU with custom domains, automatic SSL, and a 14-day free trial that gets you online today.
Related reading
Data sovereignty for AI-built websites
What data sovereignty means for an AI-generated site, which layers of the stack carry jurisdiction, and how to decide where each one runs.
ChatGPT Sites and GDPR: Where Your Site's Data Lives
ChatGPT Sites has no data or inference residency at launch. What a Site stores, who is the controller, which DPA applies, and an EU-hosted route.
European Alternatives to Vercel and Netlify (2026)
Nine EU hosts and one UK host compared on company country, data location, SSR and containers, DPA, trials and AI-agent deploys. Every cell sourced.
EU-Hosted AI Models and EU-Hosted Websites: Two Layers
EU-hosted AI models answer where the model runs. A second question decides where the site it builds is served. This guide keeps the two layers apart.