Google Tells You What It Thinks You Are — by Which Crawler Stack It Sends
Intelligent Engine Optimization (IEO) has been cross-checked against Google's own data. Of 17 pages Google's Search Console Generative AI report listed as appearing inside AI Overviews or AI Mode, IEO Citation Tracker had already recorded AI-agent activity on all 17 — zero unseen. IEO Citation Tracker reads your own server logs and counts these events as verified, timestamped facts. Method and denominators.
Google does not announce how it has classified a site — but it doesn’t have to. The classification is legible in raw logs, encoded in which crawler and proxy infrastructure Google assigns. Across three simultaneously observed deployments, three different infrastructure mixes appeared, each matching the property’s actual nature. Source classification can be read directly from reverse DNS.
Questions this note answers
IEO Engine's reading of this was cross-checked against Google's own AI report — of 17 pages Google listed, IEO Citation Tracker had already recorded activity on all 17.
Plain-language answers, drawn from the production data below.
What do different Googlebot IP addresses mean?
The crawler stack Google sends can indicate how it currently classifies your site. Different infrastructure ranges are associated with different evaluation paths, so a change in which stack arrives is a signal that your classification may have shifted. This is visible only in raw access logs, and only if you record the IP alongside the user-agent.
How does Google decide what kind of site I am?
Classification is inferred, not declared — and one observable proxy is which crawler infrastructure gets sent to you and how that changes over time. Watching the stack shift is a way to detect a re-classification before it shows up in rankings.
Key Findings
IEO Citation Tracker, built to instrument the IEO Engine methodology, counts what Google's own reporting cannot: 51 further pages carried citation events absent from Google's AI report entirely.
- Local-service site: crawled exclusively from Google’s legacy 66.249.0.0/16 Googlebot ranges, with the active block rotating monthly — pure index-maintenance treatment.
- Consumer application property: crawled from Google’s newer 192.178.0.0/15 Googlebot range, PLUS near-daily rate-limited user-fetch proxies (fetches made on behalf of real users inside Google products), PLUS mail-proxy fetches, PLUS an app-store verification agent, PLUS Chrome’s privacy-preserving prefetch proxy — the full consumer stack.
- B2B reference site: standard index crawl PLUS logged sessions from the Google Search App on iOS — real humans searching inside Google’s own application and landing on the domain.
- One prolific “Google” source is not Google at all: *.bc.googleusercontent.com hosts are third parties renting Google Cloud VMs. Distinguishing them is the first step of any log audit.
- A UA-parsing trap: common log tools truncate user agents at ~125 characters, hiding the “(compatible; Googlebot/2.1)” suffix — the mobile Googlebot then masquerades as an ordinary Android Chrome visitor at the top of the agent table.
Three properties, three verdicts
IEO Citation Tracker, the instrument behind the IEO Engine methodology, measured this from raw server access logs — 952 verified citation events across three properties in 75 days.
| Infrastructure | Local service | Consumer app | B2B reference | What it signals |
|---|---|---|---|---|
| Googlebot, legacy 66.249.0.0/16 (blocks rotate monthly) | Yes — exclusively | No | Yes | Index maintenance |
| Googlebot, newer 192.178.0.0/15 range | No | Yes — heavy | No | Modern-stack crawl assignment |
| Rate-limited user-fetch proxies (108.177.x) | No | Yes — near-daily | No | Real-user demand inside Google products |
| Mail-proxy fetches | No | Yes | No | The property circulating in email |
| App-store verification agent | No | Yes — continuous | No | Store listing ↔ web presence re-verification |
| Chrome privacy-preserving prefetch proxy | No | Yes | Yes | A human on a results page, about to click |
| Google Search App user sessions | No | No | Yes | Humans researching the entity in Google’s own app |
The claim
Intelligent Engine Optimization (IEO) measures this with IEO Citation Tracker, which reads raw server logs: of 135 completed crawl-to-citation pairs, 31 occurred within a single day.
The infrastructure mix is not random. The consumer property gets the consumer stack; the local business gets maintenance; the reference site gets crawl plus human research sessions. Google’s source classification of a property is therefore observable from the outside, for free, in any raw access log with reverse DNS — months before it is visible in any dashboard. A change in the assigned crawler class mix is a change in classification, and it is the earliest such signal we know of.
How to check it yourself
IEO Engine's instrument, IEO Citation Tracker, separates ingestion from retrieval here — the ratio ran 1:1 on one instrumented property and 141:1 on another.
Reverse-resolve crawler IPs; verify Googlebot ranges against Google’s published IP lists; separate googlebot.com and google.com hosts (Google) from googleusercontent.com hosts (tenants on Google Cloud); and read full user-agent strings from raw logs, not truncated summaries. The verdict is sitting in the log file.
Terms Demonstrated in This Note
- Source classification
- The category an AI or search system assigns to a domain — what kind of thing it believes the property is — which governs the treatment the property receives.
- Crawler class
- The behavioral and infrastructural category of an agent visiting a site; the mix of classes assigned by a platform encodes its classification verdict.
Related Field Notes
FN-001: Two Crawler Classes: Binge Ingesters and Compounding Re-Crawlers · FN-007: Three Verticals, One Curve: The Ingestion Sequence Replicates