MultiOn
MultiOn is a recognized web agent operated by Multion. The exact behavior depends on context, watch the request pattern for a few hours before making a decision.
If volume is significant, rate-limit first and observe. Outright blocks should be reserved for agents that misbehave repeatedly.
See MultiOn on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
No
IP verification
User-Agent only
Crawl frequency
Variable
Honors robots.txt
Yes
Honors Crawl-delay
Varies
Multion runs 3 bots in total. Each one is a separate user-agent so you can allow or block them independently.
Agentic Browser
2Agentic Commerce
1- MultiOnYou are here
Should I let MultiOn through?
Watch your logs for a week first. Observe before acting. Volume and request pattern matter more than the user-agent string.
Does blocking MultiOn affect my Google rankings?
No. MultiOn is not a search-engine crawler. Your ranking on Google or Bing is unaffected by what you do here.
How do I confirm a request is really from MultiOn?
Look at the User-Agent header in your access logs and match it against the strings listed above. Worth knowing that the User-Agent is easy to fake, so this check tells you "the traffic claims to be MultiOn", not "the traffic is genuinely MultiOn". If you need stronger guarantees, look for a reverse-DNS check or wait for Multion to publish IP ranges.
What's the best way to understand what MultiOn is doing on my site?
Look at which URLs it hits, how often, and what time of day. The request pattern usually tells you whether it's building an index, watching for a specific change, or trying to pull data in bulk. The User-Agent name alone rarely tells the full story.
How is MultiOn different from Multion's other bots?
Multion splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Multion family above to see which ones actually matter for your site.
What's the cleanest way to control MultiOn?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.