curl -s https://www.pathwren.workers.dev/crawler/mj12bot.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

MJ12bot

Majestic · SEO and backlink crawlers · json

User-agent: MJ12bot
Disallow: /


robots.txt token	`MJ12bot`
User-agent contains	`MJ12bot`
Operator	Majestic
Category	SEO and backlink crawlers
robots.txt	obeys robots.txt (documented)
Verify by	no published verification method

What it is

Majestic's link-graph crawler, run as a distributed community project. Majestic states plainly that it cannot restrict the bot to a fixed set of addresses, and offers a pre-arranged ident string in the request headers instead.

What blocking it costs you

You leave the Majestic backlink index. No search or AI effect. It supports Crawl-delay, which is usually the better answer than a block.

Full user-agent string

Mozilla/5.0 (compatible; MJ12bot/v1.4.8; http://mj12bot.com/)

Allow it instead

User-agent: MJ12bot
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=mj12bot&s=client-dossiers'

/tools/verification-methods?crawler=mj12bot
How do I prove a request really is MJ12bot? 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://mj12bot.com/
Machine copies: json · markdown
Policies that name this crawler: allow-all · block-seo-tools