Google to Back Unified robots.txt Standard for Blocking AI Training Data Use Starting in 2027

Google has announced plans to support a common mechanism in robots.txt that lets website owners set a single preference against the use of their content for training generative AI models. The feature will rely on work from the AIPREF working group at IETF and is scheduled for rollout in 2027. Under the proposal, a general policy marker will be introduced so that sites can express preferences regarding AI training without issuing separate directives to each provider. Google intends to treat a general prohibition the same way it currently handles the Google-Extended directive when no specific instruction exists. Existing per-company settings will remain available, allowing publishers to combine a broad rule with targeted exceptions for individual AI providers. The company noted that robots.txt only communicates usage preferences and does not technically block crawler access, so effectiveness will depend on which organizations adopt and honor the new standard.

AntiMalwareTranslated from Russian

Read at source

Google has announced support for a unified mechanism in robots.txt that will allow website owners to opt out of having their content used to train generative AI models. The change is intended to simplify the process for small and medium-sized businesses as well as larger publishers who currently must manage separate instructions for each AI provider.

The company detailed the plans in a post on its Search Central blog. The new capability will be based on work from the AIPREF working group at IETF and is expected to become available in 2027. A common policy marker will be added to robots.txt so that sites can express a single preference regarding AI training instead of maintaining individual directives for every participating company.

Google stated that it will interpret a general prohibition expressed through the new marker in the same manner as the existing Google-Extended directive when no specific instruction for Google-Extended is present. At the same time, current per-provider settings will continue to function, enabling publishers to set a broad rule and then add targeted exceptions for selected AI companies.

For content owners the approach could reduce the administrative burden created by the growing number of AI crawlers. However, the company emphasized that robots.txt only signals usage preferences and does not prevent access to servers. The practical impact will therefore depend on how many organizations adopt the standard and consistently respect the instructions it contains.

The initiative remains a proposal that will continue to be refined and standardized through the IETF process before final implementation.

Meridian digestThe week's most consequential security stories, distilled into one briefing.See the digest

More in Policy & Regulation

Russia's MinTsifry to Begin Issuing State Code Signing Certificates in 2027
Rostelecom Explores Underground Data Centers in Partnership with Nornickel for Enhanced Physical Protection
Who Pays When AI Agents Err: Insurance Gaps for AI Risks Emerge in Russia and the West