For a while, the comforting line in SEO was "AI Overviews mostly show up on informational queries. Your money pages are safe."

That's no longer true. In a study published in October 2026, Semrush tracked a fixed panel of 400 commercial keywords (banking, software, ecommerce; U.S. desktop):

  • September 2025: AI Overviews on 45.75% of them
  • August 2026: 88%
  • weighted by search volume: 97.08% of estimated commercial searches

It's one panel, not every commercial search, but the direction is clear. Queries like "X pricing", "X vs Y" and "best X for small teams" now usually get an AI-written answer above the links.

When that answer says what your product costs, it's quoting someone. This post is about making sure it's you, and that the number is right.

What goes wrong on pricing pages

Pricing pages are built for humans who click toggles. AI systems read text. The usual failures:

  1. Prices that only exist after JavaScript runs (the monthly/annual toggle renders the numbers client-side). Some AI fetchers don't run JS at all.
  2. Only one billing period in the HTML. The annual price is in the markup, and the monthly price appears only when someone clicks.
  3. No currency, or a currency picked by geo-IP. A crawler in the US sees $, your EU buyer sees €, and the AI answer picks one at random.
  4. Plan limits hidden in tooltips ("up to 5 seats" lives in an aria-describedby popover).
  5. Comparison tables built from <div>s, so the structure that makes them readable to people is invisible to machines.
  6. No date. The AI can't tell your 2026 pricing from a 2023 blog post quoting your old pricing, and the old post often has the clearer sentence.

Number 6 deserves a closer look. If a third-party review says "Acme costs $12/user/month" in one clean sentence and your page says "From $10" inside a React card, the review is easier to quote. Even when it's wrong.

The audit script

This Node 18+ script fetches the raw HTML (no JavaScript) of your pricing and comparison pages and reports on what a non-rendering reader can see.

// audit-pricing.mjs const urls = process.argv.slice(2); const PRICE = /(?:[$€£]\s?\d[\d,.]*|\d[\d,.]*\s?(?:USD|EUR|GBP))(?:\s*\/\s*(?:mo|month|yr|year|user|seat))?/gi; const strip = html => html .replace(/<script[\s\S]*?<\/script>/gi, " ") .replace(/<style[\s\S]*?<\/style>/gi, " ") .replace(/<[^>]+>/g, " ") .replace(/\s+/g, " "); for (const url of urls) { const res = await fetch(url, { headers: { "user-agent": "pricing-audit/1.0" } }); const html = await res.text(); const text = strip(html); const prices = [...new Set(text.match(PRICE) ?? [])]; const jsonLd = [...html.matchAll(/<script[^>]+application\/ld\+json[^>]*>([\s\S]*?)<\/script>/gi)] .map(m => { try { return JSON.parse(m[1]); } catch { return null; } }).filter(Boolean); const types = jsonLd.flatMap(j => (j["@graph"] ?? [j]).map(n => n["@type"])).flat(); const headings = [...html.matchAll(/<h[23][^>]*>([\s\S]*?)<\/h[23]>/gi)].map(m => strip(m[1]).trim()); const checks = { "status 200": res.status === 200, "prices in raw HTML": prices.length > 0, "monthly AND annual wording": /month|\/mo\b/i.test(text) && /year|annual|\/yr\b/i.test(text), "explicit currency": /[$€£]|USD|EUR|GBP/.test(text), "real <table>": /<table[\s>]/i.test(html), "plan names in headings": headings.length >= 2, "FAQ section": /faq|frequently asked/i.test(text), "visible date": /(updated|as of|effective)\s+(on\s+)?[A-Z]?[a-z]+\s+\d{1,2},?\s+20\d\d|\b20\d\d-\d\d-\d\d\b/i.test(text), "no noindex": !/<meta[^>]+robots[^>]+noindex/i.test(html) && !/noindex/i.test(res.headers.get("x-robots-tag") ?? ""), "structured data": types.length > 0, }; console.log(`\n${url}`); for (const [k, ok] of Object.entries(checks)) console.log(` ${ok ? "✓" : "✗"} ${k}`); console.log(` prices found: ${prices.slice(0, 8).join(", ") || "none"}`); console.log(` headings: ${headings.slice(0, 6).join(" | ") || "none"}`); console.log(` JSON-LD types: ${types.join(", ") || "none"}`); } 
node audit-pricing.mjs https://example.com/pricing https://example.com/compare/acme-vs-globex 

