MojeekBot user agent
Operated by Mojeek
MojeekBot is Mojeek's crawler that builds the independent index behind Mojeek search.
The MojeekBot bot at a glance
- MojeekBot is operated by Mojeek and crawls web pages for a search engine index.
- The robots.txt token for MojeekBot is MojeekBot.
- Blocking a search engine crawler removes your pages from that search engine's results.
- MojeekBot robots.txt support: Yes.
- Recommendation for Generative Engine Optimization (GEO): Allow.
What is MojeekBot?
MojeekBot crawls pages for Mojeek, one of the few search engines with its own index rather than a licensed one.
Genuine MojeekBot hostnames end in mojeek.com.
Should you block MojeekBot?
Allow MojeekBot unless it causes a measurable load problem.
| Effect on search rankings | Blocking a search engine crawler removes your pages from that search engine's results. |
|---|---|
| Effect on AI visibility | AI features built on that search index, such as Google AI Overviews and AI Mode on top of Googlebot, also lose access to your pages. |
| Follows robots.txt | Yes |
| Recommendation | Allow |
How to block or allow MojeekBot
Put the robots.txt rule in the file at the root of every domain and subdomain, for example https://example.com/robots.txt. The token MojeekBot is matched case-insensitively.
robots.txt: block
# Block MojeekBot
User-agent: MojeekBot
Disallow: /robots.txt: allow
# Allow MojeekBot
User-agent: MojeekBot
Allow: /robots.txt: partial
# Keep MojeekBot out of private areas only
User-agent: MojeekBot
Disallow: /wp-admin/
Disallow: /cart/
Disallow: /checkout/
Disallow: /my-account/
Allow: /Nginx
# Nginx: return 403 to MojeekBot
if ($http_user_agent ~* "(MojeekBot)") {
return 403;
}Apache
# Apache .htaccess: return 403 to MojeekBot
RewriteEngine On
RewriteCond %{HTTP_USER_AGENT} (MojeekBot) [NC]
RewriteRule .* - [F,L]Cloudflare WAF
# Cloudflare > Security > WAF > Custom rule, action: Block
(http.user_agent contains "MojeekBot")How to verify real MojeekBot traffic
Reverse DNS check: look up the request IP, confirm the hostname ends in mojeek.com, then look up that hostname and confirm it returns the same IP.
# 1. Reverse lookup: the hostname must end in mojeek.com
host REQUEST_IP
# 2. Forward lookup: must return the same REQUEST_IP
host HOSTNAME_FROM_STEP_1How to find MojeekBot in your server logs
Search the web server access log for the token. The command below counts MojeekBot requests per URL on Nginx or Apache.
grep -i "MojeekBot" access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head -20For a full report per AI bot, upload the log to the AI Log File Analyzer, a free tool by Justin Hà.
MojeekBot FAQ
MojeekBot uses the robots.txt token "MojeekBot". Mojeek does not publish a full user-agent string, so match the token inside the User-Agent header.
Yes. Mojeek states that MojeekBot follows robots.txt rules written for the "MojeekBot" token.
Blocking a search engine crawler removes your pages from that search engine's results. AI features built on that search index, such as Google AI Overviews and AI Mode on top of Googlebot, also lose access to your pages.
Add two lines to the robots.txt file at the root of each domain and subdomain: "User-agent: MojeekBot" followed by "Disallow: /". The token is case-insensitive. Changes can take up to 24 hours to be picked up.
Yes. Run a reverse DNS lookup on the request IP; a real MojeekBot request resolves to mojeek.com, and a forward lookup of that hostname returns the same IP.
Search your server access log for "MojeekBot", for example with: grep -i "MojeekBot" access.log. The AI Log File Analyzer by Justin Hà counts visits per AI bot from an uploaded log file.
Sources: Mojeek crawler documentation. Last reviewed by Justin Hà.
See which of these bots actually reach your website
The AI Log File Analyzer by Justin Hà counts visits from GPTBot, ClaudeBot, PerplexityBot and other AI crawlers in your server log, for free. The GEO Technical Package sets up robots.txt, llms.txt and crawler access for AI search.
