Bigcommerce SEO agency

BigCommerce SEO using what is already built in: URL paths you control, the redirect manager, filter pages decided on purpose, category templates with content.

BigCommerce gives you more SEO control out of the box than most hosted platforms, and most stores use very little of it. URLs are not forced into a fixed prefix, so product and category paths can be shaped to match how people search. There is a redirect manager in the admin, so URL changes do not have to cost you the rankings the old page held. Robots access can be edited per storefront. The theme templates can carry real content on a category page rather than dropping straight into a product grid.

What needs deciding is the faceted filtering. BigCommerce can generate filtered views of a category, and on a catalogue with many options that produces a very large number of near-identical pages. A few of them describe things people genuinely search for and deserve to be indexable. The rest should be usable and invisible.

The other recurring issue is multi-storefront. Running several storefronts from one catalogue is useful, and it becomes a problem when the same product text appears on all of them with nothing to tell them apart.

We work in your store, keep changes in the template so they apply catalogue-wide, and use the redirect manager rather than the theme.

Native on BigCommerce

URL paths that can be set per product, category and page without a forced prefix
The built-in 301 redirect manager in the admin
Stencil theme templates, so category pages can hold content above and below the grid
Product filtering that generates its own filtered views of a category
Multi-storefront, with separate domains, content and settings from one catalogue
Editable robots access per storefront

Settings that matter

Decide the URL pattern before the catalogue grows

Because BigCommerce lets you set the path rather than inheriting a fixed structure, the decision is yours and it is much cheaper to make early. We choose a pattern that keeps category context where it helps and stays short, apply it consistently, and write it down so new products follow it. Changing the pattern later is possible, and every change becomes a redirect you have to maintain.

Keep every redirect in the built-in manager

The admin holds redirects as records you can list, search and export. That matters more than it sounds, because redirects scattered through theme files or a third-party layer become invisible to whoever inherits the store. We move any existing ones into the manager, remove chains where one redirect points at another, and add a step to the catalogue process so a renamed product always leaves a redirect behind.

Choose which filtered views can be indexed

Filtering is good for shoppers and dangerous for crawling. We look at which filters map to real search demand, usually a single attribute inside a category, and make that small set indexable with its own heading and content. Everything else stays available to shoppers and closed to crawlers. On a large catalogue this is the highest-value technical decision on the store.

Give category templates somewhere to put content

A default category page is a heading and a grid, which is not enough to rank for a competitive term. We use the theme templates to add regions for an introduction, a buying guide, comparison content and questions, positioned so a reader sees them without scrolling past fifty products. Because it is in the template, every category gains the capability at once and your team can fill them over time.

What we avoid

Letting every filter combination be crawled on a large catalogue, which spends crawling on pages that cannot rank
Running several storefronts on the same product descriptions with nothing to distinguish them
Changing product URLs in bulk without checking the redirect manager caught each one

Questions

Yes, if every old path gets a redirect and you do it once rather than repeatedly. The redirect manager makes this manageable at catalogue scale. Expect a period where positions move while the new URLs are recrawled and the old ones are dropped, and do not make a second structural change during it.

It can, on a catalogue with many attributes, because the number of possible filtered views grows quickly. The filtering itself is good for shoppers and worth keeping. The work is deciding which views are worth indexing and closing the rest, so crawlers spend their time on categories and products rather than on combinations nobody searches for.

Each storefront is its own site as far as search engines are concerned, with its own domain and its own content. That is an advantage when the storefronts serve genuinely different markets with different language, pricing and product ranges. It becomes a liability when they share the same descriptions, because you have created several pages competing to answer the same query.

Yes, to a useful degree. Robots access is editable per storefront, page-level indexing can be controlled, and canonical behaviour is handled for the common cases. What you cannot do is treat it like a self-hosted site where every rule is yours. We work within that, which in practice covers everything a store actually needs.

Send your BigCommerce store.

The plan is written for your store on the platform it runs on.