Where Googlebot spends its fetches against where the clicks come from, by section

The index-versus-fetch reconciliation now carries a section table: each section's share of verified Googlebot page fetches against its share of Search Console clicks and impressions, with the ratio and a flag where crawl share sits far below click share. Sections are the first path segment or prefixes you save per site.

Crawl budget questions usually come down to one comparison: is Google spending its fetches on the parts of the site that earn the clicks? Until now that needed an export from each side and a spreadsheet.

What changed

  • Crawl share against click share, by section, under the reconciliation buckets on Search Performance: per section, its share of verified Googlebot 2xx page fetches over your log window (UTC; assets excluded) against its share of Search Console clicks and impressions over the trailing 28 Pacific days, the crawl-to-click ratio, pages fetched and pages with clicks. Both windows are labelled on the table.
  • A "look" flag marks a section with at least 2% of clicks and a ratio under 0.5. It is worth a look, not a diagnosis: stable pages may need fewer recrawls, and 304 rechecks count as fetches.
  • Your own sections. The default is the first path segment; save section_prefixes on the website (API PATCH /v1/websites/{id}, up to 50 prefixes) to group by the sections that matter to you, or pass sections=/blog/,/shop/ on a call.
  • The API's search/reconcile response carries the sections table and accepts sections; the MCP server's get_search_reconcile does the same (1.27.0) and the CLI's search reconcile prints it (2.7.0). GET /public/v1/definitions explains crawl_to_click_ratio.

See crawl share against click share in the help.

← What was each crawler's request for? Pages, render resources, 304 rechecks, redirectsGoogle's Crawl Stats beside your log →
← All changelog entries