PetalBot
Operated by Huawei
Quick Facts
- User-Agent:
- PetalBot
- Category:
- Search Engines
- Operator:
- Huawei
- Safety:
- Safe
- Blocking Impact:
- Critical - Blocking removes you from search results
- SEO Impact Score:
- 10/10
- Official docs:
- webmaster.petalsearch.com
What is PetalBot?
PetalBot is the web crawler for Petal Search, a search engine developed by Huawei. It is significant for reaching mobile users on Huawei devices.
PetalBot is the web crawler for Petal Search, a search engine developed by Huawei. It is significant for reaching mobile users on Huawei devices.
PetalBot is a production-grade search engine crawler operated by Huawei. 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 PetalBot 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 PetalBot?
How to block PetalBot with robots.txt
<code>User-agent: PetalBot</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.
Is PetalBot safe to allow?
PetalBot 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).What does PetalBot do?
Understanding PetalBot'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
Frequently Asked Questions
What is the official user-agent string for PetalBot?
PetalBot. 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 PetalBot by performing a reverse-DNS lookup on the source IP - legitimate bots resolve back to their operator's domain.Is PetalBot safe?
PetalBot 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 PetalBot hurt my SEO?
How do I block PetalBot in robots.txt?
/robots.txt file:
User-agent: PetalBot Disallow: /This instructs PetalBot 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 PetalBot respect robots.txt?
How do I verify if PetalBot is crawling my site?
PetalBot (case-insensitive grep: grep -i "PetalBot" /var/log/nginx/access.log). You can also check Google Search Console → Coverage → Crawl Stats for Googlebot variants. For PetalBot specifically, filter by user-agent in your log analysis tool (GoAccess, AWStats, etc.).What is the crawl frequency of PetalBot?
Can I block PetalBot from specific pages only?
Disallow: / you can restrict PetalBot to specific paths:
User-agent: PetalBot Disallow: /private/ Disallow: /staging/ Allow: /This allows PetalBot 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 PetalBot is blocked by my robots.txt?
https://aicrawlercheck.com/robots.txt and scanning for PetalBot 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 PetalBot in Search Console - what do I do?
yourdomain.com/robots.txt and look for any User-agent: PetalBot 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.