resulthack

All AI crawlers /

PetalBot

Huawei (Petal Search) · AI search · robots.txt: Yes

Petal Search's crawler: it indexes PC and mobile sites for Petal Search and for content recommendations in Huawei Assistant and AI Search services.

Block PetalBot

User-agent: PetalBot
Disallow: /

Huawei says banning PetalBot makes your pages unsearchable in Petal Search and every search service it powers, and that pages already indexed can take several months to disappear.

This token also decides Petal Search. The robots.txt generator leaves it to the rest of your file unless you choose Allow or Block for it by name.

Allow PetalBot

User-agent: PetalBot
Allow: /

An allow group only changes anything if a broader rule would block PetalBot. Under the robots.txt standard (RFC 9309, section 2.2.1) a crawler follows the group that names it and uses the User-agent: * group only when no group does — so this group lets it in even if your * group says Disallow: /. Token matching is case-insensitive.

Put these lines in /robots.txt at the root of each host (each subdomain has its own file). robots.txt is a request to well-behaved crawlers, not access control.

Block or allow it at the server

robots.txt asks; a server rule refuses. Every rule here matches PetalBot, spelled as in the User-Agent Huawei (Petal Search) documents (“compatible;PetalBot;”, “compatible; PetalBot;”), and matches it case-sensitively. The server answers 403.

What a User-Agent rule cannot do: any client can send any User-Agent. Access control by User-Agent is an unreliable technique, since the User-Agent header can be set to anything at all, at the whim of the end user. (Apache HTTP Server 2.4 documentation). A fake PetalBot is refused by the block rule along with the real one, and a crawler that hides its name passes. The “only the real one” rule is the check: it lets the name in only from Huawei (Petal Search)'s published addresses.

Your server

To block it: refuse every request that says PetalBot

In the server block (or a location)

if ($http_user_agent ~ PetalBot) {
    return 403;
}

PetalBot also decides Petal Search, so this refuses that crawl too.

The geo and map blocks go at http level; nginx's docs give Context: http for both, and for if Context: server, location. By default, the address is taken from the $remote_addr variable (nginx documentation).

To block it: refuse every request that says PetalBot

In the virtual host, a <Directory> block or .htaccess

<If "%{HTTP_USER_AGENT} =~ /PetalBot/">
    Require all denied
</If>

PetalBot also decides Petal Search, so this refuses that crawl too.

Apache httpd 2.4. Syntax: <If expression> ... </If> Context: server config, virtual host, directory, .htaccess (Apache HTTP Server 2.4 documentation). Several Require ip lines in one block: When multiple Require directives are used in a single configuration section and are not contained in another authorization directive like <RequireAll>, they are implicitly contained within a <RequireAny> directive. (Apache HTTP Server 2.4 documentation)

To block it: refuse every request that says PetalBot

Inside the site block

@petalbot header User-Agent *PetalBot*
respond @petalbot 403

PetalBot also decides Petal Search, so this refuses that crawl too.

Like directives, named matcher definitions must go inside the site blocks that use them. (Caddy documentation) On client_ip: This matcher is best used when the trusted_proxies global option is configured, otherwise it acts identically to the remote_ip matcher. (Caddy documentation)

To block it: refuse every request that says PetalBot

Expression of a custom rule; action Block

(http.user_agent contains "PetalBot")

PetalBot also decides Petal Search, so this refuses that crawl too.

