---
title: "PetalBot on WordPress: Why It Hits Your Site and How to Block It"
url: https://hostmy.blog/petalbot-wordpress/
date: 2026-11-11
modified: 2026-11-11
lang: en
author: "Aditya Sharma"
description: "PetalBot is Huawei Petal Search's crawler. What it is, its documented user agents, how to verify it, what blocking costs, and demo log lines."
categories:
  - "RankReady"
image: https://hostmy.blog/wp-content/uploads/2026/10/hmb-card-2809-1024x538.jpg
word_count: 1542
---

# PetalBot on WordPress: Why It Hits Your Site and How to Block It

PetalBot is the crawler for Petal Search, Huawei's search engine, and it is the bot that most often shows up in a small site's log with a name nobody recognises. It is not an AI training crawler by its own description. It builds a search index, and the same index feeds recommendations in Huawei Assistant and an AI Search service. Whether to block it depends on whether you want to be found there.

This post covers what PetalBot is, how to recognise it, how to confirm it is genuine, and how to block it on WordPress. It uses the crawler's [own documentation page from Petal Search](https://webmaster.petalsearch.com/site/petalbot). The log lines shown are invented demonstration lines, explained below.

![Numbered outline of this post, PetalBot on WordPress: Why It Hits Your Site and How to Block It: 1 What PetalBot is; 2 How to recognise it; 3 Count it in your own log; 4 What blocking does; 5 If it is too much load; 6 Why you still appear after blocking.](https://hostmy.blog/wp-content/uploads/2026/10/hmb-diagram-2809.png)The route through this post.

## A note on the demo lines

The log lines here are invented examples. They use PetalBot's documented user-agent strings, addresses from the documentation range 203.0.113.0/24 and made-up paths and sizes. They are not from our server and they show no real traffic or volume. They exist to show you the shape of the evidence in your own log. The one real address in this post, in the verification section, is the example Petal Search itself uses on its documentation page.

## What PetalBot is

Petal Search's documentation describes PetalBot as an automatic program of the Petal search engine. It visits both desktop and mobile pages and builds an index so that users can search your content in Petal Search. It also feeds content recommendations to users in Huawei Assistant and in an AI Search service, both powered by the Petal Search engine. So there are two things to know. It is a search crawler, and its index reaches an assistant and an AI search service. Its documentation does not describe training generative models, and it is not our place to add that.

## How to recognise it

The documentation lists two user-agent strings, one for desktop and one for mobile, and both carry the token PetalBot.

| Version | Full user-agent string, as documented |
| ------- | ------------------------------------- |
| Desktop | Mozilla/5.0 (compatible;PetalBot;+https://webmaster.petalsearch.com/site/petalbot) |
| Mobile | 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) |

The mobile string is worth a second look. It begins like an Android phone's, so a log tool that classifies visitors by device may count PetalBot as a phone. Match on the token PetalBot and not on the phone words. Here are three invented lines, one with each string and one with a refusal.

`203.0.113.30 - - [22/Oct/2026:03:02:11 +0000] "GET /sample-post/ HTTP/1.1" 200 18452 "-" "Mozilla/5.0 (compatible;PetalBot;+https://webmaster.petalsearch.com/site/petalbot)"
203.0.113.31 - - [22/Oct/2026:03:02:14 +0000] "GET /another-post/ HTTP/1.1" 200 20113 "-" "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)"
203.0.113.30 - - [22/Oct/2026:03:02:19 +0000] "GET /wp-admin/ HTTP/1.1" 403 199 "-" "Mozilla/5.0 (compatible;PetalBot;+https://webmaster.petalsearch.com/site/petalbot)"`

The third line shows a refused request to a path a search crawler has no reason to ask for. A 403 on an admin path is a rule doing its job. The same 403 on a post would be a different story.

## Count it in your own log

`grep -ci "PetalBot" /var/log/nginx/access.log
grep -i "PetalBot" /var/log/nginx/access.log | awk '{print $7}' | sort | uniq -c | sort -rn | head
grep -i "PetalBot" /var/log/nginx/access.log | awk '{print $9}' | sort | uniq -c | sort -rn`

The first counts the lines that carry the name, the second lists the paths it asked for, and the third counts the status codes. Replace the path with your log's. [Reading your server log by hand](/read-server-log-ai-crawlers/) explains where yours is and how the format works.

## Confirm it is genuine

Petal Search documents a way to check. Run a reverse DNS lookup on the address from your log with the host command. Check that the name is in petalsearch.com. Then run a forward lookup on that name and check it returns the same address. The page gives an example with the address 114.119.128.10, which resolves to a name beginning petalbot-114-119-128-10 under petalsearch.com, and the forward lookup returns the same address.

`host THE_ADDRESS_FROM_YOUR_LOG
host THE_NAME_THAT_CAME_BACK`

The forward step is the one that counts, because anyone who controls an address can set its reverse name. [How to verify a real AI crawler visit: IP lists and reverse DNS](/verify-ai-crawler-visits/) covers the same method for other vendors.

## If the check fails

If the reverse lookup returns no name, returns a name outside petalsearch.com, or the forward lookup gives a different address, the visit is not verified as PetalBot. The user-agent string proves nothing on its own, because any client can send any name. Treat the request as an unverified bot. You can leave it alone, limit it at your server or firewall, or block the address there. Do not rely on robots.txt for this. A robots.txt file is a request that well-behaved crawlers choose to follow, and it does not stop a client that ignores it.

## What blocking does

Petal Search says PetalBot complies with the robots protocol, and that you can use robots.txt to stop it entirely or to keep it out of some files. The documentation gives the two-line form that blocks it, and an example that allows one path and disallows another. It also gives a warning that matters: banning PetalBot makes your pages, and all of Petal's search services, unable to find them in Petal Search. So blocking costs you whatever audience Petal Search brings.

| Your situation | Leaning |
| -------------- | ------- |
| Your readers are not on Huawei devices or Petal Search | Blocking costs you little |
| You want to be found by Huawei Assistant users | Allow it |
| The load is the problem, not the index | Ask Petal to adjust, rather than block |
| You are unsure | Allow it, and watch the numbers |

The second example in the documentation shows how to be selective instead of all or nothing. It allows one path and disallows another, with Allow: /w/api/ and Disallow: /trap/. On a WordPress site you would adapt the shape, not copy the paths: allow what you want indexed, and disallow areas such as /wp-admin/ that no search crawler needs. Test any change on a copy of your robots.txt first, and open the live file in a browser afterwards to confirm that it says what you meant. Whichever rule you choose, write down why. A rule with no note beside it is the one nobody dares to remove a year later.

The WordPress steps for adding the rule are in [blocking or allowing 29 AI crawlers, and the robots.txt trap that exposes you](/block-ai-crawlers-robots-txt/). The file in general is in [WordPress robots.txt: what to allow, block and test](/wordpress-robots-txt/). They are not repeated here.

## If it is too much load

Petal Search says PetalBot needs to maintain a certain amount of crawling to give good results. It says it tries not to put an unreasonable burden on a site, and that it adjusts based on factors including server capacity, site quality and how often a site updates. If its visits look unreasonable, the documentation tells you to send your concerns to the address petalbot@huawei.com. That is a more targeted step than blocking, and it keeps you in the index. It does not mention a Crawl-delay directive, so do not rely on one.

## Why you still appear after blocking

The documentation also explains a common surprise. After you block PetalBot, it stops accessing your pages, but clearing the page information already in the index can take several months. Check that your robots configuration is correct, and if the matter is urgent, the page says to write to the same address. Do not assume a block takes effect in a day. Robots changes are one thing, and index removal is another.

Keep a note of the date you made the change and what you saw in your log that day. If pages still show in Petal Search a week later, that is consistent with the documentation. The better test of the block is your log: PetalBot lines for those paths should stop.

## What the demo lines cannot tell you

They cannot tell you how much PetalBot visits your site, or whether it visits it at all. That is a fact about your site, and the commands above are how you find it. The documentation tells you how the operator says PetalBot behaves. We have not published our own findings, and this post makes no claim about them.

## A routine

`1. Count PetalBot lines in your log.
2. Check the top addresses with the reverse and forward lookup.
3. Read the status codes for the genuine ones.
4. Decide whether the audience justifies the load.
5. If you block it, check the log again after a day, and expect the index to take longer.`

## Where Host My Blog fits

Host My Blog runs blogs for businesses, bloggers and agencies, and this site documents [RankReady](/plugins/rankready/), a free WordPress plugin for AI search visibility. RankReady lets you allow or block 29 AI crawlers one at a time, writes the robots.txt rules, and keeps a log of which AI crawler fetched which URL. PetalBot is a search crawler and not an AI-training one by its own description, so check the plugin's crawler list to see how it is labelled before you decide. It runs alongside Yoast, Rank Math, AIOSEO and SEOPress, and the free [AI Readiness Checker](https://hostmy.blog/plugins/rankready/ai-readiness-checker/) runs 41 checks on your live site.

If you counted PetalBot in your log tonight, would the audience it can send you justify what it costs you?