What Article 50 of the EU AI Act Actually Requires for AI-Generated Content
Article 50 of the EU AI Act went into effect on August 2, 2026, introducing new transparency rules for AI-generated and manipulated content. Much of the coverage has treated these rules as a single broad requirement to label AI content, but Article 50 creates separate obligations for AI system providers and for organizations that deploy AI to publish content. citeturn602123view1turn602123view2
The first obligation appears in Article 50(2) and applies to providers of generative AI systems. These providers must design their systems so that AI-generated or manipulated text, images, audio, and video can be marked in a machine-readable format and detected as such. This is a system-level requirement for companies providing generative AI technology, rather than a publishing requirement for every business using AI.
The second obligation, found in Article 50(4), applies to publishers, marketers, and content teams. When an organization uses an AI system to generate or manipulate text that is published for the purpose of informing the public about a matter of public interest, the organization may have to disclose that the text was artificially generated or manipulated.
That requirement is narrower than a rule requiring every piece of AI-assisted content to carry an AI label. Article 50(4) includes an exception: disclosure is not required when the content has undergone substantive human review or editorial control and a person or organization holds editorial responsibility for its publication. Simple proofreading, grammar checks, or other surface-level edits do not qualify as human review under the Commission’s guidance.
This distinction is relevant for content teams. Article 50 does not create a blanket requirement to label every article, product page, blog post, or marketing page that involved AI. The key questions are what the content is about, how AI was used, whether the subject is a matter of public interest, and whether meaningful human editorial review occurred before publication.
Timing also matters. The European Commission states that content generated before August 2, 2026 does not need to be labelled retroactively. That provides some protection for existing AI-generated material and should prevent companies from assuming they must review and label their entire historical content library solely because Article 50 became applicable.
The Disclosure – Probably Not Your Responsibility
Article 50(2) obligates providers of generative AI systems, meaning whoever develops a system and places it on the EU market or puts it into service under their own name.
For publishers, the practical issue is whether the publication falls within Article 50(4) and whether the organization’s editorial process satisfies the human review and editorial responsibility exception.
If your writers draft in ChatGPT or Claude, the marking duty sits with the AI vendor, and no watermark you could add would satisfy an obligation you do not hold. AI Systems already on the market before August 2 received until December 2, 2026 to comply with the marking and detection requirements.
The exception catches a small number of larger publishers. An organization that builds a generation system in-house, or takes an existing model, fine-tunes it on proprietary data and puts it into service under its own name, becomes a provider under the guidelines and inherits Article 50(2). Teams running SaaS tools do not have this obligation. However, teams running a fine-tuned model behind their CMS should examine the question rather than assuming the vendor absorbed it.
Unless Pages Topics are Included
Article 50(4) covers deepfakes and AI-generated text. Three criteria have to be satisfied at once: the text must be published, it must inform the public, and it must concern a matter of public interest. The third criterion is the primary filter, and the Commission introduces its list of qualifying subjects with the words “such as,” then offers:
- Politics and democratic processes
- Public administration and services
- Administration of justice and law enforcement
- Fundamental rights
- Public security
- Public health
- Environmental protection
Consumer safety, and any economic, financial, political, scientific or cultural developments that may be relevant subjects of public debate
The phrasing is illustrative rather than exhaustive, so assuming that anything unlisted is safe is risky.
Marketing does not appear on the list, nor do advertising, product copy, category pages, or comparison content. A SaaS pricing page falls outside, as does a recipe post. An explainer on new energy-efficiency rules written for European homeowners likely falls inside, along with anything published about drug interactions, financial products, or election coverage.
The difficulty sits in that final category. For example, a fintech blog covering interest rate changes is doing two things: informing readers about an economic development and selling them a product.
For client sites, I treat anything that could be read as informing the public rather than selling to them as in scope, and I make the call at the brief stage. Make sure you are keeping a review record.
What Passes
Article 50(4) does not apply to content that has undergone human review or editorial control where a natural or legal person holds editorial responsibility for the publication. That exemption is a useful provision for anyone running a content operation, and the Commission’s definition is specific:
Human review means “the deliberate examination of the substance of the content by one or more natural persons possessing relevant knowledge and professional judgment pertaining to the subject matter under scrutiny.” Editorial control means a responsible entity, an editor-in-chief for instance, holds authority to approve, alter, or reject the substance of a text on substantive grounds, including fact-checking and assessment of source reliability. The guidance states that “superficial, solely formal, or procedural checks (e.g. spell-checking or grammatical correction) are not considered to be human review or editorial control.” A junior marketer skimming for typos does not meet that requirement, whereas a subject-matter editor who checks claims against sources and has the authority to reject the piece does.
Editorial responsibility is the component teams often overlook. Someone has to bear ultimate legal responsibility for publication, and the regulation accepts either a named individual or an identifiable organization, provided that their identity and contact details are publicly available. An anonymous “Editorial Team” credit with no contact details does not apply the exemption.
Two structural points follow. Disclosures belong on the page rather than in sitewide footer boilerplate, because the obligation attaches to the content rather than to the site. Bylines are a separate question: Article 50 says nothing about who gets named on the page, and the preference for a real person over a model name comes from Google’s guidance rather than from Brussels.
What about US-Based Sites
The guidelines bring third-country deployers within the scope where the deployer “foresees dissemination and use of the AI outputs in the Union (i.e. by directing or authorizing distribution within the Union, including by posting deep fakes on the globally accessible internet)”. Relief comes only “where the content of the AI system reaches audiences in the Union through channels that are unforeseeable, and outside their control.” The parenthetical is important, because posting to the open web is offered as an example of foreseeing dissemination in the Union rather than as an example of incidental reach.
A different quote has been circulating in SEO coverage of this rule and applies to the wrong party. “Incidental, unforeseeable or unauthorised downstream use should not alone trigger the application of the obligations to such third country providers” is a line from the guidelines. However, it appears in the section governing third-country providers of interactive and generative systems, and it concerns Articles 50(1) and 50(2). It is not the deployer test, and it does not mean a US publication sits outside Article 50(4).
The regulation does not supply a market-targeting test, leaving foreseeability as the primary factor. The signals international SEOs already manage are the evidence of what a publisher foresaw, and I would expect any enforcement inquiry to reach for them first:
- ccTLDs and country subdirectories for EU markets
- hreflang annotations targeting EU locales
- Localized currency, VAT display and EU shipping options
- Paid campaigns geo-targeted to member states
- EU-language content that is not a machine-translation afterthought
If you create those, foreseeability is clear. A site running a de-DE section, German pricing and a Frankfurt sales team should assume Article 50(4) reaches it, while a US-only property carrying none of those signals holds a better position, though not a safe one. Either way the reasoning is worth writing down while the facts are fresh rather than reconstructing it later.
Enforcement runs mainly through national market surveillance authorities, with two exceptions. The AI Office picks up systems where the same entity supplies both the system and the general-purpose model under it, or where the system operates inside a platform or search engine designated as very large under the DSA, and the European Data Protection Supervisor handles EU institutions. Twenty-seven member states means twenty-seven enforcement postures, so practice will be uneven between markets for some time.
Fines under Article 99(4) reach 15 million euros or, for an undertaking, 3% of worldwide annual turnover, whichever is higher. Article 99(6) reverses that calculation for small and medium enterprises and start-ups, who face whichever of the two figures is lower, which makes 3% of turnover the current limit for most agencies and mid-market publishers.
What Disclosure Costs You in Search Results
Disclosure carries no ranking penalty, and Google’s own guidance recommends it. Search Central puts the question to publishers as a self-assessment in its people-first content documentation, asking whether “the use of automation, including AI-generation, [is] self-evident to visitors through disclosures, and in other ways,” and advising that disclosures be added “when it would be reasonably expected.” Google’s spam enforcement targets mass-produced content built to manipulate rankings, expressly “no matter how it’s created,” which places the emphasis on purpose and quality rather than on authorship method. No Google documentation treats a disclosure label as a negative signal.
The ranking data shows the same approach. Ahrefs pulled 1,000,000 pages from the top ten across 100,000 SERPs in June 2026, of which roughly 300,000 sat in their crawler database and about 150,000 carried enough text for AI detection. Among results ranking in positions one through three, 9% scored 80% or higher for AI content and 5.3% came back fully generated. Higher AI use does correlate with lower positions across the sample, which indicates average quality rather than a classifier suppressing disclosed content.
The one authorship pattern to avoid is the opposite of disclosure. Google encourages accurate authorship information, and its quality rater guidelines treat fabricated author profiles and invented credentials as a trust problem, though rater guidelines are not ranking inputs and no documented penalty attaches to fake bylines. The practice still works against the trust signals the rest of your work is building.
Six Things to Do This Week
- Classify your EU-facing pages. Run a content inventory and tag each piece as public-interest or not, treating the Commission’s examples as a minimum. Move the classification to the brief stage so it happens before writing rather than after.
- Establish who holds editorial responsibility. A named individual or the organization both satisfy the requirement, provided contact details are published, and the responsible party holds authority to reject a draft. Put it on an author or editorial page that resolves to something real.
- Rebuild the review step if it is currently a proofread. The reviewer needs subject-matter knowledge, fact-checking duties and the power to kill a piece, and that has to be written into the workflow.
- Start a review log. Record who reviewed each qualifying piece, on what date, and what they checked. The exemption is worth what you can evidence when a market surveillance authority asks, and a CMS custom field survives staff turnover better than a spreadsheet does.
- Add page-level disclosure where substantive review did not happen. Public-interest content shipping without review needs a disclosure on the page itself, in plain language and in a visible position.
- Record AI involvement in the CMS. Three states cover it: none, assisted, generated. Store the model used and the reviewer alongside, which takes an afternoon to configure and removes the reconstruction problem.
Four of those six are documentation rather than disclosure. Teams already doing substantive editorial work are already compliant. What they lack is the record that proves it, and that record costs less to build now than to assemble retroactively.
Where the Rule Is Still Unsettled
Commercial content on public-interest subjects occupies a gray zone. For example, a mortgage broker writing about rate changes, a supplement brand covering nutrition research and an energy retailer explaining efficiency rules are all informing the public about matters that appear on the Commission’s list, but all are pursuing a commercial objective.
I expect in the future the non-EU publishers will be defined by cases rather than by guidance. The text lets third-country deployers out only where EU audiences arrive through channels that are unforeseeable and outside the deployer’s control, and nobody has tested what that standard means for an ordinary public website.
“Published” also needs interpretation for gated content, email newsletters and syndicated feeds, none of which the regulation addresses or defines.
While guidance and enforcement practices are still forming, you could argue for drafting the articles now while they remain inexpensive.
NOTE: I AM NOT A LAWYER or an expert in this topic, and none of this is legal advice. Material EU exposure warrants counsel’s review of your specific setup. This was written with the help of AI and to inform international marketers on the subject
This article reflects the EU AI Act (Regulation (EU) 2024/1689) and the European Commission’s Guidelines on Transparency of AI-Generated Content, adopted 20 July 2026, as they stood on 12 August 2026.