SEO · BigCommerce
BigCommerce SEOfor category and product.
Which category should rank, which facets should not, and a front end that actually prints the fields. The catalog stays.
The short answer
Index the category you meant.
BigCommerce SEO is category and product indexation on the catalog you already run. Faceted URLs, brand pages, and a deep category tree can all target the same query. If a headless front end forgot the SEO fields, the admin can be perfect and the HTML still empty. We set canonicals, choose which level should rank, and check that the storefront prints the title. This is not a move off BigCommerce and not a Stencil reskin.
Catalog URLs
Stay on the platform. Fix which URL owns the query.
This fits when BigCommerce is home and the argument is structural. You have categories, products, and maybe brand pages. Search is splitting a query across a parent category, a child, and a facet. Or a headless storefront is rendering a pretty page with a default title. The data is in the admin. The HTML does not show it.
It is the wrong fit when you are choosing the platform, rebuilding checkout, or inventing price lists. Those are web projects. SEO can list the URL rules early so the build does not ship faceted duplicates, but it cannot substitute for the catalog work. We will not write category essays for a tree you plan to delete.
- The catalog is staying on BigCommerce.
- Headless or Stencil, the live HTML has to match the SEO fields.
Facets and fields
Pick the ranking level. Canonicalize the rest.
We choose which category level should own a query and make the others support it with links, not duplicate introductions. Faceted navigation should canonicalize to the category unless a facet is a real, stocked way people shop and has unique copy. Product SEO fields get filled where the product name collides with another item. Custom URLs are edited only with a redirect from the old path.
On a headless storefront we read the rendered HTML, not the admin preview. Title, canonical, and description have to be present. If the front end dropped them, the fix is in that template. On Stencil, the same check is simpler and still required. Guides that are not products should not sit on a URL that imitates a category you already sell.
- One category level assigned to each priority query.
- Facets canonicalized unless a facet is a true shopping hub.
- Rendered HTML checked for title and canonical, especially if headless.
Mistakes
A facet for every option, and fields the theme ignores.
Faceted URLs feel like free landing pages. They are usually copies of the category with a parameter. Indexing them splits the query and creates a cleanup later. We do not staff a program of writing a paragraph for every facet. We keep the facet out of the index and put the effort on the category.
The headless mistake is assuming the platform field is live because it is saved. The storefront repository is what the crawler sees. A deploy can wipe a canonical. SEO on BigCommerce includes that check or it is guessing. We also avoid a blog on a separate domain that targets the same categories with no plan to consolidate.
- No indexed facet per color, size, or sort.
- No assumption that a saved SEO field is in the HTML.
- No second site for guides that should reinforce the category.
Rendered result
The category URL is the one in the results.
Priority queries should show the chosen category or product as the landing page. If a facet or a brand URL is receiving them, the canonical or the internal links are unfinished. We report those landing pages, not one visibility score for the catalog.
On a headless storefront we recheck rendered titles after a deploy. That regression is invisible in the admin. Redirects from changed custom URLs are tested from the export. Coverage should move toward categories and products you kept.
- Landing URL for each priority category query.
- Post-deploy check of rendered titles on headless storefronts.
- Redirects tested when a custom URL changes.
Example engagement
A specialty retailer whose facets outranked the category.
Specialty retailer on BigCommerce, Stencil theme, wholesale prices already handled in the platform. The parent categories had unique copy. Faceted URLs for material and size were indexable and had started appearing for the category queries. A separate blog subdomain repeated the same topics and did not link back in a consistent way.
We kept Stencil and did not replatform. Facets were canonicalized to the parent category. The blog posts that targeted a category were edited to link to that category URL and stop carrying a competing title. Custom URL changes from an old cleanup got the missing redirects. The rendered category title on the storefront matched the field in the admin. The wholesale price lists were left alone. They were not the SEO problem.
Facets
Facet URLs canonicalized to the category that should rank
HTML
Storefront titles matched the fields saved in the admin
The example uses anonymized results from a Quorum engagement. It is one account, not a benchmark you should budget against.
Questions
BigCommerce questions.
Do brand pages help or hurt?
They help when shoppers search the brand and you have enough products and copy to justify the URL. They hurt when a brand page and a category page target the same wording. We pick one owner for that query instead of keeping both 'for coverage.'
What if our storefront is headless?
Then the SEO fields are only as real as the front-end template. We read the HTML after deploy. If the title is missing there, filling the admin again will not change what is crawled. The fix is a template change, scoped as that, not as more product copy.
Should every subcategory have a long description?
No. The level that should rank gets the introduction. Deeper levels that exist for browsing can stay thin and point upward. A paragraph on every node creates duplicates. Depth is a catalog choice, not an SEO quota.
Will you change our price lists or customer groups?
No. Those are merchandising rules. SEO does not rewrite who sees which price. If a customer-group URL is accidentally public and indexable, we will close that, because a private price does not belong in search.
Can this wait until after a replatform?
If you are leaving BigCommerce, do not invest in category copy that will be discarded. Do invest in a URL map. If you are staying, facet and canonical fixes are worth doing on the current store. We will not run both stories at once.
More in this lane
Other SEO platforms.
Talk through bigcommerce.
One conversation. A diagnostic. A plan you can kill if it is not the work.