Storebot-Google and GPTBot Are Testing Your Shopify Checkout. Here Is Exactly What They Do.
Published: March 22, 2026
If You Block These Bots, You May Be Hurting Your Store
If you run a Shopify store and are considering blocking Storebot-Google or GPTBot, read this first.
Storebot-Google verifies that your store can process a purchase. If it cannot complete its checkout verification, your products may lose visibility in Google Shopping, product panels, and the Buy button in Google Search. Blocking Storebot-Google tells Google your store is not open for verification. That is not a signal you want to send.
GPTBot maps your product catalog and tests your cart API. OpenAI uses this data to understand what your store sells and how it works. Blocking GPTBot removes your store from that pipeline.
Our recommendation for Shopify merchants:
- Do not block Storebot-Google or GPTBot in robots.txt
- Ensure your checkout flow works cleanly, because Google is testing it
- Filter bot-generated checkout sessions from your abandoned cart recovery emails
- Separate bot traffic from real customer traffic in your analytics (Shopify’s monorail fires for both)
- If you use an llms.txt page, know that GPTBot references it during cart API testing
- Keep your product data clean and your payment methods active, both platforms are cataloging them
What Are These Bots Doing on Shopify Stores?
Google’s Storebot and OpenAI’s GPTBot are both interacting with the Shopify checkout flow. Both add items to cart. Only Storebot-Google renders the full checkout UI. Neither completes a purchase.
Google’s official description says Storebot-Google is “used to crawl and index product information for Google Shopping.” The logs show something different. Storebot-Google adds every product to cart, generates real checkout sessions, renders the payment form, and verifies Shop Pay availability. That is checkout verification, not product indexing.
GPTBot takes a different approach. It adds products to cart, calls the Shopify Cart JavaScript API directly, probes customer authentication 64 times, and fetches product JSON endpoints. It is building a map of how the store works.
How often does this happen?
This is not continuous crawling. Both bots run infrequently, in short targeted bursts.
Storebot-Google: Twice total, 10 days apart.
- Feb 18: quick recon (86 requests, 3 seconds), same day as GPTBot’s first crawl
- Feb 28: full checkout test of all 9 products (624 requests, 7 minutes)
- Nothing since. That was 3 weeks ago at the time of publishing.
GPTBot cart activity: Three times over 3 weeks.
- Feb 18: added all 8 existing products to cart via direct URLs
- Feb 25: tested cart JavaScript API (add.js, clear.js, update.js)
- Mar 13: discovered a new product added after the initial crawl and cart-tested it
What does this tell us?
Google runs checkout verification as a periodic audit, not a daily crawl. It checks in, confirms the store works, and moves on. If the store breaks between audits, Google would not know until the next pass.
GPTBot revisits when the catalog changes. It detected a new product added after its initial crawl and came back to test it. That means GPTBot is not just indexing once. It is monitoring for inventory changes and re-testing when it finds them.
For merchants, this means your store needs to be ready at all times. You do not get a warning before Storebot-Google runs its checkout verification. If your payment processor is down, your checkout theme is broken, or your Shop Pay configuration is misconfigured during that window, Google records a failed verification.
The Data
Period: January 25 through March 21, 2026
Site: WISLR owned Shopify store. Permitted to share, no client data used.
Total requests analyzed: 1,543 (Storebot-Google: 710, GPTBot: 833)
This data is from a single Shopify store and should not be read as an overall industry pattern. Our intent is to share what we found, spark conversation, and encourage merchants to inspect this for themselves.
Want this level of visibility into your own bot traffic?
Schedule a ChatWhat Checkout Steps Does Storebot-Google Complete on Shopify?
Storebot-Google checkout verification flow
Storebot: Recon
Storebot: Full
GPTBot Shopify interaction flow
GPTBot: Data and Cart API Mapping
This flow spans 3 sessions: Feb 18 (product pages, images, JSON, cart adds), Feb 25 (cart JS API + llms.txt), Mar 13 (+1 new product). Not one continuous crawl.
How Do Storebot-Google and GPTBot Compare on Shopify?
| Behavior | Storebot-Google | GPTBot |
|---|---|---|
| Total requests | 710 | 833 |
| Active days (checkout/cart activity) | 2 | 3 |
| Checks robots.txt | No | No |
| Adds products to cart | Yes (9 products) | Yes (9 products) |
| Creates checkout sessions | Yes (8 sessions) | No |
| Renders checkout UI | Yes (full render) | No |
| Detects payment methods | Yes (Visa, MC, Amex, Shop Pay) | No |
| Tests Login with Shop | Yes | No |
| Queries checkout GraphQL | Yes | No |
| Calls cart JavaScript API | No | Yes (add.js, clear.js, update.js) |
| Probes customer auth | No | Yes (64 hits to /customer_authentication/login) |
| Fetches product JSON API | No | Yes (all products .json) |
| Downloads product images | No (homepage assets in recon, checkout assets in full session) | Yes (all product images) |
| Fires Shopify analytics | Yes (monorail, /api/collect) | Yes (monorail) |
| Completes purchase | No | No |
Storebot-Google is verifying purchase readiness: “Can a customer complete a transaction on this store?” It walks through the checkout flow, renders payment UI, and confirms the store is functional.
GPTBot is mapping the store’s data and interaction model: “What products exist, how are they structured, how does the cart work, and what API endpoints are available?” It collects product data (pages, images, JSON), tests cart mechanics (add, clear, update), and probes auth systems.
Together, they represent two different approaches to understanding e-commerce: Google validates the transaction pipeline, OpenAI maps the data and interaction layer.
Why Does Google Run Checkout Simulations on Shopify Stores?
Storebot-Google is not a general-purpose crawler. It has a specific job: verify that online stores are real, functional, and capable of processing transactions. None of this behavior is documented in detail by Google. Here is what the data suggests.
Does Storebot-Google affect Google Shopping eligibility?
Google Shopping listings require a working store behind them. Storebot-Google verifies this programmatically. If your checkout is broken, your products may lose visibility in Shopping results and the “Buy” button in Google Search.
What merchant trust signals does Storebot-Google feed into?
Google Merchant Center tracks merchant reliability. A store that passes Storebot-Google’s checkout verification demonstrates a functioning cart, valid payment methods, and a complete purchase flow. That feeds into Google’s trust scoring for merchants.
Which payment methods does Storebot-Google verify?
Storebot-Google renders the full checkout UI, which includes detecting Shop Pay, Login with Shop, and standard cards (Visa, Mastercard, Amex). If Buy with Prime is installed, that component loads as part of the checkout render as well. Google likely uses this data to display payment options in search results and Shopping listings.
How does Storebot-Google detect fake or broken stores?
By simulating the checkout flow without completing a purchase, Google can identify stores with broken checkouts, missing payment processors, or fake storefronts. This helps filter low-quality merchants from Shopping results.
Why does Storebot-Google load both the ThankYou and PaymentFailed pages?
Storebot-Google pre-loads both the ThankYou page CSS and the OffsitePaymentFailed CSS. It evaluates whether the store handles both outcomes. Proper error handling for failed payments signals a more mature, reliable merchant.
What Does a Full Storebot-Google Checkout Simulation Look Like?
How fast does each checkout cycle take?
| Checkout step | Time from cart add |
|---|---|
| Cart add | 0s |
| Checkout session created | +1s |
| Full checkout UI rendered | +3s |
| Payment card icons loaded | +6s |
| Shop Pay + Login with Shop tested | +7s |
| Checkout GraphQL queried | +7s |
| Session complete | +7s |
Each product’s full checkout cycle completes in about 7 seconds.
How Far Does Storebot-Google Get in Shopify Checkout?
Storebot-Google progresses through the checkout flow systematically. Here is exactly what it successfully completes and where it stops.
What Storebot-Google completes
| Step | Status |
|---|---|
| Add product to cart (real variant ID) | Completed |
| Checkout session created (unique Shopify token) | Completed |
| Checkout page fully rendered (all CSS, JS, payment UI) | Completed |
| Payment method detection (Visa, Mastercard, Amex SVGs) | Completed |
| Accelerated checkout probe (Shop Pay POST) | Completed |
| Login with Shop test | Completed |
| Checkout GraphQL query (internal API) | Completed |
| Phone number formatter and autocomplete loaded | Completed |
| ThankYou + OffsitePaymentFailed CSS pre-loaded | Completed |
| Monorail analytics telemetry fired | Completed |
Where Storebot-Google stops
- No POST to a payment processing endpoint
- No shipping address submission
- No order confirmation or receipt page load
- It loads the ThankYou page CSS but never navigates to a thank-you URL
It gets to the payment form render. It can see the form, it knows what payment methods are available, it has confirmed the checkout session is valid. Then it stops before submitting any payment or personal data.
The question it answers: “If a real customer clicked Buy Now right now, would they see a working checkout with valid payment options?” Yes.
It loads both ThankYou and OffsitePaymentFailed CSS but never triggers either outcome. Testing readiness, not completing a transaction.
What Shopify Behaviors Are Not Documented About Storebot-Google?
Storebot-Google creates abandoned checkouts in Shopify
Storebot-Google creates real Shopify checkout tokens. These sessions may appear as abandoned checkouts in your Shopify admin. If you are running abandoned cart recovery emails, verify that you are not sending them to bot-generated sessions.
Storebot-Google inflates Shopify analytics data
Storebot-Google executes JavaScript and fires Shopify’s monorail analytics events. These visits register as real sessions. If you are measuring conversion rate, bounce rate, or session count through Shopify analytics, Storebot-Google traffic is in your numbers.
Storebot-Google validates the entire purchase path, not just product pages
Not random crawling. Storebot-Google validates cart, checkout, payment methods, accelerated checkout, and both success and failure states. That data feeds into Google Shopping eligibility, Merchant Center trust signals, and product listing quality.
Storebot-Google checks which payment methods your store supports
It renders the full checkout which detects Shop Pay, Login with Shop, and standard card payments (Visa, Mastercard, Amex). If Buy with Prime is installed, that component loads as part of the checkout render. The more payment methods available, the more data Google has about your store’s buyer experience.
Storebot-Google tests multiple products, not just one
Session 2 tested all 9 products through checkout. 9 products were carted, 8 had full checkout sessions generated. Not verifying a single product. Testing every item in the catalog.
Google Analytics cannot detect Storebot-Google accurately
Storebot-Google identifies itself via User-Agent string, but it executes JavaScript like a real browser. Client-side analytics tools may count these visits but cannot distinguish them from real customers without server-side log analysis.
What Does GPTBot Do on Shopify Stores?
| Metric | Value |
|---|---|
| Total requests | 833 |
| Active period | Feb 18 through Mar 21 (ongoing) |
| Products added to cart | 9 (every product) |
| Checkout sessions created | 0 |
| Purchases completed | 0 |
| robots.txt checks | 0 |
GPTBot’s approach is fundamentally different from Storebot-Google. It maps the store’s data and interaction model rather than validating the checkout pipeline.
How fast does GPTBot map a product catalog?
On Feb 18, GPTBot completed a full store crawl in 3 minutes 22 seconds (360 requests). It works in phases:
| Phase | Duration | What happens |
|---|---|---|
| Homepage render | 0s to +33s | Loads homepage, downloads JS/CSS assets, fonts, images sequentially |
| Product discovery + JSON APIs | +33s to +2m 3s | Visits every product page, fetches .json and .oembed endpoints, probes auth |
| Rapid cart adds | +2m 4s to +2m 10s | Adds 5 products to cart in 6 seconds |
| Continued extraction | +2m to +3m 22s | Fetches blogs, collections, search, remaining cart adds |
Average time per product: ~20 seconds (including asset downloads between products).
GPTBot loads assets sequentially at ~0.5s intervals, not in parallel like Storebot-Google. It behaves like a single-threaded headless browser, not a distributed crawler.
| Metric | GPTBot | Storebot-Google |
|---|---|---|
| Total session time | 3 min 22 sec | 7 min (full session) |
| Products processed | 8 | 8 |
| Time per product | ~20s | ~7s |
| Parallelism | Single-threaded (1 IP) | Massively parallel (47 IPs) |
What does GPTBot extract per product?
| Data point | How |
|---|---|
| Product page HTML (title, description, meta, structured data) | GET /products/PRODUCT |
| Product images (2-3 per product) | GET /cdn/shop/files/… |
| Product videos | GET /cdn/shop/videos/… |
| Full Shopify product JSON (body_html, pricing, variants, inventory) | GET /products/PRODUCT.json |
| oEmbed data | GET /products/PRODUCT.oembed |
| Variant IDs and pricing | From JSON API + cart URL structure |
| Cart functionality | GET /cart/VARIANT_ID:1 |
| Authentication state | GET /customer_authentication/login |
GPTBot also fetches store-wide data: full product catalog JSON (/products.json), all collections (/collections.json), search, blog content, and contact page.
How does GPTBot add products to cart?
GPTBot uses two methods:
Method 1: Direct cart URLs (Feb 18)
GPTBot visited each product page, then hit the direct cart URL with the product page as the referrer.
Method 2: Cart JavaScript API (Feb 25)
A different behavior. GPTBot called the Shopify Cart AJAX API directly:
| Time | Endpoint | Referrer |
|---|---|---|
| 16:37:21 | POST /cart/add.js | /products/[product-page] |
| 16:37:39 | POST /cart/clear.js | /pages/llms-txt |
| 16:37:41 | POST /cart/update.js | /pages/llms-txt |
GPTBot called cart/add.js (the JavaScript API for adding items), then navigated to the llms.txt page and from there called cart/clear.js and cart/update.js. Programmatic cart API testing with the llms.txt page in the referrer chain.
Mar 13: New product discovered
A new product added to the store after the initial Feb 18 crawl was discovered and cart-tested on March 13.
Does GPTBot probe Shopify customer authentication?
Yes. 64 hits to /customer_authentication/login and 7 to /customer_authentication/redirect. GPTBot is probing the Shopify customer auth system repeatedly.
What does GPTBot crawl most on Shopify?
| Hits | Path | Category |
|---|---|---|
| 64 | /customer_authentication/login | Auth probing |
| 17 | / | Homepage |
| 16 | monorail/produce_batch | Telemetry (JS executed) |
| 14 | /products/[top-product] | Product page |
| 13 | Product image CDN paths | Product images |
| 11 | /search | Search |
| 9 | /products/[product] | Product page |
| 8 | /pages/contact | Contact page |
| 7 | /collections/skill-packs | Collection |
| 7 | /customer_authentication/redirect | Auth probing |
What GPTBot does NOT do on Shopify
- Check robots.txt (zero requests, ever)
- Create checkout sessions
- Render the checkout UI
- Submit payment information
What GPTBot DOES do on Shopify
- Add every product to cart (both via direct URL and JavaScript API)
- Execute page JavaScript (monorail telemetry fires)
- Download product images
- Fetch product JSON API endpoints (.json URLs)
- Probe customer authentication (64 login attempts)
- Visit the llms.txt page and reference it as a referer
- Crawl the search endpoint
Which Other Bots Interact with Shopify Checkout?
| Bot | Cart adds | Checkout sessions | Shop Pay probe | Furthest point |
|---|---|---|---|---|
| Storebot-Google | 9 products | 8 sessions | Yes | Payment form rendered |
| GPTBot | 9 products | None | No | Cart only |
| GoogleOther | 1 product | None | No | Cart add + /cart/update |
| Googlebot | None | None | 31x Shop Pay probes | Shop Pay availability check |
| ChatGPT-User | None | None | 1x Shop Pay probe | Incidental |
| DuckAssistBot | None | None | 1x Shop Pay probe | Incidental |
| Bingbot | None | None | 1x Shop Pay probe | Incidental |
| Google-Structured-Data-Testing | None | None | 11x Shop Pay probes | Rendering test |
Storebot-Google is the only bot that renders the full checkout UI. No bot completes a purchase.
Frequently Asked Questions
What is Storebot-Google?
Storebot-Google is Google’s dedicated e-commerce verification bot. It crawls online stores to validate that the purchase flow works correctly, checking everything from product availability to checkout rendering and payment method support. It is separate from Googlebot, which handles general web indexing.
Does Storebot-Google actually complete purchases?
No. Based on server log analysis, Storebot-Google adds real products to cart, generates real Shopify checkout sessions, renders the full payment UI, and tests payment methods like Shop Pay, but it stops before submitting any payment data or personal information. It verifies purchase readiness without completing a transaction.
How many requests does Storebot-Google make per session?
In the sessions analyzed, Storebot-Google made 86 requests in 3 seconds during a quick recon pass, and 624 requests over approximately 7 minutes during a full checkout simulation. The full session included adding products to cart, rendering checkout UI, and testing multiple payment methods across dozens of parallel Google IPs.
Does Storebot-Google affect Shopify analytics?
Yes. Storebot-Google executes JavaScript and triggers Shopify’s analytics telemetry (monorail tracking events), which means its visits can appear in your analytics as if a real customer visited. It also creates real checkout sessions with unique tokens, which may show up as abandoned checkouts in your Shopify admin.
Why does Storebot-Google test checkout on Shopify stores?
Storebot-Google validates that a store can process real purchases. This data likely feeds into Google Shopping, Google Merchant Center, and search result features that show product availability and buying options. A store with a verified working checkout is more likely to surface in Google Shopping results.
Can you block Storebot-Google with robots.txt?
You can add Storebot-Google to your robots.txt disallow rules, but blocking it may affect your visibility in Google Shopping and product-related search features. Google uses Storebot data to verify merchant reliability, so blocking it could signal that your store is not open for verification.
Does GPTBot add products to cart on Shopify stores?
Yes. GPTBot adds products to cart using both direct cart URLs (/cart/VARIANT_ID:1) and the Shopify Cart JavaScript API (cart/add.js, cart/clear.js, cart/update.js). In the sessions analyzed, GPTBot added every product in the store to cart. Unlike Storebot-Google, GPTBot does not create checkout sessions or render the checkout UI.
What is the difference between Storebot-Google and GPTBot on Shopify?
Storebot-Google validates purchase readiness by walking through the full checkout flow, rendering payment UI, and confirming the store is functional. GPTBot maps the store’s data and interaction model by collecting product data, testing cart mechanics, probing customer authentication, and fetching product JSON API endpoints. Google validates the transaction pipeline. OpenAI maps the data and interaction layer.