What is Google Messages fetcher, and why is it visiting my website?

Google Messages fetcher is a bot operated by Google that retrieves webpage metadata to generate rich link previews inside the Google Messages app. It is triggered only when a user shares a URL in a conversation, making the traffic strictly user-initiated rather than part of continuous crawling. The bot typically requests a single page and extracts elements like title, description, and preview images. For public websites, this traffic is expected and usually low in volume. Visits from Google Messages bot are non-harmful..

Is Google Messages fetcher a legitimate bot, or is it commonly spoofed?

Google Messages fetcher is an official bot operated by Google and is considered legitimate. However, like many well-known bots, its user-agent can be spoofed by malicious actors attempting to bypass filters or disguise automated traffic. Attackers may impersonate it to gain trust or avoid rate limits. Because of this, relying only on the user-agent string is not sufficient to confirm authenticity. You can use Google's recommended methods mentioned below to verify a legitimate visit, or use RobotSense.io API to easily verify Google Messages fetcher visits.

How can I verify that a request is really coming from Google Messages fetcher?

You can use Google's recommended official methods to verify Google Messages bot visits, these include: - IP range checks - Reverse DNS → forward DNS Do not use User-Agent based detection as that can be easily spoofed. Alternatively, you can use RobotSense.io API to easily verify Google Messages bot and all other bots from Google.

Should I allow or block Google Messages fetcher on my website?

Allowing the bot is generally beneficial if you want your content to display correctly when shared via Google Messages. It improves how links appear to users by enabling rich previews. Blocking may make sense if: - Your server resources are highly constrained - The content is private, sensitive, or behind authentication - You do not want preview generation for specific endpoints For most public websites, allowing it is safe and low impact. But, if you are suddenly seeing too many visits, you can consider throttling (crawl-delay) before completely disallowing.

How can I control or block Google Messages fetcher using robots.txt or other methods?

You cannot add a rule in your robots.txt to control Google Messages fetcher, as this crawler has no specific robots.txt user-agent. However, you can use controls in your WAF, or in RobotSense enforcement settings to manage the bot behavior.

How often does Google Messages fetcher crawl websites, and can it impact server performance?

This bot does not perform continuous crawling; it operates on a strictly event-driven basis when users share links. Each event typically results in a small number of requests to fetch preview metadata. The impact on bandwidth and server load is usually minimal, even for moderately trafficked sites. However, high volumes of shared links to the same resource could create short bursts of requests. Most websites will not notice any performance impact.

What happens if I block Google Messages fetcher? SEO, visibility, and feature impact explained.

Blocking the bot does not affect search engine rankings or indexing, as it is not part of Google Search. However, it can impact user experience in messaging contexts: - Link previews in Google Messages may not render correctly - Shared URLs may appear as plain text without images or descriptions The impact is limited to messaging preview functionality only.

Does Google Messages fetcher collect, scrape, or use my content for training or reuse?

The bot retrieves limited page content specifically to generate link previews, such as titles, meta descriptions, and Open Graph tags. It does not perform full-site scraping or indexing and is not used for search ranking purposes. There is no public documentation indicating that this bot is used for AI model training. Its activity is narrowly scoped to preview generation, and typically only metadata or small content snippets are processed.

Google Messages

Name: Google Messages
Author: Google

Others

Operated by GoogleOthers

Visit Bot Homepage

Verify Google Messages IP Address

Verify if an IP address truly belongs to Google, using official verification methods. Enter both IP address and User-Agent from your logs for the most accurate bot verification.

Google Messages uses a fetcher to retrieve webpage data for generating link previews when users send URLs in chat conversations. It fetches metadata such as titles, descriptions, images, and structured tags (e.g., Open Graph) to render rich previews inside messages. This traffic is strictly user-triggered, occurring only when a link is shared. It is not a crawler for indexing or discovery and has no impact on Google Search rankings. Blocking it may prevent previews from displaying correctly. Activity is lightweight and targeted, focused solely on enhancing the messaging experience with accurate link previews. Google Messages bot does not respect robots.txt rules. RobotSense.io verifies Google Messages using Google’s official validation methods, ensuring only genuine Google Messages traffic is identified.

