AI Policy / AI news for Malaysia
OpenAI Will Honour a Shared robots.txt Signal for AI Training Preferences
OpenAI says it will honour a shared robots.txt signal that lets website owners state a preference against generative AI training. It gives no start date, and the signal is an individual IETF draft, not a standard.

In brief
- OpenAI announced on 30 October 2026 that it will honour a common robots.txt signal for AI training preferences, and aims to implement it in the coming months.[1]
- The signal is a policy token, __usage_ai-training, in an individual IETF Internet-Draft dated 30 October 2026 that lists Anthropic as its author's affiliation. The IETF has not endorsed it.[2]
- OpenAI says the signal will not replace its existing crawler controls. Its page gives no implementation date and does not name the other participants.[1]
What OpenAI announced
OpenAI has said it will honour a shared signal in robots.txt, the file that tells automated visitors what a website allows. The signal lets a website owner state whether content may be used to train generative AI models. OpenAI announced the plan on 30 October 2026 and calls it a voluntary effort to cut the work of keeping separate rules for each AI provider.[1]
OpenAI says it aims to implement the signal in the coming months and will publish details then. The signal will not replace its existing crawler controls, which continue to apply. The page also encourages other AI providers to honour the signal. It does not say which products or models the signal will cover.[1]

How the signal works
The signal comes from an Internet-Draft titled Machine-Readable Training Preference Signal. An owner writes an ordinary robots.txt group whose User-Agent line is the token __usage_ai-training. A Disallow rule then states a preference against AI training for those paths, and an Allow rule states a preference in favour. The draft's own example disallows a whole site except a press-kit folder.[2]
The draft adds no new directive or grammar. Parsers that do not know the token ignore the group, so existing crawler rules behave as before. A wildcard group, written User-Agent: *, must not be read as matching the token, so a blanket rule for all crawlers does not state this preference. If no group names the token, no preference has been expressed.[2]

What the draft is and is not
The draft is an individual submission by K. Kelley, whose affiliation is listed as Anthropic. It is dated 30 October 2026, expires on 3 May 2027 and states an intended standards-track status. The datatracker page says the draft is not endorsed by the IETF and has no formal standing in the standards process.[2]
OpenAI says the signal draws on the IETF AI Preferences working group, whose vocabulary the draft follows for its definition of AI training. The draft says the token is not a directive for crawling. A consumer may use it to inform crawling, and private agreements may override a stated preference.[1][2]

What website owners still control
OpenAI says its existing crawler controls remain in force, and its page links to documentation for them. Rules that name OpenAI's crawlers keep working. The new signal is meant to spare owners from naming each provider's crawler and maintaining separate rules for every one.[1]
The announcement does not say how OpenAI will treat content collected before the signal takes effect. It does not say which other companies have agreed to honour the signal, beyond a reference to other working group participants. Owners cannot yet assume that one line in robots.txt will reach every provider.[1]
Why Malaysia should care
Neither source mentions Malaysia. The signal matters to any Malaysian business with a website, from publishers to online shops, because the file sits on the owner's own server. A shop or agency can edit the file without asking any provider for permission. Each owner decides whether to use it.
Malaysian publishers and content sites
They can state a preference against AI training in robots.txt once providers honour the signal.[1][2]
Practical move: Ask your web host or developer to review robots.txt.
SMEs with websites or online shops
Under the draft, a wildcard rule does not state this preference.[2]
Practical move: Add the token only after your developer tests the file.
Web agencies and developers
The draft keeps normal robots.txt grammar, and parsers that do not know the token ignore its group.[2]
Practical move: Check that your tools tolerate unknown groups.
What Malaysians can do now
- Ask your web developer to read your robots.txt and list which AI crawlers it names.
- Wait for OpenAI's implementation details before relying on the new token.
- Keep rules that name OpenAI's crawlers, because OpenAI says they continue to apply.
What we still do not know
Several details are still open.
- When OpenAI will implement the signal, and what its promised update will cover.
- Which other providers will honour it.
- Whether the IETF will adopt the draft, and in what form.
Sources
- 1.Making it easier for websites to express AI training preferences OpenAI, 30 October 2026
- 2.Machine-Readable Training Preference Signal (draft-kelley-aipref-training-preference-signal-00) IETF Datatracker, 30 October 2026
- 3.File:Person holding the OpenAI icon.jpg Wikimedia Commons, 28 August 2026
- 4.File:Server Room (22397102849).jpg Wikimedia Commons, 4 November 2015
- 5.File:2016 Kuala Lumpur, Domy-sklepy na ulicy Tun H S Lee.jpg Wikimedia Commons, 6 March 2016


