PetalBot
PetalBot is a bot operated by Huawei that indexes pages so an AI answer engine can cite them. Operated by Huawei to provide search and AI assistant services. It is documented as honouring robots.txt, but no IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine.
PetalBot at a glance
| User agent | PetalBotToken only. The operator has not published a full user-agent string, so match on the substring rather than an exact header. |
|---|---|
| Operator | Huawei |
| Purpose | Used to provide recommendations in Hauwei assistant and AI search services. |
| Respects robots.txt | Yes, documented |
| Verification method | None published, user agent only Huawei documents the crawler in its webmaster help. Traffic originates from Huawei Cloud ranges but no per-bot list is published. https://webmaster.petalsearch.com/site/petalbot |
| Crawl pattern | No explicit frequency provided. |
| Robots.txt tokens | PetalBot |
| Operator documentation | None published |
Operated by Huawei to provide search and AI assistant services.
Allow or block PetalBot
Paste one of these into the robots.txt file at the root of your domain. Rules are per token, so a block on one crawler leaves every other bot untouched.
User-agent: PetalBot
Disallow: /Blocks every path for this crawler only.
User-agent: PetalBot
Allow: /Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.
User-agent: PetalBot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own account, checkout and search URLs.
What blocking actually costs you
Blocking PetalBot takes the site out of the index behind its answers, so it stops being cited there. If referral traffic from AI answers matters to you, block the training crawler instead and leave this one alone.
Block every crawler in the directory at onceIs that really PetalBot?
A user-agent header is a string the client chooses. Scrapers copy PetalBot precisely because site owners allow it. Huawei documents the crawler in its webmaster help. Traffic originates from Huawei Cloud ranges but no per-bot list is published.
Paste the IP address from your access log below. You will see whether it belongs to a hosting provider, a residential proxy pool or a Tor exit, plus the ASN that announces it, which is what tells you whether the claim holds up.
Related crawlers
Identify crawlers automatically instead of by hand
Agentscan checks a request against published crawler ranges, reverse DNS and hosting data, then returns a verdict your edge can act on. One call per request, no range files to keep up to date.