Mojeek: User Agent, robots.txt Rules & Safety Rating

Q: What is the official user-agent string for Mojeek?

The official user-agent string for Mojeek is: Mojeek . This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from Mojeek by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.

Q: Is Mojeek safe?

Yes, Mojeek is a safe and legitimate crawler. It is operated by Mojeek, which publicly documents its crawler at an official URL and follows the Robots Exclusion Protocol (RFC 9309). The user-agent string Mojeek is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).

Q: Will blocking Mojeek hurt my SEO?

⛔ Critical Impact - Blocking Mojeek will stop Mojeek from crawling and indexing your pages. Within days or weeks you may see pages drop out of Mojeek's search index entirely, resulting in a significant loss of organic search traffic. This is the most severe possible SEO consequence. Only do this intentionally, for example if you are migrating to a different search engine or decommissioning a domain. If you accidentally blocked Mojeek, remove the rule immediately and request re-indexing via Mojeek's webmaster tools.

Q: How do I block Mojeek in robots.txt?

Add the following lines to your /robots.txt file: User-agent: Mojeek Disallow: / This instructs Mojeek not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g., Disallow: /blog/ ). Note: robots.txt is publicly readable - any bot or human can inspect it at yourdomain.com/robots.txt .

Q: How do I verify if Mojeek is crawling my site?

Search your web server access logs for the string Mojeek (case-insensitive grep: grep -i "Mojeek" /var/log/nginx/access.log ). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For Mojeek specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).

Quick Facts

User-Agent:: Mojeek
Category:: Search Engines
Operator:: Mojeek
Safety:: Safe
Blocking Impact:: Critical - Blocking removes you from search results
SEO Impact Score:: 10/10
Official docs:: www.mojeek.com

Confirmed by the operator

Mojeek names Mojeek on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Mojeek?

Mojeek is an independent, privacy-focused search engine based in the UK. It builds its own index rather than relying on other engines.

Mojeek is an independent, privacy-focused search engine based in the UK. It builds its own index rather than relying on other engines.
Mojeek is a production-grade search engine crawler operated by Mojeek. It uses a distributed crawl infrastructure that respects crawl-delay directives, follows RFC 9309 (robots.txt) spec, and processes Sitemaps to prioritise fresh content. The user-agent string Mojeek must be whitelisted if your site uses rate-limiting or WAF rules. Blocking impact is Critical - Blocking removes you from search results.

What happens if you block Mojeek?

⛔ Critical Impact - Blocking Mojeek will stop Mojeek from crawling and indexing your pages. Within days or weeks you may see pages drop out of Mojeek's search index entirely, resulting in a significant loss of organic search traffic. This is the most severe possible SEO consequence. Only do this intentionally, for example if you are migrating to a different search engine or decommissioning a domain. If you accidentally blocked Mojeek, remove the rule immediately and request re-indexing via Mojeek's webmaster tools.

Never block - it will remove your site from major search results.

How to block Mojeek with robots.txt

<code>User-agent: Mojeek</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)

User-agent: Mojeek
Disallow: /

Allow all (robots.txt)

User-agent: Mojeek
Allow: /

Block private only (robots.txt)

User-agent: Mojeek
Disallow: /private/
Disallow: /api/
Disallow: /admin/
Allow: /

Nginx server block

# Nginx: Hard-block Mojeek if ($http_user_agent ~* "Mojeek") { return 403 "Bot blocked"; }

Apache .htaccess

# Apache: Hard-block Mojeek
SetEnvIfNoCase User-Agent "Mojeek" bad_bot
Order Allow,Deny
Allow from all
Deny from env=bad_bot

Meta robots tag

X-Robots-Tag header

X-Robots-Tag: noindex, nofollow

Is Mojeek safe to allow?

Yes, Mojeek is a safe and legitimate crawler. It is operated by Mojeek, which publicly documents its crawler at an official URL and follows the Robots Exclusion Protocol (RFC 9309). The user-agent string Mojeek is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).

Verify by reverse-DNS lookup: legitimate Mojeek requests resolve to mojeek's domain.

What does Mojeek do?

Understanding Mojeek's purpose helps you decide whether to allow or block it.

Crawls and indexes web pages for search results
Discovers new and updated content on your website
Analyzes page structure, content, and links for ranking
Renders JavaScript to understand dynamic content
Checks for mobile-friendliness and page speed

Mojeek in context

Mojeek is a search engine crawler operated by Mojeek. In plain terms, it builds a search or answer index. Our database files it under search engines and ranks it Tier 3, mid-priority crawlers with a clear purpose but a smaller audience. 62 of the 63 search engines in our database share this tier.

Its safety rating is safe and its blocking impact is critical. So Mojeek is both well behaved and costly to lose: the strongest case for allowing it. How we rate safety and impact.

How site owners treat Mojeek

Our robots.txt study of the Tranco top 10,000 did not track Mojeek as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

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.

Mojeek crawlers and close alternatives

Mojeek is one of 2 Mojeek crawlers in our database. A User-agent: Mojeek group controls Mojeek only; the other Mojeek tokens below need their own lines.

Mojeek: this crawler (Tier 3)
MojeekBot: MojeekBot, builds a search or answer index (Tier 3)

To give Mojeek the same answer as its siblings, stack User-agent: Mojeek with their lines above one set of rules; to treat Mojeek differently, give it its own group.

Other search engines that do the same job (builds a search or answer index) include Amzn-SearchBot from Amazon, Applebot from Apple, baidu from Baidu, Baiduspider from Baidu, Baiduspider-favo from Baidu, Baiduspider-image from Baidu. Deciding about Mojeek is usually a decision about the whole group, so check how your file treats these too.

