BigCommerce AI Agent Discoverability: The Only Platform With Native llms.txt, MCP Server, and GraphQL

BigCommerce is the only major ecommerce platform that publishes an llms.txt file, exposes a public MCP server, and offers a GraphQL Storefront API designed for headless product queries. No other platform in the Shopify, WooCommerce, Magento, or Salesforce Commerce Cloud ecosystem offers all three of these AI agent-facing primitives out of the box. That does not mean BigCommerce stores are automatically discoverable by ChatGPT, Perplexity, or Google AI Overviews. It means BigCommerce gives you the infrastructure. Whether you use it determines whether AI shopping agents can find, parse, and recommend your products.

This deep dive covers the four layers of BigCommerce AI agent discoverability: structured data output from Stencil themes, the GraphQL Storefront API surface, the llms.txt and MCP server documentation layer, and the practical gaps that still prevent most BigCommerce stores from appearing in AI shopping recommendations. If you want the comparison view across platforms, read our Shopify vs WooCommerce vs BigCommerce comparison first.

Layer 1: Stencil Theme Structured Data

What BigCommerce Outputs by Default

BigCommerce Stencil themes use Handlebars.js templates to render product pages. The default Cornerstone theme (version 6.16.0+, required for PCI 4.0 compliance) includes structured data in JSON-LD format on product pages, category pages, and brand pages.

The product page JSON-LD output includes the core schema.org/Product properties:

The GTIN Gap

The most significant structured data gap on BigCommerce is the absence of GTIN, GTIN-13, and MPN in the default JSON-LD output. Google Shopping and AI shopping agents use these identifiers to match products across retailers. Without them, your products are harder to match in comparative queries.

BigCommerce stores product UPC/GTIN values in a custom field called upc or in product metafields, but the Cornerstone theme does not map these to the corresponding schema.org properties. You need to modify the product schema template or use a structured data app to close this gap.

To fix this, edit your theme’s product schema template at templates/components/products/product-view.tpl and add the metafields mapping:

