Bot intelligence record
GoogleMessages
Usually allowUse the GoogleMessages identifier to separate Google link preview, prefetch, or user-triggered rendering traffic from normal visitor requests in server logs.
- Operator
- Family
- Type
- Preview
- Source type
- Official
- Last checked
- 2026-05-20
User-Agent Pattern
GoogleGoogleMessages
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 copyNo 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
DependsThis bot is usually safe to allow when the request source is verified and the traffic matches your site policy.
Link previews, page rendering, social unfurls, prefetching, or user-triggered content previews.
Record Details
Structured data- Operator
- Family
- Type
- Preview
- Purpose
- Preview
- 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.
- IP ranges
- https://developers.google.com/static/search/apis/ipranges/user-triggered-fetchers-google.json
- Spoofing risk
- User-agent strings for GoogleMessages 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
GoogleMessages is listed in the Botcrawl directory as a preview or prefetch bot from Google. The primary identifier for log review is GoogleMessages.
Identification
- User-agent pattern:
GoogleMessages - Family: Google
- Type: Preview
- Kind: Preview
Common use
Link previews, page rendering, social unfurls, prefetching, or user-triggered content previews.
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 `GoogleMessages` 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.
- Link previews, page rendering, social unfurls, prefetching, or user-triggered content previews.
- User-agent strings for GoogleMessages 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.
https://developers.google.com/crawling/docs/crawlers-fetchers/google-user-triggered-fetchers
Monitor This Bot In Edge
Botcrawl EdgeUse Botcrawl Edge to see matching traffic, create allow or block rules, and control this bot across connected sites.
