Google Site Verifier
VerifierVerify Google Site Verifier 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 Site Verifier is a Google service that confirms ownership of websites for tools like Google Search Console, Google Workspace, and other property-based products. It performs targeted requests to verify the presence of verification tokens, such as HTML files, meta tags, or DNS records. These checks are one-time or periodic, triggered when a user initiates verification or when Google revalidates ownership. The bot does not crawl or index content and has no impact on Search rankings. It's activity is minimal, focused solely on confirming site ownership credentials. It ignores the global user agent (*) rule. RobotSense.io verifies Google Site Verifier / Google-Site-Verification using Google’s official validation methods, ensuring only genuine Google Site Verifier / Google-Site-Verification traffic is identified.
User Agent Examples
Contains: Mozilla/5.0 (compatible; Google-Site-Verification/1.0)Robots.txt Configuration for Google Site Verifier
No Robots.txt Identifier
Google Site Verifier 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 Site Verifier, and why is it visiting my website?
- Google Site Verifier is a service operated by Google that checks whether a user owns or controls a website for products like Search Console or Workspace. It makes targeted requests to confirm verification tokens such as HTML files, meta tags, or DNS records. Visits are triggered by user-initiated verification actions or periodic revalidation by Google. The traffic is minimal, not part of normal crawling, and is expected only when verification is in progress.
- Is Google Site Verifier a legitimate bot, or is it commonly spoofed?
- Google Site Verifier is an official Google-operated bot, but its user-agent can be spoofed like any other well-known crawler. Attackers may impersonate it to probe for verification files or bypass weak bot filtering rules. Because of this, user-agent strings alone are not reliable for identifying legitimate bot traffic. Proper verification using network-level checks is required. You can use Google's recommended methods mentioned below to verify a legitimate visit, or use RobotSense.io API to easily verify Google Site Verifier visits.
- How can I verify that a request is really coming from Google Site Verifier?
- You can use Google's recommended official methods to verify Google Site Verifier 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 Site Verifier bot and all other bots from Google.
- Should I allow or block Google Site Verifier on my website?
- Allowing Google Site Verifier is necessary if you want to verify site ownership for Google services. It is neutral in terms of SEO and does not crawl or index content. Blocking may be appropriate if: - You are not using any Google verification-based services - The server enforces strict access policies - Verification attempts are unauthorized or unexpected In most cases, allowing it temporarily during verification is sufficient.
- How can I control or block Google Site Verifier using robots.txt or other methods?
- You cannot add a rule in your robots.txt to control Google Site Verifier bot, 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 Site Verifier crawl websites, and can it impact server performance?
- The bot operates on an event-driven basis, not continuous crawling. Requests occur when a user initiates verification or when Google periodically rechecks ownership. As a result: - Request frequency is very low - Bandwidth and request load are negligible - No meaningful impact on dynamic page performance It is unlikely to appear frequently in website logs outside of verification events.
- What happens if I block Google Site Verifier? SEO, visibility, and feature impact explained.
- Blocking Google Site Verifier does not affect search rankings or indexing, but it prevents ownership verification for Google services. Potential impacts include: - Inability to verify your site in Google Search Console - Loss of access to Google Workspace or other property-based tools - Failure of periodic revalidation, which may revoke verified status There is no direct SEO impact, but it may limit access to tools used for SEO analysis.
- Does Google Site Verifier collect, scrape, or use my content for training or reuse?
- Google Site Verifier does not crawl or collect general page content. It only checks for the presence of specific verification tokens such as HTML files, meta tags, or DNS records. It is not used for indexing, SEO datasets, analytics, or AI training. Any data accessed is minimal and limited strictly to confirming ownership credentials.
Other Google Bots
Google operates other crawlers you may also need to configure.
AdsBot
AdsAdsBot-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
AdsMediapartners-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 ToolsAPIs-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 ToolsChrome 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.