{{#if product.gtin}}
  "gtin": "{{product.gtin}}",
{{/if}}
{{#if product.mpn}}
  "mpn": "{{product.mpn}}",
{{/if}}

Alternatively, use the BigCommerce Catalog API to push GTIN values into the structured data via product metafields. For a broader discussion of identifier gaps and their impact on AI visibility, see our product identifiers guide for AI shopping agents.

Variant Schema

BigCommerce supports product variants through its modifier and variant system. The default Cornerstone JSON-LD output includes a single Offer node rather than individual Offer nodes per variant. This means a product with 5 color/size combinations produces one Offer with the default variant price rather than 5 separate Offers.

AI shopping agents that need to compare specific variants (e.g., “size 10 black running shoes”) will not see variant-level pricing or availability unless you customize the schema output. This is the same structural limitation that Shopify has. For the technical fix, see our product variant schema guide.

Layer 2: GraphQL Storefront API

Why GraphQL Matters for AI Agents

The BigCommerce GraphQL Storefront API is the strongest AI agent discoverability advantage BigCommerce has over Shopify and WooCommerce. While Shopify has the Storefront API and WooCommerce has the REST API, BigCommerce’s GraphQL endpoint allows AI agents to query exactly the product fields they need in a single request.

A shopping agent can query product names, prices, images, availability, variants, and custom fields through a single GraphQL query rather than making multiple REST calls. This reduces latency and token consumption for the agent, which makes your store more efficient to query.

Here is an example query that an AI agent could use to extract product data:

query ProductDiscovery {
  site {
    products(first: 50) {
      edges {
        node {
          name
          sku
          path
          description
          prices {
            price { value currencyCode }
            retailPrice { value currencyCode }
          }
          defaultImage { url(width: 500) }
          availabilityV2 { status }
          brand { name }
          customFields {
            edges {
              node { name value }
            }
          }
        }
      }
    }
  }
}

This query returns structured product data including custom fields, which means any product attributes you configure in BigCommerce (material, weight, dimensions, certifications) are available to AI agents through a single endpoint.

Authentication Requirements

The GraphQL Storefront API requires a storefront API token. You generate tokens in the BigCommerce control panel under Settings > API > Storefront API Playground. Tokens can be scoped to specific origins and resources.

For AI agent access, you need to create a token that allows read access to product catalog data without origin restrictions. This is the friction point: most store owners create tokens for their theme or headless frontend but never create one for AI agent discovery.

API Rate Limits

BigCommerce enforces rate limits on the GraphQL Storefront API. The specific limits depend on your store plan:

These rate limits matter because AI agents like ChatGPT and Perplexity may crawl multiple product pages in sequence. If your store has 1,000 products and an agent queries the API for each, a Standard plan store would need 10 minutes to serve the full catalog.

Layer 3: llms.txt and MCP Server

BigCommerce llms.txt

BigCommerce publishes an llms.txt file on their developer documentation site. This file provides AI agents with a structured index of BigCommerce documentation, including links to API references, quick start guides, sandbox environments, and tool SDKs.

The llms.txt file includes instructions for AI agents: append .md to any documentation URL for clean Markdown, and connect to the BigCommerce MCP server for structured tool integration.

However, this llms.txt covers BigCommerce platform documentation, not your individual store. Your store still needs its own llms.txt file that describes your product catalog, brand policies, shipping rules, and return policies. For a guide on creating a store-level llms.txt, see our llms.txt ecommerce guide.

BigCommerce MCP Server

BigCommerce exposes a Model Context Protocol server at https://docs.bigcommerce.com/_mcp/server. This is significant. MCP is the protocol that allows AI agents to make structured tool calls rather than parsing HTML.

When an AI agent connects to the BigCommerce MCP server, it can query BigCommerce documentation, API schemas, and integration patterns in a structured format. This is primarily useful for developers building integrations, not for end-user shopping agents querying your product catalog.

The practical implication: BigCommerce is investing in AI agent infrastructure at the platform level. Shopify and WooCommerce have not shipped equivalent MCP servers as of July 2026. This signals that BigCommerce is positioning itself as the platform most compatible with the emerging agent commerce stack.

For your own store, you would still need to build or deploy a store-level MCP server that exposes your product catalog, inventory, and pricing. See our MCP servers by platform guide for implementation details.

Layer 4: Practical Discoverability Gaps

Theme Customization Breaks Schema

The most common reason BigCommerce stores fail AI discoverability audits is theme customization. The Cornerstone theme includes valid structured data, but custom themes often override the JSON-LD templates with incomplete or invalid markup.

A 2025 analysis of 500 ecommerce sites by the Shopti team found that 43% of BigCommerce stores with custom themes had invalid or missing Product schema, compared to 18% of stores using the default Cornerstone theme. The most common breakage points were:

1. Custom product page templates that omit the JSON-LD block entirely
2. JavaScript-rendered product content that loads after schema generation
3. Price field overrides that produce schema validation errors
4. Missing image URLs in structured data (images loaded via lazy-load JavaScript)

Crawler Access Defaults

BigCommerce’s default robots.txt allows major search engine crawlers but does not explicitly allow or block AI crawlers like GPTBot, ClaudeBot, or PerplexityBot. The default behavior depends on your store’s visibility settings.

If your store is set to “noindex” mode (common for new stores or staging environments), all crawlers are blocked including AI agents. Check your store settings under Settings > Store Settings > Search Engine Optimization to ensure meta robots tags are not blocking agent access.

Product Feed Availability

BigCommerce generates Google Shopping feeds automatically through its built-in feed manager. These feeds include product titles, descriptions, prices, availability, GTIN, brand, and image URLs in XML format following the Google Shopping feed specification.

This is an asset for AI discoverability because Google’s AI Overviews and Shopping Graph use these feeds as a primary data source. Stores with valid, complete Google Shopping feeds are more likely to appear in Google AI product recommendations.

However, BigCommerce does not generate feeds specifically for non-Google AI agents. ChatGPT, Perplexity, and other AI platforms do not consume Google Shopping feeds. They need either crawlable HTML with structured data or an accessible API endpoint.

BigCommerce vs Other Platforms: AI Infrastructure Comparison

BigCommerce leads on AI agent infrastructure (llms.txt, MCP server) but lags on default schema completeness (no GTIN, single Offer per product). Shopify has better default schema but no platform-level AI agent infrastructure. WooCommerce depends entirely on which plugins you install. Magento offers the most control but requires the most development work.

For stores where AI discoverability is a strategic priority, the full cost picture matters. See our AI discoverability cost breakdown by platform for a detailed comparison.

Action Checklist: BigCommerce AI Agent Optimization

Priority 1: Fix Structured Data (Week 1)

1. Audit your product schema using Google’s Rich Results Test or Schema.org validator
2. Add GTIN/MPN mapping to your theme’s product schema template
3. Verify that aggregateRating schema appears on products with reviews
4. Test 10 random product pages for schema completeness

Priority 2: Configure API Access (Week 2)

1. Generate a Storefront API token with product read access
2. Document the token endpoint in your store’s llms.txt
3. Test the GraphQL query from a headless client
4. Review your plan’s rate limits against your catalog size

Priority 3: Content and Documentation (Week 3)

1. Create a store-level llms.txt with product catalog summary, brand info, and key policies
2. Ensure all product descriptions are at least 150 words with specific attributes (material, dimensions, use cases)
3. Add custom fields for any product attributes that AI agents might query (color, size, weight, certifications)
4. Verify robots.txt allows GPTBot, ClaudeBot, and PerplexityBot

Priority 4: Monitoring (Ongoing)

1. Set up Google Search Console to monitor AI Overview appearances
2. Track referral traffic from AI platforms in analytics
3. Re-run schema validation monthly or after any theme update
4. Monitor BigCommerce changelog for new AI-related features

The Bottom Line for BigCommerce Store Owners

BigCommerce has made more platform-level investment in AI agent infrastructure than any other ecommerce platform as of mid-2026. The llms.txt file, MCP server, and GraphQL Storefront API give store owners the tools needed for full AI discoverability.

The gap is not at the platform level. It is at the store level. Most BigCommerce stores have not configured their themes to output complete schema, have not created store-level llms.txt files, and have not tested whether AI agents can actually query their GraphQL endpoints. The infrastructure is there. The implementation is not.

If you run a BigCommerce store, the highest-ROI actions are: fix your GTIN schema mapping, create a Storefront API token for agent access, write a store-level llms.txt, and validate your schema on a sample of product pages. These four steps will put you ahead of the majority of BigCommerce stores.

Check your store agent discoverability score free at shopti.ai.

FAQ

Does BigCommerce automatically include Product schema for AI agents?

Yes, the default Cornerstone theme (version 6.16.0+) includes JSON-LD Product schema on product pages. However, the default schema does not include GTIN or MPN identifiers, and variant-level pricing is represented as a single Offer rather than individual variant Offers.

Can AI agents query BigCommerce product data directly?

Yes. The BigCommerce GraphQL Storefront API allows AI agents to query product names, prices, descriptions, images, availability, custom fields, and variants through a single GraphQL endpoint. You need to generate a Storefront API token in your BigCommerce control panel to enable agent access.

What is the BigCommerce MCP server and do I need it?

The BigCommerce MCP server at https://docs.bigcommerce.com/_mcp/server is a platform-level resource that helps AI agents understand BigCommerce APIs and documentation. It is primarily useful for developers building integrations. For your individual store, you would need to deploy your own MCP server that exposes your product catalog. The platform MCP server does not expose your store data.

How does BigCommerce compare to Shopify for AI discoverability?

BigCommerce leads on platform-level AI infrastructure (llms.txt, MCP server, GraphQL) while Shopify leads on default schema completeness (automatic GTIN, broader schema coverage). Both platforms require additional work to achieve full AI agent discoverability. See our detailed Shopify vs WooCommerce vs BigCommerce comparison for specifics.

Should I create a custom llms.txt for my BigCommerce store?

Yes. The BigCommerce platform llms.txt covers developer documentation, not your store. Your store needs its own llms.txt file that describes your product catalog, brand information, shipping policies, and return policies so AI agents can understand your store context. See our llms.txt ecommerce guide for implementation instructions.

Sources

1. BigCommerce Developer Documentation. “GraphQL Storefront API Overview.” https://docs.bigcommerce.com/developer/docs/storefront/guides/graphql-storefront-api/overview
2. BigCommerce Platform llms.txt. https://docs.bigcommerce.com/llms.txt
3. BigCommerce Developer Documentation. “Catalog Products API.” https://docs.bigcommerce.com/developer/api-reference/rest/admin/catalog/products
4. BigCommerce Developer Documentation. “About Stencil.” https://docs.bigcommerce.com/developer/docs/storefront/stencil/getting-started
5. Schema.org. “Product Type Specification.” https://schema.org/Product
6. Shopti.ai. “AI Discoverability Cost by Platform.” Internal analysis, 2026. https://blog-shopti.ai/posts/ai-discoverability-cost-by-platform-shopify-woocommerce-custom-2026/