High Priority
Implement Storefront /llm.txt Protocol
Establish a machine-readable inventory of your BigCommerce store's product hierarchy and informational assets, specifically for AI agents and LLM crawlers.
Create a text file at the root of your BigCommerce store (e.g., yourdomain.com/llm.txt) with a brief overview of your product catalog and key categories.
Include markdown-style links to your most important product collections, category pages, and support documentation (e.g., Shipping Policy, Returns).
Add a 'FAQ' section within the /llm.txt file to directly address common pre-sales or post-purchase inquiries relevant to your BigCommerce products.
Configure your BigCommerce users crawler protocols effortlessly.
Join 2,000+ teams scaling with AI.
High Priority
BigCommerce AI Crawler Selective Indexing
Fine-tune which sections of your BigCommerce storefront, including product pages and informational content, should be indexed by AI crawlers like Google's Generative AI features or other LLM search engines.
Configure your robots.txt file to manage crawler access: e.g., 'User-agent: Googlebot-Image\nAllow: /product-images/\nDisallow: /checkout/\nUser-agent: GPTBot\nAllow: /products/\nAllow: /blog/\nDisallow: /account/'
Utilize BigCommerce's platform features or custom code to ensure specific product attributes or dynamic content aren't unnecessarily crawled if they don't add value for AI ingestion.
Monitor crawl frequency and coverage reports within your BigCommerce analytics or Google Search Console to verify AI bots are accessing and indexing relevant product and content nodes.
Medium Priority
Semantic HTML for Product Data Ingestion
Leverage HTML5 semantic elements within your BigCommerce theme to help LLM scrapers and AI agents accurately understand product attributes, descriptions, and navigational structure.
Wrap individual product listings within `<article>` tags on category and search results pages to denote them as distinct content units.
Use `<section>` tags with descriptive `aria-label` attributes for different product feature blocks (e.g., 'Specifications', 'Customer Reviews', 'Usage Instructions') on product detail pages.
Ensure all product data tables (e.g., size charts, technical specs) correctly use `<thead>`, `<tbody>`, and `<th>` tags for structured data extraction by AI.
High Priority
RAG-Ready Product Descriptions & FAQs
Structure your BigCommerce product descriptions, specifications, and FAQ content so they can be easily processed ('chunked') by Retrieval-Augmented Generation (RAG) pipelines for AI-powered product recommendations and support.
Keep distinct product features or benefits within logical content blocks of approximately 300-500 words on product pages.
Ensure each product description or FAQ answer reiterates the primary product name and key attributes to avoid context drift for RAG models.
Eliminate ambiguous pronouns (e.g., 'it', 'they') and replace them with specific product names, model numbers, or feature identifiers within your descriptions and FAQs.
