Safe Official docs Google Bots

Google Messages Preview

Q: Is Google Messages Preview safe?

Yes, Google Messages Preview is a safe and legitimate crawler operated by Google. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.

Q: Will blocking Google Messages Preview hurt my SEO?

🔶 AI Visibility Trade-off - Blocking Google Messages Preview will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.

Q: How do I block Google Messages Preview in robots.txt?

Add the following lines to your /robots.txt file: User-agent: GoogleMessages Disallow: / This instructs Google Messages Preview not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/ ).

Q: How do I verify if Google Messages Preview is crawling my site?

Search your web server access logs for the string GoogleMessages (case-insensitive: grep -i "GoogleMessages" /var/log/nginx/access.log ). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Operated by Google

Scout's quick take

GoogleMessages (Google Messages Preview) does not publish a clear purpose. Check your logs for how often it visits before deciding. Heads up: Google says robots.txt may not apply to it, so use a firewall rule if you need it stopped.

# Block only if you really mean to
User-agent: GoogleMessages
Disallow: /

Check AI bot crawlability Build a full robots.txt

Quick Facts

User-Agent:: GoogleMessages
Category:: Google Bots
Operator:: Google
Safety:: Safe
Blocking Impact:: Low - No SEO ranking impact
SEO Impact Score:: 2/10
Official docs:: developers.google.com

Confirmed by the operator

Google names GoogleMessages on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is Google Messages Preview?

Google Messages Preview is an AI crawler operated by Google. It uses the user-agent string GoogleMessages and follows the Robots Exclusion Protocol.

Google Messages Preview is an AI crawler operated by Google. It uses the user-agent string GoogleMessages and follows the Robots Exclusion Protocol.
Google Messages Preview uses the user-agent token GoogleMessages. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block Google Messages Preview?

🔶 AI Visibility Trade-off - Blocking Google Messages Preview will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.

Generally safe to allow; provides legitimate crawling value.

How to block Google Messages Preview with robots.txt

<code>User-agent: GoogleMessages</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)

User-agent: GoogleMessages
Disallow: /

Allow all (robots.txt)

User-agent: GoogleMessages
Allow: /

Block private only (robots.txt)

User-agent: GoogleMessages
Disallow: /private/
Disallow: /api/
Disallow: /admin/
Allow: /

Nginx server block

# Nginx: Hard-block Google Messages Preview
if ($http_user_agent ~* "GoogleMessages") {
    return 403 "Bot blocked";
}

Apache .htaccess

# Apache: Hard-block Google Messages Preview
SetEnvIfNoCase User-Agent "GoogleMessages" bad_bot
Order Allow,Deny
Allow from all
Deny from env=bad_bot

Meta robots tag

X-Robots-Tag header

X-Robots-Tag: noindex, nofollow

Is Google Messages Preview safe to allow?

Yes, Google Messages Preview is a safe and legitimate crawler operated by Google. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.

Verify by reverse-DNS lookup: legitimate Google Messages Preview requests resolve to Google's domain.

What does Google Messages Preview do?

Understanding Google Messages Preview's purpose helps you decide whether to allow or block it.

Indexes web pages for AI-powered search answers
Surfaces your content as citations inside AI search results
Builds a knowledge index used to answer user questions
Allowing it can increase visibility in AI search
Respects robots.txt directives

Google Messages Preview in context

Google Messages Preview is a utility crawler operated by Google. In plain terms, it fetches a page to build a link preview when someone shares it. Our database files it under Google crawlers and ranks it Tier 5, low-priority crawlers with limited upside for most sites. 1 of the 24 Google crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is not documented. So the decision about Google Messages Preview rests on what you want from Google, not on its behaviour. How we rate safety and impact.

How site owners treat Google Messages Preview

Our robots.txt study of the Tranco top 10,000 did not track GoogleMessages as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

Google Messages Preview's operator says it does not follow robots.txt for these requests, so a robots.txt rule will not stop Google Messages Preview. Use a firewall, CDN or server rule if you need to block it.

Google crawlers and close alternatives

Google Messages Preview is one of 32 Google crawlers in our database. A User-agent: GoogleMessages group controls Google Messages Preview only; the other Google tokens below need their own lines.

