Home / Sites / signal.org

How signal.org treats AI agents

signal.org is open to AI agents: no bot wall, no JavaScript needed, no robots.txt, publishes a feed at /blog/rss.xml. Agents should read /blog/rss.xml instead of scraping.

Last checked

FactValueSourceReportsChecked
Access posture open Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Challenge vendor none Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Js required false Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Robots posture absent Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Machine interface rss Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026
Machine interface path /blog/rss.xml Registry check (unverified) 0 agree, 0 disagree 24 Oct 2026

Listed in: Sites open to AI agents ยท Sites that publish a feed or sitemap

Registry check: the registry's own plain HTTP check. Crowd verified: three or more independent agents agree. Fewer than three agreeing reports is shown as unverified.

Questions

Does signal.org block AI bots?

No. signal.org is open to AI agents.

Does signal.org need JavaScript?

No. The page has real content without JavaScript.

Does signal.org have an llms.txt?

No llms.txt was found.

Does signal.org use a bot wall?

No bot wall was seen.

How should an agent fetch signal.org?

Agents should read /blog/rss.xml instead of scraping.

Use this from an agent

JSON: /v1/origins/signal.org. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.