Each expression is one custom rule with the action Block (Cloudflare's own example: Expression: (cf.bot_management.score lt 2 and http.user_agent contains "App_Name 2.0") Action: Block).

No “only the real one” rule: Huawei (Petal Search) publishes no IP list file this site holds for PetalBot. Huawei says to run a reverse DNS lookup on the IP and check the host name is in aspiegel.com (in the form petalbot.*.aspiegel.com), then a forward lookup on that name must return the same IP. Huawei also offers a Verify PetalBot tool; it publishes no IP list.

The IP rules compare the address your server sees. Behind a CDN or load balancer that is the proxy's address, so every claim would be refused: restore the client address first, or put the rule at the CDN.

Syntax from each server's own documentation, fetched 9 Oct 2026: nginx (rewrite module, map module, geo module); Apache (Access Control, <If>, expressions, mod_authz_core, mod_authz_host); Caddy (request matchers, respond); Cloudflare (custom rule example, operators, values and lists, http.user_agent). Every line form above is listed with its quote in server-rules-sources.json.

Who blocks it

Of the 1,000 most-visited domains on Tranco list PY35J (generated 2026-10-08), we read 508 robots.txt files on 2026-10-09 and ran each through the same RFC 9309 matcher as the checker, for the path /. 58 block PetalBot from the whole site by name, 30 block it through their User-agent: * group, and 4 name it with partial rules (some paths closed, the home page open). 1 more name it only to let it in.

58

block it by name 11.4%

30

block it through * 5.9%

4

name it, partial rules 0.8%

Percentages are of the 508 files we could read, not of all 1,000 sites.

Highest-ranked sites that block PetalBot by name

  1. facebook.com rank 4
  2. instagram.com rank 11
  3. fbcdn.net rank 12
  4. amazon.com rank 27
  5. whatsapp.net rank 32
  6. whatsapp.com rank 57
  7. tiktok.com rank 58
  8. yahoo.com rank 61
  9. amazonvideo.com rank 111
  10. snapchat.com rank 134

Each links to the site's live robots.txt, which may have changed since 2026-10-09.

robots.txt is only what a site asks for. A site can also turn a crawler away at its firewall or CDN, or let an operator in under a licensing deal, and neither shows in its robots.txt. A block through * stops every crawler the file does not name, so it says nothing about this one in particular. The files we could not read are not counted: 222 of the 1,000 domains are infrastructure names with no website at the bare domain (CDN and DNS zones, for example), 59 answered our request with 401 or 403, 93 failed (timeout, TLS or server error), 59 have no robots.txt (404 and similar) and 59 answered with an HTML page instead of a robots.txt file. Every agent's count, side by side.

Facts

Operator
Huawei (Petal Search)
Purpose
AI search index

Huawei says the index PetalBot builds serves Petal Search and also content recommendations in Huawei Assistant and AI Search services, all powered by the Petal Search engine.

Obeys robots.txt
Yes. Huawei says PetalBot complies with robots.txt, for the whole site or for single files, and that pages already indexed can take several months to clear after you block it.
In your server logs
The user-agent string contains "compatible;PetalBot;" (desktop) or "compatible; PetalBot;" (mobile).
How to verify it
Huawei says to run a reverse DNS lookup on the IP and check the host name is in aspiegel.com (in the form petalbot.*.aspiegel.com), then a forward lookup on that name must return the same IP. Huawei also offers a Verify PetalBot tool; it publishes no IP list.

What Huawei (Petal Search) says

Quoted word for word from the operator's documentation.

“PetalBot is an automatic program of the Petal search engine. The function of PetalBot is to access both PC and mobile websites and establish an index database which enables users to search the content of your site in Petal search engine and present content recommendations for the user in Huawei Assistant and AI Search services, both services are powered by Petal Search enigine.”

“PetalBot complies with the Internet robots protocol. You can use the robots.txt file to completely prevent PetalBot from accessing your website, or to prevent PetalBot from accessing some files on your website.”

“Note: Banning PetalBot from accessing your site will make the pages on your site and all search engine services provided by Petal unsearchable in the Petal search engine.”

“Although PetalBot has stopped accessing the pages on your site, it may take several months to clear the page index information that has already been established in the Petal search engine database.”

“Mozilla/5.0 (compatible;PetalBot;+”

“PetalBot’s hostname is in the format petalbot.*.aspiegel.com, and it is impersonated if it is not petalbot.*.aspiegel.com.”

“2. Verify that the domain name is in aspiegel.com.”

“3. Run a forward DNS lookup on the domain name retrieved in step 1 using the host command on the retrieved domain name. Verify that it is the same as the original accessing IP address from your logs.”

Sources

Same purpose, other operators

← All 49 AI crawlers

Made with AI tools. · Privacy