New EU GDPR Requirements for Disclosing AI-Generated Content

On August 6, 2026, focusing on content compliance for B2B independent websites operated for EU users, the European Data Protection Board (EDPB) issued new enforcement guidelines, with emphasis on transparent disclosure of AI-generated content. For companies conducting overseas business through product pages, multilingual content, SEO customer acquisition, and customer case presentations, this is no longer merely a content production issue. It is a new compliance requirement directly related to website delivery, channel visibility, and communication with EU procurement parties.

What disclosure requirements are specified in the guidelines?

According to the confirmed information, the EDPB issued the AI Content Transparency Enforcement Guidelines on August 6, 2026, requiring all B2B independent websites operated for EU users to label product descriptions, multilingual translations, SEO copy, customer cases, and other content generated by AI on their websites.

According to the summary, such labels must be placed at the bottom of the page or in the corresponding section, and must be presented in a machine-readable format using schema.org/AIContentDisclosure.

The summary also specifies that the disclosure must cover at least the model type, the training data cutoff date, and the status of human review.

In terms of its scope of impact, this requirement will directly affect the website compliance of Chinese suppliers delivering websites to EU buyers. For websites that fail to meet the requirements, the summary mentions that they may be removed from Google Shopping and the LinkedIn B2B recommendation pool.

Which business processes will the regulatory changes begin to affect?

Export companies acquiring customers in the EU need to recheck website delivery content

From the perspective of the business chain, export companies that acquire customers online directly from EU buyers will be affected first. The reason is that product descriptions, multilingual pages, SEO content, and customer cases are core sales-supporting information for B2B independent websites, while the new requirements directly impose constraints on how this content is generated and disclosed. The main changes companies need to focus on are content review before website launch, page structure configuration, and whether machine-readable labeling capabilities are available at the time of delivery.

Supply chain businesses providing website development and content services face new compliance delivery requirements

For supply chain service companies that provide manufacturers and suppliers with independent website development, content translation, SEO optimization, and case study packaging services, the impact is also direct. According to the analysis, copywriting and translation, which were originally part of marketing delivery, now also need to be assessed to determine whether they constitute AI-generated content, whether human review has been completed, and whether the relevant information can be structurally labeled on the page or within the corresponding section. This means delivery standards may extend from “content that is usable” to “content that can be disclosed, identified, and verified.”

Buyers and channels will pay greater attention to the credibility of website information

For buyers and channel distribution processes that rely on website information for preliminary screening, the main change lies in how information credibility is assessed. The summary states that websites failing to meet the requirements may be removed from Google Shopping and the LinkedIn B2B recommendation pool. This means that website content disclosure is no longer merely an internal compliance issue; it may also affect external traffic entry points and opportunities to be seen. Relevant companies need to focus not only on whether the content is accurate, but also on whether the explanation of the content source complies with the new rules.

Practical details that require closer attention at present

First identify which page content falls within the disclosure scope

Based on current observations, the first task for companies is not to expand content production, but to review which content on their websites falls within the scope of AI-generated content. According to the summary provided, product descriptions, multilingual translations, SEO copy, and customer cases have all been explicitly identified. Therefore, the relevant pages, sections, and templates should become priority areas for review.

Incorporate the “human review status” into the content publishing process

This requirement concerns not only the labeling of the model type and training data cutoff date, but also the status of human review. According to the analysis, this means that the content publishing process may need to retain clearer review records. For websites delivered by external service providers, companies also need to determine whether the delivery materials can specify the review status of the relevant content, so as to avoid a situation in which the frontend page has already gone live while the backend lacks a supporting information trail.

Pay attention to the impact of machine-readable labeling on technical delivery

The summary clearly requires the use of schema.org/AIContentDisclosure for machine-readable labeling. Therefore, technical implementation itself will become part of the delivery inspection. For website operations teams, website development service providers, and outsourced development teams, the current focus should be whether the structured implementation at the bottom of the page or in the corresponding section is properly completed, rather than merely adding a paragraph of ordinary explanatory text.

Channel visibility risks need to be incorporated into scheduling in advance

Since the summary mentions that websites failing to meet the requirements may be removed from Google Shopping and the LinkedIn B2B recommendation pool, companies should include these risks in schedule assessments when arranging website revisions, translation launches, and new website deliveries. This is more appropriately understood as a sign that channel rules and website compliance are beginning to interact. However, the specific enforcement standards, inspection methods, and timing still require continued observation of subsequent public information.

This change shows that the market is paying greater attention to “disclosable content sources”

This information sends a relatively clear signal: for B2B independent websites targeting EU users, the use of AI content itself is not the only focus. The ability to express the content’s generation source, training time boundaries, and human review status in a machine-readable manner is becoming a new enforcement priority.

Looking further, this appears more like a signal that the rules are entering the implementation stage, rather than merely a matter of principle. The reason is that the summary has already specified relatively concrete disclosure subjects, disclosure locations, and disclosure fields, while also mentioning consequences related to platform recommendation visibility. However, based on current observations, the industry still needs to continue monitoring subsequent enforcement standards, platform coordination methods, and actual corporate remediation feedback, so as to avoid treating details that have not yet been publicly clarified as established procedures.

How should this information currently be understood?

Overall, this change should be understood as an extension of website compliance requirements for the EU market from traditional data and privacy statements to the transparent disclosure of AI-generated content. Its direct impact is not limited to a single marketing activity, but concerns the coordination among website content production, translation delivery, technical implementation, and channel presentation.

At present, it is more appropriate to view this as an enforcement development that has released a clear signal: companies need to promptly verify the content of B2B independent websites targeting EU users and their technical capacity for implementing labels. However, they should continue to monitor the specific inspection standards, platform enforcement timeline, and market feedback that follow.

Basis of this article and directions for subsequent verification

This article was generated based on the information title, event date, and event summary provided by the user. The confirmed facts are limited to the input information itself. For events of this type, subsequent verification would normally need to incorporate releases from regulatory authorities, official announcements, updates to trade or platform rules, information from industry associations, documents issued by standards organizations, and reports from authoritative media.

As no specific official source link was provided in the input, the relevant formal texts, enforcement details, and public links still require continued verification. Topics worth monitoring include whether policy details will be further clarified, the enforcement standards for machine-readable labeling, changes to platform recommendation rules, whether bidding or delivery documents will be adjusted accordingly, and feedback from companies on actual implementation.