A verified Googlebot request means Google requested the URL. A successful response means your server or CDN recorded a successful delivery. Neither tells you whether Google indexed the page or showed it to a searcher.
Use the data source that answers the question you are investigating:
| Question | Where to check |
|---|---|
| Can Google discover the page? | Crawlable internal links, sitemap entries, and known referring pages |
| Did Google request it? | Verified crawler logs with the exact URL and timestamp |
| What did the server return? | Status, headers, bytes, response time, and captured content when available |
| Is it indexed, and which canonical was selected? | URL Inspection and the Page indexing report |
| Did it appear in search or get clicks? | Search Console performance reports |
| Did it produce a useful inquiry or sale? | Analytics linked to the actual lead or order record |
Break a crawl increase into useful groups
More requests can come from more final pages, or from repeated visits to the same parameters, redirects, missing pages, feeds, or assets.
Compare request counts and unique URLs by:
- hostname and page type;
- verified crawler or fetcher;
- status and request method;
- cache result and response size;
- date range and deployment period.
For example, an increase in successful requests to unique product pages tells you more about product discovery than a sitewide request total. A spike in redirects may instead expose old links left after a migration.
Keep bots out of visitor totals
One crawler can request hundreds of pages, and one page can be fetched repeatedly. Requests for scripts and images add more rows. These are not people, visits, or search clicks.
Label crawler charts as requests and unique URLs. Keep those charts separate from user analytics and acquisition reports.
Check the indexing result directly
A successfully fetched page can remain unindexed. It may duplicate another URL, contain missing or misleading content, be interpreted as a soft 404, or still await processing. A log count cannot distinguish these cases.
Inspect a representative URL and compare the crawl date, page-fetch result, indexing state, and canonical fields. Use the Page indexing report to see the wider pattern, remembering that its update date may differ from the logs.
If the URL was crawled after a deployment, check whether Google received the corrected page. If the latest inspection still predates the deployment, keep that timing difference visible in the diagnosis.
Measure search results and inquiries separately
An indexed page is eligible to appear in search. It can still receive no relevant impressions or clicks.
Compare Search Console performance over a fixed period by page and query. Add country, device, or search appearance only where those dimensions answer a specific question. Then check whether the visitors produced the action you care about: a qualified inquiry, purchase, or signup.
For a crawler dashboard, the essential fields are the date range and timezone, verified identity, requests, unique URLs, page types, and response statuses. Those fields help find crawl problems. They should not be relabeled as organic traffic or business growth.