E-Commerce

BigCommerce B2B SEO for Wholesale Stores

F
Faris Khalil
Apr 16, 2026
19 min read

BigCommerce B2B stores hide most of their commercial value behind login walls. Customer-specific price lists, wholesale-only catalogues, quote request funnels, and net-30 invoicing pages only render for authenticated buyers. Google crawls as an anonymous shopper. What Google sees is a stripped-down storefront that looks like a retail site, not the full B2B capability underneath.

We’ve built and optimized B2B BigCommerce stores for wholesale distributors, industrial suppliers, and multi-brand manufacturers. The pattern is always the same: a store with $3M in annual wholesale revenue that generates zero organic traffic for its B2B keywords. The catalog is rich. The pricing is competitive. But Google can’t see any of it.

This post breaks down how to rank a BigCommerce B2B store in organic search despite gated pricing and restricted catalogues. Real admin paths, real Stencil template fixes, and the specific architecture that surfaces a wholesale portal to the buyers actively searching for it.

Table of contents

The gated-content SEO problem on BigCommerce B2B

BigCommerce B2B Edition and the B2B features on Enterprise let merchants configure customer groups with dedicated price lists, product visibility rules, and payment terms. A wholesale customer sees $18/case pricing. An anonymous visitor sees a “login to view wholesale pricing” message or nothing at all.

Google crawls as an anonymous visitor. It sees the login-gated version of every product and category page. The consequences are specific:

  • Product pages look empty. Core information like price, volume discounts, and case-pack options are hidden. Google indexes a product title, one image, and a “request quote” button. That’s not enough content for Google to understand what the page is about, let alone rank it.
  • Category pages show zero products. When product visibility is restricted to approved buyers, anonymous crawlers land on a category page with an empty product grid. Google treats this as a soft-404.
  • Commercial intent is invisible. The wholesale value proposition, tiered pricing, net-30 terms, case packs, lives behind the login. Google can’t index what it can’t see.
  • Sitemap includes URLs that return soft-404s. BigCommerce’s default sitemap generator doesn’t check customer group visibility. It lists every product URL, including ones that show empty pages to anonymous visitors. Google crawls them, finds thin content, and your crawl budget gets wasted on pages that actively hurt your quality score.

The standard B2C SEO playbook falls apart here. Optimizing product pages for “wholesale mens t-shirts case pack” fails when the page visible to Google doesn’t contain any of those terms in indexable content.

Setting up restricted catalogues correctly

BigCommerce B2B Edition controls catalogue visibility through customer groups. Open your control panel and go to Customers > Customer Groups. Each group has a “Category Access” tab. This is where you define which product categories a group can see.

Here’s the setting most agencies get wrong: category visibility doesn’t cascade to sub-categories. If you restrict the “Wholesale” parent category to the “Approved Dealers” customer group, the sub-categories under “Wholesale” are NOT automatically restricted. You have to set visibility on every single sub-category individually.

We discovered this on a building materials store that had 14 sub-categories under their wholesale parent. The parent was locked down. Twelve of the sub-categories were wide open. Anonymous visitors (and Google) could see wholesale pricing on 80% of the B2B catalogue. The store owner had no idea because they only tested access to the parent category page.

The audit process:

  1. Go to Customers > Customer Groups
  2. Click the “Guest” group (this is what Google sees)
  3. Open the “Category Access” tab
  4. Walk through every category and sub-category in your tree
  5. Confirm that every B2B-only category shows “No Access” for the Guest group

This takes 20 minutes on a store with 50 categories. Skip it and you’ll have wholesale prices indexed in Google Shopping results within a week. We’ve seen it happen.

Price list configuration and the SEO trap

Price lists live at Products > Price Lists in the BigCommerce admin. They let you assign custom pricing to specific customer groups without modifying the base product price. This is core B2B functionality: Dealer Group A gets 30% off, Distributor Group B gets 45% off, and retail customers see the MSRP.

The SEO trap is in how price lists interact with Product schema. BigCommerce’s default Stencil theme outputs Product JSON-LD with the price field pulled from whatever the current visitor sees. For anonymous visitors, that’s the retail price. Fine. But here’s the problem: if you’ve configured a price list to show “$0.00” or “Call for pricing” to visitors who don’t belong to any customer group, that value ends up in your Product schema.

Google Shopping rejects products with a $0 price. Google’s Rich Results Test flags it as an error. Your product pages lose their rich snippets.

The fix is straightforward. Open your Stencil theme and find templates/pages/product.html. Look for the JSON-LD block. The price output typically uses {{product.price.without_tax.value}}. Wrap it in a conditional:

