BigCommerce SEO tips for products and URLs
Improve BigCommerce product and category SEO with URL settings, facet controls, metadata and storefront checks that protect catalogue discovery.
- Published
- Last updated
BigCommerce SEO tips start with accurate product and category metadata, stable URLs and a clear policy for filtered pages. Check the storefront’s output after each change: saved catalogue fields alone don’t prove that customers or search engines receive the intended page.
Work through one product family before changing the whole catalogue. A theme update, import or custom storefront can affect many pages at once, so keep the previous settings and a small release sample.
Map the store’s SEO controls
Separate catalogue settings from the code that renders them before assigning the work. BigCommerce’s control panel holds product and category fields. A Stencil theme or headless storefront determines how those values appear in the delivered page.
Use this responsibility map for the store you operate.
| Area | Catalogue or store owner | Storefront developer |
|---|---|---|
| Product and category copy | Maintain names, descriptions and SEO fields | Render the intended fields without duplicate tags |
| URL changes | Approve destination paths and retain old URLs | Confirm routing and redirects on the public domain |
| Filters | Maintain attributes and visible filter choices | Inspect generated URLs and crawl controls |
| Page output | Supply accurate stock and product information | Maintain headings, structured data and loading behaviour |
Confirm permissions before scheduling a bulk change. BigCommerce lists Manage Settings for store settings, product-editing permissions for products and category-editing permissions for categories. Its user permissions reference also identifies a separate 301 Redirects permission.
Record the storefront channel, domain, active theme or headless release, current URL settings and proposed change owner. Export the affected catalogue values and redirect records where available. Save the previous template version separately. A rollback record must identify which values to restore and who can restore them.
Set product and category metadata
Give each product a title and description that distinguish it from its parent category and neighbouring products. Open a product’s SEO section for its page title and meta description. Category SEO fields sit under Products, Product Categories and the category’s edit screen.
For a hypothetical outdoor retailer, use these examples only where the catalogue supports the stated features.
| Page | Page title | Meta description |
|---|---|---|
| Parent category | Waterproof hiking jackets | Ridge Outfitters | Compare waterproof hiking jackets by weight, hood design and intended use. Explore lightweight shells and insulated options. |
| Lightweight product | Creek lightweight waterproof jacket | Ridge Outfitters | Explore the Creek waterproof shell with an adjustable hood and packable design. Check available colours, sizes and product details. |
| Insulated product | Summit insulated waterproof jacket | Ridge Outfitters | See the Summit waterproof jacket with insulated lining. Compare its features and choose from the sizes and colours available. |
Write the visible descriptions with the same distinctions. A category helps customers choose across the range. Each product explains its own construction and use. Keep claims such as waterproofing tied to the manufacturer’s specifications.
BigCommerce supports product metadata through CSV imports, as its SEO fields guide explains. Review the mapped SEO columns before importing. An older export can replace individual edits with stale values if those columns are included in the update.
Treat template defaults as a separate check. If the live title ignores a saved product title, inspect the theme’s field selection and fallback logic. A shared default or headless title template can make individually edited pages display the same text. Compare the saved field with the final HTML before rewriting the catalogue again.
Control custom URLs and redirects
Inspect the existing product and category URL formats before choosing a replacement. Open URL Structure under Settings and record the selected formats alongside several real product URLs. Keep working URLs unless a specific navigation or maintenance problem justifies changing them.
For an approved URL-format change, follow this sequence.
- Build an old-to-new path list for the affected products and categories. Include URLs used in navigation and links from other sites.
- Save the intended format, then review the Update action’s scope. BigCommerce distinguishes untouched URLs from all URLs, including customised ones.
- Select creation of 301 redirects for old URLs when applying the update. Retain the mapping with the release record.
- Request an old URL directly. Expect a permanent redirect to the intended new page, followed by a successful response.
- Inspect the destination’s canonical URL, the HTML declaration of its preferred address. It must name the intended public page without an old path or preview domain.
For example, an old /products/creek-jacket/ link might move to /creek-waterproof-jacket/. Record that exact pair. Confirm the destination displays the Creek jacket, then update internal links to the new address so they avoid the redirect.
On a headless storefront, give the developer the mapping too. A redirect stored in the commerce system still needs an observable result on the domain customers visit. If an old link returns an error there, inspect that storefront’s routing before repeating the catalogue update.
Keep facets from multiplying search pages
Choose which category pages deserve search visibility before exposing every filter combination to crawlers. In the jacket example, /waterproof-hiking-jackets/ is a useful category. Colour, size and sort combinations mainly help customers narrow that range.
BigCommerce documents automatically added robots.txt rules for URLs containing _bc_fsnf=1. Those rules are visible in the delivered robots.txt even though they aren’t shown in the settings editor. Read its robots.txt instructions before adding another rule.
First open the actual filtered URL and the public robots.txt on the same storefront. Compare the parameter spelling with the rule. A custom headless filter can generate different URLs, so don’t assume the native pattern covers it. Sort-only URLs also need their own inspection.
If “lightweight waterproof jackets” warrants a lasting landing page, create a useful category with its own copy and internal links. Don’t make every possible colour-and-size combination a search landing page.
Google’s faceted navigation guidance distinguishes crawl prevention from canonical hints. A canonical can suggest a preferred version, while robots.txt controls crawl access. A blocked crawler cannot read a page’s new canonical or noindex instruction. Keep already-indexed URLs separate from the decision about future crawling.
Have the developer document the chosen treatment for each URL pattern. Keep the parent category and product pages crawlable. Test narrow patterns against real URLs before changing a broad robots rule that could hide the whole range.
Check storefront markup and speed
Inspect headings and product structured data in the actual storefront, including any customised product template. BigCommerce’s Cornerstone base template renders the supplied head title and metadata. Its product page also includes a product schema component. Custom themes and headless implementations need their own output check.
Open a product and inspect both its initial HTML and rendered page. Confirm the visible main heading identifies the product. Check that its title and description match the intended fields. Find every Product structured-data declaration so an app and the theme don’t publish conflicting prices or stock states.
Use Google’s merchant listing requirements to validate the relevant Product and Offer properties. Compare the reported price, currency and availability with the customer-visible offer. Run the Rich Results Test, then inspect the published URL. Valid markup creates eligibility for supported search appearances, without guaranteeing a rich result.
Check mobile loading separately. Compare a product and a category before and after the release under the same device and connection conditions. Inspect oversized product images, delayed main images and scripts that delay interaction. Assign image sizing or template work to the developer, and remove unused third-party scripts through their owner. A saved SEO setting doesn’t establish a ranking improvement.
Validate a catalogue release
Release a small sample first and record the result on the published storefront. Include a changed product, an unchanged sibling, their category and a filtered URL. Add an unavailable item to catch stock and routing differences.
| Sample | Expected outcome | Failure to investigate |
|---|---|---|
| Changed product | New URL returns 200, intended metadata appears and canonical names that URL | Wrong product, old canonical or repeated default title |
| Old product URL | 301 reaches the intended product without a loop | Error, chain or unrelated destination |
| Unchanged sibling | Existing URL and individual metadata remain intact | Bulk update overwrites the sibling |
| Parent category | Returns 200 with distinct category copy and intended canonical | Category blocked or canonical points elsewhere |
| Filtered page | Customer filters work and crawl treatment matches the recorded policy | New URL pattern escapes the chosen controls |
| Unavailable item | Page status, purchase state and structured availability agree | Purchasable offer remains in markup after the page disables buying |
In Search Console, inspect representative destination URLs and compare the declared canonical with Google’s selected canonical. Check the sitemap after URL changes. Watch indexing exclusions and impressions for the affected category and product group against their earlier baseline.
If useful pages lose discovery, inspect crawl access, internal links and redirects first. A simultaneous rise in blocked category URLs is a specific lead. A short-term impression change alone doesn’t identify the cause.
Run a BigCommerce SEO audit
Audit one product, its category, a faceted URL and an unavailable item before expanding the crawl. Start with access and status codes, then inspect the page content and loading behaviour.
- Request each URL without signing in. Record its status, redirect destination and robots access. Confirm public products and categories remain reachable through ordinary category links.
- Inspect title, description, main heading and canonical. Compare the output with saved catalogue fields and the intended search page.
- Follow the category’s product links and the product’s breadcrumb links. Repair destinations that fail or send customers through outdated paths.
- Validate product structured data against the displayed offer. For unavailable items, decide whether the page remains useful during a temporary stock gap or needs a permanent retirement treatment.
- Load the pages on mobile and inspect the main image and first usable interaction. Compare results after a correction under the same test conditions.
Prioritise corrections by their effect on discovery. A blocked product family or broken category takes priority over a weak description on one product. Give each finding an owner and a published-page recheck, using this model.
| Finding | Correction owner | Recheck |
|---|---|---|
| Wrong saved product title | Catalogue manager corrects the SEO field | Published HTML uses the corrected title |
| Correct field but wrong output | Stencil or headless developer repairs field selection | Product and sibling render their own titles |
| Old link returns an error | Store manager records the redirect; developer checks public routing | Old URL reaches the correct live product |
| Category unexpectedly blocked | Store settings owner and developer locate the responsible rule | Category is crawlable and reachable internally |
| Markup shows stale stock | Catalogue manager checks source stock; developer repairs the output | Visible availability and structured data agree |
For priorities across the wider catalogue, use the ecommerce SEO audit guide. Wholesale access and catalogue design need separate decisions covered in the BigCommerce B2B guide.
Close each finding only after its owner repeats the failed check on the published page. Keep the same sample for the next import or theme release so a repaired title, redirect or stock declaration can’t silently regress.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.