Read the locations grid#

A crawl produces one thing: a list of locations. A location is a distinct URL the crawler reached, together with the request it sent and the response it received. Everything else on this tab is a different view of that list, or a judgement about it.

The results area splits in two: the locations the crawler reached above, and the findings and the detail behind the selected row below. You can drag the divider between them.

Read the progress counts#

The strip along the top names the phase the crawler is in: seeding, crawling, then completed. Beside it sit three running counts: locations, requests, and findings. They climb while the crawl works. A Done chip replaces them when the crawl finishes on its own, or Cancelled if you stopped it.

The bar that fills during a crawl is not a completion percentage. The crawler does not know how big a site is until it reads all of it. The bar compares requests already sent against requests sent plus requests still queued, so it can move backwards when a page turns up a batch of new links.

Until the first location arrives you see Crawling, and nothing else.

List view and Map view#

Two icon buttons above the results switch between List view and Map view. List view is the default.

List view pairs a tree with a grid. The tree on the left arranges locations by host and URL path, so /api/public and /api/safe collapse under a shared api folder with a count beside it. Folders expand and collapse. Select a leaf to select that location. The tree is the fastest way to see the shape of a site.

The grid on the right lists every location as a flat row, one per URL. Four more columns describe each row.

• Kind: separates pages from forms, API endpoints, and assets.
• Status: the HTTP status code the response carried.
• Depth: counts navigation steps from the seed URL, so the seed is 0 and anything it links to directly is 1.
• Found by: records how the crawler learned of the URL. It usually reads seed, links, or sitemap, and it reads api-scan when the location came from an API definition rather than a crawl.

Read the Found by column closely. No page the crawler saw links to a URL discovered only by sitemap, which is a different fact about a site than a URL reached by following links.

The grid has no sorting and no filter box. To narrow a large result set, use the URL filter in Map view instead.

Select any row, in either the tree or the grid, to load that location into the detail pane at the bottom right. Findings and evidence covers what that pane shows.

Note The tree draws every visible row at once. At the default ceiling of 2000 locations it can feel slow where the grid stays responsive. Map view and the grid are the better choices on large crawls.

When no locations appear#

If the crawl finishes with no locations, the grid reads No locations discovered yet and the tree reads No locations yet. That usually means one of two things: the crawler could not fetch the seed URL, or every URL it found fell outside your scope rules.