Pricing Visibility

TL;DR — AI assistants answering "how much does X cost?" need machine-readable price data. Pages without visible pricing, or pricing loaded via JavaScript after render, are invisible to AI shopping queries.

Why Pricing Visibility Matters for AI Engines

AI shopping assistants answering pricing queries — "how much does TrustData cost?", "what is the cheapest analytics tool under €50/month?" — need price data that is:

1. Present in the page HTML (not hidden or loaded post-render via JavaScript)
2. Machine-readable (ideally in schema.org/Offer markup)
3. Unambiguous (specific numbers, not "contact us for pricing")

Pages that hide pricing behind a "contact us for a quote" form are effectively invisible to AI shopping queries. The model cannot fabricate a price — it will skip the page and cite a competitor that publishes pricing openly.

JavaScript-rendered pricing is also a problem. Many modern e-commerce and SaaS pricing pages load prices dynamically after the initial page render. AI crawlers that don't execute JavaScript will see no pricing data in the HTML, even if users see it in their browser. The fix is to either server-side render pricing or ensure the price is in the initial HTML payload.

How to Implement

• Ensure pricing is in the initial server-rendered HTML (not loaded via JavaScript)
• Add Offer schema for each price point:

{
  "@type": "Offer",
  "name": "Pro Plan",
  "price": "99.00",
  "priceCurrency": "EUR",
  "availability": "https://schema.org/InStock",
  "priceValidUntil": "2026-12-31"
}

• For tiered pricing, create one Offer per tier
• If you have regional pricing, use eligibleRegion in the Offer schema

Common Mistakes

• Pricing only in a JavaScript-rendered component — AI crawlers see an empty price slot; server-side render your pricing
• "Starting from" pricing without a specific number — vague price floors are not machine-readable; provide the specific entry price
• No priceValidUntil — without an expiry date, stale pricing in AI engines' knowledge cache can cause user confusion

Sources

• schema.org/Offer
• Google — Price structured data