# [Products: the URL-level view](https://rebilder.com/help/console/console-products)

> Which URLs agents fetch, how often they get markdown, which platforms visit, and which orders touch each URL. The view stays honestly URL-level and never guesses product identity.

Products (a Pro surface) rolls up agent traffic by request URL for the selected range. The header states the honest scope: “URL-level view: product identity comes from your catalog wiring.” The gateway observes request URLs, not SKUs; until your catalog is wired through gateway sources, no product name is ever invented for a URL.



## The columns

| Column | What it means |
| --- | --- |
| Product URL | The URL agents requested (hover for the full URL). |
| Agent visits | Requests to this URL classified as kind `agent`; crawlers are excluded here. |
| Markdown served | What share (and count) of those agent requests were answered with markdown. |
| Platforms seen | The distinct agent platforms observed on this URL. |
| Last visit (UTC) | The most recent agent request. |
| Orders touching URL | Orders in the range whose reported product URLs include this exact URL: presence on the order, not attribution credit. The funnel is where attribution lives. |

> Rows are sorted by agent visits, up to 50 URLs. If the table is empty, agents have not fetched product URLs through the gateway in the range yet.