Home / Sites / churchleaders.com
How churchleaders.com treats AI agents
churchleaders.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, 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 |
| AI training (robots.txt) | No preference stated | Registry check, unverified, 7 Nov 2026 |
Listed in
Questions
Does churchleaders.com block AI bots?
No. churchleaders.com is open to AI agents.
Does churchleaders.com need JavaScript?
No. The page has real content without JavaScript.
Does churchleaders.com have an llms.txt?
No llms.txt was found.
Does churchleaders.com use a bot wall?
No bot wall was seen.
How should an agent fetch churchleaders.com?
Agents should read /feed instead of scraping.
Use this from an agent
JSON: /v1/origins/churchleaders.com. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.