B2B SaaS Pricing Pages: Why AI Thinks Your Software is Free (And How to Fix It)

Why AI models think your SaaS is free

A growing pattern in AI search responses: users ask "how much does [SaaS product] cost?" and receive either "pricing is available on their website" or, worse, an incorrect price. In some cases, AI models confidently state a product is free because they extracted the text from a free tier card while missing the paid tier entirely.

This isn't a hallucination problem. It's a parsing problem. Modern SaaS pricing pages are built with JavaScript-dependent interactive components — monthly/annual toggles, feature comparison sliders, seat-count calculators — that collapse to zero or incomplete text when DOM-stripped by AI ingestion pipelines.

The JavaScript toggle trap

Standard SaaS pricing page architecture uses a React or Vue component with a state toggle. On initial page load (before JavaScript executes), the DOM contains one of two states — typically the monthly pricing. The annual pricing exists as a hidden element that appears only after user interaction.

What AI crawlers extract from a typical pricing toggle

What AI actually sees on your pricing page

When a Trafilatura-based scraper (used by Perplexity and many RAG pipelines) processes a typical SaaS pricing page, the output looks something like this:

The Starter plan at $49/month, the Pro plan at $149/month, and all feature differentiators are completely absent. The AI's retrieved context contains only "Free" and "Contact sales" — which it accurately (but misleadingly) reports.

Fix 1: The hidden Markdown pricing table

The simplest fix is adding a visually hidden but DOM-present Markdown-style pricing table that AI crawlers can extract, while your interactive toggle remains visible to human users.

Fix 2: Product JSON-LD with Offer schema

The more robust, future-proof solution is implementing strict Product and Offer structured data. JSON-LD is parsed before DOM stripping and is treated as ground truth by AI systems that have been trained to trust structured data over body text.

{{ "@context": "https://[schema](/blog/howto-schema-complete-implementation-guide).org", "@type": "SoftwareApplication", "name": "YourProduct", "applicationCategory": "BusinessApplication", "offers": [ { "@type": "Offer", "name": "Starter Plan", "price": "49.00", "priceCurrency": "USD", "priceSpecification": , "description": "20 projects, 500 analyses per month, email support" }, { "@type": "Offer", "name": "Pro Plan", "price": "149.00", "priceCurrency": "USD", "priceSpecification": , "description": "Unlimited projects, 2000 analyses per month, priority support" } ] }}

Implementation priority by scenario

Scenario Recommended fix Priority

AEO for B2B SaaS: Complete Guide The full AEO playbook for software companies, from pricing pages to documentation. Schema markup's new job in AI search How structured data has shifted from SERP enhancement to AI citation infrastructure.