Aizii Learn · AI Search

[← Back to Learn](https://aizii.ai/learn)

# AI SEO setup guide for BigCommerce

This guide sets up a BigCommerce store so AI systems can find it, read it, and quote it. Work in this order: let the crawlers in, fix the product facts on the page, check the structured data your theme already ships, add the short files that describe your store, then publish content worth citing. Nothing here promises a citation or a recommendation. No vendor publishes a formula for what gets cited.

BigCommerce is a hosted platform, so it handles part of the job for you. It generates your XML sitemap automatically, it ships a robots.txt file by default, and its Stencil themes ship Product markup by default. Your job is to check what the platform already does, fix the parts it leaves to you, and keep the product facts current. Platform screens change, so check the vendor docs in Sources for the current path before relying on a menu name in this guide.

## Where it goes wrong

BigCommerce stores fail in AI search in a few specific ways. Each one is fixable, and each one sits in a different place.

-   A robots.txt rule blocks an AI crawler. BigCommerce ships a default robots.txt file that blocks cart, checkout, and account pages, and it also applies a delay to AI bots. If someone added a broad block on top of that, or a security app blocks a crawler the file allows, the crawler never reaches your product pages.
-   The product page states the facts, but the theme markup does not. Stencil themes ship Product markup by default, and BigCommerce points to JSON-LD as the expected format on current Cornerstone versions. If a product page does not display certain data, such as brand information, the matching markup will not be present either.
-   Prices and stock disagree across places. Your store says one price, a marketplace listing says another, and the markup says a third. An AI system given three answers has no reason to trust any of them.
-   The store has good product pages and nothing else. Product pages give an AI system facts. Guides and comparisons give it answers to quote. A store with no guides gives an assistant little to cite beyond a price.
-   The sitemap was never submitted. BigCommerce generates the sitemap for you, but search engines still need to be told where it is, or new and changed pages stay harder to find.

## The steps

Two people may be involved, and the split matters. The marketer uses the control panel, the product editor, and page settings to edit titles and descriptions, set prices and stock, and write content. The developer uses theme files, working in a local copy of the theme with the Stencil CLI and pushing the theme update, or using the theme file editor in the control panel where the plan and theme support direct edits. If you are both people, keep the split in mind anyway, because a theme edit made like a dashboard edit is how stores break.

**Step 1. Let the AI crawlers in.** The marketer or the developer opens the live robots.txt file by adding robots.txt to the store domain in a browser and reads it top to bottom. BigCommerce documents that you view or edit the file under Settings, then Website, in the Search Engine Robots section. If you see a rule that blocks GPTBot, OAI-SearchBot, PerplexityBot, ClaudeBot, or Google-Extended, that rule is the first thing to fix. Keep the blocks on the account, cart, and checkout pages. Do not stop at robots.txt. A security app or a firewall can block a crawler that robots.txt allows, so after any change, check the live file again and check your server logs for the crawlers you want.

**Step 2. Fix the product data in the editor.** The marketer does this part in the product editor. A product page is the unit an AI system reads, quotes, and links to, so make the pages worth reading before you add any file. Write a product name that names the product plainly, and a description that states what it is, what it is for, what it is made of, and the limits a buyer needs to know. Put the price, the options, and the stock status where a reader can see them without clicking, and keep the price current. When a product sells out, update the stock status the same day. When a product is discontinued, say so on the page. Work through your best sellers first.

**Step 3. Check the structured data, and keep one source.** The developer opens a live product page, views the page source, and searches for the structured data block. Confirm it states the product name, price, currency, and availability, and that it matches what the visible page says. If fields are missing, check whether the underlying data is on the page first. BigCommerce documents that missing product data on the page means missing markup, so fill in the product fields in the control panel, such as brand and SKU, and recheck the source. If the data is on the page but absent from the markup, the theme needs the fields added to its JSON-LD block, and that is developer work in the theme files. Google says structured data is not required for its generative AI features, and there is no special markup you need to add for them. Treat markup as the confirmation of the facts on the page, not as a ticket into an answer.

**Step 4. Confirm the sitemap and submit it.** BigCommerce generates an XML sitemap automatically at your store domain followed by xmlsitemap.php, split into separate sitemaps by page type, with each page holding up to 50,000 URLs. The marketer opens that address in a browser to confirm it loads and lists current products. Submit it in Google Search Console using the Sitemaps report. BigCommerce also documents that you can add a sitemap line to your robots.txt file so crawlers can find it there. Submitting a sitemap is a hint, not a guarantee. Google says submitting it does not guarantee it will download the sitemap or use it for crawling.

**Step 5. Add llms.txt.** An llms.txt file is a short markdown briefing at your site root that tells models what you sell, who it is for, and where the key pages are. Keep it short: name your brand, state what you sell, and link to your best category pages, guides, and shipping and returns pages. Do not paste your whole catalog into it. BigCommerce does not publish llms.txt by default, so this is a step to plan. The marketer writes the content, and the developer publishes it at the site root and confirms it loads at your store domain followed by llms.txt. Google Search does not use llms.txt, and Google says so directly, but other assistants can read it.

**Step 6. Publish content worth citing.** The marketer writes the guides and comparisons customers actually ask for: how to choose between two of your products, how to use the product, and how to fix the common problem. Open with a direct answer, then give the detail, then state the limits. Use your own first-hand experience, because Google says a first-hand review provides a unique perspective based on personal experience, while a summary of existing content simply restates information already available. Do not create a separate page for every possible phrasing of the same question. Google warns against creating separate content for every possible variation to manipulate rankings. One good guide per real question beats ten thin pages.

## The machine-readable piece

This is the robots.txt block to check against your live file. Replace yourdomain.com with your actual domain. It allows the AI crawlers named in our [robots.txt guide](https://aizii.ai/learn/ai-search/how-to-write-robots-txt-for-ai-search), keeps the account, cart, and checkout pages closed, and points crawlers at the sitemap BigCommerce generates for you.

```
User-agent: GPTBot
Allow: /

User-agent: OAI-SearchBot
Allow: /

User-agent: PerplexityBot
Allow: /

User-agent: ClaudeBot
Allow: /

User-agent: Google-Extended
Allow: /

User-agent: *
Disallow: /account.php
Disallow: /cart.php
Disallow: /checkout.php

Sitemap: https://[yourdomain.com]/xmlsitemap.php
```

Check the result in the browser. Open your store domain followed by robots.txt and confirm the allow lines and the sitemap line appear. Then check one product page: view the page source, search for the structured data block, and confirm the name, price, currency, and availability match the visible page. A short Product block looks like this, with your own values in place of the placeholders:

```
<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Product",
  "name": "Example product name",
  "offers": {
    "@type": "Offer",
    "price": "49.00",
    "priceCurrency": "USD",
    "availability": "https://schema.org/InStock"
  }
}
</script>
```

The fields in this block come from the schema.org Product and Offer types and the Google Product structured data page. Do not add a field you cannot fill with a true value. A block with a guessed price is worse than a block with no price.

## What it looks like when it works

On the page, a shopper sees a plain product name, a description that says what the part fits and what it does not fit, the price next to the options, and the stock status in words. Under the surface, the same facts appear in the structured data block, the crawler allow rules let AI crawlers reach the page, and the sitemap lists the page. Nothing looks different to a human reader. The change is that a machine reading the page finds the same facts in every place it looks.

Say you run a bicycle parts store on BigCommerce, selling chains, cassettes, brake pads, and tires. The marketer rewrites the product pages so each chain states which drivetrains it fits, each tire states the width and the terrain it suits, and each page shows the price for every option in plain text. The developer checks the page source, finds the theme block carries name, price, and availability but no brand, and traces it to brand fields never filled in on the products. The marketer fills them in, and the developer confirms the block now carries the brand. The developer also finds a broad robots.txt rule blocking PerplexityBot, removes it, and confirms the crawler arrives in the logs. The marketer writes one guide, how to pick a chain for your drivetrain, opening with a direct answer and showing the compatibility checks used in the shop. A shopper asks an assistant for a chain that fits a specific drivetrain under a set budget. The assistant can check the fit, the price, and the stock, and it cites the guide for the compatibility advice.

### The fundamentals

These mechanics are shared across every engine and covered in full in their own guides:

-   •The llms.txt format and a complete sample, see our [guide to writing a good llms.txt file](https://aizii.ai/learn/ai-search/how-to-write-a-good-llms-txt-file)
-   •The markup AI systems read to verify facts, see our [product schema guide](https://aizii.ai/learn/ai-search/how-to-add-product-schema-markup-for-ai-search)
-   •The complete crawler rule reference, see our [robots.txt guide for AI search](https://aizii.ai/learn/ai-search/how-to-write-robots-txt-for-ai-search)

## What this guide does not cover

This guide covers the AI SEO setup for a BigCommerce store. It does not cover the full technical audit that checks every crawler and every page, the transaction layer that lets an agent complete a purchase, or the per-engine playbooks for getting each assistant to find you. It does not cover keeping prices and availability accurate as inventory changes. Those are separate jobs, and this guide is the map, not the whole trip.

## Check your own store now

Run the free scan. One click, no signup, and it shows whether AI crawlers can read your store today: aizii.ai/aeo-scan

[Run the free scan](https://aizii.ai/aeo-audit)

## Sources

-   BigCommerce support, Understanding the Robots.txt File (specific): [https://support.bigcommerce.com/s/article/Understanding-the-Robots-txt-File](https://support.bigcommerce.com/s/article/Understanding-the-Robots-txt-File)
-   BigCommerce support, Locating Your Sitemap (specific): [https://support.bigcommerce.com/s/article/Sitemaps](https://support.bigcommerce.com/s/article/Sitemaps)
-   BigCommerce support, Google Search Engine (specific): [https://support.bigcommerce.com/s/article/Google-Search-Engine?language=en\_US](https://support.bigcommerce.com/s/article/Google-Search-Engine?language=en_US)
-   BigCommerce developer docs home (general docs): [https://developer.bigcommerce.com/](https://developer.bigcommerce.com/)
-   Google Search Central, Optimizing your website for generative AI features on Google Search (specific): [https://developers.google.com/search/docs/fundamentals/ai-optimization-guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide)
-   Google Search Central, Product structured data (specific): [https://developers.google.com/search/docs/appearance/structured-data/product](https://developers.google.com/search/docs/appearance/structured-data/product)
-   Google Search Central, Build and submit a sitemap (specific): [https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap](https://developers.google.com/search/docs/crawling-indexing/sitemaps/build-sitemap)
-   Schema.org, Product type (specific): [https://schema.org/Product](https://schema.org/Product)
-   Schema.org, Offer type (specific): [https://schema.org/Offer](https://schema.org/Offer)
-   OpenAI, Overview of OpenAI crawlers (specific): [https://platform.openai.com/docs/bots](https://platform.openai.com/docs/bots)
-   Perplexity, Perplexity crawlers (specific): [https://docs.perplexity.ai/guides/bots](https://docs.perplexity.ai/guides/bots)
-   llms.txt proposal (specific): [https://llmstxt.org](https://llmstxt.org/)

Note: links marked specific point to the page that supports the claim in this guide. Links marked general docs point to the vendor's general docs section for that topic, not to a page that proves every step. Check the vendor docs for the current path before relying on a menu name or click path in this guide.
