Customer questions: what AI assistants searched for · Rebilder Help
Customer questions is included with Insights, Pro and Agency. It covers the selected site over 7, 30 or 90 days, 30 by default. Download searches (CSV) saves the searches for the range.
Find the questions worth answering next
Customer searches are grouped by what the customer needed, such as price or availability. Groups with the most searches that found nothing come first.
What agents searched for
The three most common searches lead, with how many times each was made and how many returned no results. Search details and counts opens the full table: Query, Searches, Zero results and Last seen. Work on your answers opens Answers Hub.
Searches come from search requests to your site and to your agent protocol endpoints. Text that could identify a person is dropped before anything is stored.
What needs your attention
Findings come from your site’s recorded requests for the range. Each shows its real counts and, where there is one, a next step:
| Finding | What it means | Next step |
|---|---|---|
| Pages needing a source check | AI assistant requests that could not get a sourced answer, with the pages involved. | Check the source for these pages. |
| Searches with no matching result | Searches that returned nothing, with how many distinct queries they were. | Review the questions and matching pages. |
| No orders received from your connected feed | Your order feed was active before and reported no orders in this range. | Check your order reporting connection. |
| Protocol requests recorded | Requests reached your agent protocol endpoints. | Review the requested operations. |
| Requester identity is not verified | AI assistant requests without a verified signature. Their platform names are claims. | Nothing to do. It is for information. |
With no findings, the page says “No coverage gaps detected” for the range and names what it checked. Improvements holds the work list.
Explore the evidence behind the questions
- What agents received: requests to public pages per day, and the platforms requesters claimed.
- Where visitors came from: visits with an AI referrer or a UTM tag, with related orders when an order feed is connected.
- Technical request details: agent protocol operations, which formats agents asked for and got, the milliseconds the gateway itself spent, and whether search crawlers got your regular pages.
How this is counted, at the foot of the page, explains every figure.