Web search

MojeekBot

Builds the independent Mojeek search index.

See your agent traffic
PurposeWeb search
HTTP identifierMojeekBot
IdentityVerify beyond the name

THE SIGNAL

What this visit tells you

Mojeek requests are one search engine’s crawl activity.

URL coverage
Crawl errors
Repeat crawls

Your next move

Compare successful public-page coverage with any Mojeek referrals.

The technical details

Markdown
How to identify it

Look for the MojeekBot identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.

How to check identity

Use Mojeek’s current published IP list or forward-confirmed reverse DNS under mojeek.com.

Access and robots.txt

MojeekBot follows its named robots.txt group, falling back to the wildcard group. It does not support Crawl-delay.

Optional full-site opt-out. Merge with existing rules only if intended. robots.txt does not secure private content.

User-agent: MojeekBot
Disallow: /
Seeing 403 or 404 responses?

403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.

Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.

SourcesReviewed 2026-09-14

Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.

APOSTL Pulse

See MojeekBot in context

See their requests. Find the pages that matter.

See your agent traffic