This bot does not honor Crawl-Delay rule.

User Agent Examples

Contains: GoogleMessages

Robots.txt Configuration for Google Messages

No Robots.txt Identifier

Google Messages does not have a unique robots.txt User-Agent identifier, which means this bot cannot be specifically targeted in your robots.txt file.

Looking to detect or manage this bot? RobotSense.io provides real-time bot detection and management beyond robots.txt, helping you identify and control bots that cannot be blocked through traditional means.

Frequently Asked Questions

What is Google Messages fetcher, and why is it visiting my website?: Google Messages fetcher is a bot operated by Google that retrieves webpage metadata to generate rich link previews inside the Google Messages app. It is triggered only when a user shares a URL in a conversation, making the traffic strictly user-initiated rather than part of continuous crawling. The bot typically requests a single page and extracts elements like title, description, and preview images. For public websites, this traffic is expected and usually low in volume. Visits from Google Messages bot are non-harmful..
Is Google Messages fetcher a legitimate bot, or is it commonly spoofed?: Google Messages fetcher is an official bot operated by Google and is considered legitimate. However, like many well-known bots, its user-agent can be spoofed by malicious actors attempting to bypass filters or disguise automated traffic. Attackers may impersonate it to gain trust or avoid rate limits. Because of this, relying only on the user-agent string is not sufficient to confirm authenticity. You can use Google's recommended methods mentioned below to verify a legitimate visit, or use RobotSense.io API to easily verify Google Messages fetcher visits.
How can I verify that a request is really coming from Google Messages fetcher?: You can use Google's recommended official methods to verify Google Messages bot visits, these include: - IP range checks - Reverse DNS → forward DNS Do not use User-Agent based detection as that can be easily spoofed. Alternatively, you can use RobotSense.io API to easily verify Google Messages bot and all other bots from Google.
Should I allow or block Google Messages fetcher on my website?: Allowing the bot is generally beneficial if you want your content to display correctly when shared via Google Messages. It improves how links appear to users by enabling rich previews. Blocking may make sense if: - Your server resources are highly constrained - The content is private, sensitive, or behind authentication - You do not want preview generation for specific endpoints For most public websites, allowing it is safe and low impact. But, if you are suddenly seeing too many visits, you can consider throttling (crawl-delay) before completely disallowing.
How can I control or block Google Messages fetcher using robots.txt or other methods?: You cannot add a rule in your robots.txt to control Google Messages fetcher, as this crawler has no specific robots.txt user-agent. However, you can use controls in your WAF, or in RobotSense enforcement settings to manage the bot behavior.
How often does Google Messages fetcher crawl websites, and can it impact server performance?: This bot does not perform continuous crawling; it operates on a strictly event-driven basis when users share links. Each event typically results in a small number of requests to fetch preview metadata. The impact on bandwidth and server load is usually minimal, even for moderately trafficked sites. However, high volumes of shared links to the same resource could create short bursts of requests. Most websites will not notice any performance impact.
What happens if I block Google Messages fetcher? SEO, visibility, and feature impact explained.: Blocking the bot does not affect search engine rankings or indexing, as it is not part of Google Search. However, it can impact user experience in messaging contexts: - Link previews in Google Messages may not render correctly - Shared URLs may appear as plain text without images or descriptions The impact is limited to messaging preview functionality only.
Does Google Messages fetcher collect, scrape, or use my content for training or reuse?: The bot retrieves limited page content specifically to generate link previews, such as titles, meta descriptions, and Open Graph tags. It does not perform full-site scraping or indexing and is not used for search ranking purposes. There is no public documentation indicating that this bot is used for AI model training. Its activity is narrowly scoped to preview generation, and typically only metadata or small content snippets are processed.

Other Google Bots

Google operates other crawlers you may also need to configure.

View all 29 Google bots →

AdsBot

Ads

