B2B PRICING VISIBILITY
The Illusion of “Hidden Pricing”
You set up your B2B store like this:
- Prices hidden behind login ✅
- Wholesale discounts applied dynamically ✅
- Custom scripts or apps controlling visibility ✅
So you assume:
👉 “Only approved customers can see our prices.”
But here’s the reality:
👉 Google might already have.
WHY THIS HAPPENS
Why it’s more common
than you think.
Most “hidden pricing” setups rely on:
- Frontend logic (Liquid, JavaScript)
- Conditional rendering
- CSS hiding
👉 And that’s the problem.
Because:
👉 Google doesn’t browse your site like a human
👉 It reads your code
THE CORE ISSUE: FRONTEND VS BACKEND PROTECTION
❌ Frontend hiding (what most stores do)
Examples: {% if customer %}, display: none, JavaScript hiding
👉 The price is still in the HTML
Which means: 👉 Bots (including Google) can still see it
✅ Backend protection (what you actually need)
True protection means: 👉 The price is never sent unless authorized
If it’s not in the answer… 👉 It can’t be indexed
HOW GOOGLE ENDS UP SEEING YOUR “HIDDEN” PRICES
Here’s where it gets interesting.
01
Cached Pages
If a logged-in session gets indexed or cached:
👉 Prices can leak into search results
02
Structured Data (Schema)
Many themes include "price": "..." in their schema markup.
👉 Even if hidden visually, it’s exposed in structured data
Google LOVES this.
03
JavaScript Rendering
Google can execute JS. So even if prices load dynamically:
👉 They may still be indexed
04
App Conflicts
Some wholesale apps:
- Hide prices visually
- But leave raw data accessible
👉 False sense of security
05
Staging or Preview Links
If exposed:
👉 Google can crawl them
And index content not meant to be public.
THE REAL RISKS (THIS IS WHERE IT HURTS)
This isn’t just a technical glitch.
It affects your entire business.
💸 Pricing Strategy
- Competitors see your wholesale rates
- Undercutting becomes easier
🤝 Supplier Relationships
Some agreements require: 👉 Strict price confidentiality
Leaks can damage trust.
📅 Brand Positioning
If B2B pricing is public:
👉 Retail customers may question your margins
🔍 SEO Confusion
Google may index:
- Incorrect pricing
- Mixed price signals
👉 Hurts search clarity
🔧 HOW TO ACTUALLY PROTECT YOUR PRICING
Let’s fix this properly.
Remove Price From Unauthenticated Responses
Not hidden. 👉 Removed.
If the user isn’t authenticated:
👉 The price is never sent at all.
Controlled Structured Data
Ensure:
- No price schema for public users
- Conditional schema rendering
👉 Don’t feed Google what you want hidden
Use Server-Side Logic
Instead of: 👉 Frontend conditions
Use: 👉 Backend validation
Only return price data when:
- Customer is logged in
- Customer has correct tag/role
Block Indexing Where Needed
Use:
noindexon sensitive pages- Robots.txt rules
- Login walls
👉 Reduce crawl exposure
Audit Your Store Like Google Would
Check:
- Source page (not visual page)
- Structured data
- API responses
👉 If you can see it in code, so can Google
Choose Apps Carefully
Not all wholesale apps are equal.
Look for:
👉 True access control (not visual hiding)
THE MINDSET SHIFT
Here’s the key:
👉 Hidden ≠ protected
If your pricing is in the frontend…
👉 It’s not hidden
QUICK REALITY CHECK
Ask yourself:
👉 “If I right-click → view page source… can I find my prices?”
If yes…
👉 So can Google
👉 So can competitors
💡 FINAL THOUGHT
Most B2B stores don’t leak prices because of hacks.
They leak them because of: 👉 Misunderstood architecture
So the goal isn’t just to hide better.
👉 It’s to control what gets exposed at all.
Because in ecommerce…
👉 If Google can see it, it’s not private.