# PetalBot

> Huawei's crawler for Petal Search, shipped as the default search on Huawei devices.

| field | value |
|---|---|
| operator | Huawei |
| category | Search engines |
| robots.txt token | `PetalBot` |
| user-agent contains | `PetalBot` |
| robots.txt | obeys robots.txt (documented) |
| verify by | reverse DNS |
| published IP ranges | none published |
| prefixes mirrored | 0 IPv4 / 0 IPv6 |
| operator docs | https://aspiegel.com/petalbot |
| last reviewed | 2026-09-14 |

## What blocking it costs you

Removal from Petal Search. Frequently blocked for volume rather than for policy.

## Full user-agent string

```
Mozilla/5.0 (Linux; Android 7.0;) AppleWebKit/537.36 (KHTML, like Gecko) Mobile Safari/537.36 (compatible; PetalBot;+https://webmaster.petalsearch.com/site/petalbot)
```

## Block it

```
User-agent: PetalBot
Disallow: /
```

## Allow it

```
User-agent: PetalBot
Allow: /
```

## Ask this page a question, with one GET

A question about this page, answered by a call you can make right now — no key, no account, no JSON-RPC, nothing to assemble. The query string is already filled in with this page's own subject.

- **How do I prove a request really is PetalBot?**  
  `curl -s 'https://www.pathwren.workers.dev/tools/verification-methods?crawler=petalbot&s=client-dossiers'`  
  The verification method its operator actually publishes — published IP ranges, reverse DNS, or nothing at all — and the mirror of it on this host.

Every parameter above is a value the endpoint reads, not an address it visits: nothing is fetched on your behalf. Called without any parameter, each endpoint returns its own specification instead of an error.

JSON: https://www.pathwren.workers.dev/crawler/petalbot.json · index: https://www.pathwren.workers.dev/llms.txt