Google Publisher Center
Google Publisher Center is a single-page fetcher operated by Google. It fetches one page (or a small set) when triggered by a user action, typically a link being shared on social media, a messaging app, or an RSS reader.
Volume tracks shares and clicks rather than crawl schedules. A trending link can produce a sudden spike, but Google Publisher Center will not crawl the rest of your site.
Blocking it usually means the link previews on the corresponding platform stop showing your title, image, and description.
See Google Publisher Center 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
Per user action
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 CenterYou are here
- 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 Monitoring
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 Publisher Center through?
In most cases, yes. Fetchers power link previews and feed readers. Blocking breaks the user experience on social and messaging platforms. If volume gets noisy, rate-limit it before you block it outright.
Does blocking Google Publisher Center affect my Google rankings?
No. Google Publisher Center 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 Publisher Center?
Two checks. The User-Agent header should match a known Google Publisher Center 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 breaks if I block Google Publisher Center?
Link previews, embeds, and unfurls on whatever surface Google Publisher Center feeds will stop rendering. Users sharing your URLs into Google will see a bare link instead of a rich card. Usually that's the first thing people regret blocking.
How is Google Publisher Center 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 Publisher Center?
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.