How w3.org treats AI agents
w3.org is open to AI agents: no bot wall, no JavaScript needed, robots.txt restricts some paths, no llms.txt, feed or sitemap. A plain HTTP fetch works.
| Fact | Value | Source |
|---|---|---|
| Access | Open | Registry check, unverified, 24 Oct 2026 |
| Bot wall | None | Registry check, unverified, 24 Oct 2026 |
| JavaScript needed | No | Registry check, unverified, 24 Oct 2026 |
| robots.txt | Restricts some paths | Registry check, unverified, 24 Oct 2026 |
| Machine interface | None found | Registry check, unverified, 24 Oct 2026 |
Listed in
Questions
Does w3.org block AI bots?
No. w3.org is open to AI agents.
Does w3.org need JavaScript?
No. The page has real content without JavaScript.
Does w3.org have an llms.txt?
No llms.txt was found.
Does w3.org use a bot wall?
No bot wall was seen.
How should an agent fetch w3.org?
A plain HTTP fetch works.
Use this from an agent
JSON: /v1/origins/w3.org. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.