Example output (illustrative):

https://example.com/pricing ✓ status 200 ✗ prices in raw HTML ✗ monthly AND annual wording ✓ explicit currency ✗ real <table> ✓ plan names in headings ✓ FAQ section ✗ visible date ✓ no noindex ✗ structured data prices found: none headings: Starter | Team | Business | Frequently asked questions JSON-LD types: none 

"Explicit currency ✓, prices found: none" is a classic result. A $ sign appears somewhere in the static text, but every actual number is rendered client-side.

The fixes, in order of impact

1. Put every price in the server-rendered HTML

Render both billing periods and hide one with CSS. Don't fetch prices after load:

<section aria-labelledby="team-plan"> <h2 id="team-plan">Team</h2> <p class="price" data-period="monthly">$12 per user / month, billed monthly</p> <p class="price" data-period="annual" hidden>$10 per user / month, billed annually ($120 per user / year)</p> <ul> <li>Up to 50 users</li> <li>10 GB storage per user</li> <li>SSO (SAML)</li> </ul> </section> 

Content behind a hidden attribute is still in the HTML. Whether a given AI system reads hidden text varies, so put the key sentence in visible copy as well (next fix).

2. Write one plain sentence per plan

Directly under the plan cards, add the sentence you'd want quoted:

Acme pricing (as of October 2026): Starter is free for up to 3 users. Team costs $12 per user per month, or $10 billed annually. Business costs $24 per user per month, or $20 billed annually, and adds SSO and audit logs. All prices in USD, excluding tax.

This one paragraph fixes problems 1, 2, 3 and 6 for a reader that doesn't run JavaScript. It also helps humans who skim.

3. Use a real <table> for plan comparison

<table> <caption>Acme plans compared (October 2026)</caption> <thead><tr><th scope="col">Feature</th><th scope="col">Starter</th><th scope="col">Team</th><th scope="col">Business</th></tr></thead> <tbody> <tr><th scope="row">Price (monthly billing)</th><td>Free</td><td>$12/user</td><td>$24/user</td></tr> <tr><th scope="row">Users</th><td>Up to 3</td><td>Up to 50</td><td>Unlimited</td></tr> <tr><th scope="row">SSO</th><td>—</td><td>—</td><td>✓</td></tr> </tbody> </table> 

4. Add structured data that matches the page

For SaaS, SoftwareApplication with offers is the common pattern. Keep the numbers identical to the visible text. Mismatches are worse than having no markup.

<script type="application/ld+json"> { "@context": "https://schema.org", "@type": "SoftwareApplication", "name": "Acme", "applicationCategory": "BusinessApplication", "operatingSystem": "Web", "offers": [ { "@type": "Offer", "name": "Team (monthly)", "price": "12", "priceCurrency": "USD" }, { "@type": "Offer", "name": "Business (monthly)", "price": "24", "priceCurrency": "USD" } ] } </script> 

5. Clean up the third-party pages that quote your old pricing

Search your brand plus "pricing" and see what the AI answer cites. If it cites a review site with old numbers, ask that site to update. Most will, because nobody wants to be wrong. Your own old blog posts and changelogs count too: add a dated note that links to the current pricing page.

Comparison pages: same rules, more risk

"X vs Y" pages are now often summarized rather than clicked. The same audit applies, plus:

  • Name both products in the title and H1, using the words people search ("Acme vs Globex"), not a clever headline.
  • State the verdict early. "Choose Acme if you need SSO under $25/user; choose Globex if you need on-prem." AI answers quote verdicts.
  • Be fair. Comparison pages that never admit a weakness read as ads, and both people and models discount them.

If you want this audit run across every page of your site rather than just a few, Vista AI's page audit checks AI readability at scale. For your top five commercial pages, the script and an afternoon of edits will cover most of it.

Quick checklist

  • [ ] Every price in server-rendered HTML, both billing periods
  • [ ] One plain "as of [date]" pricing sentence per page
  • [ ] Explicit currency, no geo-IP-only pricing
  • [ ] Plan comparison in a real <table>
  • [ ] SoftwareApplication/Offer markup matching the visible numbers
  • [ ] Third-party pages with old pricing found and contacted

Next in the series: Agentic checkout for developers: ACP vs Google's UCP.