Safe Official docs Google Bots

Chrome Web Store Fetcher

Q: Is Chrome Web Store Fetcher safe?

Yes, Chrome Web Store Fetcher is a safe and legitimate crawler operated by Google. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.

Q: Will blocking Chrome Web Store Fetcher hurt my SEO?

🔶 AI Visibility Trade-off - Blocking Chrome Web Store Fetcher will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.

Q: How do I block Chrome Web Store Fetcher in robots.txt?

Add the following lines to your /robots.txt file: User-agent: Google-CWS Disallow: / This instructs Chrome Web Store Fetcher not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/ ).

Q: How do I verify if Chrome Web Store Fetcher is crawling my site?

Search your web server access logs for the string Google-CWS (case-insensitive: grep -i "Google-CWS" /var/log/nginx/access.log ). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).

Operated by Google

Scout's quick take

Google-CWS (Chrome Web Store Fetcher) does not publish a clear purpose. Check your logs for how often it visits before deciding. 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: Google-CWS
Disallow: /

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

Quick Facts

User-Agent:: Google-CWS
Category:: Google Bots
Operator:: Google
Safety:: Safe
Blocking Impact:: Low - No SEO ranking impact
SEO Impact Score:: 2/10
Official docs:: developers.google.com

Confirmed by the operator

Google names Google-CWS 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 Chrome Web Store Fetcher?

Chrome Web Store Fetcher is a monitoring and validation agent operated by Google. It checks pages, ad destinations, or policy compliance rather than collecting training data. It has no effect on search rankings.
Chrome Web Store Fetcher uses the user-agent token Google-CWS. You can control it via robots.txt, meta tags (noai), or the emerging llms.txt standard. Robots.txt is voluntary; for hard enforcement, combine it with server-level IP blocking.

What happens if you block Chrome Web Store Fetcher?

🔶 AI Visibility Trade-off - Blocking Chrome Web Store Fetcher will not hurt Google or Bing rankings, but it can remove your content from AI search answers and assistant citations powered by this crawler. Block only if you have a deliberate reason.

Generally safe to allow; provides legitimate crawling value.

How to block Chrome Web Store Fetcher with robots.txt

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

Block completely (robots.txt)

User-agent: Google-CWS
Disallow: /

Allow all (robots.txt)

User-agent: Google-CWS
Allow: /

Block private only (robots.txt)

User-agent: Google-CWS
Disallow: /private/
Disallow: /api/
Disallow: /admin/
Allow: /

Nginx server block

# Nginx: Hard-block Chrome Web Store Fetcher if ($http_user_agent ~* "Google-CWS") { return 403 "Bot blocked"; }

Apache .htaccess

# Apache: Hard-block Chrome Web Store Fetcher
SetEnvIfNoCase User-Agent "Google-CWS" 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 Chrome Web Store Fetcher safe to allow?

Yes, Chrome Web Store Fetcher is a safe and legitimate crawler operated by Google. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.

Verify by reverse-DNS lookup: legitimate Chrome Web Store Fetcher requests resolve to Google's domain.

What does Chrome Web Store Fetcher do?

Understanding Chrome Web Store Fetcher's purpose helps you decide whether to allow or block it.

Validates pages, ads, or policy compliance
Performs automated quality and safety checks
Does not collect training data
No impact on search rankings
Generally safe to allow

Chrome Web Store Fetcher in context

Chrome Web Store Fetcher is a utility crawler operated by Google. In plain terms, it checks pages for an SEO, uptime or analytics service. Our database files it under Google crawlers and ranks it Tier 4, specialist crawlers that matter to particular sites or markets. 1 of the 24 Google crawlers in our database share this tier.

Its safety rating is safe and its blocking impact is not documented. So the decision about Chrome Web Store Fetcher rests on what you want from Google, not on its behaviour. How we rate safety and impact.

How site owners treat Chrome Web Store Fetcher

Our robots.txt study of the Tranco top 10,000 did not track Google-CWS 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?

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

Google crawlers and close alternatives

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

Google-CWS: this crawler (Tier 4)
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 Chrome Web Store Fetcher the same answer as its siblings, stack User-agent: Google-CWS with their lines above one set of rules; to treat Chrome Web Store Fetcher differently, give it its own group.

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

We first recorded Google-CWS on September 22, 2026. Google documents it on developers.google.com, and we recheck that page before each release.

