Google Stackdriver Monitoring
Google Stackdriver Monitoring is a developer or operator tool operated by Google. It runs on behalf of a site owner for monitoring, uptime checks, performance audits, or internal QA.
If you run the site, you are probably the customer of whoever is running this agent. Blocking it would hide your own monitoring data from yourself.
If you are an end-user surprised to see this in your logs, it is almost always something a third-party SaaS is doing on behalf of someone who manages your site.
See Google Stackdriver Monitoring on your own site
Match the User-Agent header on incoming requests against the pattern below.
regex
Verify by IP
For higher confidence, also verify the source IP against the operator's published ranges. UA strings can be spoofed; IP ownership is harder to fake.
Renders JavaScript
No
IP verification
Published IP ranges
Crawl frequency
Scheduled probes
Honors robots.txt
Yes
Honors Crawl-delay
Varies
Google runs 103 bots in total. Each one is a separate user-agent so you can allow or block them independently.
Link Unfurler
25- Google Feed Fetcher
- Google Image Proxy
- Google Publisher Center
- Google Web Preview
- Google-AdWords-Express
- Google-PageRenderer
- Google-Read-Aloud
- GoogleDocs
- GoogleImageProxy
- GoogleProducer
- Gmail Image Proxy
- Google Calendar Importer
- Google Page Renderer
- Google Web Snippet
- Google API
- Google Cloud Scheduler
- Google-Document-Conversion
- Google Sheets
- Google Slides
- Google Docs
- Google Area 120 Privacy Policy Fetcher
- Chrome Privacy Preserving Prefetch Proxy
- Google Cloud Function
- GoogleApps-DocumentScanner
- GoogleStackdriverMonitoring
Search Engine
14DevOps & Monitoring
13- Chrome-Lighthouse
- Google Inspection Tool
- Google Schema Markup Testing Tool
- Google Trust Services (DCV Check)
- Google-Structured-Data-Testing-Tool
- GoogleAssociationService
- ProjectShield Url Check
- Google Read Aloud
- Google Search Console
- Google Page Speed Insights
- Google Partner Monitoring
- Google Structured Data Testing Tool
- Google Stackdriver MonitoringYou are here
Ads Network Bot
11Training Crawler
9Agentic Browser
8Security Scanner
7SEO Crawler
4Brand Intelligence
3Shopping Bot
3Live-Fetch AI
2Ad Verification
2AI Coding Tool
1Agentic Commerce
1Should I let Google Stackdriver Monitoring through?
In most cases, yes. Almost always run by you or your vendor. Blocking hides your own monitoring data. If volume gets noisy, rate-limit it before you block it outright.
Does blocking Google Stackdriver Monitoring affect my Google rankings?
No. Google Stackdriver Monitoring is not a search-engine crawler. Your ranking on Google or Bing is unaffected by what you do here.
How do I confirm a request is really from Google Stackdriver Monitoring?
Two checks. The User-Agent header should match a known Google Stackdriver Monitoring string, and the request's source IP should fall inside Google's published ranges. The User-Agent alone is trivially spoofable, so the IP check is what gives you confidence. Google publishes the ranges so you can validate at the CDN or edge.
What's the best way to understand what Google Stackdriver Monitoring is doing on my site?
Look at which URLs it hits, how often, and what time of day. The request pattern usually tells you whether it's building an index, watching for a specific change, or trying to pull data in bulk. The User-Agent name alone rarely tells the full story.
How is Google Stackdriver Monitoring different from Google's other bots?
Google splits work across multiple user-agents so site owners can decide on each one independently. Training crawlers, live-fetch agents, search indexers, and agentic browsers each get their own name. Worth scanning the rest of the Google family above to see which ones actually matter for your site.
What's the cleanest way to control Google Stackdriver Monitoring?
Two layers. Robots.txt for the polite crawlers that read it, and rules at your CDN or edge for the ones that don't. Rankly's Agent Experience handles both from a single config, so you can allow, block, rate-limit, or serve a stripped-down version per bot. Agent Analytics handles the observation half so you know which bots are actually worth a rule.
Verify everything above against the operator's own documentation.