24 supported bots and services.
Supported bots & services
APIs-Google
Delivers push notifications from Google APIs.
AdsBot-Google
Checks landing-page quality for Google Ads.
AdsBot-Google-Mobile
Checks mobile landing-page quality for Google Ads.
Chrome Private Prefetch Proxy
Chrome privacy proxy for cross-site prefetching.
FeedFetcher-Google
Fetches RSS and Atom feeds requested through Google services.
Google-Agent
Google-Agent performs navigation and actions on user request using Google infrastructure.
Google-CWS
Fetches URLs supplied in Chrome Web Store extension metadata.
Google-CloudVertexBot
Crawls content requested by site owners for Vertex AI agents.
Google-GeminiNotebook
Fetches source URLs supplied by Gemini Notebook users.
Google-InspectionTool
Fetches pages for Search Console inspection and search testing tools.
Google-Pinpoint
Fetches source URLs supplied by Google Pinpoint users.
Google-Read-Aloud
Fetches pages for Google text-to-speech services on user request.
Google-Safety
Fetches pages for abuse and malware investigations.
Google-Site-Verification
Fetches site verification tokens for Google Search Console.
GoogleMessages
Fetches links to create previews in Google Messages.
GoogleOther
Fetches public content for Google product teams and research.
GoogleOther-Image
Fetches public images for Google product teams.
GoogleOther-Video
Fetches public video content for Google product teams.
GoogleProducer
Fetches publisher-supplied feeds for Google News.
Googlebot
Crawls pages for Google Search and related search products.
Googlebot-Image
Fetches images for Google image and search features.
Googlebot-Video
Fetches video content for Google video and search features.
Mediapartners-Google
Crawls participating pages to support relevant advertising.
Storebot-Google
Checks merchant pages for Google Shopping.
Verify Google IP addresses
Confirm whether a connecting IP from your server logs belongs to Google's published ranges.
1. Find the connecting IP
Look up the connecting client IP ($remote_addr) in your server or proxy logs rather than relying on the User-Agent header.
2. Test against published ranges
Check the address in the tool against published network ranges for Google.
3. Read the result
A match confirms the address is in Google's published ranges. No match means the IP is unlisted or someone is spoofing the name.
Notes on published ranges
- Shared pool: the feed does not identify which prefixes this bot uses or authenticate a request.
- Proxy pool for browser prefetches; an IP match does not identify a crawler or user agent.
- An IP match supports the association; it does not authenticate an individual request.
Coverage reflects published network ranges. Some services publish no address lists, and shared ranges can return multiple bots for a single IP.
Sources reviewed .