Home / Sites / sandiegouniontribune.com
How sandiegouniontribune.com treats AI agents
sandiegouniontribune.com is open to AI agents: no bot wall, no JavaScript needed, robots.txt restricts some paths, publishes a feed at /feed/. Agents should read /feed/ instead of scraping.
| Fact | Value | Source |
|---|---|---|
| Access | Open | Registry check, unverified, 25 Oct 2026 |
| Bot wall | None | Registry check, unverified, 25 Oct 2026 |
| JavaScript needed | No | Registry check, unverified, 25 Oct 2026 |
| robots.txt | Restricts some paths | Registry check, unverified, 25 Oct 2026 |
| Machine interface | Feed at /feed/ | Registry check, unverified, 25 Oct 2026 |
Listed in
Questions
Does sandiegouniontribune.com block AI bots?
No. sandiegouniontribune.com is open to AI agents.
Does sandiegouniontribune.com need JavaScript?
No. The page has real content without JavaScript.
Does sandiegouniontribune.com have an llms.txt?
No llms.txt was found.
Does sandiegouniontribune.com use a bot wall?
No bot wall was seen.
How should an agent fetch sandiegouniontribune.com?
Agents should read /feed/ instead of scraping.
Use this from an agent
JSON: /v1/origins/sandiegouniontribune.com. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.