Mojeek
SafeUser-agent: Mojeek
Category: Search Engines
SEO impact if blocked: 10/10
Mojeek
2 crawlers operated by Mojeek
Who Mojeek is, for site owners
Mojeek operates 2 crawlers in our directory, filed under Search Engines. Of those 2, 2 rated safe for crawl behaviour.
Blocking Mojeek carries an SEO impact score of 10/10 across its crawlers. Every crawler here carries the same blocking impact: Critical - Blocking removes you from search results.
Our recommendation for Mojeek, set by its least reassuring crawler (Mojeek, rated safe): Never block - it will remove your site from major search results.
Mojeek at a glance
| Operator | Mojeek |
|---|---|
| Crawlers in directory | 2 |
| Categories | Search Engines |
| SEO impact if blocked | 10/10 |
| Crawl behaviour | 2 rated safe |
| Official crawler docs | Mojeek crawler documentation |
Crawlers operated by Mojeek
What Mojeek's crawlers are for
Mojeek runs 2 crawlers in our database. Grouped by the job each one does:
- a search engine crawler:
Mojeek,MojeekBot
The highest-priority token is Tier 3. That makes Mojeek a lower-priority operator for most sites: worth a deliberate decision, but rarely the one that decides your visibility.
How site owners treat Mojeek
None of Mojeek's tokens were among the names tracked in our robots.txt study of the Tranco top 10,000, which usually means few large sites write rules for them yet. Your own logs are the best evidence of how often they visit.
Writing one policy for Mojeek
A robots.txt file cannot say "Mojeek"; it can only name Mojeek's tokens, one group at a time. So "block Mojeek" really means naming each of its 2 tokens, and you can give them different answers.
# Allow Mojeek search and assistants, refuse training
User-agent: Mojeek
Disallow: /
User-agent: Mojeek
User-agent: MojeekBot
Allow: /- Decide per job, not per company. Training, search and user-triggered fetching have different trade-offs, even from the same operator.
- Name every token you mean. A token you leave out follows
User-agent: *. - Repeat shared rules. A named group ignores the
*group, so copy anyDisallowlines you still want it to obey. - Verify from outside. Run the AI crawler tester after any change to see the result for each Mojeek token, including firewall refusals.
Test yourself: does User-agent: Mojeek block all of Mojeek's crawlers?
No. robots.txt matches crawler tokens, not company names. Name each token: Mojeek, MojeekBot.
Test yourself: if you block one Mojeek token, are the others blocked too?
No. Each token is read separately. Blocking one leaves the rest following whatever group applies to them.
Each Mojeek crawler, explained
A one-paragraph brief for every Mojeek token in our database, covering what it does, how it treats robots.txt and how often large sites write rules for it:
- Mojeek (
Mojeek, Tier 3): a search engine crawler that builds a search or answer index. Rated safe. Mojeek's operator does not clearly document how it treats robots.txt. Write the Mojeek rule anyway, then confirm in your logs that its requests stop. Not tracked in our robots.txt study. - MojeekBot (
MojeekBot, Tier 3): a search engine crawler that builds a search or answer index. Rated safe. MojeekBot's operator does not clearly document how it treats robots.txt. Write the MojeekBot rule anyway, then confirm in your logs that its requests stop. Not tracked in our robots.txt study.
Common mistakes with Mojeek's crawlers
The errors we see most often with Mojeek's crawlers in the files and firewalls we test:
- Blocking Mojeek's crawlers to save bandwidth and then wondering why pages drop out of that search engine. Use crawl-rate settings or caching first.
- Writing a
User-agent: Mojeekgroup to add one rule for Mojeek's crawlers and accidentally dropping every rule it used to follow underUser-agent: *. - Disallowing CSS and JavaScript folders, which can stop Mojeek's crawlers rendering your pages properly.
All three hide inside a file that looks correct, so check Mojeek's crawlers from outside after every change.
Spotting Mojeek in your logs
robots.txt says what Mojeek and MojeekBot may do; your access logs show what they actually did.
Count requests
On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):
grep -iE "Mojeek|MojeekBot" /var/log/nginx/access.log \
| awk '{print $4}' | cut -d: -f1 | sort | uniq -cAnd this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:
grep -iE "Mojeek|MojeekBot" /var/log/nginx/access.log \
| awk '{print $7}' | sort | uniq -c | sort -rn | head -20Check the requests are genuine
Anyone can send these user-agents, so confirm the source before acting on a match:
Mojeek: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Mojeek request with caution. Check it separately from MojeekBot.MojeekBot: we hold no published IP list, so use reverse DNS where Mojeek documents a hostname and treat an unverifiable MojeekBot request with caution. Check it separately from Mojeek.
What our own data shows about Mojeek
Everything below comes from the AI Crawler Check bot database and our two most recent robots.txt scans of the Tranco top 10,000, not from Mojeek's marketing. It covers 2 Mojeek tokens in turn.
Mojeek in our records
We first recorded Mojeek on March 17, 2026. Mojeek documents it on mojeek.com, and we recheck that page before each release. No file in our top-10,000 scans names Mojeek, so any rule you write for it puts you ahead of almost every large site.
Among the 63 search engines in our database, Mojeek sits 21th by priority (Tier 3), level with AdIdxBot, Amzn-SearchBot, Applebot, baidu. 62 of the 63 share its safe rating. Other operators with a crawler that builds a search or answer index: AddSearchBot (AddSearch, Tier 2), AIWebIndex (Lyrenth, Tier 2), atlassian-bot (Atlassian, Tier 2), AzureAI-SearchBot (Microsoft, Tier 2), Cloudflare-AI-Search (Cloudflare, Tier 2). A policy for Mojeek is usually a policy for these too.
A decision record for Mojeek
Teams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the Mojeek entry reads:
- Operator and job: Mojeek; it builds a search or answer index.
- Priority and behaviour: Tier 3, rated safe, blocking impact critical.
- Suggested starting point: Allow by default; revisit if it costs you bandwidth.
- Enforcement: Mojeek's operator does not clearly document how it treats robots.txt. Write the Mojeek rule anyway, then confirm in your logs that its requests stop.
User-agent: Mojeek
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the Mojeek entry once a quarter, or when Mojeek publishes a new token next to it.
MojeekBot in our records
We first recorded MojeekBot on March 17, 2026. Mojeek documents it on mojeek.com, and we recheck that page before each release. No file in our top-10,000 scans names MojeekBot, so any rule you write for it puts you ahead of almost every large site.
Among the 63 search engines in our database, MojeekBot sits 22th by priority (Tier 3), level with AdIdxBot, Amzn-SearchBot, Applebot, baidu. 62 of the 63 share its safe rating. Other operators with a crawler that builds a search or answer index: AddSearchBot (AddSearch, Tier 2), AIWebIndex (Lyrenth, Tier 2), atlassian-bot (Atlassian, Tier 2), AzureAI-SearchBot (Microsoft, Tier 2), Cloudflare-AI-Search (Cloudflare, Tier 2). A policy for MojeekBot is usually a policy for these too.
A decision record for MojeekBot
Teams that review crawlers once a quarter keep one short entry per token, so anyone can see why a rule exists and when it was last checked. Filled in from our data, the MojeekBot entry reads:
- Operator and job: Mojeek; it builds a search or answer index.
- Priority and behaviour: Tier 3, rated safe, blocking impact critical.
- Suggested starting point: Allow by default; revisit if it costs you bandwidth.
- Enforcement: MojeekBot's operator does not clearly document how it treats robots.txt. Write the MojeekBot rule anyway, then confirm in your logs that its requests stop.
User-agent: MojeekBot
Allow: /Paste the line into the validator with one of your own URLs before it goes live. Revisit the MojeekBot entry once a quarter, or when Mojeek publishes a new token next to it.
How top sites treat Mojeek's crawlers
From our robots.txt study of the Tranco top 10,000 (5,583 valid files, fetched October 20, 2026):
None of the tokens for Mojeek's crawlers is tracked by name in our study. For scale, 20.1% of top-site files block at least one AI training crawler and 4.3% refuse every unnamed crawler with User-agent: * and Disallow: /, which would catch Mojeek's crawlers too.
More questions about Mojeek
- Will blocking Mojeek affect my Google rankings?
- Only if one of its tokens is a Google search crawler. None of Mojeek's tokens are Googlebot, so classic Google rankings are unaffected.
- How quickly does a robots.txt change take effect for Mojeek?
- Crawlers cache robots.txt, commonly for up to a day. Expect a change to apply within about 24 hours, and confirm it in your logs.
- Can I allow Mojeek on some sections and block it on others?
- Yes. Inside the group for
Mojeek, addDisallowlines for the paths to keep private andAllowlines for exceptions. The longest matching rule wins. - Does blocking Mojeek delete content it already collected?
- No. robots.txt only controls future visits. For content already collected, check whether Mojeek offers a removal or opt-out process.
- Is a firewall block better than robots.txt for Mojeek?
- A firewall enforces the decision, while robots.txt asks politely. Many operators recommend robots.txt because blocking their IPs can stop them reading your rules at all. Use robots.txt first, and add a firewall rule only if requests continue.
A five-minute Mojeek review
- Confirm the token. Compare the user-agent in your logs with the tokens listed on this page. A close spelling is not the same crawler.
- Decide the outcome per crawler. Use the briefs above to choose allow, limit or block for each token.
- Write the group. Add or edit one
User-agentgroup per decision and repeat any shared rules inside it. - Publish and wait. Allow about a day for crawlers to fetch the new file.
- Confirm the result. Check your logs, then run the AI bot access checker to see the outcome from outside, including any firewall layer.
How to block or allow Mojeek in robots.txt
These rules cover all 2 crawlers Mojeek operates. Add them to the robots.txt file at the root of your domain.
Block Mojeek completely
User-agent: Mojeek
User-agent: MojeekBot
Disallow: /
Allow Mojeek explicitly
User-agent: Mojeek
User-agent: MojeekBot
Allow: /
These Mojeek rules ask; they do not enforce. If a Mojeek token ignores them, block it at the server or CDN. Paths are case-sensitive, and each rule matches the token, not the full user-agent string.
Frequently asked questions about Mojeek
What crawlers does Mojeek run?
Mojeek operates 2 crawlers in our directory: Mojeek (user-agent Mojeek), MojeekBot (user-agent MojeekBot).
Should I block Mojeek?
Never block - it will remove your site from major search results. That guidance follows this operator's least reassuring crawler, Mojeek, rated safe, because allowing an operator allows every crawler it runs. The SEO impact score for blocking is 10/10, where 10 means blocking costs you the most visibility.
How do I block Mojeek in robots.txt?
Add the following to robots.txt at your domain root: User-agent: Mojeek then User-agent: MojeekBot then Disallow: /. One Disallow line covers all 2 user-agent tokens.
Does blocking Mojeek hurt my search rankings?
Every crawler here carries the same blocking impact: Critical - Blocking removes you from search results. Those are search-indexing crawlers, so blocking them can remove your pages from the corresponding search results. Block them only if you intend to leave that index. Every crawler in this group is rated the same way, so there is no subset here that is safe to block for ranking purposes.