PetalBot
The crawler for Huawei's Petal Search, the default search on Huawei devices without Google services.
PetalBot;+https://webmaster.petalsearch.com/site/petalbotOfficial documentation: webmaster.petalsearch.com
What PetalBot does
PetalBot builds Petal Search's index, serving the large installed base of Huawei devices. It is documented and states robots.txt compliance; some operators report heavy crawl volume and throttle it with crawl-delay.
Why it visits your site
Search indexing for the Huawei ecosystem.
The bigger picture: search engine crawlers
Search crawlers remain the one category with a decades-old, well-understood bargain: they consume crawl budget and return ranked visibility. Everything about them is comparatively mature - published IP ranges, verification methods, granular directives, webmaster consoles. Blocking them is almost always self-harm, which is precisely why they need to be cleanly separated from AI crawlers in your data: a blanket bot block that catches Googlebot costs you your organic channel.
The complication the AI era added is that search indexes now feed AI features too - AI Overviews draw on Google's index, Copilot on Bing's. Operators have answered with control tokens that split AI use from search use of the same crawl. The practical upshot: your lever for AI concerns is usually a token, not a block on the search crawler itself.
Should you block it?
If Huawei-device users matter to your audience, allow it, possibly with a crawl-delay. Otherwise it is a common candidate for blocking purely on crawl-volume grounds.
Block via robots.txt
Add these lines to the robots.txt at your site root to ask PetalBot to stay away:
User-agent: PetalBot Disallow: /
Remember that robots.txt is a request, not a lock - compliance is voluntary, and enforcement happens at the server. Viz's AI Control pairs robots.txt rules with server-level 403 responses and then probes your site to verify the block is actually holding.
How to see PetalBot traffic on your site
You have three windows onto it, each with a catch. Raw hosting access logs contain every PetalBot request, but many managed WordPress hosts don't expose them, and when they do you are grepping text files by hand. A CDN dashboard sees the traffic at the edge, but it lives outside WordPress and speaks in totals, not in your site's terms. And JavaScript analytics - GA4 and friends - will never show it at all, because PetalBot doesn't run scripts.
Viz's answer is the request log: filter to PetalBot and read exactly which URLs it fetched and when, right inside wp-admin - then watch the same filter after any blocking decision to see whether the visits stopped, slowed, or kept coming.