Which rule Chrome Web Store Fetcher actually follows

Chrome Web Store Fetcher reads exactly one group in robots.txt, the most specific one that names Google-CWS, and never combines rules across groups. This short file shows the trap:

User-agent: *
Disallow: /private/

User-agent: Google-CWS
Disallow: /drafts/

Find the group. Chrome Web Store Fetcher looks for a group naming Google-CWS. 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 Chrome Web Store Fetcher, 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 Chrome Web Store Fetcher if the file also has a User-agent: Google-CWS group?

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

Test yourself: will blocking Chrome Web Store Fetcher remove your pages from AI answers?

Often, yes. Chrome Web Store Fetcher is a utility crawler, so pages it cannot fetch can drop out of the answers or results it supports.

Test yourself: is User-agent: google-cws the same as User-agent: Google-CWS?

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

Should you allow Chrome Web Store Fetcher? Decide by situation

Recommended setting for Chrome Web Store Fetcher by type of site
If you are...	Recommended setting
You publish content and want AI answers to cite it	Low stakes either way. It does not decide whether AI answers cite you.
You license content and want to stop AI training	Blocking it does not stop training, because Chrome Web Store Fetcher is a utility crawler. 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 Chrome Web Store Fetcher on your own site

Open /robots.txt on your domain and search for Google-CWS. If it is not named, it follows User-agent: *.
List the Disallow lines in the group Chrome Web Store Fetcher 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 Chrome Web Store Fetcher even when robots.txt allows it, and that never shows in the file.
Run our LLM crawler checker to see how Chrome Web Store Fetcher and every other crawler we track are treated in one pass, including firewall refusals.

Common mistakes with Chrome Web Store Fetcher

The errors we see most often with Chrome Web Store Fetcher in the files and firewalls we test:

Treating Chrome Web Store Fetcher as an AI or search crawler. Blocking it has little effect on visibility; decide based on load and what it does with your data.
Relying on robots.txt alone when Chrome Web Store Fetcher is rated caution or aggressive. Back the rule with a server-side block.
Blocking Chrome Web Store Fetcher by IP alone. Ranges change; match the token and verify with logs.

All three hide inside a file that looks correct, so check Chrome Web Store Fetcher from outside after every change.

Spotting Chrome Web Store Fetcher in your logs

robots.txt says what Chrome Web Store Fetcher 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 "Google-CWS" /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 "Google-CWS" /var/log/nginx/access.log \
  | awk '{print $7}' | sort | uniq -c | sort -rn | head -20

Check the requests are genuine

Anyone can send the Chrome Web Store Fetcher user-agent, so confirm the source before acting on a match:

Google-CWS: we hold no published IP list, so use reverse DNS where the operator documents a hostname and treat an unverifiable Chrome Web Store Fetcher request with caution.

Frequently Asked Questions

What is the official user-agent string for Chrome Web Store Fetcher?

The official user-agent string for Chrome Web Store Fetcher is: Google-CWS. Use this exact string in robots.txt, Nginx, Apache, or Cloudflare firewall rules to target this bot. Matching in robots.txt is case-insensitive. Verify a request genuinely comes from Chrome Web Store Fetcher by performing a reverse-DNS lookup on the source IP.

Is Chrome Web Store Fetcher safe?

Yes, Chrome Web Store Fetcher is a safe and legitimate crawler operated by Google. It follows the Robots Exclusion Protocol (RFC 9309) and can be controlled with standard robots.txt rules.

Will blocking Chrome Web Store Fetcher hurt my SEO?

How do I block Chrome Web Store Fetcher in robots.txt?

Add the following lines to your /robots.txt file:

User-agent: Google-CWS
Disallow: /

This instructs Chrome Web Store Fetcher not to crawl any path on your site. To block only specific sections, replace / with the path (e.g., Disallow: /blog/).

Does Chrome Web Store Fetcher respect robots.txt?

Chrome Web Store Fetcher is operated by Google and is expected to fetch and parse /robots.txt before crawling, following RFC 9309. For hard enforcement, combine robots.txt with server-level IP or user-agent blocking.

How do I verify if Chrome Web Store Fetcher is crawling my site?

Search your web server access logs for the string Google-CWS (case-insensitive: grep -i "Google-CWS" /var/log/nginx/access.log). Filter by user-agent in your log analytics tool (GoAccess, AWStats, etc.).