BigCommerce SEO automation: catalogue-scale content without the agency
AutoSEO publishes optimised articles straight into your BigCommerce blog through the store API, and keeps the same post updated when the content is refreshed.
Try AutoSEO with BigCommerceQuick answer
You create an API account in your BigCommerce control panel and paste the store hash and access token into AutoSEO. Articles are then POSTed directly to the store's blog API, and a re-publish PUTs the same post rather than creating a duplicate. AutoSEO handles the research, writing, meta and internal linking before that; what it does not do is invent product data — prices, SKUs and stock stay with your catalogue.
A direct BigCommerce API call. In your control panel you create an API account with content permissions and copy the store hash and access token. AutoSEO POSTs each article to /stores/{storeHash}/v2/blog/posts with title, HTML body, slug, meta description, tags and publish state; a re-publish PUTs the existing post by ID so the URL and its accumulated signals survive the refresh.
Step-by-step setup lives in the webhook integration guide.
Generic SEO advice fails on BigCommerce for platform-specific reasons. These are the ones that actually change what you should do.
On a large store, category and collection pages target the highest-volume commercial queries and usually contain a heading, a filter bar and nothing else. Supporting content on those pages tends to move more revenue than another product-description rewrite.
If the description shipped with the feed, every competitor selling the same SKU has the identical text. That is not a penalty, but it is a reason none of those pages can differentiate — which is why the ranking has to be earned by content the feed did not supply.
Check what your theme outputs before adding a schema app. Two sources of Product markup on the same page is a common cause of rich results quietly disappearing.
Generative engine optimisation is a different job from ranking. An answer engine lifts a passage and decides whether to credit a source — so the questions that matter on BigCommerce are whether AI crawlers can read the page, whether you control what they're told, and whether the page carries attribution they can resolve.
The pattern across every platform is the same: content quality is rarely what stops a citation — missing attribution is. Check what an engine can currently see with the free SEO tools, or read the SEO automation overview.
What is BigCommerce SEO automation?
How do you improve SEO on BigCommerce?
| Manual on BigCommerce | AutoSEO | |
|---|---|---|
| Keyword research | Occasional, when someone has time | Scheduled, before every article |
| Writing | In-house hours or a freelancer | AI-drafted, reviewed as much or as little as you want |
| Getting it into BigCommerce | Copy, paste, format, fix | Published through the API |
| Meta, schema, internal links | Remembered sometimes | Applied to every article |
| Refreshing old content | Rarely — nothing prompts it | Decay detection flags it |
| Rank + AI-visibility tracking | — | ✓ |
| Ongoing cost | Writers and tools billed separately | One subscription — see pricing |
Key takeaways
BigCommerce is a hosted SaaS ecommerce platform that gives merchants direct control over most technical SEO settings without requiring developer intervention. Unlike WordPress, BigCommerce separates SEO configuration into store-level settings, channel-level settings, and individual page settings — meaning the same product can have different metadata depending on which storefront channel it appears on. Understanding this architecture is the foundation of every BigCommerce SEO strategy.
BigCommerce generates pages from templates (called Stencil themes) that pull dynamic data from its API. This means your SEO output — title tags, canonical URLs, structured data — depends partly on your theme code and partly on what you enter in the control panel. A misconfigured theme can silently override every metadata field you set, which is one of the most common sources of BigCommerce SEO problems.
BigCommerce organizes content into distinct URL namespaces. Each content type lives under a predictable path prefix by default, and Google's crawler treats each prefix as a signal about content type. The default structure looks like this:
| Content Type | Default URL Pattern | SEO Implication |
|---|---|---|
| Category pages | /category-name/ | Flat, keyword-rich paths rank well for faceted navigation |
| Product pages | /product-name/ | No subfolder by default; avoids diluting product authority |
| Brand pages | /brand-name/ | Auto-generated; often thin unless enriched with content |
| Blog posts | /blog/post-name/ | Subfolder signals editorial content to crawlers |
| Web pages (static) | /page-name/ | Flat path; good for high-authority informational pages |
| Search results | /search.php?q= | Must be noindexed; BigCommerce does this by default |
BigCommerce does not nest products inside category paths (e.g., /category/product/). This is intentional and beneficial: it prevents duplicate URL problems when a product belongs to multiple categories. However, it also means category pages carry the full burden of topical relevance — they cannot borrow authority from product URL strings.
BigCommerce supports up to three levels of category nesting (parent, child, grandchild). Stores with large catalogs should audit whether grandchild categories receive enough internal links to be crawled regularly. Categories that exist in the control panel but appear nowhere in navigation or internal links will be crawled infrequently and may rank poorly even with strong content.
BigCommerce's built-in faceted filtering appends parameters to category URLs (e.g., ?brand=acme&color=red). By default, these parameterized URLs are not canonicalized to the base category URL, which means Googlebot can crawl thousands of parameter combinations and dilute crawl budget. The fix is to enable the Faceted Search setting under Storefront › SEO and verify that filtered URLs return a canonical tag pointing to the clean category URL.
BigCommerce exposes more native SEO controls than most hosted platforms. Here is where each setting lives and what it actually does.
Navigate to Store Setup › Store Settings › URL Structure to choose between two URL formats: with or without a trailing slash, and with or without a file extension. Pick one format and never change it after launch — BigCommerce does not automatically 301-redirect the old format to the new one for all page types. Changing URL structure post-launch requires a manual redirect import via Server Settings › 301 Redirects.
BigCommerce generates product URLs from the product name by default. You can override this with a custom URL slug on each product's Other Details tab. Always set custom slugs for products with long or keyword-poor names before the product is indexed. Changing a slug after indexing requires a 301 redirect, which BigCommerce can create automatically if you check Create a 301 redirect from the old URL when saving.
Every product, category, brand, and web page in BigCommerce has three metadata fields:
<title> tag; if left blank, BigCommerce falls back to the product or category nameThe store-level Homepage Title and Meta Description live under Storefront › SEO. These are separate from the channel-level overrides available in Channel Manager for multi-storefront setups.
BigCommerce automatically outputs a canonical tag on every indexable page. For product pages, the canonical always points to the product's primary URL regardless of which category the shopper navigated through. This is correct behavior. The problem arises when themes are customized: some theme edits accidentally duplicate the canonical tag or output a relative URL instead of an absolute URL, which some crawlers interpret inconsistently. Audit canonical output with a crawl tool after any theme update.
BigCommerce auto-generates an XML sitemap accessible at yourdomain.com/xmlsitemap.php. The sitemap includes products, categories, brand pages, web pages, and blog posts. It does not include:
Submit the sitemap directly in Google Search Console. BigCommerce does not auto-ping Google when the sitemap updates, so large catalogs with frequent product additions benefit from a scheduled re-submission or a third-party integration that triggers pings.
BigCommerce provides a default robots.txt that disallows several internal paths including /cart.php, /checkout, and /account. You can edit robots.txt under Storefront › robots.txt. Common additions include disallowing /search.php (already blocked by default), /wishlist, and any staging or preview paths. Do not disallow /cdn/ — BigCommerce serves product images and CSS from CDN paths, and blocking them prevents Google from rendering your pages correctly for Core Web Vitals assessment.
BigCommerce Stencil themes output Product schema (JSON-LD) automatically on product pages, including name, description, image, sku, offers, and availability. However, the default schema implementation has known gaps:
Script Manager is the correct place to inject additional JSON-LD without editing theme files directly, because it survives theme updates.
BigCommerce hosts on Google Cloud and includes a global CDN. Despite this, several platform-specific factors degrade Core Web Vitals scores:
These are errors that appear repeatedly on BigCommerce stores and are either caused by platform-specific defaults or by misunderstanding how BigCommerce handles SEO settings.
BigCommerce auto-creates a brand page for every brand you assign to a product. These pages default to a grid of products with no descriptive text. Google frequently treats them as thin content. Add a brand description in Products › Brands › Edit Brand and include the brand's primary keywords naturally in the first paragraph.
BigCommerce's Product schema includes a condition property. If you sell new products but leave the condition field unset, some theme implementations output no condition value, which can suppress price-drop and availability rich results. Set condition explicitly to New on all applicable products.
The default BigCommerce title tag format appends your store name to every page: Product Name | Store Name. For stores with long product names, this pushes the most important keywords past the 60-character display limit. Shorten the store name suffix or remove it from product and category pages using theme-level logic in templates/layout/base.html.
BigCommerce does not enforce a canonical domain at the platform level for all configurations. Verify in Store Setup › Store Settings › URL Structure that your preferred domain (www or non-www) is set, and confirm with a browser that the alternate version 301-redirects correctly. A missing redirect splits link equity between two versions of every URL on your site.
Under Products › Product Settings, BigCommerce can automatically hide products when inventory reaches zero. Hidden products return a 404, which loses any accumulated backlinks and ranking signals. Instead, keep out-of-stock pages live with a noindex tag or with an in-stock date estimate, depending on whether the product will return. Only 404 products that are permanently discontinued, and implement a 301 redirect to the closest category or replacement product.
Merchants using BigCommerce's Multi-Storefront feature (available on Plus plans and above) can run multiple storefronts from one control panel. Each channel has its own SEO settings that override store-level defaults. A common mistake is updating metadata at the store level and assuming it propagates to all channels — it does not. Audit each channel independently in Channel Manager › Edit Channel › SEO.
Most BigCommerce stores lose organic traffic not because they ignore SEO, but because they skip platform-specific setup steps that silently create duplicate content, orphaned pages, and unindexed product launches. This section walks through the exact on-page workflow for BigCommerce, then shows how AutoSEO compresses that workflow into a single automated pipeline.
BigCommerce generates multiple URL paths for the same product when it belongs to more than one category. A product sitting in both /tools/ and /sale/ gets two crawlable URLs by default. Fix this before writing a single word of content.
BigCommerce faceted search creates hundreds of filter-combination URLs—color, size, price range—that Google can crawl and index as thin duplicate pages. Left unmanaged, these dilute crawl budget and split ranking signals.
Category pages, not just product pages, drive the majority of BigCommerce organic revenue. Each category page needs a keyword-targeted H1, a 150–300 word introductory description above the fold, and a longer supporting section below the product grid.
BigCommerce does not automatically compress images or generate descriptive file names. Before uploading, rename image files using the target keyword and a descriptor—black-leather-wallet-front.jpg rather than IMG_4821.jpg. Fill the Alt Text field in the image upload dialog with a natural description that includes the product name. Use WebP format where your theme supports it to reduce page weight without a separate app.
BigCommerce auto-generates an XML sitemap at yourdomain.com/xmlsitemap.xml. Submit this URL in Google Search Console → Sitemaps and in Bing Webmaster Tools. After any major category restructure or product launch, re-submit the sitemap to prompt faster recrawling. Check the sitemap report monthly for URLs flagged as excluded or errored.
Internal linking on BigCommerce is often limited to the navigation menu and related-products widgets. Supplement these with manual contextual links inside category descriptions and blog posts. Link from high-traffic blog content to the relevant category or product page using anchor text that matches the target page's primary keyword. This passes crawl signals and distributes page authority across the catalog.
AutoSEO connects directly to BigCommerce via API and handles every stage of the workflow—research, writing, publishing, indexing, and rank tracking—without requiring manual exports or copy-paste into the admin panel.
| Pipeline Stage | Manual Approach | AutoSEO Approach |
|---|---|---|
| Keyword Research | Export product catalog, run keywords in a separate tool, map manually | AutoSEO scans your live BigCommerce catalog and assigns search-volume-ranked keywords to each product and category automatically |
| Content Writing | Brief a writer or write descriptions individually | AutoSEO generates SEO-optimized title tags, meta descriptions, and page descriptions in bulk using your catalog data and target keywords |
| Publishing to BigCommerce | Log into admin, navigate to each product or category, paste content, save | AutoSEO pushes title tags, meta descriptions, and descriptions directly to BigCommerce via the Catalog API—no admin login required |
| Index Request | Submit sitemap manually in Search Console; wait for Googlebot | AutoSEO submits updated URLs to the Google Indexing API immediately after publishing, reducing time-to-index from weeks to hours for eligible pages |
| Rank Tracking | Check rankings in a separate rank tracker; reconcile with revenue manually | AutoSEO tracks keyword positions for every optimized page and surfaces ranking changes alongside the specific content that was changed, so you can attribute movement to actions |
BigCommerce provides a solid technical foundation—auto-generated sitemaps, canonical tag output, and native Product schema—but it does not configure these correctly for every store setup. Multi-category products, faceted navigation, and paginated category pages all require manual decisions about canonicalization and crawl control. The platform gives you the tools; the configuration is your responsibility.
Disallow low-value filter parameter combinations in your robots.txt file and confirm that BigCommerce is applying canonical tags to filtered URLs pointing back to the root category page. For filter combinations with genuine search demand and distinct intent, write unique introductory copy and allow indexing. Audit your coverage report in Search Console quarterly to catch newly generated filter URLs that have slipped through.
Choose a URL structure that places the product name directly after the root domain or a single category segment—for example, /products/product-name/ or /category/product-name/. Avoid deep nesting beyond two levels. Once you have chosen a structure and your store has indexed pages, do not change it without setting up 301 redirects, as BigCommerce does not redirect old URLs automatically unless you enable that setting.
Yes. BigCommerce outputs standard Product schema by default, but you can extend it by editing your theme's product.html template in the Stencil framework or by injecting additional JSON-LD via a script tag in the Script Manager under Storefront → Script Manager. Common additions include FAQPage schema on product pages with Q&A sections and BreadcrumbList schema if your theme does not already generate it.
Blog posts on BigCommerce function as supporting content that builds topical authority and passes internal link equity to category and product pages. A buying guide targeting an informational query—such as how to choose a camping tent—can rank for that query and then link internally to your /camping-tents/ category with keyword-rich anchor text. This signals to Google that your category page is the authoritative destination for the commercial version of that topic.
The most common causes are: the page is blocked by robots.txt or a noindex meta tag added unintentionally through a theme or app; the page has not yet been crawled because it is not linked from any indexed page; or the page is marked as a duplicate because another URL with the same content has been canonicalized as the preferred version. Check the URL Inspection tool in Search Console for the specific page to identify which issue applies.
A newly published BigCommerce product page with a complete title tag, meta description, unique description, and at least one internal link from an indexed page typically gets crawled within one to two weeks. Ranking for competitive keywords takes longer—often three to six months—as Google assesses the page's relevance and the site's overall authority. Using the Google Indexing API or submitting the URL directly in Search Console can accelerate the initial crawl to within 24–48 hours.
BigCommerce's native blog is functional for basic content publishing—it supports custom URLs, meta fields, and image alt text—but it lacks features such as category taxonomy for posts, schema output for articles, and advanced internal linking tools. For stores where content marketing is a primary acquisition channel, some teams use a headless WordPress blog on a subdirectory path to access a richer content management environment while keeping link equity on the main domain. For most stores, the native blog is sufficient if content is well-structured and internally linked.
BigCommerce connects with your store hash + an API account access token. There is no plugin to install and no theme code to change; AutoSEO calls the BigCommerce API directly.
Only what you ask it to. New articles are delivered on the cadence you choose — as drafts for review, or published straight away. Existing pages are audited and surfaced as recommendations first; nothing is rewritten in place until you turn that on.
It depends on the domain, not the platform. An established site with existing authority usually sees movement on long-tail queries within weeks; a new domain in a competitive niche takes considerably longer. Publishing consistently is what compounds — which is the part automation actually fixes.
Plans are per site with volume discounts as you add more, and there is a trial. Current numbers are on the pricing page rather than repeated here, so they cannot go stale.
Yes. AutoSEO is built to sit alongside what you already run rather than take over the page head — on WordPress it writes into your existing SEO plugin's fields instead of adding a competing set of tags, and on every platform it leaves the platform's own SEO settings alone.
The connection publishes blog content. Product copy is generated and reviewed inside AutoSEO — it is not pushed into your catalogue automatically, and AutoSEO does not generate prices, SKUs or stock levels.
AutoSEO updates the existing BigCommerce post by its ID rather than publishing a second one, so the URL, its links and its ranking history carry forward.
Works alongside your existing BigCommerce setup. See pricing for plans and the trial.
Connect BigCommerce