Safe Official docs Google Bots

GoogleProducer

Q: What is the user-agent string for GoogleProducer?

GoogleProducer uses the token GoogleProducer . Match it case-insensitively in robots.txt and in any server-level rule.

Operated by Google

Scout's quick take

GoogleProducer visits a page only when a person asks Google's assistant to open it. It is not a background crawler. Heads up: Google says robots.txt may not apply to it, so use a firewall rule if you need it stopped.

# Block only if you really mean to
User-agent: GoogleProducer
Disallow: /

Test my robots.txt against AI bots Build a full robots.txt

Quick Facts

User-Agent:: GoogleProducer
Category:: Google Bots
Operator:: Google
Safety:: Safe
Blocking Impact:: Medium - Affects a specific feature, not rankings
SEO Impact Score:: 6/10
Official docs:: developers.google.com

Confirmed by the operator

Google names GoogleProducer on its own documentation page, linked above. The token, purpose and robots.txt behaviour on this profile come from that page, re-checked on October 19, 2026.

What is GoogleProducer?

GoogleProducer fetches article content for Google News publisher tooling, supporting the editorial and syndication side of Google News rather than general search indexing.

GoogleProducer fetches article content for Google News publisher tooling, supporting the editorial and syndication side of Google News rather than general search indexing.
GoogleProducer identifies itself with the user-agent token GoogleProducer. You can control it with a User-agent: GoogleProducer group in robots.txt. Robots.txt is voluntary, so for hard enforcement combine it with server-level blocking.

What happens if you block GoogleProducer?

⚠️ Blocking GoogleProducer does not remove you from Google Search, because it is not the general indexing crawler and it is distinct from Googlebot-News discovery. It affects the Google News publisher tooling that fetches article content for editorial and syndication workflows. If your site is not in Google News, blocking it has no practical effect.

Allow it if your site is published in Google News.

How to control GoogleProducer with robots.txt

<code>User-agent: GoogleProducer</code> - Matching is case-insensitive. Robots.txt is fetched from the root of each subdomain separately.

Block completely (robots.txt)

User-agent: GoogleProducer
Disallow: /

Allow all (robots.txt)

User-agent: GoogleProducer
Allow: /

Block private only (robots.txt)

User-agent: GoogleProducer
Disallow: /private/
Disallow: /api/
Disallow: /admin/
Allow: /

Nginx server block

# Nginx: Block GoogleProducer
if ($http_user_agent ~* "GoogleProducer") {
    return 403 "Bot blocked";
}

Apache .htaccess

# Apache: Block GoogleProducer
SetEnvIfNoCase User-Agent "GoogleProducer" bad_bot
Order Allow,Deny
Allow from all
Deny from env=bad_bot

Meta robots tag

X-Robots-Tag header

X-Robots-Tag: noindex, nofollow

Is GoogleProducer safe to allow?

Yes, GoogleProducer is a safe and legitimate crawler. It is operated by Google and documented publicly, and it identifies itself honestly with the token GoogleProducer. Allow it if your site is published in Google News.

Verify by reverse-DNS: genuine Google fetchers resolve to googlebot.com, google.com or googleusercontent.com. Confirm the forward lookup matches the original IP.

What does GoogleProducer do?

Understanding what GoogleProducer is for helps you decide whether to allow or block it.

Fetches article content for Google News tooling
Supports publisher and editorial workflows
Distinct from Googlebot-News discovery crawling
Relevant to sites in Google News
Respects robots.txt directives

GoogleProducer in context

GoogleProducer is a user-triggered agent operated by Google. In plain terms, it builds a search or answer index. Our database files it under Google crawlers and ranks it Tier 3, mid-priority crawlers with a clear purpose but a smaller audience. 20 of the 24 Google crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is critical. So GoogleProducer is both well behaved and costly to lose: the strongest case for allowing it. How we rate safety and impact.

How site owners treat GoogleProducer

Our robots.txt study of the Tranco top 10,000 did not track GoogleProducer as a named token, so we do not publish an adoption figure for it. If you run a large site, your own logs are the best evidence of how often it visits.

Does it follow robots.txt?

GoogleProducer's operator says it does not follow robots.txt for these requests, so a robots.txt rule will not stop GoogleProducer. Use a firewall, CDN or server rule if you need to block it.

Google crawlers and close alternatives

GoogleProducer is one of 32 Google crawlers in our database. A User-agent: GoogleProducer group controls GoogleProducer only; the other Google tokens below need their own lines.

GoogleProducer: this crawler (Tier 3)
AdsBot-Google: Google Ads Quality (Desktop), checks pages for an SEO, uptime or analytics service (Tier 3)
AdsBot-Google-Mobile: Google Ads Quality (Mobile), checks pages for an SEO, uptime or analytics service (Tier 3)
APIs-Google: APIs-Google, fetches a page when a person asks an assistant or app to open it (Tier 3)
Chrome-Lighthouse: Lighthouse Audit, checks pages for an SEO, uptime or analytics service (Tier 4)
FeedFetcher-Google: Google Feed Fetcher, builds a search or answer index (Tier 3)
Gemini-Deep-Research: Gemini-Deep-Research, fetches a page when a person asks an assistant or app to open it (Tier 3)
Google-Agent: Google Agent (Project Mariner), fetches a page when a person asks an assistant or app to open it (Tier 2)
Google-CloudVertexBot: Google Vertex AI, fetches a page when a person asks an assistant or app to open it (Tier 3)

