Google Storebot Is Shopping in Your PrestaShop Store: What Merchants Need to Know in 2026

If you run a PrestaShop store with Google Shopping listings, you may have noticed something unusual in your database recently: hundreds of abandoned carts that no real customer ever created. No guest ID. No customer ID. No shipping address. Just phantom carts piling up, day after day, created by a Google bot that is literally shopping in your store.

This is not a bug, and it is not a hack. It is Google's Storebot — and in 2026, it is more active than ever because Google Merchant Center is enforcing stricter verification of your store's checkout flow, pricing accuracy, and stock availability. Understanding what is happening and how to handle it is now essential for every PrestaShop merchant using Google Shopping.

What Is Storebot-Google?

Storebot-Google is a specialized crawler operated by Google, separate from the regular Googlebot that indexes your pages for organic search. Its sole purpose is e-commerce verification: it visits your product pages, reads prices and availability, and then tests your checkout flow by actually adding products to the cart.

The user agent string looks like this:

Mozilla/5.0 (X11; Linux x86_64; Storebot-Google/1.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/136.0.0.0 Safari/537.36

It uses a full JavaScript rendering engine — behaving like a real browser — and follows this sequence on every visit:

1. Loads the product page — reads price, availability, structured data
2. Clicks "Add to Cart" — creates a real cart record in your database
3. Visits the cart page — verifies the cart price matches the product page price
4. Proceeds toward checkout — fills in address forms with generated data to extract shipping costs and tax calculations
5. Abandons the cart — never completes a purchase

This is how Google verifies that what your Merchant Center feed says actually matches what a real customer would experience. And as of 2026, this verification is no longer optional or occasional — it is continuous and thorough.

Why This Is Happening Now: Google Merchant Center's 2026 Crackdown

Google has been steadily tightening Merchant Center policies, and 2025-2026 has seen the most aggressive enforcement changes in years. Understanding the bigger picture explains why Storebot activity has surged.

Preemptive Item Disapprovals Are Increasing

Google now uses AI-powered crawlers to proactively compare your product feed against your live store. If the price in your feed says €49.99 but the product page shows €54.99, the product gets disapproved before any customer even sees the discrepancy. These Preemptive Item Disapprovals (PIDs) increased significantly in recent years, and the trend has continued through 2025 and into 2026.

The critical detail: Google does not just check the product page. It checks the cart price and the checkout price too. That is exactly what Storebot is doing when it adds products to your cart — verifying price consistency across the entire purchase journey.

Out-of-Stock Product Pages: What Google Expects

Google has been tightening its expectations for out-of-stock product pages. Current best practices to avoid disapprovals:

• Out-of-stock products must display a disabled (grayed-out) buy button — you cannot hide the button entirely
• An active, clickable buy button on an out-of-stock product page can trigger misrepresentation flags during checkout verification
• The availability text on the page must exactly match what your feed reports — "temporarily unavailable" is not an acceptable substitute for "out of stock"

Storebot verifies all of this. It checks whether it can add an out-of-stock product to the cart (it should not be able to), and it checks whether in-stock products have a working add-to-cart flow (they must).

New Product Data Specification (April 2026)

Google released an updated product data specification on April 14, 2026, introducing new requirements and attributes:

• Minimum image resolution raised to 500×500 pixels — warnings began immediately, enforcement starts January 2027
• product_highlight attribute is recommended with 4 to 6 entries per product (minimum 2, maximum 100 allowed)
• video_link attribute — submit product videos, with validation beginning June 30, 2026
• return_method — configuring return details in Merchant Center is increasingly important for all categories
• handling_cutoff_time and minimum_order_value — new shipping-related attributes

The Content API for Shopping shuts down on August 18, 2026, requiring migration to the new Merchant API v1. If you use any third-party feed modules, verify they support the new API.

Automatic Item Updates Are Now Default

Since September 2025, Google has enabled automatic item updates by default. Google's crawlers read your product pages' structured data (schema.org/Product markup) and automatically correct mismatches between your feed and your live store for price, availability, and condition.

This is a safety net — but it only works if your structured data is accurate. Without proper schema.org markup on your product pages, Google cannot auto-correct, and mismatches lead directly to disapprovals.

Google I/O 2026: Universal Cart and AI Shopping

At Google I/O 2026 (May 19-20), Google announced the Universal Cart — an AI-powered shopping cart that works across Search, YouTube, Gmail, and Gemini. They also introduced Agent Payments Protocol (AP2), allowing AI agents to make purchases on behalf of users.

What this means for merchants: Google is building a future where AI agents shop for customers. For that to work, Google needs to trust that your store's data is accurate and your checkout flow is reliable. Storebot is the foundation of that trust verification. Expect its crawling to increase, not decrease.

The Real Problem: Cart Spam and Database Bloat

While Google's verification is legitimate and ultimately serves your interests (accurate listings get more visibility), the side effect is real and problematic.

Here is what one PrestaShop store experienced over just five days:

• 527 spam carts created by Storebot (vs. 85 legitimate carts in the same period)
• All spam carts had id_customer=0, id_guest=0, id_carrier=0, id_address=0 — completely anonymous
• The bot was adding real products (the same ones it found on product pages) at a rate of 7 carts per hour, 24/7
• IPs from Google's known ranges: 66.102.8.*, 66.249.83.*, 66.249.93.*, 74.125.212.*

This is not unique. Merchants across PrestaShop, WooCommerce, Shopify, and Magento have reported the same pattern. The "John Smith" phenomenon — where Storebot fills checkout forms with generated names and Gmail addresses — is well-documented across every major e-commerce platform.

The consequences go beyond a messy database:

• Inflated abandoned cart metrics — your cart abandonment rate looks catastrophically high
• Wasted email marketing — abandoned cart recovery emails sent to bot addresses hurt your sender reputation
• Database table growth — the ps_cart and ps_cart_product tables grow continuously
• Skewed analytics — conversion funnels, GTM events, and analytics data become unreliable
• Performance impact — on stores with limited database resources, thousands of extra cart rows slow down queries

What NOT to Do

Before we talk about solutions, let us be clear about what you should not do:

Do Not Block Storebot-Google Entirely

If you use Google Merchant Center — and you should, since free product listings are available to everyone — blocking Storebot will cause your products to be disapproved. Google's official documentation is explicit: "Allowing the crawler access to your pages is highly encouraged." Products will stop appearing in Shopping ads and free listings until Google can crawl your pages again.

Do Not Block Storebot from POST /cart

While it is tempting to allow Storebot to read product pages but block its cart submissions, this breaks the checkout flow verification that Google requires. If Storebot cannot verify your cart prices, you risk the "landing page doesn't match" error and preemptive disapprovals.

Do Not Block Google IP Ranges at the Firewall

Google's IP ranges (66.102.*, 66.249.*, 74.125.*) are shared across all Google crawlers. Blocking these IPs would also block Googlebot, killing your organic search visibility entirely.

What You Should Do: The Balanced Approach

1. Keep Your Product Data Consistent

The single most effective thing you can do is make sure Storebot finds what it expects. When your feed, your structured data, your product page, and your cart all show the same price and availability, Storebot's visit is verified successfully and does not trigger any issues.

• Ensure your Merchant Center feed module updates prices and stock in real time (or as close to it as possible)
• Verify your product pages have proper schema.org/Product markup with price, priceCurrency, availability, and brand
• Make sure cart prices include the same taxes and currency as the product page

2. Handle Out-of-Stock Products Correctly

Following Google's March 2026 policy update, your PrestaShop product pages must:

• Show a visibly disabled add-to-cart button when a product is out of stock (grayed out, with the HTML disabled attribute)
• Display clear "Out of stock" text that matches your feed's availability value
• Not allow adding out-of-stock products to the cart under any circumstances

Check your theme's product template. Many PrestaShop themes hide the add-to-cart button entirely for out-of-stock products, which is no longer compliant. The button must be visible but disabled.

3. Clean Up Bot Carts Periodically

The most practical solution for the database bloat is regular cleanup. Bot-generated carts are easy to identify:

• id_customer = 0
• id_guest = 0 (or the guest record has a Storebot user agent)
• id_carrier = 0
• id_address_delivery = 0
• Created by IPs in Google's known ranges

You can safely delete these carts. They have no associated customer, no payment, no order — they are pure database weight. Set up a cron job or use a database maintenance module to clean carts older than 48 hours that match these criteria.

Example SQL for identifying Storebot carts (adapt the table prefix to your installation):

SELECT COUNT(*) FROM ps_cart
WHERE id_customer = 0
  AND id_guest = 0
  AND id_carrier = 0
  AND id_address_delivery = 0
  AND date_add > DATE_SUB(NOW(), INTERVAL 7 DAY);

4. Exclude Bot Carts from Analytics and Email

If you use abandoned cart recovery emails (and you should — they are one of the highest-ROI email automations), make sure your module or integration filters out carts with no customer and no guest. Sending recovery emails to bot-generated carts wastes resources and damages your email deliverability score.

Similarly, exclude anonymous carts from your conversion funnel analytics. Your true cart abandonment rate is the one calculated from carts with a real customer or identified guest session.

5. Use robots.txt Strategically

While you should not block Storebot from product pages or the cart, you can use robots.txt to prevent it from crawling URLs that generate unnecessary load:

User-agent: Storebot-Google
Disallow: /wishlist/
Disallow: /*?order=
Disallow: /*?utm_
Allow: /

Google respects robots.txt directives for Storebot, and this approach keeps your product pages and checkout accessible while reducing crawl waste on non-commercial pages.

6. Ensure Structured Data Is Complete and Accurate

With automatic item updates enabled by default, your schema.org markup is now a critical safety net. Google reads it to auto-correct feed mismatches before they become disapprovals. At minimum, every product page should include:

• @type: Product with name, image, brand, sku
• Offer with price, priceCurrency, availability (using schema.org enumeration values like InStock or OutOfStock)
• MerchantReturnPolicy with return window and method
• OfferShippingDetails with delivery time

Test your markup with Google's Rich Results Test tool. Inconsistencies between structured data and the visible page content trigger crawl warnings.

The 2026 Merchant Center Compliance Checklist

Here is a practical checklist for PrestaShop merchants to ensure compliance with all current Google Merchant Center requirements:

Key Dates: Google Merchant Center 2026 Timeline

Looking Ahead: AI Agents Will Shop in Your Store

Google's Universal Cart and Agent Payments Protocol are not distant concepts — they were announced at Google I/O 2026 with launch partners already onboard: Nike, Sephora, Target, Walmart, Wayfair, and select Shopify merchants including Fenty and Steve Madden. The Universal Commerce Protocol (UCP), co-developed with Shopify in January 2026, standardizes how AI agents interact with merchant stores.

What this means: in the near future, it will not just be Storebot adding products to your cart. AI shopping agents acting on behalf of real customers will navigate your store, verify prices, check availability, and potentially complete purchases autonomously. Your store's data accuracy and checkout reliability are becoming the foundation for a new kind of commerce.

The stores that have their product data, structured markup, and checkout flow in perfect order will be the ones that AI agents trust — and recommend to their users. The stores with broken carts, price mismatches, and sloppy availability data will be filtered out long before a human ever sees them.

Conclusion

Storebot-Google creating hundreds of carts in your database is annoying. But blocking it would be worse — disapproved products, lost Shopping visibility, and being excluded from Google's growing AI commerce ecosystem. The right approach is to welcome the verification while managing its side effects: keep your data consistent, clean up bot carts periodically, exclude them from analytics and email automations, and make sure your store meets all of Google Merchant Center's 2026 requirements.

The rules of Google Shopping are changing faster than ever. Merchants who stay ahead of these changes — with accurate feeds, proper structured data, compliant product pages, and clean checkout flows — will see their products surface more often, in more places, and eventually through AI agents that do the shopping for their customers.