We first recorded Mojeek on March 17, 2026. Mojeek documents it on mojeek.com, and we recheck that page before each release.

Which rule Mojeek actually follows

Mojeek reads exactly one group in robots.txt, the most specific one that names Mojeek, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: Mojeek
Disallow: /drafts/

Find the group. Mojeek looks for a group naming Mojeek. One exists, so it ignores User-agent: * completely.
Apply only that group. It is refused /drafts/ and nothing else.
The surprise. /private/ is open to Mojeek, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.

Test yourself: does a rule under User-agent: * apply to Mojeek if the file also has a User-agent: Mojeek group?

No. Once a group names it, Mojeek reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Mojeek remove your pages from AI answers?

Often, yes. Mojeek is a search engine crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: mojeek the same as User-agent: Mojeek?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Mojeek? Decide by situation

Recommended setting for Mojeek by type of site
If you are...	Recommended setting
You publish content and want AI answers to cite it	Allow it. It is how this search engine finds your pages.
You license content and want to stop AI training	Blocking it does not stop training, because Mojeek is a search engine crawler. Block the operator's training crawler instead.
You run an online shop	Allow it unless it is overloading your servers.
Your server is under load from bots	Rate-limit before blocking. It is rated safe in our database.

Check Mojeek on your own site

Open /robots.txt on your domain and search for Mojeek. If it is not named, it follows User-agent: *.
List the Disallow lines in the group Mojeek follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
Look beyond the file. A firewall or bot manager can refuse Mojeek even when robots.txt allows it, and that never shows in the file.
Run our free AI crawler check to see how Mojeek and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Mojeek

The errors we see most often with Mojeek in the files and firewalls we test:

Blocking Mojeek 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: Mojeek group to add one rule for Mojeek and accidentally dropping every rule it used to follow under User-agent: *.
Disallowing CSS and JavaScript folders, which can stop Mojeek rendering your pages properly.

All three hide inside a file that looks correct, so check Mojeek from outside after every change.

Spotting Mojeek in your logs

robots.txt says what Mojeek may do; your access logs show what it 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" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "Mojeek" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Mojeek user-agent, 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.

Frequently Asked Questions

What is the official user-agent string for Mojeek?

The official user-agent string for Mojeek is: Mojeek. This is the exact string you must use in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. User-agent matching in robots.txt is case-insensitive, but the string must be spelled correctly. You can verify that a request genuinely comes from Mojeek by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.

Is Mojeek safe?

Yes, Mojeek is a safe and legitimate crawler. It is operated by Mojeek, which publicly documents its crawler at an official URL and follows the Robots Exclusion Protocol (RFC 9309). The user-agent string Mojeek is verifiable via reverse-DNS lookup on the crawling IP addresses. You can safely allow it unless you have a specific reason to block (e.g., AI training opt-out or SEO tool visibility).

Will blocking Mojeek hurt my SEO?

⛔ Critical Impact - Blocking Mojeek will stop Mojeek from crawling and indexing your pages. Within days or weeks you may see pages drop out of Mojeek's search index entirely, resulting in a significant loss of organic search traffic. This is the most severe possible SEO consequence. Only do this intentionally, for example if you are migrating to a different search engine or decommissioning a domain. If you accidentally blocked Mojeek, remove the rule immediately and request re-indexing via Mojeek's webmaster tools.

How do I block Mojeek in robots.txt?

Add the following lines to your /robots.txt file:

User-agent: Mojeek
Disallow: /

This instructs Mojeek not to crawl any path on your site. The Disallow: / directive covers the entire domain including subfolders. To only block specific sections, replace / with the path (e.g., Disallow: /blog/). Note: robots.txt is publicly readable - any bot or human can inspect it at yourdomain.com/robots.txt.

Does Mojeek respect robots.txt?

Yes - Mojeek is a well-behaved bot operated by Mojeek. It fetches and parses /robots.txt before crawling any page, following RFC 9309.

How do I verify if Mojeek is crawling my site?

Search your web server access logs for the string Mojeek (case-insensitive grep: grep -i "Mojeek" /var/log/nginx/access.log). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For Mojeek specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).

What is the crawl frequency of Mojeek?

Critical-impact search crawlers like Mojeek typically crawl popular pages daily and less popular pages weekly. You can manage crawl rate via the crawl-delay directive or via the search console.

Can I block Mojeek from specific pages only?

Yes. Instead of a global Disallow: / you can restrict Mojeek to specific paths:

User-agent: Mojeek
Disallow: /private/
Disallow: /staging/
Allow: /

This allows Mojeek everywhere except the listed paths. Path matching in robots.txt uses prefix matching - Disallow: /private/ blocks /private/page.html but NOT /public/private/.

How do I check if Mojeek is blocked by my robots.txt?

Use Google's robots.txt Tester in Search Console, or a third-party checker to simulate a Mojeek request. You can also manually check by opening https://aicrawlercheck.com/robots.txt and scanning for Mojeek entries. If a block exists, immediately test it against your most important URLs using the Google Search Console URL Inspection tool.

My site is blocked by Mojeek in Search Console - what do I do?

1. Open yourdomain.com/robots.txt and look for any User-agent: Mojeek or User-agent: * Disallow rules covering your key pages.
2. Remove or restrict the blocking rules.
3. Validate via Google Search Console → robots.txt Tester.
4. Request re-indexing using the URL Inspection tool.
5. Wait 1-2 weeks for re-crawl. Monitor Coverage report for recovery.