D

DuplexWeb-Google

Visit Bot Homepage

Verify DuplexWeb-Google 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.

[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.

This bot does not honor Crawl-Delay rule.

User Agent Examples

Mozilla/5.0 (Linux; Android 11; Pixel 2; DuplexWeb-Google/1.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/86.0.4240.193 Mobile Safari/537.36
Example user agent strings for DuplexWeb-Google

Robots.txt Configuration for DuplexWeb-Google

Robots.txt User-Agent:DuplexWeb-Google

Use this identifier in your robots.txt User-agent directive to target DuplexWeb-Google.

Recommended Configuration

Our recommended robots.txt configuration for DuplexWeb-Google:

# This bot is officially retired by Google
User-agent: Google-Safety
Disallow: /

Completely Block DuplexWeb-Google

Prevent this bot from crawling your entire site:

User-agent: DuplexWeb-Google
Disallow: /

Completely Allow DuplexWeb-Google

Allow this bot to crawl your entire site:

User-agent: DuplexWeb-Google
Allow: /

Block Specific Paths

Block this bot from specific directories or pages:

User-agent: DuplexWeb-Google
Disallow: /private/
Disallow: /admin/
Disallow: /api/

Allow Only Specific Paths

Block everything but allow specific directories:

User-agent: DuplexWeb-Google
Disallow: /
Allow: /public/
Allow: /blog/

Set Crawl Delay

Limit how frequently DuplexWeb-Google can request pages (in seconds):

User-agent: DuplexWeb-Google
Allow: /
Crawl-delay: 10

Note: This bot does not officially mention about honoring Crawl-Delay rule.

Frequently Asked Questions

What is DuplexWeb-Google, and why is it visiting my website?
DuplexWeb-Google is a crawler operated by Google to support Assistant and Duplex-related features. Its primary purpose is to fetch webpage content needed for task-oriented interactions, such as retrieving business details, menus, or booking flows. Visits are typically triggered by user actions or systems preparing data for conversational responses, and crawl behavior is selective rather than broad. For publicly accessible pages that support such use cases, this bot traffic is expected. Visits from DuplexWeb-Google are non-harmful.
Is DuplexWeb-Google a legitimate bot, or is it commonly spoofed?
DuplexWeb-Google is an official Google crawler and is considered legitimate. However, like other Google bots, its user-agent may be spoofed by malicious actors attempting to bypass security controls or disguise automated requests. Attackers may impersonate it because Google-related traffic is often trusted. User-Agent strings alone cannot reliably confirm whether requests are authentic. You can use Google's recommended methods mentioned below to verify a legitimate visit, or use RobotSense.io API to easily verify DuplexWeb-Google visits.
How can I verify that a request is really coming from DuplexWeb-Google?
You can use Google's recommended official methods to verify DuplexWeb-Google 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 DuplexWeb-Google crawler and all other bots from Google.
Should I allow or block DuplexWeb-Google on my website?
Allowing DuplexWeb-Google is generally beneficial if your site provides structured content such as business information, booking systems, or menus that may be used in Assistant-driven interactions. The bot helps ensure accurate data retrieval for these use cases. Blocking may be appropriate if: - Your content is not intended for automated interaction - You restrict machine-driven access to workflows or APIs - You are concerned about exposing structured or transactional data - Your infrastructure has strict resource limitations If you are suddenly seeing too many visits, you can consider adding a small crawl-delay in your robots.txt before completely disallowing.
How can I control or block DuplexWeb-Google using robots.txt or other methods?
You can add a rule in your robots.txt, as given above to control (crawl-delay) or disallow DuplexWeb-Google crawler. Also, you can use further controls in your WAF, or in RobotSense enforcement settings to manage the bot behavior.
How often does DuplexWeb-Google crawl websites, and can it impact server performance?
DuplexWeb-Google uses event-driven crawling tied to user interactions or Assistant-related processes. It targets specific pages needed for tasks rather than performing continuous crawling. Any impact is typically low: - Bandwidth usage: minimal - Request rates: limited and context-driven - Dynamic load: slight if accessing interactive endpoints Most websites will not experience noticeable performance impact. Though some administrators choose to rate-limit or restrict it.
What happens if I block DuplexWeb-Google? SEO, visibility, and feature impact explained.
Blocking DuplexWeb-Google does not affect traditional search engine rankings but may limit Assistant-related functionality. Potential effects include: - Reduced ability for Google Assistant to access or interpret your content - Limited functionality for automated tasks like bookings or information retrieval Blocking DuplexWeb-Google will not have any direct impact on search engine SEO performance.
Does DuplexWeb-Google collect, scrape, or use my content for training or reuse?
DuplexWeb-Google retrieves page content needed to support real-time interactions, such as structured data, text, and workflow-related elements. It is not designed for broad indexing or public dataset creation. Usage typically includes: - Supporting conversational responses - Extracting structured data for task execution - Interpreting page content for Assistant workflows There is no public documentation indicating that this crawler stores full-page content for open datasets or uses it for general AI training purposes.

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.

Feedfetcher

Developer Tools

Feedfetcher is Google’s crawler responsible for retrieving RSS and Atom feeds used in Google News, Google Reader (historically), and other syndication-based services. It fetches feed URLs rather than full webpages. The bot does not index content for Google Search and does not follow links within feeds; its role is purely to collect updates for subscribed users or Google systems that aggregate feed content. Most publishers allow it to ensure timely distribution of updates. Crawl activity is periodic and lightweight, triggered when feed subscribers or internal services request refreshes. It ignores robots.txt rules. RobotSense.io verifies Feedfetcher using Google’s official validation methods, ensuring only genuine Feedfetcher 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.