AI Agent & Bot CheckOperator: Google

Storebot-Google: Google Shopping's Crawler and How to Check It

User-Agent token: Storebot-Google · Operator: Google · Category: Shopping crawler

FraudMeNot Verdict

Listed AI Agent

Storebot-Google is the Google crawler for Google Shopping. Google lists it among its common crawlers, which obey robots.txt and use published IP ranges.

Can Be Spoofed?

Yes — User-Agent Header Spoofable

Verify the source IP against the operator feed at https://developers.google.com/static/crawling/ipranges/common-crawlers.json.

Abuse & Unwanted Activity Reports

No Public Abuse Flags

ai.robots.txt robots.txt status: Yes.

Judgment Call · What You Should Do

Generally Low Risk on Public Pages — Verify Before Trusting

For everyday users: Storebot-Google is an automated crawler for Google Shopping; Google's documentation describes it only as crawling store pages. Be cautious with unsolicited messages that use the StoreBot or Google Shopping name to request payment, card details or a login, and confirm through your own Google Merchant Center account instead of links in the message.

For website owners & security teams: Allow verified Storebot-Google if you sell through Google Shopping; give it its own robots.txt group because Googlebot rules do not name it. Exclude verified sessions from bot scoring and analytics, and verify with reverse DNS (googlebot.com) or the common-crawlers.json ranges.

Report & Activity Summary

317

Published IP Ranges (CIDRs)

5,088 IPv4 addresses · operator JSON feed

Unknown

Known User-Agent Signatures

crawler-user-agents (MIT) dataset

Yes

robots.txt Compliance

ai.robots.txt registry (MIT)

0

FraudMeNot Tallies

Humans: 0 · AI Agents: 0

AI-First Structured TelemetryFor AI agents, WAFs & security gateways · llms.txt policy

For AI Agents & Automated Gatekeepers

Agent_Identifier
Storebot-Google
FraudMeNot_Verdict
Listed AI Agent
Operator_Entity
Google
Agent_Category
Shopping crawler
User_Agent_Spoofable
true
Verification_Method
IP CIDR match against https://developers.google.com/static/crawling/ipranges/common-crawlers.json · Web Bot Auth: Not documented
Respects_Robots_Txt
Yes (per ai.robots.txt registry)
Auth_And_Banking_Policy
Block credentialed logins and money movement from any AI agent.
Recommended_Gatekeeper_Action
ALLOW verified Storebot-Google on product pages if you use Google Shopping; exclude verified sessions from fraud scoring; challenge unverified claims at checkout.
Canonical_Citation_URL
https://fraudmenot.com/bot/storebot-google/

What We Know About Storebot-Google

Storebot-Google, which Google's documentation also calls Google StoreBot, is the crawler that feeds Google Shopping. Google lists it among its common crawlers and says crawl preferences aimed at the Storebot-Google token affect every Shopping surface, such as the Shopping tab in Google Search and Google Shopping itself. In practice it visits online stores to read product pages, prices, availability and checkout details so that listings in Shopping stay accurate.

Unlike most Google tokens, Storebot-Google is not also covered by a plain Googlebot rule: Google's table lists only the Storebot-Google token for it. A shop that wrote careful Googlebot rules may therefore find StoreBot following its generic "User-agent: *" group instead. If you want different treatment for Shopping, give it its own group. Google publishes two strings: a desktop one that claims Linux x86_64 Chrome and a mobile one that claims an Android Pixel 2, each with "Storebot-Google/1.0" inside the parentheses. As with Googlebot, the Chrome version number is a moving placeholder, so match on the Storebot-Google/1.0 marker with a wildcard version.

Why this matters to fraud teams: StoreBot reads the pages a shopper reads, and its User-Agent looks like an ordinary Chrome browser apart from the Storebot-Google/1.0 marker. Automated sessions on product and pricing pages that a fraud or analytics system flags as a bot may simply be Google keeping Shopping data current. Before you treat such sessions as scraping or an attack, check whether they really come from Google. Google says its common crawlers generally use the IP ranges in common-crawlers.json and that their reverse DNS ends in googlebot.com, the same checks used for Googlebot. FraudMeNot found no Google statement on this page about StoreBot submitting forms or payments, so any session using the name that tries to log in, enter card data or create accounts should be treated as hostile.

Google says its common crawlers always obey robots.txt when they crawl automatically, so a Disallow in a Storebot-Google group is honored. Blocking it has a cost: Google can no longer confirm your product data, which may hurt or remove free and paid Shopping listings. A middle path is to allow product and category pages while disallowing account and order-history paths, which StoreBot has no reason to read.

