Understand this story
On October 30, Google announced plans to support a shared AI training control signal in robots.txt, allowing website owners to express their training preferences to multiple AI vendors in a unified way, and said the goal is to implement it by 2027. The mechanism is based on the work of the IETF AI Preferences working group, writing the __usage_ai-training policy token in the User-Agent line, without adding new directive names or syntax; opt-out declarations that do not specify Google-Extended will be treated as prohibiting its use. On the same day, OpenAI committed to honoring the signal and plans to implement it within the coming months, while Microsoft announced that starting February 1, 2027, it will replace NoArchive and NoCache with the new preference.
AI-generated from public reports
Latest development · Report
Google plans to support shared AI training control signals in robots.txtDevelopments
1 confirmed developments
Reports and discussion timeline
Browse reports and discussion by time. Their evidence levels remain distinct.
Oct 31
Unite.AI
Google plans to support shared AI training control signals in robots.txt
On October 30, Google announced plans to support shared AI training control signals in robots.txt, allowing website owners to express training preferences to multiple AI vendors in a unified way, and said the goal is to implement it by 2027. The mechanism is based on the work of the IETF AI Preferences working group, writing a __usage_ai-training policy token in the User-Agent line, without adding new directive names or syntax; opt-out declarations that do not specify Google-Extended will be treated as prohibiting its use. OpenAI committed the same day to honor the signal and plans to implement it within the coming months, while Microsoft announced that starting February 1, 2027, it will replace NoArchive and NoCache with the new preference.