# [Insights: coverage findings with fixes](https://rebilder.com/help/console/console-insights)

- **Summary:** Findings Rebilder computes from your events (unserved agent routes, missing outcome wiring, protocol demand, verification readiness), each with one concrete fix.

Insights (a Pro surface) checks the last 30 days of your store’s recorded events and shows findings, each with its real observed counts, the window they cover, and at most one concrete fix. Findings are computed live from your events; nothing is a projection. If nothing needs attention, the page says exactly what was checked: “No coverage gaps detected in the last 30 days.”



## Search crawlers still get your real pages

The most common worry about putting anything in front of a website is search. This panel answers it from your own traffic: how many search-crawler requests arrived, and how many were answered with your canonical HTML.

Search crawlers receive canonical HTML, and matching agent requests receive the same business information as markdown.

Compare the responses in Preview to check that prices, availability and policies match your website.

## What the gateway costs your responses

This panel shows the milliseconds the gateway itself spent, measured on every single request rather than sampled. It is NOT your page load time, and the difference matters: on a human page view the gateway classifies the request and hands off before your page runs, so your page is not in the number at all.

Compare performance by response path. Pass-through measures gateway handling; markdown includes source resolver time, and protocol responses include the configured handler.

The performance assessment appears once pass-through requests have been recorded.

## What agents asked for, and what they got

Compare total agent requests, explicit markdown requests and structured responses served. The Accept header records the requested format; the response records what the gateway supplied.

“Asked” counts explicit `text/markdown` values in the Accept header. Wildcard requests are counted separately because they do not specify markdown.

The table lists the most common Accept headers your agents actually sent. Where a store has a long tail, the remainder is folded into a single labelled row carrying the number of headers it stands for. Nothing is silently dropped.

## The finding catalog

| Finding | What it means | The fix |
| --- | --- | --- |
| Agent requests passing through unserved | Agents asked for your pages but received HTML instead of markdown because the gateway had no content source wired for those routes. The finding lists the top offending URLs with counts and last-seen times. | Wire a content source for those routes (the fix links to the sources docs). Once wired, those requests start getting clean markdown. |
| No orders reported | Agent traffic exists but zero orders have been reported, so the funnel cannot show whether any of it converts. | Wire the Shopify order webhook or the outcomes API; the fix links to the docs with both contracts. |
| Protocol demand at your endpoints | Requests reached the configured protocol endpoints. Review the operation and response to understand the interaction. | Wire `createProtocolHandler` so protocol requests get your live catalog instead of stubs. |
| Verified-agent readiness | How many of your agent requests carried no cryptographic verification (Web Bot Auth). Informational only. | Verification depends on signed requests and trusted platform keys. This informational card helps you track adoption. |

> Each finding is based on recorded events and includes the evidence supporting its suggested fix.