Manus-User is operated by Butterfly Effect. Browses, compares and buys on a person’s behalf. Blocking it removes you from the shortlist before anyone sees it.
Butterfly Effect runs it as an autonomous agent, which means it works through a task on somebody’s behalf — compare these suppliers, book the table, find the part that fits. It reads pages to decide, and what it cannot read it cannot put on the shortlist it hands back to the person.
What blocking it costs you: Manus, a general task agent with a large user base, cannot use your site as part of a job somebody asked it to finish. You are removed from the comparison before the customer sees it. The agent shortlists what it can read, and a refused fetch is not a lower score, it is an empty row.
The user agent, and the token a rule matches on
These are two different strings and confusing them is why a rule that looks right does nothing.
A robots.txt rule matches on the product token, case-insensitively, and
ignores the rest of the user-agent header entirely.
robots.txt token
Manus-User
Operator
Butterfly Effect
Category
Autonomous agent
Full user agent
Not published by Butterfly Effect. Match on the token above.
Where an operator has not published the exact string, this page says so rather than
inventing a plausible one. A user agent you can grep your logs for is worth nothing if it is a guess.
Allowing Manus-User
Paste this into robots.txt at the root of your domain.
An empty Disallow: and Allow: / mean the same thing to a crawler. What does
not mean the same thing is having no rule at all: absence is permission by default, but it is
permission nobody wrote down, and it survives only until somebody adds a blanket
User-agent: * block without thinking about this crawler.
Blocking Manus-User
User-agent: Manus-User
Disallow: /
Before you paste that: manus, a general task agent with a large user base, cannot use your site as part of a job somebody asked it to finish. That is the cost, and it is paid silently — no error appears in your logs, no report tells you, and the traffic you lose was traffic you never saw arrive.
How the web actually treats Manus-User
Measured on 2026-09-06, by reading the robots.txt of
292 public websites and resolving each one against this crawler specifically.
Verdict
Sites
Share
Blocked
10
3%
Explicitly allowed
228
78%
No rule either way
54
18%
No site is named, here or anywhere else on this domain. The count is the useful part; a league table of
businesses that never asked to be measured is not.
The row worth reading twice is the last one. 54 of 292 sites have written no rule about
Manus-User at all, which means their position on it is an accident rather than a decision — whatever
their User-agent: * block happens to say.
Checking what your site does right now
Reading your own robots.txt is not the same as knowing what a crawler concludes from it.
Precedence between a User-agent: * group and a named one, the longest-match rule between
overlapping paths, and a token you spelled slightly wrong all produce a file that looks correct and
behaves otherwise.
npx axray-cli your-site.com
The scan resolves your file against all 54 crawlers on this list individually and reports
which ones are allowed, blocked, or covered by nothing. It is free, needs no account, and installs nothing.
Questions people ask about Manus-User
What is Manus-User?
Manus-User is an autonomous agent operated by Butterfly Effect: it works through a task on somebody’s behalf — compare these suppliers, book the table, find the part that fits. It reads pages to decide, and what it cannot read it cannot put on the shortlist it hands back to the person.
Should I block Manus-User in robots.txt?
Only if you are willing to pay what it costs. Manus, a general task agent with a large user base, cannot use your site as part of a job somebody asked it to finish. You are removed from the comparison before the customer sees it. The agent shortlists what it can read, and a refused fetch is not a lower score, it is an empty row.
What is the Manus-User user agent string?
Butterfly Effect does not publish a full user-agent string for this crawler. The robots.txt product token is Manus-User, and that is what a rule matches on; matching is case-insensitive.
How do I check whether my site is blocking Manus-User right now?
Scan your site with AXRAY. It resolves your robots.txt against 54 named AI crawlers individually rather than reporting one verdict for all of them, so it will tell you whether this specific crawler is allowed, blocked, or covered by no rule at all. It is free and needs no account.