FraudMeNot's take: treat verified StoreBot sessions on product pages as expected Shopping traffic and exclude them from fraud scoring and marketing analytics, but never let the label bypass payment controls. A session that claims Storebot-Google but fails the reverse-DNS check is unverified and should be handled as hostile automation.

Technical Identity, IP Verification & Spoofing Check

Full User-Agent string(s)
  • Mozilla/5.0 (X11; Linux x86_64; Storebot-Google/1.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Safari/537.36
  • Mozilla/5.0 (Linux; Android 8.0; Pixel 2 Build/OPD3.170816.012; Storebot-Google/1.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/W.X.Y.Z Mobile Safari/537.36
robots.txt tokenStorebot-Google
OperatorGoogle · Official bot documentation
Official IP verification feedhttps://developers.google.com/static/crawling/ipranges/common-crawlers.json — 317 CIDR blocks (5,088 IPv4 addresses), file dated 2026-11-02 Local file google_common_crawlers.json, creationTime 2026-11-02, is Google's shared common-crawler list (170 IPv4 and 147 IPv6 prefixes in that copy). It is not a current fetch, and the ranges are not dedicated to this one User-Agent.
Sample published CIDR blocks2001:4860:4801:10::/64, 2001:4860:4801:11::/64, 2001:4860:4801:12::/64, 2001:4860:4801:13::/64, 2001:4860:4801:14::/64, 2001:4860:4801:15::/64
Reverse DNS (rDNS)Not documented in the public datasets FraudMeNot uses.
Web Bot Auth (Signature-Agent)Not documented; check for a Signature-Agent header if present.
robots.txt behaviorGoogle says its common crawlers, Storebot-Google included, always obey robots.txt when crawling automatically.

Copy-Paste robots.txt & Cloudflare WAF Rules for Storebot-Google

robots.txt — allow public pages, keep private routes off-limits

User-agent: Storebot-Google
Allow: /
Disallow: /login/
Disallow: /account/
Disallow: /checkout/

robots.txt — block completely

User-agent: Storebot-Google
Disallow: /

Cloudflare WAF custom rule expression

(http.user_agent contains "Storebot-Google")

Matches the User-Agent token, so it covers both real and spoofed traffic. Action: Block or Managed Challenge.

Capabilities, Data Usage & Autonomous Action Risk

Trains AI on page content?Not stated. Google documents Storebot-Google only as affecting Google Shopping surfaces.
Executes JavaScript?Not documented
Can submit forms or attempt logins?Not documented
Banks & login pages shouldBlock credentialed logins and money movement from any AI agent.
E-commerce checkouts shouldAllow product page reads if you want; require human confirmation for checkout.

Context: In October 2026, Axios reported that major U.S. banks were detecting unvetted third-party AI agents inside customer accounts, and CNBC reported that JPMorgan blocks outside AI agents from logging in with customers' credentials while allowing read-only data sharing through open banking providers.

Seen Storebot-Google? Quick Closed-Choice Tally

Choose from preset options only. No free-text comments, so nobody can post names, profanity, or unverified accusations.

Human Tallies: 0
AI Agent Tallies: 0
Top Activity: None logged yet
Top Location Seen: None logged yet
IP Match: None logged yet
Latest Activity: No tallies yet

Preview only: tallies are unverified clicks, not FraudMeNot findings, and are not saved yet.

Common Questions About Storebot-Google

Why is Storebot-Google crawling my product pages?

Google says crawl preferences for this token affect all Google Shopping surfaces, so it reads store pages to keep Shopping listings current. Verify the IP is Google's before excluding those sessions from bot or fraud rules.

Does a Googlebot robots.txt rule cover Storebot-Google?

Not according to Google's crawler table, which lists only the Storebot-Google token for it. Add a separate "User-agent: Storebot-Google" group if you want specific rules.

What happens if I block Storebot-Google?

Google can no longer crawl your store for Shopping, which can affect your product listings there. It does not by itself remove you from regular Google Search.

Could This Be a Scam? What to Do

  • Anyone can copy the Storebot-Google User-Agent. Google publishes an IP list for it, so compare the visiting address against that list before you trust the visit.
  • Never give an AI agent your logins, bank access, or one-time codes unless you set it up yourself.
  • If a call, text or email asking for money or access uses the Storebot-Google or Google name, stop and report it.

Guide: how to check whether a crawler visit is really who it claims to be.

More from Google

Related on FraudMeNot

Sources (checked Nov. 16, 2026): ai.robots.txt (MIT), crawler-user-agents (MIT), Google IP feed, Axios (Oct. 22, 2026), CNBC (Oct. 13, 2026), Google: List of Google's common crawlers (Google StoreBot). FraudMeNot is not affiliated with Google. Product and company names are trademarks of their owners and are used here only to identify the bots. General information, not security advice.