# BigCommerce AI agent readiness What BigCommerce does for AI agents by default, from its hidden robots.txt rules to WebMCP on Stencil, what it leaves to you, and where UCP and ACP stand in its own words. By Valerii Checha, 3 Nov 2026 Is a BigCommerce store ready for AI agents? Partly. BigCommerce lets AI crawlers in by default, turns on WebMCP tools for browser agents on eligible Stencil stores, keeps reCAPTCHA off at checkout and ships product structured data in its default theme. Guest checkout, policies, price-range products and agent checkout through UCP or ACP are still yours to sort out, or not yet available. This guide covers what BigCommerce already does for agents, what is off or missing by default, and how to fix each common gap, with the control panel path for each setting and the [check](https://storewalk.ai/checks) in our scan that reads it. BigCommerce's behaviour comes from its help center, developer docs, theme source code and announcements, read on 3 November 2026. Storewalk is ours: we build it, and this blog is part of its site. Where we explain something in plain words, the explanation is ours. [The hub article](https://storewalk.ai/blog/why-agents-cant-buy) sets out the five walls between an agent and a finished purchase. Here is how a BigCommerce store meets each one. ## What does BigCommerce already do for AI agents? Quite a lot, and part of it is in a robots.txt section you cannot edit. BigCommerce's help page on robots.txt is direct about AI: "By default, you do not need to include any robots.txt entries to allow AI bot crawling." The file you can edit, under Settings › Website › Search Engine Robots, has one group for every crawler, and its 15 lines keep crawlers out of the account, cart, checkout, login, search and admin pages, among others. No AI agent is named. The live file has more. The same help page explains that "a separate set of rules applies specifically to known high-volume and AI crawlers", adding "a crawl delay as well as block crawlers from select sensitive pages, such as cart, checkout, account, admin, and filter pages", with `Crawl-delay: 10`. BigCommerce keeps the list of those crawlers itself, and "While you cannot view or edit these entries or list of crawlers from your store's website settings, they are visible by directly navigating to your robots.txt file". So open `/robots.txt` on your own domain once; it is the only place the whole file is shown. Browser agents get tools. Since 21 October 2026, BigCommerce and Cloudflare have offered [WebMCP](https://storewalk.ai/blog/agentic-commerce-glossary#webmcp), which lets an agent in the browser call tools the page provides instead of clicking through it. BigCommerce's announcement says "Eligible stores have WebMCP turned on by default" and "To start, it's available for eligible BigCommerce storefronts built on Stencil." Cloudflare "injects a tiny script at the edge" that adds the tools, and the press release says an agent can "add the best match to a cart and hand back a link to complete checkout on the merchant's store." Cloudflare's post adds that Commerce.com "already uses Cloudflare to run their almost 100,000 domains"; that count is Cloudflare's. Our [WebMCP check](https://storewalk.ai/checks/DISC-015) looks for those tools. Stencil's default theme, Cornerstone, prints Product JSON-LD with name, SKU, MPN, GTIN, brand, image, description and an offer with price, currency, condition and availability, plus ratings when there are reviews. That covers most of what our [product structured data check](https://storewalk.ai/checks/DISC-004) wants. Checkout reCAPTCHA is off. BigCommerce's page says reCAPTCHA "can also be enabled for the checkout page to help prevent bots from creating orders. It is disabled by default", and gives the reason: it "can affect your conversion rate due to increased checkout friction." Agents and impatient shoppers would both sign that sentence. What BigCommerce ships, against what an agent needs. - robots.txt lets AI agents in: Fine by default. BigCommerce says no entries are needed to allow AI crawling. Its hidden rules ask the crawlers it lists to wait 10 seconds between requests and stay off cart, checkout, account, admin and filter pages. Checks: [DISC-001 robots.txt allows AI agents](https://storewalk.ai/checks/DISC-001). Source: [BigCommerce Support: Understanding the robots.txt file](https://support.bigcommerce.com/articles/en_US/Knowledge/Understanding-the-Robots-txt-File). - Site search open to crawlers: Gap by default. /search.php is disallowed by default, so a polite agent will not run your search through its URL. Checks: [DISC-008 Search endpoint usable by GET](https://storewalk.ai/checks/DISC-008). Source: [BigCommerce Support: Understanding the robots.txt file](https://support.bigcommerce.com/articles/en_US/Knowledge/Understanding-the-Robots-txt-File). - Product JSON-LD (Stencil, Cornerstone): Fine by default. Name, sku, mpn, gtin, brand, image, description and an offer with price, currency and availability. Checks: [DISC-004 Product structured data](https://storewalk.ai/checks/DISC-004) and [EVAL-004 Availability explicit](https://storewalk.ai/checks/EVAL-004). Source: [Cornerstone source: schema.html](https://raw.githubusercontent.com/bigcommerce/cornerstone/master/templates/components/products/schema.html). - Price-range products (Cornerstone): Gap by default. The offer gets minPrice and maxPrice instead of price. Those are not Offer properties in schema.org, and our DISC-004 reports the price missing. Checks: [DISC-004 Product structured data](https://storewalk.ai/checks/DISC-004) and [EVAL-003 Price transparency](https://storewalk.ai/checks/EVAL-003). Source: [Cornerstone source: schema.html](https://raw.githubusercontent.com/bigcommerce/cornerstone/master/templates/components/products/schema.html). - Price in Catalyst: Fine by default. Catalyst puts price and currency in offers.priceSpecification. That is valid schema.org, but some tools may miss it. Our DISC-004, DISC-005 and EVAL-003 read it. Checks: [DISC-004 Product structured data](https://storewalk.ai/checks/DISC-004), [DISC-005 Structured data matches rendered page](https://storewalk.ai/checks/DISC-005) and [EVAL-003 Price transparency](https://storewalk.ai/checks/EVAL-003). Source: [Catalyst source: product-schema](https://raw.githubusercontent.com/bigcommerce/catalyst/canary/core/app/%5Blocale%5D/\(default\)/product/%5Bslug%5D/_components/product-schema/index.tsx). - Shipping and returns in JSON-LD: Gap by default. Neither Cornerstone nor Catalyst prints shippingDetails or a return policy. The policy is a web page you write. Checks: [EVAL-001 Shipping cost and terms machine-readable](https://storewalk.ai/checks/EVAL-001) and [EVAL-002 Return policy machine-readable](https://storewalk.ai/checks/EVAL-002). Sources: [Cornerstone source: schema.html](https://raw.githubusercontent.com/bigcommerce/cornerstone/master/templates/components/products/schema.html) and [BigCommerce Support: Processing returns](https://support.bigcommerce.com/articles/en_US/Knowledge/Processing-Returns). - Guest checkout: Yours to set. Three options and no stated default. Checks: [TRX-001 Guest checkout available](https://storewalk.ai/checks/TRX-001). Source: [BigCommerce Support: Guest customers and checkout](https://support.bigcommerce.com/articles/Public/Guest-Customers-and-Checkout). - No CAPTCHA before payment: Fine by default. Checkout reCAPTCHA is disabled by default. Checks: [TRX-002 No CAPTCHA before the payment step](https://storewalk.ai/checks/TRX-002). Source: [BigCommerce Support: reCAPTCHA](https://support.bigcommerce.com/articles/en_US/Knowledge/Updating-Themes-with-reCAPTCHA-v2). - WebMCP for browser agents: Fine by default. On by default for eligible Stencil stores, injected at the edge by Cloudflare. Checks: [DISC-015 WebMCP tools exposed to browser agents](https://storewalk.ai/checks/DISC-015). Sources: [BigCommerce blog: WebMCP (21 October 2026)](https://www.bigcommerce.com/blog/webmcp-browser-ai-agents/) and [Cloudflare blog: WebMCP for commerce (21 October 2026)](https://blog.cloudflare.com/webmcp-commerce/). - Storefront MCP: Yours to set. A toggle the store owner switches on. The docs page shows no status label. Checks: [DISC-012 MCP server card published](https://storewalk.ai/checks/DISC-012). Source: [BigCommerce docs: MCP overview](https://docs.bigcommerce.com/developer/api-reference/mcp/overview). - llms.txt: Not stated or not shipped. We found no native setting for a store’s own llms.txt. Apps exist. Checks: [DISC-002 llms.txt present and non-trivial](https://storewalk.ai/checks/DISC-002). Source: [Your Store Wizards: llms.txt for BigCommerce stores](https://blog.yourstorewizards.com/llms-txt-generator-for-bigcommerce-stores/). - UCP and ACP agent checkout: Not stated or not shipped. Commerce, BigCommerce’s parent, is “building toward” UCP, and says Stripe’s suite “will enable” its merchants. We found no live setting. Checks: [TRX-004 Agent checkout endpoint present](https://storewalk.ai/checks/TRX-004). Sources: [Commerce: support for UCP (11 January 2026)](https://finviz.com/news/272920/commerce-supports-universal-commerce-protocol-plans-to-offer-buying-directly-across-googles-ai-surfaces) and [Commerce: Stripe Agentic Commerce Suite (18 December 2025)](https://www.commerce.com/press/pr-stripe-agentic-commerce-suite/). Statuses are ours, read from each source’s own words. “Not stated or not shipped” means the platform’s pages do not say, or the feature is announced but not something you can switch on. ## Where do the BigCommerce settings live? Six places decide most of what an agent meets. Pick one to see its path, its default as BigCommerce states it, and the checks it moves. Where each BigCommerce setting lives, and what it defaults to. 1. robots.txt. Where: Settings › Website › Search Engine Robots. Default: One User-agent: \* group with 15 Disallow lines, plus hidden rules for crawlers BigCommerce lists. In its words: “By default, you do not need to include any robots.txt entries to allow AI bot crawling.” What to do (our advice): Edit only the visible part; the hidden lines are BigCommerce’s and cannot be changed here. On Multi-Storefront, each storefront has its own file. Checks: [DISC-001 robots.txt allows AI agents](https://storewalk.ai/checks/DISC-001) and [DISC-008 Search endpoint usable by GET](https://storewalk.ai/checks/DISC-008). Source: [BigCommerce Support: Understanding the robots.txt file](https://support.bigcommerce.com/articles/en_US/Knowledge/Understanding-the-Robots-txt-File). 2. Guest checkout. Where: Settings › Checkout. Default: Three options; the help page marks none as the default. In its words: “Customers are not required to have an account to check out” What to do (our advice): Pick that first option, or the one that creates an account after the order. With guest checkout off, wallet buttons show only to signed-in shoppers. Checks: [TRX-001 Guest checkout available](https://storewalk.ai/checks/TRX-001). Source: [BigCommerce Support: Guest customers and checkout](https://support.bigcommerce.com/articles/Public/Guest-Customers-and-Checkout). 3. Checkout reCAPTCHA. Where: Settings › General › Security & Privacy. Default: Off for checkout. In its words: “It is disabled by default” What to do (our advice): Leave the checkout one off unless bots are creating orders. The form reCAPTCHA for sign-ups, reviews and contact does not touch checkout. Checks: [TRX-002 No CAPTCHA before the payment step](https://storewalk.ai/checks/TRX-002) and [VER-003 Checkout has stricter controls than the product page](https://storewalk.ai/checks/VER-003). Source: [BigCommerce Support: reCAPTCHA](https://support.bigcommerce.com/articles/en_US/Knowledge/Updating-Themes-with-reCAPTCHA-v2). 4. WebMCP. Where: The MCP settings menu in the Control Panel. Default: On for eligible Stencil stores, since 21 October 2026. In its words: “Eligible stores have WebMCP turned on by default” What to do (our advice): Nothing to do if you want it. Browser agents get tools such as product search and add to cart; checkout stays on your site. Checks: [DISC-015 WebMCP tools exposed to browser agents](https://storewalk.ai/checks/DISC-015). Sources: [BigCommerce blog: WebMCP (21 October 2026)](https://www.bigcommerce.com/blog/webmcp-browser-ai-agents/) and [Cloudflare blog: WebMCP for commerce (21 October 2026)](https://blog.cloudflare.com/webmcp-commerce/). 5. Storefront MCP. Where: Settings › API and MCP › MCP › Storefront MCP. Default: A toggle only the store owner can switch on. What to do (our advice): Switch it on if you want agents to search, fill a cart and hand off to checkout. Each storefront gets its own endpoint. Checks: [DISC-012 MCP server card published](https://storewalk.ai/checks/DISC-012) and [TRX-010 A path to buy exists](https://storewalk.ai/checks/TRX-010). Source: [BigCommerce docs: MCP overview](https://docs.bigcommerce.com/developer/api-reference/mcp/overview). 6. Shipping and returns. Where: Storefront › Web Pages, and Settings › Returns. Default: No policy page until you make one; returns requests off until ticked. What to do (our advice): Make a page called “Shipping and Returns Policy” with the window in days, and tick “Yes, enable returns requests”. Checks: [EVAL-001 Shipping cost and terms machine-readable](https://storewalk.ai/checks/EVAL-001) and [EVAL-002 Return policy machine-readable](https://storewalk.ai/checks/EVAL-002). Source: [BigCommerce Support: Processing returns](https://support.bigcommerce.com/articles/en_US/Knowledge/Processing-Returns). Guest checkout needs a decision, because the help page labels none of its three options as the default. Under Settings › Checkout you choose between "Customers are not required to have an account to check out", the same "but automatically create one after ordering", and "Customers must have or create an account to check out". The first two let an agent through; the third stops it, and with guest checkout off BigCommerce shows wallet buttons only to signed-in shoppers. Our [guest checkout check](https://storewalk.ai/checks/TRX-001) reports which you have. Storefront MCP is the other switch. Under Settings › API and MCP › MCP, only the store owner can turn on "Storefront MCP", and each storefront then gets its own MCP API endpoint where agents can, in BigCommerce's words, "search products, manage a shopping cart, and hand off to checkout." The docs page shows no beta or preview label, so we give it none. ## What is off or missing by default? Search, some prices and all of the policies. Site search is closed to crawlers. `Disallow: /search.php` sits in the group every crawler follows. A polite agent will not run your search through its URL, which is what our [search check](https://storewalk.ai/checks/DISC-008) tests. There is a twist: an agent on BigCommerce's own crawler list follows its own group instead, and that group, as the help page prints it, does not mention `/search.php`. You cannot see which agents are on the list. Price-range products lose their price. When a product shows a range, Cornerstone puts `minPrice` and `maxPrice` on the Offer instead of `price`. Those are not Offer properties in schema.org, and our DISC-004 reports the price missing on those pages. Catalyst stores have a different quirk. Catalyst, BigCommerce's Next.js storefront, prints JSON-LD from a `ProductSchema` component that puts price and currency inside `offers.priceSpecification`. That is valid schema.org, but some tools may miss it, because they look for `price` on the Offer itself. Our own checks read it: [DISC-004](https://storewalk.ai/checks/DISC-004), the [price match check](https://storewalk.ai/checks/DISC-005) and [price transparency](https://storewalk.ai/checks/EVAL-003) take the price from `priceSpecification` when the Offer has none of its own. Shipping and returns are web pages only. Neither theme prints `shippingDetails` or a return policy in structured data. BigCommerce's returns help suggests you "set the Page Name to "Shipping and Returns Policy" or something similar" under Storefront › Web Pages, and returns requests stay off until you tick "Yes, enable returns requests" under Settings › Returns. There is no llms.txt for stores. BigCommerce's developer docs have one of their own, but we found no native setting that makes one for a store, and apps fill the gap. Our [llms.txt check](https://storewalk.ai/checks/DISC-002) will fail without one. ## How do you fix the common failures? Most of these are one setting or one page, and none needs a developer except the structured data. If our [robots.txt check](https://storewalk.ai/checks/DISC-001) fails, someone added a block to the editable part; the hidden part blocks cart, checkout, account, admin and filter pages, not the whole store. Remove the line, or narrow it to the bot you mean. For harder controls, BigCommerce's own advice is that "you must use a service, such as Cloudflare". With the default file, our check reports WARN rather than PASS, which is expected: every agent inherits the cart and checkout lines. If you want agents to use your search, you can add `Allow: /search.php` to the editable file. That is our example, not BigCommerce's advice, and search pages can trap crawlers in endless combinations, so weigh it. Try it on the files below. BigCommerce’s default robots.txt, hidden lines included. The first file is the editable part, as BigCommerce’s help page lists it. The live /robots.txt adds lines you cannot edit, which the same page also prints; the second file adds them. Control panel default. No AI agent is named here. Search results (/search.php) are disallowed for everyone, along with cart and checkout. By the rule of our DISC-001, this file is WARN: no agent is fully blocked, but each inherits some Disallow lines, such as cart or checkout. That is normal for a store and costs little. ```text User-agent: * Disallow: /account.php Disallow: /cart.php Disallow: /checkout.php Disallow: /checkout Disallow: /finishorder.php Disallow: /login.php Disallow: /orderstatus.php Disallow: /postreview.php Disallow: /productimage.php Disallow: /productupdates.php Disallow: /remote.php Disallow: /search.php Disallow: /viewfile.php Disallow: /wishlist.php Disallow: /admin/ ``` | Path | GPTBot under “Control panel default” | | ----------------------------------------------------- | ------------------------------------ | | A product page: /linen-shirt/ | Allowed | | Site search: /search.php?search_query=linen | Blocked, by Disallow: /search.php | | The cart: /cart.php | Blocked, by Disallow: /cart.php | | Checkout: /checkout | Blocked, by Disallow: /checkout | | Sign-in: /login.php | Blocked, by Disallow: /login.php | | A filtered category: /shirts/?\_bc_fsnf=1\&Color=Blue | Allowed | With the hidden lines. BigCommerce adds two filter lines for everyone, and a group for “known high-volume and AI crawlers” with a 10-second crawl delay. It does not publish that list, so GPTBot stands in as an example name. An agent on the list follows its own group instead of the \* one, and that group does not mention /search.php. By the rule of our DISC-001, this file is WARN: no agent is fully blocked, but each inherits some Disallow lines, such as cart or checkout. That is normal for a store and costs little. ```text User-agent: * Disallow: /account.php Disallow: /cart.php Disallow: /checkout.php Disallow: /checkout Disallow: /finishorder.php Disallow: /login.php Disallow: /orderstatus.php Disallow: /postreview.php Disallow: /productimage.php Disallow: /productupdates.php Disallow: /remote.php Disallow: /search.php Disallow: /viewfile.php Disallow: /wishlist.php Disallow: /admin/ Disallow: /*?_bc_fsnf=1* Disallow: /*&_bc_fsnf=1* # A crawler on BigCommerce's list (GPTBot is our example name) User-agent: GPTBot Crawl-delay: 10 Disallow: /account.php Disallow: /cart.php Disallow: /checkout.php Disallow: /checkout Disallow: /admin/ Disallow: /*?_bc_fsnf=1* Disallow: /*&_bc_fsnf=1* ``` | Path | GPTBot under “With the hidden lines” | | ----------------------------------------------------- | --------------------------------------- | | A product page: /linen-shirt/ | Allowed | | Site search: /search.php?search_query=linen | Allowed | | The cart: /cart.php | Blocked, by Disallow: /cart.php | | Checkout: /checkout | Blocked, by Disallow: /checkout | | Sign-in: /login.php | Allowed | | A filtered category: /shirts/?\_bc_fsnf=1\&Color=Blue | Blocked, by Disallow: /\*?\_bc_fsnf=1\* | With search allowed (our example). Our example, not BigCommerce’s advice. An Allow of the same length wins the tie, so search opens to crawlers again. Search pages can be crawl traps, so weigh it. By the rule of our DISC-001, this file is WARN: no agent is fully blocked, but each inherits some Disallow lines, such as cart or checkout. That is normal for a store and costs little. ```text User-agent: * Disallow: /account.php Disallow: /cart.php Disallow: /checkout.php Disallow: /checkout Disallow: /finishorder.php Disallow: /login.php Disallow: /orderstatus.php Disallow: /postreview.php Disallow: /productimage.php Disallow: /productupdates.php Disallow: /remote.php Disallow: /search.php Allow: /search.php Disallow: /viewfile.php Disallow: /wishlist.php Disallow: /admin/ ``` | Path | GPTBot under “With search allowed (our example)” | | ----------------------------------------------------- | ------------------------------------------------ | | A product page: /linen-shirt/ | Allowed | | Site search: /search.php?search_query=linen | Allowed, by Allow: /search.php | | The cart: /cart.php | Blocked, by Disallow: /cart.php | | Checkout: /checkout | Blocked, by Disallow: /checkout | | Sign-in: /login.php | Blocked, by Disallow: /login.php | | A filtered category: /shirts/?\_bc_fsnf=1\&Color=Blue | Allowed | Source: [BigCommerce Support: Understanding the robots.txt file](https://support.bigcommerce.com/articles/en_US/Knowledge/Understanding-the-Robots-txt-File). If our [CAPTCHA check](https://storewalk.ai/checks/TRX-002) fails, look under Settings › General › Security & Privacy. The form reCAPTCHA there covers "account sign-ups, reviews, and contact forms", which is fine; turn the checkout one off unless bots are placing orders. If price-range products fail DISC-004, give the Offer a real `price` in the theme's `schema.html` template, for example the lowest price, or list one Offer per variant. Keep the range for people; agents need a number. If our [shipping](https://storewalk.ai/checks/EVAL-001) and [returns](https://storewalk.ai/checks/EVAL-002) checks fail, write the Shipping and Returns Policy page with a cost and its currency, or free delivery, and a return window in days. "Returns accepted within 30 days" passes; "contact us" does not. [How agents read a page](https://storewalk.ai/blog/how-agents-read-a-page) explains what agents look for. If you want an llms.txt, an app can make one. Our check wants a title, at least 20 lines and links that work, so list your main categories and policy pages in it. ## Can a BigCommerce store take agent checkout? Not through UCP or ACP yet, in BigCommerce's own wording. Commerce, BigCommerce's parent company, announced on 11 January 2026 its "endorsement of Google's new Universal Commerce Protocol (UCP)" and said "Commerce is building toward the protocol". Its December 2025 release on Stripe's Agentic Commerce Suite says the suite "will enable BigCommerce merchants to capitalize on the emerging era of AI agent-driven shopping." At Commerce Live in April 2026 it listed "Distribution across AI-driven discovery surfaces including ChatGPT, Gemini, Microsoft Copilot, Perplexity, PayPal, and Stripe" and "Agent-enabled checkout experiences", with no status attached. We found no BigCommerce UCP profile or setting, so our [agent checkout check](https://storewalk.ai/checks/TRX-004) will not find one on a stock store. [UCP explained](https://storewalk.ai/blog/ucp-explained) covers what one looks like when it arrives. What works today is the route WebMCP and Storefront MCP take: the agent finds products, fills a cart and hands the shopper a link to your checkout. That keeps guest checkout and a CAPTCHA-free checkout page important, because the last step is still on your site. ## BigCommerce agent readiness checklist Tick as you go. The ticks stay in this browser, and unlike BigCommerce's crawler list, you can see all of them. Your BigCommerce checklist, saved in this browser. - \[ ] Read your live /robots.txt, hidden lines included. Checks: [DISC-001 robots.txt allows AI agents](https://storewalk.ai/checks/DISC-001). - \[ ] Guest checkout allowed (Settings › Checkout). Checks: [TRX-001 Guest checkout available](https://storewalk.ai/checks/TRX-001). - \[ ] Checkout reCAPTCHA off unless bots are placing orders (Settings › General › Security & Privacy). Checks: [TRX-002 No CAPTCHA before the payment step](https://storewalk.ai/checks/TRX-002). - \[ ] Stencil: WebMCP left on, if you want browser agents. Checks: [DISC-015 WebMCP tools exposed to browser agents](https://storewalk.ai/checks/DISC-015). - \[ ] Decided on Storefront MCP (Settings › API and MCP › MCP). Checks: [DISC-012 MCP server card published](https://storewalk.ai/checks/DISC-012). - \[ ] Price-range products give agents a real price somewhere they can read it. Checks: [DISC-004 Product structured data](https://storewalk.ai/checks/DISC-004) and [EVAL-003 Price transparency](https://storewalk.ai/checks/EVAL-003). - \[ ] A Shipping and Returns Policy page with the window in days; returns requests on (Storefront › Web Pages; Settings › Returns). Checks: [EVAL-001 Shipping cost and terms machine-readable](https://storewalk.ai/checks/EVAL-001) and [EVAL-002 Return policy machine-readable](https://storewalk.ai/checks/EVAL-002). - \[ ] An llms.txt from an app, if you want one. Checks: [DISC-002 llms.txt present and non-trivial](https://storewalk.ai/checks/DISC-002). ## Frequently asked questions ### Does BigCommerce block AI crawlers? Not by default. BigCommerce says "you do not need to include any robots.txt entries to allow AI bot crawling." Its hidden rules give a list of high-volume and AI crawlers a 10-second crawl delay and keep them off cart, checkout, account, admin and filter pages. You can see them at your store's `/robots.txt`, not in the control panel. ### Is WebMCP on for my BigCommerce store? BigCommerce says "Eligible stores have WebMCP turned on by default", starting with stores built on Stencil, and that you can opt out in the MCP settings menu in the control panel. ### Does BigCommerce support UCP or ACP? Not yet as a setting we could find. Commerce, BigCommerce's parent, says it "is building toward" UCP, and that Stripe's Agentic Commerce Suite "will enable" its merchants. ### Is guest checkout on by default on BigCommerce? BigCommerce's help page lists three options under Settings › Checkout and marks none as the default. Choose one that does not require an account. ### Why does a tool say my Catalyst store has no product price? Catalyst puts price and currency in `offers.priceSpecification`, which is valid schema.org. Some tools only look for `price` on the Offer and report it missing. Our DISC-004, DISC-005 and EVAL-003 read the price from `priceSpecification`, so they don't. The sources below were last checked on the date shown. ## Sources - [BigCommerce Support: Understanding the robots.txt file](https://support.bigcommerce.com/articles/en_US/Knowledge/Understanding-the-Robots-txt-File) - [Cornerstone source: schema.html](https://raw.githubusercontent.com/bigcommerce/cornerstone/master/templates/components/products/schema.html) - [Catalyst source: product-schema](https://raw.githubusercontent.com/bigcommerce/catalyst/canary/core/app/%5Blocale%5D/(default)/product/%5Bslug%5D/_components/product-schema/index.tsx) - [BigCommerce docs: MCP overview](https://docs.bigcommerce.com/developer/api-reference/mcp/overview) - [BigCommerce blog: WebMCP (21 October 2026)](https://www.bigcommerce.com/blog/webmcp-browser-ai-agents/) - [Commerce and Cloudflare: WebMCP press release (21 October 2026)](https://finviz.com/news/405335/commerce-and-cloudflare-bring-ai-shopping-assistants-to-bigcommerce-merchants-online-stores-with-webmcp) - [Cloudflare blog: WebMCP for commerce (21 October 2026)](https://blog.cloudflare.com/webmcp-commerce/) - [BigCommerce Support: Guest customers and checkout](https://support.bigcommerce.com/articles/Public/Guest-Customers-and-Checkout) - [BigCommerce Support: reCAPTCHA](https://support.bigcommerce.com/articles/en_US/Knowledge/Updating-Themes-with-reCAPTCHA-v2) - [BigCommerce Support: Processing returns](https://support.bigcommerce.com/articles/en_US/Knowledge/Processing-Returns) - [BigCommerce docs: AI agent setup](https://docs.bigcommerce.com/developer/docs/ai-agent-setup) - [Commerce: support for UCP (11 January 2026)](https://finviz.com/news/272920/commerce-supports-universal-commerce-protocol-plans-to-offer-buying-directly-across-googles-ai-surfaces) - [Commerce: Stripe Agentic Commerce Suite (18 December 2025)](https://www.commerce.com/press/pr-stripe-agentic-commerce-suite/) - [Commerce: Commerce Live 2026 announcements (30 April 2026)](https://finviz.com/news/349291/commerce-introduces-new-product-innovations-across-storefronts-b2b-payments-and-ai-driven-commerce-at-commerce-live-2026) Last checked 4 Nov 2026