Guide · Practitioner
Pricing Pages and AI: Why Hidden Pricing Hurts
If your pricing isn't public, AI engines can't quote it accurately. When buyers ask "how much does X cost?", engines that ground answers in web sources (Google) can only use what's published: your page, a reseller, a review site or an outdated forum post. Our view: a clear, dated pricing page is the simplest way to make sure the number engines repeat is yours.
Facts are from Google Search Central and EU law, accessed 30 Oct 2026. This isn't legal advice. Recommendations marked "our view" are interpretation.
On this page
- Why does pricing matter in AI answers?
- What happens when pricing is hidden?
- What are the rules for consumer prices?
- What can engines read on a pricing page?
- What should a transparent pricing page include?
- What if pricing is truly custom?
- Should you use structured data?
- What's a worked example?
- How do you keep prices accurate everywhere?
- How do you test it?
- What about discounts and promotions?
- Who should own pricing content?
- Does publishing prices help competitors?
- How should you present price ranges?
- How do you handle multiple currencies and regions?
- Checklist
- From MentionX data: how rarely pricing pages are cited
- Worked example: Ledgerline publishes clearer pricing
- What do buyers ask about pricing?
- How should you write plan descriptions?
- How do you handle add-ons and usage-based fees?
- How do you handle annual and monthly billing?
- How do you make the page easy for engines to read?
- How do you handle sales objections to publishing prices?
- How do you check what engines say about your prices?
- What should you do after a price change?
- How do you handle free plans and trials?
- How do you present prices on comparison pages?
- How do you work with finance and legal?
- Common questions
- Related
- Sources
Checked on 31 October 2026. "Our view" marks MentionX opinion. Ledgerline is a fictional company used for illustration.
Why does pricing matter in AI answers?
Price is among the most common decision-stage questions. Google says its generative AI features retrieve relevant pages from its index to ground answers (Google). Our view: if no page states your price, the answer may be "pricing not disclosed", a competitor's comparison table, or a stale number.
What happens when pricing is hidden?
Fictional scenarios:
| Your page says | An engine may say |
|---|---|
| "Contact sales" | "Pricing isn't public; contact the vendor" |
| Nothing, but a 2023 review lists €29 | "Starts at €29" (outdated) |
| Competitor table says "expensive" | "Considered expensive" |
| "From €49/user/month, as of Oct 2026" | "From €49 per user per month" |
What are the rules for consumer prices?
In the EU, the Price Indication Directive 98/6/EC requires traders to indicate the selling price, and the unit price where applicable, of products offered to consumers (EUR-Lex). B2B SaaS has more freedom, but consumer-facing businesses must show prices.
What can engines read on a pricing page?
Our view:
- Prices in HTML text or tables: readable
- Prices in images: hard to read without alt text
- Prices only in a calculator that needs interaction: may not be read
- Prices behind a login: not read by public crawlers
Google can process JavaScript content that isn't blocked, but test rendering (Google).
What should a transparent pricing page include?
| Element | Example |
|---|---|
| Plan names and prices | Starter €19, Pro €49 per user/month |
| Billing basis | Monthly vs annual, currency, VAT |
| What's included | Seats, limits, features |
| What costs extra | Add-ons, overages |
| As-of date | "Prices as of 30 Oct 2026" |
| Enterprise | "From €X" or what drives price |
| Free trial or plan | Terms |
What if pricing is truly custom?
Our view: publish what's stable:
- A starting price or typical range, labelled as such
- The factors that drive cost (seats, volume, modules)
- What every plan includes
- A worked, fictional example
Should you use structured data?
For ecommerce products, Google's Product structured data supports offers with price; merchant listing markup adds shipping and returns (Google). Merchant Center feeds also supply product prices (Google). Google says product info in Merchant Center can help visibility in AI responses (Google). For SaaS plans, there's no AI-specific markup requirement; the visible table matters.
What's a worked example?
Fictional example: a CRM vendor replaces "Contact us" with three plans, an enterprise "from" price, a list of cost drivers and a monthly as-of date. Within a quarter, its prompt tests show engines quoting its own price rather than a 2022 review.
How do you keep prices accurate everywhere?
| Place | Action |
|---|---|
| Pricing page | Single source of truth, dated |
| Comparison and help pages | Pull from the same source |
| Review sites and marketplaces | Update vendor profiles |
| Old blog posts | Add update notes or remove prices |
How do you test it?
Monthly, ask engines "How much does [brand] cost?" and "[brand] pricing for 20 users". Record the figure, source and date. Fix whichever source is wrong.
What about discounts and promotions?
Our view: state list prices clearly and label promotions with an end date. In the EU, Directive (EU) 2019/2161 amended the Price Indication Directive so that announcements of price reductions must show the prior price (EUR-Lex). Expired promotions left on the page are a common source of wrong prices in AI answers.
Who should own pricing content?
| Role | Responsibility |
|---|---|
| Product marketing | Pricing page and plan descriptions |
| Finance | Accuracy and approval |
| Legal | Consumer price rules |
| Web team | One source of truth across pages |
Does publishing prices help competitors?
Our view: competitors can usually find your prices through sales calls or customers anyway. The bigger risk is buyers and engines filling the gap with wrong numbers. If you're worried, publish starting prices and cost drivers rather than every discount tier.
How should you present price ranges?
| Weak | Strong |
|---|---|
| "Affordable plans" | "€19–€49 per user per month" |
| "Custom pricing" | "Enterprise from €2,000/month; depends on seats and modules" |
| "Cheaper than competitors" | A dated comparison table with sources |
How do you handle multiple currencies and regions?
State the currency on every price and whether VAT or sales tax is included. If prices vary by region, show the buyer's region by default with a selector, and keep each regional price in HTML. Our view: engines answering for different countries need to see which price applies where.
Checklist
- Prices in HTML text, dated
- Billing basis and VAT stated
- Enterprise "from" price or cost drivers
- Old prices removed elsewhere
- Consumer price rules checked
- Monthly engine price tests
From MentionX data: how rarely pricing pages are cited
Method. Read-only aggregate queries over MentionX scans from 22 August to 29 October 2026 (UTC): 2,217 engine runs (2,154 completed) across 18 anonymised projects and six engines.
In the MentionX sample, pricing pages make up a small share of cited URLs:
| Cited URL type | Share of 9,750 citations |
|---|---|
| Blog or article | 19.6% |
| Homepage | 10.0% |
| Review page | 2.7% |
| Docs | 2.6% |
| Pricing | 1.9% |
| Wikipedia | 1.6% |
Comparison prompts, where buyers often ask about cost, mention brands far more often than other prompt types:
| Intent | Brand mentioned | Share of voice |
|---|---|---|
| Brand-specific | 100% | 64.3 |
| Comparison | 91.9% | 44.6 |
| Recommendation | 29.2% | 26.8 |
| Best-of | 26.6% | 22.7 |
| Problem | 5.7% | 7.7 |
Our view: pricing questions are common in comparison prompts, yet pricing pages are rarely cited. Clear, crawlable pricing gives engines a first-party source instead of leaving them to rely on other sites.
Limits. A convenience sample of mostly B2B software projects, run through engine APIs, which can behave differently from the consumer apps. Perplexity, Copilot and DeepSeek figures come from a single day (26 October 2026), so treat them as a snapshot, not a trend.
Worked example: Ledgerline publishes clearer pricing
Ledgerline is a fictional accounts-payable tool. Figures are illustrative.
Ledgerline's pricing page shows three plan names and a "Contact sales" button, with no prices. AI answers to "how much does Ledgerline cost" quote an old figure from a review site, and some say pricing is "not available".
The team publishes starting prices for the two self-serve plans, lists what each includes and states the main limits, such as the number of approvers. For the enterprise plan, it explains what affects the price: invoice volume, number of entities and integrations. All of this is in HTML text, not images. The team asks the review site to update its listing. Prices here are illustrative.
What do buyers ask about pricing?
Buyers ask how much a product costs, what's included in each plan, whether there's a free trial, how billing works, what happens if they exceed limits and how prices compare with alternatives. Use sales notes and support tickets to find the questions your buyers ask most. Answer each one on the pricing page or in a linked FAQ.
How should you write plan descriptions?
Describe each plan in one sentence that says who it suits. List the main features and limits underneath. Use the same feature names as your product and docs. Avoid vague phrases such as "advanced features" without saying what they are.
How do you handle add-ons and usage-based fees?
List add-ons and their prices or ranges separately from plans. For usage-based pricing, explain the unit, such as per invoice or per user, and give examples of what typical usage might cost, labelled as examples. Make it clear what counts towards usage.
How do you handle annual and monthly billing?
Show both if you offer them, and make the difference clear. State whether prices include tax. If annual billing has a discount, show the actual price rather than only a percentage.
How do you make the page easy for engines to read?
Use HTML text for prices and features, not images or scripts that load after the page. Use a table to compare plans. Keep the page at a stable URL. Avoid hiding prices behind tabs or toggles that only load on click, or test that the content is in the initial HTML.
How do you handle sales objections to publishing prices?
Sales teams sometimes worry that published prices will scare buyers or help competitors. Discuss the trade-off openly: buyers and engines look for prices anyway, and if you don't provide them, someone else will, possibly wrongly. Starting prices or ranges can address both concerns.
How do you check what engines say about your prices?
Run prompts such as "how much does [brand] cost", "[brand] pricing" and "[brand] vs [competitor] price" in several engines each month. Record the figures quoted and the sources cited. If answers are wrong, find the source and fix it, starting with your own pages and then third-party listings. Our view: wrong prices in AI answers are among the most fixable visibility problems, because the cause is usually a page you or a partner control.
What should you do after a price change?
Update the pricing page, docs, help articles, comparison pages and partner listings on the same day. Ask review sites to update their listings. Keep a note of the change date and check AI answers over the following weeks. Expect old figures to linger for a while in some engines.
How do you handle free plans and trials?
State clearly whether a free plan or trial exists, how long a trial lasts, what's included and whether a card is required. Explain what happens when the trial ends. These are common buyer questions, and engines often answer them from third-party sites when the pricing page is unclear.
How do you present prices on comparison pages?
If you compare yourself with competitors, use their public prices with a date and a link to the source. Avoid guessing prices that aren't public; say they aren't published instead. Keep your own prices on comparison pages in sync with the pricing page, ideally from one shared source in your CMS.
How do you work with finance and legal?
Agree who approves pricing content and how quickly changes go live. Check legal requirements for showing prices in each market, such as including tax for consumers. Keep a record of approved wording for terms like "starting at" and "per user".
Common questions
Should I show prices if we negotiate every deal? Consider a starting price or range and explain what affects it.
Do AI engines read pricing tables? They can read HTML tables; images and scripted content are less reliable.
How often should I check pricing in AI answers? After every price change and at least monthly for key prompts.
Related
Sources
- Google, AI optimization guide; Product structured data; Merchant Center; JavaScript SEO
- EUR-Lex, Directive 98/6/EC on price indication; Directive (EU) 2019/2161
All accessed 30 Oct 2026.
Questions
Does hiding pricing hurt AI visibility?
No engine publishes that as a rule. But an engine can only state your price if a source does; with no public price, answers to 'how much does X cost' rely on third parties or say nothing.
What if our pricing is genuinely custom?
Publish what you can: starting prices, what drives cost, typical ranges labelled as such, and what's included. That gives engines and buyers something accurate.
Should pricing be in structured data?
For products sold online, Google's Product markup supports price in offers. For SaaS plans, a clear HTML table matters most.