AdsBot-Google is Google’s crawler responsible for evaluating landing pages used in Google Ads campaigns. It performs desktop-focused checks on page quality, load speed, relevance, and policy compliance. These assessments directly influence ad quality scores, cost efficiency, and overall eligibility. Blocking AdsBot prevents Google from reviewing landing pages, which can degrade or disable ad performance. Crawl activity is selective and tied to active or recently modified ad campaigns rather than broad indexing. Its purpose is to ensure that advertisers maintain fast, trustworthy, and policy-compliant landing pages. It ignores the global user agent (*) rule. RobotSense.io verifies AdsBot/AdsBot-Google using Google’s official validation methods, ensuring only genuine AdsBot/AdsBot-Google traffic is identified.

AdsBot Mobile Web

Ads

[This crawler is officially retired as per Google] AdsBot-Google-Mobile bot is Google’s mobile-focused crawler used to evaluate the landing page experience for Google Ads. It simulates mobile device conditions to assess page quality, load performance, mobile usability, and policy compliance. These evaluations directly influence Google Ads quality scores and ad eligibility. If you run ads, blocking it may negatively affect ad performance because Google cannot verify the mobile landing page experience. Crawl activity is targeted and low-volume, triggered when ads are created, updated, or actively running. Its purpose is ensuring advertisers provide fast, compliant, and user-friendly mobile pages. It ignores the global user agent (*) rule. RobotSense.io verifies AdsBot Mobile Web/AdsBot-Google-Mobile using Google’s official validation methods, ensuring only genuine AdsBot Mobile Web/AdsBot-Google-Mobile traffic is identified.

AdSense / Mediapartners-Google

Ads

Mediapartners-Google is Google’s crawler dedicated to evaluating webpages for Google AdSense. It scans pages to understand content, layout, and context so Google can deliver relevant ads and optimize revenue for publishers. Unlike Googlebot, this crawler does not index content for Search - its role is purely advertising-related. Blocking it may prevent AdSense from analyzing pages and serving targeted ads effectively. Crawl activity is generally light and focused on pages where AdSense code is present, helping Google match ad inventory with page themes and user interests. It ignores the global user agent (*) rule. RobotSense.io verifies AdSense / Mediapartners-Google using Google’s official validation methods, ensuring only genuine AdSense / Mediapartners-Google traffic is identified.

APIs-Google

Developer Tools

APIs-Google is a service crawler used by Google to verify and interact with endpoints tied to various Google APIs. It is typically triggered when applications, scripts, or integrations using Google services need to fetch or validate external resources. Common use cases include OAuth flows, link previews, data validation, push notification messages, and API-driven checks performed on behalf of Google products. Crawl activity is usually low-volume and event-driven, reflecting specific API operations rather than broad crawling or indexing associated with Google Search. It ignores the global user agent (*) rule. RobotSense.io verifies APIs-Google using Google’s official validation methods, ensuring only genuine APIs-Google traffic is identified.

Chrome Web Store / Google-CWS

Developer Tools

Chrome Web Store fetcher or Google-CWS is a Google user-agent associated with Chrome Web Services, typically used for link preview generation, safe browsing checks, and content fetching triggered by Chrome features. It performs lightweight requests to retrieve metadata, page titles, favicons, and safety signals from URLs that developers provide in the metadata of their Chrome extensions and themes. This bot is not a search crawler and does not influence Google Search indexing or rankings. Activity occurs when Chrome or Google services need to quickly inspect a URL for previews, safety evaluation, or rendering behavior. It ignores robots.txt rules. RobotSense.io verifies Chrome Web Store fetcher using Google’s official validation methods, ensuring only genuine Chrome Web Store fetcher traffic is identified.

DuplexWeb-Google

Others

[This crawler is officially retired as per Google] DuplexWeb-Google is a Google crawler associated with Duplex and Assistant-related technologies that fetch web content to help generate conversational responses and perform task-oriented actions. It retrieves page information needed to understand structured data, business details, menus, appointment flows, and other interactive elements. Crawl activity is selective and generally tied to user-initiated tasks or systems that prepare content for automated assistance. Its purpose is to support natural-language interactions by ensuring Google’s assistant technologies can interpret and use real-time webpage information accurately. It ignores the global user agent (*) rule. RobotSense.io verifies DuplexWeb-Google using Google’s official validation methods, ensuring only genuine DuplexWeb-Google traffic is identified.

Similar Bots

Other Others bots from different operators.

Amazonbot

Others

