Bot intelligence record

Google-Pinpoint

Usually allow

Use the Google-Pinpoint identifier to separate Google search indexing or content discovery traffic from normal visitor requests in server logs.

Search Official Documented Confidence: High Verified: Yes robots.txt: No
Operator
Google
Family
Google
Type
Search
Source type
Official
Last checked
2026-05-20

User-Agent Pattern

Google
Google-Pinpoint
Verification note

User-agent strings are identification signals, not proof of identity. Confirm important allow, block, or rate-limit decisions with logs, DNS or IP evidence, request behavior, or operator documentation when available.

Robots.txt Snippet

Click snippet to copy
No general robots.txt block is guaranteed; this is a user-triggered fetcher and may require server-side access controls.

Click the snippet to copy it, or highlight the text manually.

Handling Guidance

Depends

This bot is usually safe to allow when the request source is verified and the traffic matches your site policy.

Search indexing, content discovery, rendering, or search-result freshness checks.

Record Details

Structured data
Operator
Google
Family
Google
Type
Search
Purpose
Search
Identity type
Official Documented
Confidence
High
Last verified
2026-04-01
Last checked
2026-05-20
Source type
Official
Verification
Verify as a Google fetcher using reverse DNS and Google's published user-triggered fetcher IP ranges.
Spoofing risk
User-agent strings for Google-Pinpoint can be spoofed. Treat user-agent detection as a classification signal, then verify with published IP ranges, reverse DNS, signatures, operator documentation, or published operator documentation, IP ranges, reverse DNS, signatures, or other verified identity signals before allow-listing.

Notes

Google-Pinpoint is listed in the Botcrawl directory as a search crawler from Google. The primary identifier for log review is Google-Pinpoint.

Identification

  • User-agent pattern: Google-Pinpoint
  • Family: Google
  • Type: Search
  • Kind: Fetcher

Common use

Search indexing, content discovery, rendering, or search-result freshness checks.

Verification and handling

Verify as a Google fetcher using reverse DNS and Google's published user-triggered fetcher IP ranges.

Directory guidance marks the risk level as Safe and the blocking decision as Depends. Do not rely on the user-agent string alone because user-agent strings can be copied or spoofed.

Robots.txt handling: No.

Evidence and Source

  • Verify as a Google fetcher using reverse DNS and Google's published user-triggered fetcher IP ranges.
  • Match `Google-Pinpoint` as a case-insensitive substring in HTTP user-agent logs. Review bot_aliases for alternate names or product labels. Do not treat a user-agent match alone as proof of identity for allow-listing.
  • Search indexing, content discovery, rendering, or search-result freshness checks.
  • User-agent strings for Google-Pinpoint can be spoofed. Treat user-agent detection as a classification signal, then verify with published IP ranges, reverse DNS, signatures, operator documentation, or published operator documentation, IP ranges, reverse DNS, signatures, or other verified identity signals before allow-listing.

Monitor This Bot In Edge

Botcrawl Edge

Use Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.