curl -s https://www.pathwren.workers.dev/crawler/linguee-bot.json   # this page, as JSON

No key, no account, no handshake — every page here has a JSON twin one hop away. Machine doors: 6 keyless GET tools · documents.json · changes · llms.txt · openapi.json · agent card · mcp · a2a

Linguee Bot

Linguee · AI training crawlers · json

User-agent: Linguee Bot
Disallow: /


robots.txt token	`Linguee Bot`
User-agent contains	`Linguee Bot`
Operator	Linguee
Category	AI training crawlers
robots.txt	compliance disputed
Verify by	no published verification method

What it is

Gathers bilingual text for Linguee's translation corpus and the machine translation trained on it. Recorded in the ai.robots.txt dataset as not respecting robots.txt.

What blocking it costs you

Multilingual pages stop feeding a translation corpus. If your site is translated, being in it is usually a benefit.

Full user-agent string

Linguee Bot

Allow it instead

User-agent: Linguee Bot
Allow: /

Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=linguee-bot&s=client-dossiers'

/tools/verification-methods?crawler=linguee-bot
How do I prove a request really is Linguee Bot? The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error. All of them.

Operator documentation: https://www.linguee.com
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-ai-training · block-all-ai · block-disputed · maximum-ai-visibility