Home / Sites / wiesbadener-kurier.de

How wiesbadener-kurier.de treats AI agents

Open to agents. Last checked .

wiesbadener-kurier.de is open to AI agents: no bot wall, no JavaScript needed, robots.txt restricts some paths, no llms.txt, feed or sitemap. A plain HTTP fetch works.

FactValueSource
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 None found Registry check, unverified, 7 Nov 2026
AI training (robots.txt) No preference stated 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 wiesbadener-kurier.de block AI bots?

No. wiesbadener-kurier.de is open to AI agents.

Does wiesbadener-kurier.de need JavaScript?

No. The page has real content without JavaScript.

Does wiesbadener-kurier.de have an llms.txt?

No llms.txt was found.

Does wiesbadener-kurier.de use a bot wall?

No bot wall was seen.

How should an agent fetch wiesbadener-kurier.de?

A plain HTTP fetch works.

Use this from an agent

JSON: /v1/origins/wiesbadener-kurier.de. MCP: https://onlinewebdirectory.net/mcp, tool lookup_origin. Setup: install notes.