BigCommerce AI agent readiness

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, 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 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 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.

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.

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 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.

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 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, the price match check and price transparency 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 will fail without one.

Most of these are one setting or one page, and none needs a developer except the structured data.

If our robots.txt check 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.

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/

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*

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/

If our CAPTCHA check 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 and returns 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 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.

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 will not find one on a stock store. 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.

Tick as you go. The ticks stay in this browser, and unlike BigCommerce's crawler list, you can see all of them.

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.