To give GoogleProducer the same answer as its siblings, stack User-agent: GoogleProducer with their lines above one set of rules; to treat GoogleProducer differently, give it its own group.

No other crawler in our Google crawlers category has exactly the same purpose, which makes GoogleProducer an unusual case: decide about it on its own merits.

We first recorded GoogleProducer on May 31, 2026. Google documents it on developers.google.com, and we recheck that page before each release.

Which rule GoogleProducer actually follows

GoogleProducer reads exactly one group in robots.txt, the most specific one that names GoogleProducer, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: GoogleProducer
Disallow: /drafts/

Find the group. GoogleProducer looks for a group naming GoogleProducer. One exists, so it ignores User-agent: * completely.
Apply only that group. It is refused /drafts/ and nothing else.
The surprise. /private/ is open to GoogleProducer, because that rule lives in the * group it no longer reads. To keep it out of both, repeat Disallow: /private/ inside its own group.

Test yourself: does a rule under User-agent: * apply to GoogleProducer if the file also has a User-agent: GoogleProducer group?

No. Once a group names it, GoogleProducer reads only that group. Put every rule you want it to follow inside its own group.

Test yourself: will blocking GoogleProducer remove your pages from AI answers?

Often, yes. GoogleProducer is a user-triggered agent, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: googleproducer the same as User-agent: GoogleProducer?

Yes. RFC 9309 makes user-agent matching case-insensitive. Paths are a different story: Disallow: /Blog/ does not block /blog/.

Should you allow GoogleProducer? Decide by situation

Recommended setting for GoogleProducer by type of site
If you are...	Recommended setting
You publish content and want AI answers to cite it	Allow it. GoogleProducer fetches pages for answers, so blocking it can remove you from them.
You license content and want to stop AI training	Blocking it does not stop training, because GoogleProducer is a user-triggered agent. Block the operator's training crawler instead.
You run an online shop	Allow it unless it is overloading your servers.
Your server is under load from bots	Rate-limit before blocking. It is rated safe in our database.

Check GoogleProducer on your own site

Open /robots.txt on your domain and search for GoogleProducer. If it is not named, it follows User-agent: *.
List the Disallow lines in the group GoogleProducer follows and test your key URLs against them; the longest match wins, and Allow wins a tie.
Look beyond the file. A firewall or bot manager can refuse GoogleProducer even when robots.txt allows it, and that never shows in the file.
Run our blocked AI crawler check to see how GoogleProducer and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with GoogleProducer

The errors we see most often with GoogleProducer in the files and firewalls we test:

Assuming a robots.txt rule will stop GoogleProducer. User-triggered fetches act for a person, and some operators say robots.txt may not apply to them. Check the operator's statement above.
Blocking GoogleProducer as if it were a bulk crawler. It fetches one page because a person asked; blocking it means that person's assistant cannot read your page.
Counting GoogleProducer visits as crawl volume. Each request maps to a real user question, which makes the paths it requests a useful signal of what people ask about you.

All three hide inside a file that looks correct, so check GoogleProducer from outside after every change.

Spotting GoogleProducer in your logs

robots.txt says what GoogleProducer may do; your access logs show what it actually did.

Count requests

On a server with standard Nginx or Apache logs, this counts matching requests per day (adjust the log path for your host):

grep -iE "GoogleProducer" /var/log/nginx/access.log \
  | awk '{print $4}' | cut -d: -f1 | sort | uniq -c

And this shows which paths it requested most, which is the quickest way to see whether your Disallow lines are being respected:

grep -iE "GoogleProducer" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the GoogleProducer user-agent, so confirm the source before acting on a match:

GoogleProducer: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable GoogleProducer request with caution.

Frequently Asked Questions

What is the user-agent string for GoogleProducer?

GoogleProducer uses the token GoogleProducer. Match it case-insensitively in robots.txt and in any server-level rule.

Is GoogleProducer safe?

Yes. GoogleProducer is operated by Google and is documented publicly. GoogleProducer fetches article content for Google News publisher tooling, supporting the editorial and syndication side of Google News rather than general search indexing.

Will blocking GoogleProducer hurt my SEO?

Blocking GoogleProducer does not remove you from Google Search, because it is not the general indexing crawler and it is distinct from Googlebot-News discovery. It affects the Google News publisher tooling that fetches article content for editorial and syndication workflows. If your site is not in Google News, blocking it has no practical effect.

How do I block GoogleProducer in robots.txt?

Add these lines to /robots.txt:

User-agent: GoogleProducer
Disallow: /

To restrict only part of your site, disallow specific paths and allow the rest.