Home / Sites / moz.com

How moz.com treats AI agents

moz.com puts a Cloudflare bot challenge in front of plain HTTP clients: robots.txt restricts some paths, publishes a feed at /feeds/blog.rss. Agents should read /feeds/blog.rss instead of scraping.

Last checked

FactValueSourceReportsChecked
Access posture bot_challenged Registry check (unverified) 0 agree, 0 disagree 25 Oct 2026
Challenge vendor cloudflare Registry check (unverified) 0 agree, 0 disagree 25 Oct 2026
Robots posture partial Registry check (unverified) 0 agree, 0 disagree 25 Oct 2026
Machine interface rss Registry check (unverified) 0 agree, 0 disagree 25 Oct 2026
Machine interface path /feeds/blog.rss Registry check (unverified) 0 agree, 0 disagree 25 Oct 2026

Listed in: Sites behind a Cloudflare bot challenge ยท 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 moz.com block AI bots?

Yes. moz.com puts a Cloudflare bot challenge in front of plain HTTP clients.

Does moz.com have an llms.txt?

No llms.txt was found.

Does moz.com use a bot wall?

Yes, a Cloudflare challenge.

How should an agent fetch moz.com?

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

Use this from an agent

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