{{#if product.price.without_tax.value}}
  "price": "{{product.price.without_tax.value}}",
{{else}}
  "price": "{{product.price.rrp_without_tax.value}}",
{{/if}}

This falls back to the recommended retail price when the visitor-specific price is empty or zero. The RRP field (rrp_without_tax) is set at the product level and doesn’t change based on customer group. It gives Google a valid price for schema while keeping customer-group pricing intact for logged-in buyers.

One more price list gotcha: bulk pricing rules and price lists conflict. If a product has both a bulk pricing rule (e.g., “buy 10+ get 15% off”) and a price list entry for the same customer group, the price list takes precedence. The bulk discount never fires. We’ve seen stores spend months troubleshooting “broken” bulk discounts when the real issue was a price list override they forgot about.

BigCommerce has a checkbox on every product and page: “Hide from search results.” The label is misleading. This checkbox removes the item from BigCommerce’s internal site search. It has absolutely nothing to do with Google.

Checking “Hide from search results” does not add a <meta name="robots" content="noindex"> tag. It does not remove the URL from the XML sitemap. It does not block Googlebot. The page remains fully crawlable and indexable.

We’ve audited stores where the agency’s entire B2B SEO strategy was checking this box on wholesale products. They believed Google couldn’t see those pages. Google had indexed every single one of them, complete with “Login to view pricing” as the meta description in search results.

If you need to prevent Google from indexing a page on BigCommerce, you have two real options:

  1. Theme-level noindex. Add <meta name="robots" content="noindex, follow"> to the <head> section of the relevant Stencil template. For product pages, this goes in templates/pages/product.html inside a conditional that checks product visibility or a custom field flag.
  2. robots.txt. Go to Server Settings > Robots.txt in the BigCommerce admin. Add Disallow rules for the URL patterns you want blocked. This prevents crawling entirely, but it also means Google can’t follow internal links on those pages to discover your public content.

Theme-level noindex is the better approach for B2B. The pages stay crawlable (so Google can follow links from gated pages to your public wholesale landing pages) but they don’t appear in search results.

The architecture that ranks B2B BigCommerce stores

The B2B SEO fix is not to expose gated pricing to Google. The fix is to build a parallel public-facing content layer that explains the B2B offering, targets commercial keywords, and funnels qualified buyers into the login/application flow.

The architecture has four parts:

1. Public wholesale landing pages. One page per product category explaining the wholesale offering in that category. Content covers product range, case pack sizes, MOQs, tier pricing structure (without specific dollar amounts), lead times, and who this product category serves. Optimize these for category-level B2B keywords like “wholesale mens t-shirts” or “bulk hoodies for print shops.”

These pages don’t show wholesale prices. They describe the offering and funnel to the wholesale application.

2. A public dealer application page. One page explaining the application process, who qualifies, what documentation is required (business license, resale certificate, EIN), and how long approval takes. This page targets transactional keywords like “apply for wholesale account” or “become a [category] wholesaler.”

3. Public FAQ and content pages about your B2B workflow. Net-30 terms explained. Case-pack pricing explained. How tiered pricing works. Shipping and LTL freight for wholesale volumes. These target informational queries buyers run before applying for an account.

4. Gated product pages for approved buyers only. These stay exactly as BigCommerce configures them: login-required, customer-group-specific pricing, full catalogue visibility. Google doesn’t need to crawl these. They serve authenticated buyers.

The public content layer does the SEO work. The gated layer does the commerce work. Together they rank a B2B store for the keywords buyers actually search without requiring Google to see wholesale prices.

Handling partially gated product catalogues

Some B2B stores run a hybrid model. Retail customers buy individual units at retail prices. Wholesale customers, once approved, see case-pack pricing and tier discounts. The product catalogue is partially visible to anonymous crawlers.

For these stores, the public product page optimization strategy works differently:

  • Anonymous visitors (and Google) see retail pricing on the product page
  • The product description includes a paragraph explaining wholesale availability: “This product is available in wholesale case packs for approved dealers. Tier pricing starts at 5-case orders. Apply for wholesale access.”
  • A link in the description points to the wholesale application page
  • Structured data includes Product schema for the retail version. The product description’s mention of wholesale availability gives Google the semantic signal without needing a dedicated schema field.

This approach lets the same product page serve retail SEO (ranking for the product name) while surfacing the B2B option to buyers who find it through search.

One thing to watch: the product description paragraph about wholesale availability needs to be in the main content, not in a tab that requires a click to expand. BigCommerce themes often put long descriptions in an accordion tab. Google indexes the tab content, but it carries less weight than content visible on initial page load. Move the wholesale mention to the primary description field.

Building the public wholesale page layer using BigCommerce Pages

Use BigCommerce Pages for your public wholesale landing pages, not blog posts. Pages live at Storefront > Web Pages in the admin. Blog posts live under Storefront > Blog. The difference matters for three reasons:

  1. Pages appear in the main navigation. Blog posts don’t. Your wholesale landing pages need to be discoverable from the top-level nav. A “Wholesale” link in the header pointing to your wholesale overview page is essential for both users and crawlers.
  2. Pages accept custom templates. You can assign a custom Stencil template to a page. This means you can build a wholesale landing page with a custom layout: hero section, product category grid, MOQ table, application CTA. Blog posts use the standard blog template with limited layout control.
  3. Pages get their own URL structure. By default, BigCommerce pages get clean URLs like /wholesale-apparel/. Blog posts get /blog/wholesale-apparel/. The /blog/ prefix signals informational content to both users and search engines. Wholesale landing pages are commercial content. They belong in the page URL structure.

For the wholesale overview page, create a page at /wholesale/ that explains your B2B program and links to each category-level wholesale page. Think of this as the hub in a hub-and-spoke model. The category-level pages (/wholesale-apparel/, /wholesale-electronics/) are the spokes. The hub page targets broad queries like “wholesale supplier [your brand].” The spokes target category-specific queries.

Converting a retail store to hybrid B2B/DTC

We’ve handled this migration six times in the past two years. Every time, the store owner is worried about losing their existing organic traffic. The concern is valid. Here’s the redirect and URL strategy that preserves traffic.

URLs that stay: All existing retail product pages keep their current URLs. Don’t move them, don’t add prefixes, don’t reorganize the catalogue. Google has already indexed these URLs and assigned them ranking signals. Moving them triggers a 301 redirect chain that costs you ranking momentum for weeks.

URLs that get added: Create new pages for the wholesale landing pages. /wholesale/, /wholesale-apparel/, /wholesale-electronics/, /dealer-application/. These are new URLs that don’t conflict with anything existing.

URLs that change behavior: Product pages that were previously retail-only now show different content based on customer group. The URL doesn’t change. But the content Google sees changes if you restrict product visibility. Before you restrict any product to a customer group, verify that the anonymous (Google) view still shows enough content to satisfy the ranking requirements. At minimum: product title, full description, retail price (or RRP), images, and specs.

The redirect trap: If you’ve been running a retail store and you decide to gate the entire catalogue behind a login, every product page becomes thin content overnight. Google notices. Your rankings drop within two crawl cycles. Never gate an entire existing catalogue at once. Phase it: restrict one category per week, monitor GSC for crawl error spikes, and build the public wholesale landing page for each category before you gate it.

On a sporting goods store with 4,200 SKUs, we phased the B2B conversion over eight weeks. Traffic dipped 11% in week three (the first batch of gated categories) and recovered to 96% of baseline by week six because the public wholesale pages started ranking for B2B queries that the retail pages never captured.

Schema for B2B BigCommerce pages

Product schema doesn’t have a native “wholesale pricing” field. The correct approach is to use Product schema for the retail-visible information and rely on page copy to communicate wholesale availability.

For the public wholesale landing pages (category-level B2B pages), use a combination of schema types:

  • Service schema declaring the wholesale service: areas served, price range (if published), service type “Wholesale Distribution”
  • FAQPage schema for the FAQ section. Each Q&A pair becomes a FAQ entity in Google’s index. Target the long-tail queries buyers ask before applying: “What are the minimum order quantities?” “Do you offer net-30 payment terms?” “How long does dealer application approval take?”
  • Organization schema for the merchant, including the B2B offering in the description field
  • BreadcrumbList schema for the navigation hierarchy: Home > Wholesale > [Category]

For the wholesale application page, HowTo schema maps naturally to the application process: step 1 (gather documents), step 2 (submit application), step 3 (receive approval notification), step 4 (start ordering). This earns a HowTo rich snippet in search results on application-intent queries. We’ve seen click-through rates jump 28% on one store after implementing HowTo schema on their dealer application page.

Implement all schema via the Stencil theme files, not Script Manager. BigCommerce’s Script Manager injects JavaScript that runs client-side. Google renders JavaScript for indexing, so the schema is technically visible. But Script Manager scripts don’t execute on AMP pages (if your theme supports AMP), and some schema testing tools show errors when schema only appears in rendered HTML. Theme-level injection in templates/layout/base.html avoids both issues.

Internal linking for B2B BigCommerce SEO

The internal linking structure on a B2B BigCommerce store reinforces the B2B positioning at every level of the site.

  • Public wholesale landing pages link to each other (sibling hub structure). Each category-level B2B page supports the others. Google understands that your wholesale apparel page and your wholesale electronics page are part of the same B2B offering.
  • Blog posts about wholesale topics link to the relevant wholesale landing page with contextual anchor text. Not “click here.” Use “our wholesale apparel program” or “the dealer application process.”
  • The main navigation includes a “Wholesale” top-level link. This goes to the wholesale overview page, which then links to category-level pages. Navigation links carry PageRank. A top-level link signals to Google that the wholesale section is a core part of the site.
  • Retail product pages link to the relevant wholesale landing page from the product description body. Not in the footer. Not in a sidebar widget. In the main content, where the link carries full contextual weight.

Modifying the navigation requires Stencil theme changes. Open templates/components/common/navigation.html (the exact filename varies by theme). Add a “Wholesale” link in the <nav> block at the same level as your product categories. Then go to Storefront > Web Pages in the admin and verify the wholesale overview page is marked “Show in Navigation.”

The combined effect: Google sees a content network where retail pages, wholesale landing pages, blog content, and the dealer application all interlink around the B2B topic. That’s how BigCommerce SEO builds topical authority for B2B queries.

Content that ranks B2B BigCommerce stores

B2B buyers run different queries than retail shoppers. The content strategy reflects this.

Three content types consistently drive qualified B2B traffic:

Category-level wholesale guides. These rank for informational-commercial queries that precede a wholesale account application. “How to Source Wholesale Apparel for Boutiques.” “Wholesale Restaurant Uniform Supplier Guide.” “Bulk Buying for Print Shops: Supplier Selection Framework.” Each guide targets a specific buyer persona and links to the relevant wholesale landing page.

Comparison content for buyer evaluation. Buyers evaluating wholesale suppliers search for comparisons. “Wholesale supplier A vs supplier B” captures evaluation-stage intent. Frame your offering in the context of the category, explain your differentiators (MOQ, case packs, payment terms), and let the buyer decide. Honest comparison content earns backlinks from industry forums where buyers share supplier recommendations.

Regulatory and compliance content. B2B verticals have regulatory considerations: PPE standards for workwear, flammability ratings for fabrics, food safety certifications for restaurant uniforms, ANSI classes for hi-vis gear. Content explaining these requirements builds trust with professional buyers. It also ranks for specification-driven queries that retail-focused competitors never target. A purchasing manager searching “ANSI Class 3 hi-vis vest supplier” has their credit card ready. That query will never appear in a B2C keyword research tool.

Technical considerations for B2B BigCommerce SEO

Customer group visibility and the sitemap. If your wholesale products are hidden from anonymous visitors, confirm they’re also excluded from the sitemap. BigCommerce’s default sitemap generator at /xmlsitemap.php doesn’t filter by customer group visibility. It lists every published product URL. Google crawls them, gets soft-404s, and flags them in the Coverage report.

The fix: install a custom sitemap solution that checks product visibility before including URLs. Or use robots.txt to block the URL patterns for gated products. The robots.txt approach is blunter but faster to implement.

Price list URLs and indexability. Some B2B themes generate customer-specific pages at URLs like /account/price-list/ or /account/orders/. Add noindex tags to all /account/ paths in your theme’s layout template. These are buyer-specific and have no SEO value.

Quote request form pages. The quote request form itself should be public and indexable. It’s part of the buyer journey, and it targets transactional queries like “request wholesale quote

.” The thank-you page after submission should be noindexed. Add <meta name="robots" content="noindex"> to the confirmation template.

Sitemap and crawl cleanup for gated content

After setting up customer group restrictions, run a full crawl of your site with Screaming Frog configured as an anonymous visitor (no cookies, no login). Compare the crawl results against your XML sitemap. Every URL in the sitemap that returns a soft-404, empty page, or login redirect in the anonymous crawl needs to be either:

  1. Removed from the sitemap (preferred for fully gated pages)
  2. Given a noindex tag (preferred for pages that have some anonymous content but shouldn’t rank)
  3. Rebuilt as a public page with anonymous-visible content (preferred for pages targeting valuable keywords)

On a food service equipment distributor with 8,000 SKUs, we found 3,200 URLs in the sitemap that returned empty pages to anonymous visitors. Cleaning those out of the sitemap and adding noindex tags reduced Google’s crawl error count from 3,400 to 12 within three weeks. The remaining 12 were legitimate 404s from deleted products.

After the cleanup, organic impressions for the store’s public wholesale pages increased by 340% over the following month. Google stopped spending its crawl budget on dead-end gated pages and started recrawling the public content more frequently.

Measuring B2B BigCommerce SEO success

Ranking a B2B store is different from ranking a retail store. The metrics that matter:

  • Wholesale application submissions are the primary conversion. Track these in Google Analytics as a goal. If you’re using BigCommerce’s built-in form, set up a destination goal for the thank-you page URL.
  • Organic traffic to public wholesale landing pages. Not raw sessions. Look at traffic that progresses to the application page. If 1,000 visitors land on your wholesale apparel page and 40 click through to the dealer application, your page-to-application rate is 4%. Benchmark this and optimize the page to improve it.
  • Search Console impressions for B2B commercial queries. Filter GSC by queries containing “wholesale,” “bulk,” “dealer,” “distributor,” and your product categories. Impression growth comes before click growth. If impressions are rising but clicks are flat, your meta titles and descriptions need work.
  • Application-to-approval conversion rate. If organic traffic applies at a 40% lower approval rate than direct traffic, your keyword targeting is attracting the wrong buyers. Refine the targeting to match your actual dealer qualification criteria.

Raw organic sessions to a B2B store matter less than retail. A wholesale account application is worth more than 100 retail purchases. Fifty qualified monthly visits that convert to 10 approved dealer accounts can outperform 10,000 retail sessions.

Digital Roxy has built B2B BigCommerce storefronts with the full public/gated content architecture for distributors across Texas, California, and New York. The typical audit of a B2B store that isn’t ranking uncovers three or four of the problems described in this post, plus two or three store-specific configuration issues that only show up during a hands-on crawl analysis. Our BigCommerce SEO service includes the technical audit, the public content layer build, and the ongoing optimization.

Frequently asked questions

How do I make my BigCommerce B2B catalogue visible to Google without showing wholesale prices?

Build a public content layer: wholesale landing pages per product category, a dealer application page, and FAQ pages explaining your B2B terms. These pages describe the offering and target B2B keywords without displaying actual wholesale pricing. The gated product pages with customer-group-specific prices stay hidden from anonymous visitors. Google indexes the public layer and ignores the gated layer.

Does BigCommerce’s “Hide from search results” checkbox prevent Google from indexing a page?

No. That checkbox only removes the item from BigCommerce’s internal site search feature. It does not add a noindex meta tag. It does not block Googlebot. The page remains fully crawlable and indexable by Google. To actually prevent indexing, add a <meta name="robots" content="noindex"> tag in your Stencil theme template or use robots.txt rules.

What schema markup should B2B BigCommerce pages use?

Public wholesale landing pages use Service schema (describing the wholesale offering), FAQPage schema (for the Q&A section), Organization schema (for the merchant entity), and BreadcrumbList schema. Product pages use standard Product schema with the retail/RRP price visible to anonymous visitors. The dealer application page uses HowTo schema mapping the application steps. Implement all schema in Stencil theme files, not Script Manager.

How do I stop BigCommerce from including gated product pages in the XML sitemap?

BigCommerce’s default sitemap generator doesn’t filter by customer group visibility. You have two options: use a custom sitemap solution that checks visibility before including URLs, or add robots.txt Disallow rules for the URL patterns of gated products. After either fix, resubmit the sitemap in Google Search Console and monitor the Coverage report for improvement.

Can I convert an existing retail BigCommerce store to B2B without losing organic traffic?

Yes, but phase the conversion. Don’t gate the entire catalogue at once. Restrict one product category per week. Build the public wholesale landing page for each category before you gate it. Monitor GSC for crawl error spikes after each batch. Existing retail product URLs stay unchanged. New wholesale landing pages get new URLs. The retail pages retain their organic rankings while the new B2B pages start capturing wholesale queries.

Do restricted catalogues in BigCommerce B2B Edition cascade to sub-categories?

No. Category visibility restrictions set at the parent level don’t automatically apply to sub-categories. You must configure visibility for every sub-category individually in Customers > Customer Groups > Category Access. This is the most commonly missed configuration step in B2B BigCommerce setups.

Ready to automate your marketing?

Deploy 7 AI agents per client. Research, strategy, content, SEO, and sales on autopilot.

Get Started
FK
Faris Khalil
Founder and lead developer at Digital Roxy. Builds custom e-commerce stores on Shopify, WordPress, and BigCommerce. Specializes in platform migrations, headless architecture, and AI-driven marketing systems for agencies.