by Amazon

[Amazon Bots can take upto 30 days to read your Robots.txt updates.] Amazonbot is Amazon’s official web crawler, used to discover and fetch webpage content for applications such as Alexa, product-related features, and Amazon’s AI and search systems. Crawl activity varies based on Amazon services that rely on external web content, but it is generally moderate and focused on structured data, text content, and page metadata. Its purpose is to enhance Amazon’s search, AI models, and user-facing features. It ignores the global user agent (*) rule. RobotSense.io verifies Amazonbot using Amazon’s official validation methods, ensuring only genuine Amazonbot traffic is identified.

Amzn-User

Others

by Amazon

[Amazon Bots can take upto 30 days to read your Robots.txt updates.] Amzn-User is a bot associated with Amazon services that fetch webpage content on behalf of end users or Amazon applications rather than acting as a general-purpose crawler. It typically appears when Amazon apps, devices, or internal systems request metadata, previews, or content needed for features like link expansion, in-app browsing, or contextual analysis. The traffic is user-driven, not designed for large-scale indexing or scraping. Amzn-User usually performs lightweight, targeted fetches limited to specific URLs users interact with. Its purpose is to support Amazon product experiences by retrieving just enough page data to power user-facing functionality. It ignores the global user agent (*) rule. RobotSense.io verifies Amzn-User using Amazon’s official validation methods, ensuring only genuine Amzn-User traffic is identified.

BingPreview

Others

by Microsoft

BingPreview is Microsoft’s rendering and compatibility crawler used to evaluate how webpages appear in browsers and Bing search features. It fetches pages to test layout, mobile responsiveness, JavaScript rendering, and visual elements. These checks help Bing understand how content will display in search results and improve snippet generation and ranking signals tied to user experience. Crawl activity is moderate and often concentrated on pages important to Bing’s index. Its purpose is to simulate real-browser behavior and refine Bing’s presentation quality. RobotSense.io verifies BingPreview using Microsoft’s official validation methods, ensuring only genuine BingPreview traffic is identified.

FacebookExternalHit

Others

by Meta / Facebook

FacebookExternalHit is Facebook’s (Meta’s) crawler used to fetch webpage content for link previews across Facebook, Messenger, Instagram, and other Meta surfaces. It retrieves metadata such as Open Graph tags, titles, descriptions, images, and structured data. These requests are user-triggered, occurring when someone shares or pastes a URL on a Meta platform. The bot does not index or rank websites and has no connection to search algorithms. Blocking it may prevent accurate link previews. Crawl activity is lightweight and focused on fetching just enough content to generate rich social previews. It ignores the global user agent (*) rule. RobotSense.io verifies FacebookExternalHit using Meta’s official validation methods, ensuring only genuine FacebookExternalHit traffic is identified.

iTMS (iTunes Crawler)

Others

by Apple

iTMS (iTunes Crawler) is Apple’s crawler used to fetch and validate webpages associated with content distributed through Apple services such as the iTunes Store, Apple Podcasts, and related media platforms. It retrieves metadata, feeds, and linked resources required for listing, previewing, or validating content. This crawler does not perform general web indexing and does not influence search rankings outside Apple’s ecosystem. Crawl activity is typically targeted and low-volume, triggered when content is submitted, updated, or refreshed within Apple’s media services. As per official documentation, iTMS does not respects robots.txt rules. RobotSense.io verifies iTMS using Apple's official validation methods, ensuring only genuine iTMS traffic is identified.

Meta-ExternalFetcher

Others

by Meta / Facebook

Meta-ExternalFetcher is a Meta crawler that retrieves webpage content to support link previews, metadata extraction, and other external content processing tasks across Facebook, Instagram, and related Meta products. It fetches titles, descriptions, images, and structured data required for rendering shared links or enriching user interactions. These requests are typically user-driven but may also support automated metadata refreshes. Crawl volume is lightweight and focused, targeting only the URLs needed for previews or content enrichment within Meta’s ecosystem. It ignores the global user agent (*) rule. RobotSense.io verifies Meta-ExternalFetcher using Meta’s official validation methods, ensuring only genuine Meta-ExternalFetcher traffic is identified.