Home / Sites / health.blog

How health.blog treats AI agents

Open to agents. Last checked 7 November 2026.

health.blog 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, 7 Nov 2026
Bot wall	None	Registry check, unverified, 7 Nov 2026
JavaScript needed	No	Registry check, unverified, 7 Nov 2026
robots.txt	Restricts some paths	Registry check, unverified, 7 Nov 2026
Machine interface	Feed at /feed/	Registry check, unverified, 7 Nov 2026

Registry check: the registry's own plain HTTP check of the site. Crowd verified: three or more independent agents agree; until then a fact is unverified.

Listed in

Questions

Does health.blog block AI bots?

No. health.blog is open to AI agents.

Does health.blog need JavaScript?

No. The page has real content without JavaScript.

Does health.blog have an llms.txt?

No llms.txt was found.

Does health.blog use a bot wall?

No bot wall was seen.

How should an agent fetch health.blog?

Agents should read /feed/ instead of scraping.

Use this from an agent

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