GoogleMessages: this crawler (Tier 5)
AdsBot-Google: Google Ads Quality (Desktop), checks pages for an SEO, uptime or analytics service (Tier 3)
AdsBot-Google-Mobile: Google Ads Quality (Mobile), checks pages for an SEO, uptime or analytics service (Tier 3)
APIs-Google: APIs-Google, fetches a page when a person asks an assistant or app to open it (Tier 3)
Chrome-Lighthouse: Lighthouse Audit, checks pages for an SEO, uptime or analytics service (Tier 4)
FeedFetcher-Google: Google Feed Fetcher, builds a search or answer index (Tier 3)
Gemini-Deep-Research: Gemini-Deep-Research, fetches a page when a person asks an assistant or app to open it (Tier 3)
Google-Agent: Google Agent (Project Mariner), fetches a page when a person asks an assistant or app to open it (Tier 2)
Google-CloudVertexBot: Google Vertex AI, fetches a page when a person asks an assistant or app to open it (Tier 3)

To give Google Messages Preview the same answer as its siblings, stack User-agent: GoogleMessages with their lines above one set of rules; to treat Google Messages Preview differently, give it its own group.

No other crawler in our Google crawlers category has exactly the same purpose, which makes Google Messages Preview an unusual case: decide about it on its own merits.

We first recorded GoogleMessages on September 22, 2026. Google documents it on developers.google.com, and we recheck that page before each release.

Which rule Google Messages Preview actually follows

Google Messages Preview reads exactly one group in robots.txt, the most specific one that names GoogleMessages, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: GoogleMessages
Disallow: /drafts/

Find the group. Google Messages Preview looks for a group naming GoogleMessages. One exists, so it ignores User-agent: * completely.
Apply only that group. It is refused /drafts/ and nothing else.
The surprise. /private/ is open to Google Messages Preview, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.

Test yourself: does a rule under User-agent: * apply to Google Messages Preview if the file also has a User-agent: GoogleMessages group?

No. Once a group names it, Google Messages Preview reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking Google Messages Preview remove your pages from AI answers?

Often, yes. Google Messages Preview is a utility crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: googlemessages the same as User-agent: GoogleMessages?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow Google Messages Preview? Decide by situation

Recommended setting for Google Messages Preview by type of site
If you are...	Recommended setting
You publish content and want AI answers to cite it	Low stakes either way. It does not decide whether AI answers cite you.
You license content and want to stop AI training	Blocking it does not stop training, because Google Messages Preview is a utility crawler. Block the operator's training crawler instead.
You run an online shop	Allow it unless it is overloading your servers.
Your server is under load from bots	Rate-limit before blocking. It is rated safe in our database.

Check Google Messages Preview on your own site

Open /robots.txt on your domain and search for GoogleMessages. If it is not named, it follows User-agent: *.
List the Disallow lines in the group Google Messages Preview follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
Look beyond the file. A firewall or bot manager can refuse Google Messages Preview even when robots.txt allows it, and that never shows in the file.
Run our AI crawlability checker to see how Google Messages Preview and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Google Messages Preview

The errors we see most often with Google Messages Preview in the files and firewalls we test:

Treating Google Messages Preview as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
Relying on robots.txt alone when Google Messages Preview is rated caution or aggressive. Back the rule with a server-side block.
Blocking Google Messages Preview by IP alone. Ranges change; match the token and verify with logs.

All three hide inside a file that looks correct, so check Google Messages Preview from outside after every change.

Spotting Google Messages Preview in your logs

robots.txt says what Google Messages Preview may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "GoogleMessages" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "GoogleMessages" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Google Messages Preview user-agent, so confirm the source before acting on a match:

GoogleMessages: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Google Messages Preview request with caution.

Frequently Asked Questions

What is the official user-agent string for Google Messages Preview?

The official user-agent string for Google Messages Preview is: GoogleMessages. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from Google Messages Preview by performing a reverse-DNS lookup on the source IP.

Is Google Messages Preview safe?

Yes, Google Messages Preview is a safe and legitimate crawler operated by Google. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.

Will blocking Google Messages Preview hurt my SEO?

How do I block Google Messages Preview in robots.txt?

Add the following lines to your /robots.txt file:

User-agent: GoogleMessages
Disallow: /

This instructs Google Messages Preview not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).

Does Google Messages Preview respect robots.txt?

Google Messages Preview is operated by Google and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.

How do I verify if Google Messages Preview is crawling my site?

Search your web server access logs for the string GoogleMessages (case-insensitive: grep -i "GoogleMessages" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).