A new storefront reused every product URL
Channel two went live. The same paths now serve two brands or two countries. Sitemaps overlap. We name which channel owns which public URL. Sharing stock is not the same as sharing paths.
BigCommerce SEO
BigCommerce SEO to Split Storefronts From One Catalog
BigCommerce can share one catalog across channels. Each storefront still publishes its own product and category URLs. We name which channels may go live. We keep product paths stable when you move a category. We make custom fields print in the theme, not sit in admin.
- Channel
- Category
- Field
- Script
Position
One catalog. Each channel still needs its own pages.
BigCommerce is not Shopify Markets, and it is not a Magento rewrite table. It is a catalog that can feed more than one storefront. Search intent has to be true on the HTML that channel actually serves. A Page Builder preview while you are logged in is not that HTML.
Catalog rules on any stack
Ecommerce SEO writes which product and filter classes may be documents, platform aside. Stay here when the leak is a BigCommerce channel, a nested path, or a field the theme never prints.
Open ecommerce SEOAdobe Commerce
Magento SEO owns URL rewrites and store views. BigCommerce channels and custom URLs are a different admin. Open Magento SEO if that is the stack.
Open Magento SEOA Shopify store
Shopify uses theme HTML, apps, handles, and Markets. This page assumes BigCommerce. A move onto or off BigCommerce is migration work.
Open Shopify SEOA one-time catalog snapshot
An ecommerce SEO audit ranks crawl waste and thin templates, then it stops. This program is the channel and URL settings merchandising has to keep after the report.
Open ecommerce SEO auditWe start with channels. Then category and product URLs. Then custom fields the Stencil theme prints. Then Script Manager and apps. Catalog rules that would be true on any stack stay on ecommerce SEO. Magento, Shopify, and WooCommerce keep their own pages. Fetch after a theme deploy stays on technical SEO.
We will not nest five category folders into a product URL to look tidy. We will not turn on a second channel that copies every product path. We will not treat a marketplace SEO app as the whole program. If the stack is Magento, open that page.
When this fits
When a second channel copied the catalog
This page fits when BigCommerce itself is the constraint: channels, product URLs, nested categories, custom fields, or scripts. If you needed a catalog rule that travels, Magento rewrites, or Shopify theme work, start there instead.
Moving a product changed its public path
You dragged it to another category. The URL followed the tree. Ads and links still hit the old path. We keep the product URL stable. Breadcrumbs can change. The path should not.
Unique specs sit in custom fields the theme never prints
Editors filled the fields. View-source does not show them. Keyword targeting in admin is not enough. The Stencil template has to output the spec.
Script Manager or an app added extra URLs
A landing or filter script published pages the theme never meant as documents. We inventory scripts and apps before anyone adds another SEO app from the marketplace.
Process
Channel, category, field, script
Four BigCommerce jobs in order. Each one ends with a note admin can keep. We do not start a Catalyst rebuild in the last step. The point is a storefront whose product URLs stay put when merchandising moves a SKU.
-
Channel
We list storefronts and channels already live. Which ones are real catalogs. Which only change currency or a banner. Topical relevance is the test: does this channel match a real shopping job, or is it a copy of channel one? Admin theme editor is not a fetch.
Outcome A channel list that says which storefronts may publish.
-
Category
We map product and category URLs. Nested trees. Custom URLs already set. Redirects in the 301 manager. Keyword targeting stays one job per money template. A category move must not mint a new product path.
Outcome A URL map merchandising can follow when they move a SKU.
-
Field
We name custom fields the Stencil template must print. Specs you sell. Fit. Materials. Keyword density in a hidden field is not a BigCommerce score. If the unique sentence is only in admin, we put it on the page.
Outcome A field list the theme must output, plus where it prints.
-
Script
We inventory Script Manager, marketplace apps, and faceted search. Semantic keywords belong on the kept category, not as extra script URLs. Coverage on the named set is the watch. A ranking report for every filter mix is not.
Outcome A script and app list that says what may publish URLs.
Deliverables
What BigCommerce admin can keep after we leave
You leave with a channel list, a URL map, a field print list, and a script allow list. You do not leave with a Magento rewrite table, a Shopify theme pass, or a ranking date.
Channel list
Which storefronts may publish. Which share stock but not paths. Dated. Last quarter's screenshot is not this list.
Product URL rule
The path a SKU keeps when merchandising moves it. Nested categories can stay in crumbs. They should not rewrite the public URL.
Field print list
Custom fields that must appear in the first HTML. A field that only lives in admin is named as missing.
Redirect log
Paths already moved, plus 301s that should have shipped the same week. A campaign rename is not a reason to skip the log.
Script and app list
What may emit URLs or extra canonicals. A second SEO app is named. An empty cell is not a decision.
Benefits
What a new channel should not copy
Two storefronts stop sharing one product URL
Stock can still be shared. Public paths get a owner. Sitemaps stop overlapping.
Category moves stop breaking links
Merchandising can refile a SKU. Ads and reviews still hit the same product URL.
Specs stop living only in admin
Custom fields print. Crawlers and shoppers see the same facts.
Scripts stop inventing extra pages
The next marketplace app is a decision. It is not a default.
Methodology
Who can launch a new channel
This works when one person can edit storefront URLs, and one person can refuse a new channel. If both are missing, we are touring BigCommerce settings. We are not holding a catalog.
We start with the products that must work this month, the channels already live, and the person who can edit a custom URL. If any of those is missing, we name it first.
We fetch published HTML on the public storefront. We do not trust Page Builder while you are logged in. Does this category match a real assortment? Is this channel a store, or only a price list?
You may rename the roles below. You may not leave channel launches implied. An implied storefront is how a brand site copies the whole catalog overnight.
- BigCommerce SEO lead SEOConsultants.ai writes the channel list, the URL rule, and the field print list. We do not become your BigCommerce agency because the SKU count is large.
- Whoever owns BigCommerce admin Can edit channels, URLs, theme files, and Script Manager. A locked agency seat with no editor is a finding.
- Merchandising Names real categories and whether a product URL may move. Moving a SKU must not mint a new public path.
- Whoever installs apps and scripts Stops URL generators the script list did not approve. They do not need to write Stencil for that.
- Leadership Funds theme field work or refuses another channel this period. An unread coverage sample is not a failure of this page. A ranking promise would be.
First working session
Start with the channel that went live last
The first hour is the newest storefront, plus one product whose URL changed when you moved a category. It is not a tour of the app marketplace.
We list channels. We pick a money SKU. We open every public URL BigCommerce currently serves for it. If two channels share one path, that is the job. If two categories share one unique paragraph, we merge or rewrite before we touch titles. If the real question is catalog classes that would be true off BigCommerce, that is ecommerce SEO. If the store is mid-cutover, that is migration SEO.
Then we fetch published HTML, robots, and sitemaps per channel. We compare that to Search Console. The extra paths are usually the job. A Stencil preview while you are logged in is not evidence.
We leave with a first list or a stop. A list names the channel, the kept product URL, and who may launch the next storefront. A stop names what is missing: admin access, a merch owner, or a stack that is not BigCommerce. Both are outcomes. A marketplace roundup is not.
AI search
A BigCommerce SEO app is not an AI Overview
Honest product HTML on the channel you keep can help later extraction. This page cannot sell AI Overviews, a shopping-chat mention, or LLM visibility as a score.
People ask whether a marketplace SEO app will land SKUs in Google AI Overviews (AIO). If two channels share paths, or if unique specs never print, generative search has copies or nothing honest to lift. That is ours to tidy. If the kept page already tells the truth and models still invent SKUs, that is an AI search audit. A program across search UIs is AI SEO.
The spec has to print on the live channel
AI search needs a page it can fetch. A custom field the template never outputs does not help. We do not sell Overview presence.
The name on that page should match the product you sell
We check brand and product names in the published HTML. That is entity optimization as a storefront input. It is not a Knowledge Graph project from this page.
Measuring model answers is another URL
LLM visibility needs a sentence a model can quote, then measurement on LLM SEO. Unique BigCommerce HTML can make a SKU look real. It does not sample answers.
Schema
Markup follows the channel you keep
JSON-LD helps a machine read a product the page already states. This work can stop the theme and an app from injecting two Product blocks. It is not a schema campaign as the whole job.
One Product block on the kept URL
If Stencil and an SEO app both inject markup, we pick one. Valid types still need facts that match the HTML.
No FAQ stuffing on a category grid
We refuse FAQ blocks that exist only to host more terms. A real spec question can live on the product template.
Extra fields do not buy a shopping mention
Markup will not force generative search to cite the SKU. A paid Shopping placement is a different job.
Who we work with
The person who can edit a custom URL
Someone has to refuse the next channel. We work with that person. We do not replace them with a second BigCommerce retainer.
BigCommerce admin owner
Ships channels, URLs, theme fields, and Script Manager. Rechecks after a Stencil update.
Merchandising
Names real categories and whether a product URL may move. Holds the path rule when a campaign wants nested folders in the URL.
Apps or ads already in motion
Can keep going once public paths are honest. If they try to run this as Merchant Center only, two jobs collide. Paid Shopping still belongs on shopping ads.
Questions
Frequently asked questions
Is a BigCommerce channel the same as a Magento store view?
No. Magento store views live inside one Adobe catalog and rewrite table. A BigCommerce channel is a storefront that can share inventory while still publishing its own URLs. We set which channels may publish. We do not import Magento rewrite rules into BigCommerce admin.
Should the product URL keep every parent category?
Usually no. Nested categories help merchandising. They should not force a long public path that changes when you move a product. We pick a stable product URL. Breadcrumbs can still show the tree. Moving a category should not mint a new product path.
Do custom fields count if the Stencil template never prints them?
No. Search intent has to show in the HTML a crawler gets. A custom field that only lives in admin is not on the page. We name which fields the template must output. Keyword targeting in a hidden field is not a BigCommerce plan.
Is Catalyst or headless BigCommerce this page?
Only when the live storefront still uses BigCommerce URLs and Stencil or a theme you control. A full headless build with a custom front end is closer to custom SEO plus technical SEO. We will not sell a Catalyst rebuild as the first step on this URL.
Will a marketplace SEO app get products into AI Overviews?
No. An app cannot buy a place in Google AI Overviews (AIO). Honest product HTML on the channel you keep can help AI search later. It does not sell a generative-search mention or an LLM visibility score. If the page already tells the truth and a model still invents a SKU, that work sits on an AI search audit and on LLM SEO.
On this BigCommerce channel
Did a new channel publish the same product URLs twice?
Send the live storefront, BigCommerce admin, and whether a second channel is on. We will say if the leak is a shared URL, a nested category path, or a field the theme never prints. Then we name the next setting to change.
- Channels that are real storefronts
- Product URLs that survive a category move
- Custom fields that print in HTML
- Scripts that do not spawn extra pages
Channels named. Paths held. Fields that print.