- What the shared AI training opt-out published on October 30 says
- Why "User-Agent: *" must not be used to block everything
- The difference between refusing training and appearing in AI answers
- What to decide for your own site now
Short answer
On October 30, 2026, a draft was submitted to the IETF, the body that develops internet standards, for a single way to say "please do not use this site's content to train AI", instead of a separate instruction for each AI company. The same day, Google said on its official blog that it aims to support this signal, along with other AI providers, in 2027. It is still a draft, and companies will only start honouring it later. There is no need to rush a change, but it is a good moment to decide, as a business, whether your text and images may be used for training.
What was settled
The draft is titled "Machine-Readable Training Preference Signal" and expires on May 3, 2027. If you write a group named __usage_ai-training in robots.txt, the file at the root of your website, it expresses a preference that content at those paths should not be used for AI training. robots.txt was originally a way to tell crawlers such as search engines "please don't fetch this". The draft adds no new directives; it reuses the existing syntax to express a preference about use.
Until now, a site that wanted to refuse training had to look up a different name for each company, such as Google-Extended for Google, and list each one. Google says that if a site refuses training with the shared token and does not mention Google-Extended, it plans to treat that as a disallow for Google-Extended. Existing company-specific controls will keep working.
Three things to watch
"User-Agent: *" does not count
The draft states that a User-Agent: * group, which addresses every crawler, must not be read as a training preference. The reverse mistake is worse: writing Disallow: / under User-Agent: * to refuse training would also stop search engines, and your site could drop out of search results.
Writing nothing means no preference
If no group names the token, you have expressed no preference either way. Saying nothing is not the same as saying no.
Training and appearing in AI answers are different
According to Google, Google-Extended covers training future Gemini models and also "grounding", where Search content is given to the model when it answers. Sites that allow Google-Extended are eligible to appear in Gemini app answers and receive clicks from them. Google also says Google-Extended does not affect inclusion or ranking in Google Search.
"We don't want to be used for training" and "we want AI answers to mention us" can pull in opposite directions. Which matters more is a decision for each business.
What to decide for your own site now
- Group your content: things you want widely known, like your company profile; columns you put real effort into; photos whose rights you want to protect.
- For each group, decide whether it may be used for training and whether you want it mentioned in AI answers.
- Add /robots.txt to the end of your site address in a browser and see what it says today.
- Find out whether you can edit it yourselves, or whether it is changed by your web developer or through a settings screen.
- When you change it, keep the existing company-specific lines and add the shared group alongside them.
robots.txt is a request; it cannot stop a crawler that ignores the rules. Anything you truly do not want seen needs a different measure, such as not publishing it or putting it behind a login.
One thing to check today
Add /robots.txt to the end of your site address, open it, and see what it says today.