Commerce

Storebot-Google

Checks pages for Google Shopping.

See your agent traffic
PurposeCommerce
HTTP identifierStorebot-Google
IdentityVerify beyond the name

THE SIGNAL

What this visit tells you

Product and checkout requests deserve their own series alongside the merchant feed.

Product URLs
Checkout responses
Redirect failures

Your next move

Compare requested product URLs with current inventory and checkout access.

The technical details

Markdown
How to identify it

Look for the Storebot-Google identifier in a request’s User-Agent. This is a name match, not identity verification. Version strings may change.

How to check identity

Use Google’s published IP ranges for this crawler class and its forward-confirmed reverse DNS procedure.

Access and robots.txt

The operator documents robots.txt rules for this identifier.

Optional full-site opt-out. Merge with existing rules only if intended. robots.txt does not secure private content.

User-agent: Storebot-Google
Disallow: /
Seeing 403 or 404 responses?

403 means access was denied; 404 means the resource was not found. Compare the public path, request time, edge security event and origin response to find the cause.

Separate intended restrictions and secret-file probes from pages that should work. A User-Agent name alone does not justify allowing a request.

SourcesReviewed 2026-09-14

Identity and purpose are based on these sources. Analytics interpretation and suggested checks are Apostl guidance.

APOSTL Pulse

See Storebot-Google in context

See their requests. Find the pages that matter.

See your agent traffic