What can Google see on a B2B ecommerce site?
Google can see only what a visitor who is not logged in can see. 1Digital Agency explains that Googlebot crawls without logging in, so if a page returns a normal 200 response but shows a login form, Google indexes the form instead of the product data. Reveation Labs puts the same rule positively: Google needs a public URL that loads real content without a customer login, and eligibility for search does not guarantee rankings.
Check this yourself before changing anything. Use the URL Inspection tool in Google Search Console, which shows the page Googlebot received, on a sample of product, category and account URLs. Our B2B ecommerce SEO page describes how a catalogue audit starts.
Should you gate the catalogue or only the price?
Gate the price, not the catalogue, unless a legal or relationship reason forces otherwise. Helium Development recommends keeping the catalogue public and indexable while requiring authentication for pricing, stock and minimum order quantities. 1Digital Agency calls this a two-tier model: public product pages with real content, and an authenticated layer that shows net pricing after login.
| Keep public | Keep private |
|---|---|
| Categories and product families | Customer-specific catalogues |
| Product pages with descriptions, general specifications and applications | Negotiated pricing |
| Compatibility, certifications and public documents | Credit terms |
| How to request a quote or open an account | Orders, invoices, quotes, approvals and customer records |
Gating the product itself is justified in four cases, according to 1Digital Agency: regulated industries where public pricing may be legally restricted, relationship-based pricing, high-value lead qualification and proprietary technical content. If you fall into one of them, put effort into public category pages, glossaries and buying guides that serve research-stage queries. Reveation Labs warns against the common mistake of gating all product copy along with the price.
What can you put in structured data when prices are private?
Put in structured data only what a visitor can see. Google's structured data guidelines say "Don't mark up content that is not visible to readers of the page" and that structured data must be a true representation of the page. Google's product snippet documentation says a page needs one of review, aggregate rating or offers, and that an offer needs a price.
The advice you will meet online conflicts on this point:
- Product markup with offers while the page says contact for pricing. 1Digital Agency says this signals relevance. Our reading of Google's rule is that an offer with a price the visitor cannot see is markup for content that is not visible.
- Aggregate offer or price specification to hint at wholesale pricing. Arslan Emre suggests this to signal that wholesale pricing exists. The same objection applies.
- Leave private offer data out of markup. Reveation Labs advises this, and it matches Google's rule.
If your price is not public, a Product snippet may simply not apply, and that is acceptable. Some platforms offer a setting to hide prices from Google, such as BSS Commerce's, which it says adjusts how price data appears in templates and structured data and does not remove product pages from Google. Check what any such setting actually outputs in the rendered page. Our guide to B2B schema markup covers the types that describe a page without a price.
How do you handle customer-specific URLs, filters and duplicates?
Give each product one stable public URL and keep customer views off the index. Reveation Labs lists four related mistakes: duplicate URLs for customer groups, sessions or pricing states; canonical tags on public pages that point to login or account URLs; thin, templated pages at scale; and a blanket noindex left on public templates. Arslan Emre advises canonicalising B2B views, such as a wholesale view parameter, to the master public product URL.
Be precise about what each control does. Reveation Labs says authentication blocks access, noindex keeps reachable pages out of results, robots.txt manages crawling and canonicals consolidate duplicates, and quotes Google that robots.txt "is not a secure way to hide pages from Search." Arslan Emre recommends noindex on logged-in price pages. Googlebot cannot reach authenticated pages in the first place, so the risk is publicly reachable price-state URLs, which is where noindex belongs.
Filters need their own rules. Google says faceted navigation "can generate infinite URL spaces" and recommends using robots.txt to disallow crawling of faceted navigation URLs. It says fragment-based filters have no effect on crawling and that canonical tags are generally less effective in the long term. Our guide to enterprise SEO on 10,000-page sites shows how to decide which filtered URLs should exist.
How should the quote and sign-in path work?
The quote and sign-in path should remember what the buyer chose. Reveation Labs lists losing the selected product after sign-in as a mistake and advises carrying the product, SKU, quantity and configuration through authentication without exposing sensitive account data. A buyer who clicks a product from search, signs in to see a price and lands on a generic dashboard has to start again.
Handle stock the same way. Arslan Emre notes that a product may be in stock yet unavailable to a particular customer, and suggests offering a notify-me or request-a-quote option instead of a sold-out button. Track the handoff as well as the visit: visibility, evaluation, intent, sign-in or quote and commercial contribution, as Reveation Labs suggests. Define the attribution model before you claim that organic search created revenue.
How do you audit a B2B catalogue for search?
Audit the catalogue as groups of URLs, not as individual pages. Reveation Labs' audit list is a sound base, and these seven steps adapt it:
- Inventory the URL groups. List public catalogue, filtered, account, login and quote URLs.
- Check status codes. A login form served with a 200 response is the problem described above. 1Digital Agency advises 302 redirects for login responses, to avoid permanent removal of the URL.
- Inspect the rendered HTML of each group with URL Inspection.
- Review canonicals. No public page should point to a login or account URL.
- Review robots.txt, meta robots and X-Robots-Tag for blanket rules on public templates.
- Check the sitemap. It should hold only canonical, indexable URLs that return content to anonymous visitors.
- Fix patterns at the template level, not page by page, then retest.
Where does B2B ecommerce SEO start?
Start with one category and its path from search to a quote. Decide what is public, what is private and what happens after sign-in for that category, test the result, and expand. Platform and implementation responsibilities are agreed for each project before work begins, as our service page explains.
To see which of your catalogue URLs Google can actually read, book a free B2B SEO audit. For product pages built around specifications, see our guide to manufacturing product pages.