Google to Support a Shared AI Training Control in robots.txt
Google Search Policy Announced Announced Rollout: Not stated by the platform Last verified
Quick answer
On 30 October 2026 Google said it plans to support a robots.txt policy token, based on IETF AIPREF work, that lets a site opt out of AI training across participating providers at once. When a site uses the token to opt out and does not name Google-Extended, Google plans to treat it as a Google-Extended disallow.
Not sure how this affects your account? Send me a brief
What changed
- Google announced plans to support a shared AI training control placed in robots.txt.
- The control is a policy token drawn from the AIPREF working group at the IETF.
- If a site opts out with the token and has no explicit Google-Extended rule, Google plans to read it as though Google-Extended were disallowed.
- Google-Extended and other company-specific controls keep working next to the shared token.
- Google said it aims to support the control in 2027, and its crawler documentation names the user-agent __usage_ai-training.
Who is affected
- Site owners who manage AI training preferences in robots.txt, including anyone who already uses Google-Extended.
What to check this week
- Read your current robots.txt and note whether it has a Google-Extended group, since an explicit Google-Extended rule takes priority for Google. Recommended in the platform documentation: read the official page
Official sources
- Supporting a shared AI training control for websitesGoogle Search Central Blog · checked 13 November 2026
- Google's common crawlersGoogle Search Central · checked 13 November 2026
Related
How it works
Glossary
Not sure how this affects your account? Send me a brief and I will look at it with you.
Send me a briefPage history
- Updated on 13 November 2026: Published automatically after verification against the official source.