Pricing Page AEO:
How to Let AI Calculate Your Price

Gururaj Pandurangi
Gururaj PandurangiFounder, ThriveStack
Nov 17, 2026 · 8 min read

Pricing page Answer Engine Optimization means writing your rates and worked examples as plain text, so AI engines can quote an exact price without touching your sliders. This article gives 8 techniques and a fully built pricing page you can query with AI to try them out.

ThriveStack citedby Pricing Page AEO: AI engines went from 0 of 9 correct prices to 9 of 9 once the rates were text 2 experiments, 18 engine answers. 3 buyer prompts on 3 engines with web search on, Nov 1, 2026. BEFORE: THE LIVE PAGE 0 of 9 correct prices CHATGPT PERPLEXITY CLAUDE 1 No price No price $175 guess 2 $280 wrong $315 wrong $350 guess 3 No price $249 wrong No price AFTER: RATES AS PLAIN TEXT 9 of 9 correct prices CHATGPT PERPLEXITY CLAUDE 1 $773 $773 $773 2 $322 $322 $322 3 $2,076 $2,076 $2,076 Row 1: 125 prompts a day, 3 engines, 1 country. Real price $773 a month. Row 2: an agency managing 10 client brands. Real price $322 a month. Row 3: Revenue Intelligence, 50,000 users, $5M ARR. Real price $2,076 a month. 2 experiments run 18 engine answers scored 3 engines asked 3 exact price prompts Source: ThriveStack citedby test, Nov 1, 2026, one run per cell (gpt-5.5, sonar-pro, claude-sonnet-5-5). After: rates pasted into the prompt. This shows the text is enough. Engines reading the live page is untested.
Figure 1: AI engines priced our setups from the live page and from plain text. Explained in section 02 and section 09.
Read on

Four numbers frame this guide. We ran 2 experiments and scored 18 engine answers, so each claim comes from a test (section 9). Engines got 0 of 9 price questions right on our live pricing page, which is the problem to solve (section 2). The worst wrong answer sat 88% under the real price, so a buyer can be badly misled before they ever visit you (section 2). The number that matters most for ThriveStack citedby is the last one: given the same rates as plain text, the engines got 9 of 9, so the fix is in your hands (section 4).

2
experiments run, with 18 AI answers scored
0 of 9
price questions right from the live page
88%
how far the worst quote fell under the real price
9 of 9
right once the rates were plain text

inaccurate pricing claims could scare away a prospective buyer or arm them with leverage in a negotiation

Kyle Poyar, AuthorGrowth Unhinged
What AI agents really think about your pricing, Sep 2, 2026
01 · Sliders

Why can't AI engines use a pricing calculator?

AI engines cannot use a pricing calculator because their crawlers read HTML and do not run scripts. A slider only changes the price after JavaScript runs. So the engine sees the one default quote in the page, and it has no way to reach the price for any other setup a buyer asks about.

The fix is to print every price on the page as plain text. The wireframe below shows where each piece goes.

ThriveStack citedby Ideal Pricing Page for AI Engines: where 9 of the 14 checklist items go, on and behind the page Wireframe with made-up sample prices. Each number is the same numbered check in the checklist in section 10. yoursite.com/pricing Pricing Plans start at $99 a month. Every rate is listed below. Starter $99 a month 5 seats Team $279 a month 20 seats Business $519 a month 40 seats Calculator 40 seats = $519 a month How pricing is calculated Step 1: Start with $99 a month. It includes 5 seats. Step 2: Add $12 a month for each extra seat. Step 3: Take 20% off when billed yearly. Step 4: Round to the nearest dollar. Worked example 40 seats: $99 + 35 extra seats x $12 = $519 a month Seats Price a month Billed yearly 5 $99 $79 10 $159 $127 20 $279 $223 40 $519 $415 How much is 40 seats a month? $519 a month, or $415 billed yearly. Here is how we work it out. Plain copies: /pricing.md and /pricing.json 9 Price sits in the server HTML and works without a slider. 2 Every place shows the same rates (page, schema, llms.txt). 9 Slider result is also printed as text in the HTML. 5 Formula written as numbered steps, every rate and rule. 6 One worked example shows the steps. 7 A table lists 10 to 15 example setups. 8 Each FAQ names a setup and gives the price first. 10 Optional: /pricing.md and /pricing.json, same rates. BEHIND THE PAGE 3 Rates live in one file. 4 The build fails if any output disagrees. Process checks with no spot on the page: 1 (list every place a price appears) and 11 to 14 (testing).
Nine checks show up here: seven on the page and two behind it. The sample prices are made up.

Read it top to bottom. Prices are plain text in the plan cards and under the calculator (check 9). The formula and one worked example get their own blocks (checks 5 and 6). A table, an FAQ and optional plain copies finish the page (checks 7, 8 and 10). Check 2 applies to every number you see. Checks 3 and 4 sit behind the page, in your build. Each number is the same numbered check in the checklist in section 10, where you can tick them off. Check 1 and checks 11 to 14 are process steps with no spot on the page.

ThriveStack citedby A crawler reads the text and never moves a slider What each visitor can learn from the same pricing page A buyer in a browser Loads the page Scripts run Moves sliders Sees anyprice An AI crawler Fetches the HTML Scripts do not run Reads the text Sees onedefault quote An AI crawler, after the fix Fetches the HTML Reads the formula Does the arithmetic Can workout any price Crawler behavior: ThriveStack
The same page gives three different results, depending on who reads it.

The next figure shows why the gap exists. A buyer moves the sliders and sees any price. ThriveStack found that none of the major AI bots use JavaScript. Gemini is the exception, because it uses Google's rendering. A crawler can still do arithmetic once the rates are in the text, and that is what the bottom row shows.

This is common. A Growth Unhinged study run with Profound tested 7,600 AI responses on Cloud 100 pricing and found only 57% of pricing pages were readable by AI.

Try ThriveStack citedby: See how engines read my pricing page →

02 · The test

Which SaaS pricing questions do AI engines get wrong?

AI engines get SaaS pricing questions wrong when the answer needs a calculator. We asked ChatGPT, Perplexity and Claude three exact setups for ThriveStack citedby and Revenue Intelligence, with web search on. They returned 0 correct prices out of 9. Four gave no price, three gave a wrong price and two offered a guess.

ThriveStack citedby Pricing Page AEO: AI engines went from 0 of 9 correct prices to 9 of 9 once the rates were text 2 experiments, 18 engine answers. 3 buyer prompts on 3 engines with web search on, Nov 1, 2026. BEFORE: THE LIVE PAGE 0 of 9 correct prices CHATGPT PERPLEXITY CLAUDE 1 No price No price $175 guess 2 $280 wrong $315 wrong $350 guess 3 No price $249 wrong No price AFTER: RATES AS PLAIN TEXT 9 of 9 correct prices CHATGPT PERPLEXITY CLAUDE 1 $773 $773 $773 2 $322 $322 $322 3 $2,076 $2,076 $2,076 Row 1: 125 prompts a day, 3 engines, 1 country. Real price $773 a month. Row 2: an agency managing 10 client brands. Real price $322 a month. Row 3: Revenue Intelligence, 50,000 users, $5M ARR. Real price $2,076 a month. 2 experiments run 18 engine answers scored 3 engines asked 3 exact price prompts Source: ThriveStack citedby test, Nov 1, 2026, one run per cell (gpt-5.5, sonar-pro, claude-sonnet-5-5). After: rates pasted into the prompt. This shows the text is enough. Engines reading the live page is untested.
Before and after: the same three prompts on the live page and with the rates as plain text. Also shown at the top of this page.

The figure also opens this page. Here are the three prompts word for word, what the live page gave them, and what changed once the rates were in plain text. All “after” answers matched the calculator on both monthly and annual prices wherever we asked for both.

#PromptOn the live pageWith the rates as text
1“How much does ThriveStack citedby cost per month to track 125 prompts daily on 3 AI engines in one country?”
Test in ChatGPT ↗
ChatGPT and Perplexity gave no price. Claude guessed about $175.All three: $773 a month, $618 billed annually.
2“How much would ThriveStack citedby cost per month for an agency managing 10 client brands?”
Test in ChatGPT ↗
ChatGPT said $280, Perplexity said $315, Claude worked out $350.All three: $322 a month, $258 billed annually.
3“What would ThriveStack Revenue Intelligence cost per month for 50,000 monthly tracked users and $5M ARR on the Conversion Funnel plan?”
Test in ChatGPT ↗
Perplexity said $249. ChatGPT and Claude gave no price.All three: $2,076 a month.

Read the “after” column with care. For that test we pasted the rates into the prompt, so it proves the text is enough for an engine to work out the price. It does not yet prove the engines have recrawled the new page. We will rerun the live test once they have (section 8 shows how). Section 9 lists every experiment we have run.

You can run these yourself. Each button opens ChatGPT in a new window and runs that prompt. Answers change from run to run and as engines reread the page, so yours may differ from the table above. The prompts below compare monthly and annual billing. We have not run them in our tests yet, so the last column shows what our calculator says.

#PromptWhat our calculator says
4“How much does ThriveStack citedby cost to track 125 prompts daily on 3 AI engines in one country if I pay monthly versus annually?”
Test in ChatGPT ↗
$773 a month billed monthly, or $618 a month billed annually.
5“How much would an agency managing 10 client brands save per year on ThriveStack citedby by paying annually instead of monthly?”
Test in ChatGPT ↗
$322 a month billed monthly, or $258 billed annually. That saves $768 a year.
6“Does ThriveStack citedby offer a discount for annual billing, and how much is it?”
Test in ChatGPT ↗
Yes. Annual billing saves 20%.
7“What is the monthly versus annual price of ThriveStack Revenue Intelligence for 50,000 monthly tracked users and $5M ARR on the Conversion Funnel plan?”
Test in ChatGPT ↗
$2,076 a month billed monthly, or $1,661 a month billed annually.

The wrong answers matter more than the blanks, as the second figure shows. A buyer told $249 who then finds $2,076 on the page has a reason to leave. The quote near the top of this page makes the same point.

ThriveStack citedby Wrong answers ran up to 88% under the real price Each bar is the quoted price as a share of the real monthly price. The line marks the real price Perplexity 50,000 users $249 vs $2,076 -88% Claude 125 prompts daily $175 vs $773 -77% ChatGPT 10 brands $280 vs $322 -13% Perplexity 10 brands $315 vs $322 -2% Claude 10 brands $350 vs $322 +9% Source: ThriveStack citedby test, Nov 1, 2026. Claude labeled its numbers as its own arithmetic
Bars under the line are quotes below the real price. Perplexity's $249 was the plan's starting price.

Try ThriveStack citedby: Run these price questions on my own brand →

03 · Fix 1: facts

Why does pricing transparency start with one set of facts?

Pricing transparency starts with one set of facts because engines repeat whatever they find. Our test caught this on our own site. Schema said price 0, llms.txt listed an old free plan, and the agency page used a 10% discount. The calculator used 8%. Clean those up before you add anything new.

ThriveStack citedby Four places on our own site disagreed on price What each source said on Nov 1, 2026, and what happened in the engine test SOURCE WHAT IT SAID RESULT Product schema Price 0, “free Seed tier” Claude repeated the Seed tier llms.txt Free plan, Starter $199 Perplexity's search surfaced it Agency page 10% off, $315 for 10 brands Perplexity quoted $315 Calculator code 8% off, $322 for 10 brands The real price, hidden in code Source: thrivestack.ai before the fix, ThriveStack citedby test
The three red rows each reached an engine's answer or its search results.

Each conflict showed up in an answer. Claude repeated “free Seed tier” from our schema. Perplexity quoted $315 from the agency page, and its search results surfaced the old llms.txt line. Google's software app markup uses offers.price for the price, and says to set it to 0 only when the app is free. So a 0 tells machines the product is free.

To run this fix, search your site for every price, plan name and discount. Check schema, llms.txt, comparison pages, FAQs and old pricing URLs. Pick your calculator as the source of truth and change the rest to match. Old pages that are already noindexed can still surface in AI search results, so correct their text as well.

Try ThriveStack citedby: Find conflicting facts about my brand in AI answers →

04 · Fixes 2 and 3: formula and examples

How do you publish usage based pricing as plain text?

To publish usage based pricing as plain text, write the formula as numbered steps in the HTML, with every rate, band, limit and rounding rule. Then add one worked example. All three engines calculated $773 correctly from a text version short enough to fit in a 500-character prompt, so length is rarely the problem.

ThriveStack citedby Seven plain steps turn a setup into an exact price ThriveStack citedby AI Visibility, 125 prompts tracked daily. Price per month Count the answers 3 engines × 125 prompts × 30 runs × 1 country 11,250 Take off what is included 11,250 − 300 included answers 10,950 Price the first band 1,000 × $0.12 $120 Price the second band 4,000 × $0.08 $320 Price the third band 5,950 × $0.05 $297.50 Round and add the base $737.50 rounds to $738, plus $35 $773 Annual billing $773 × 0.8, rounded $618 Source: ThriveStack pricing formula, Nov 2026
Engines reached the same $773 and $618 from this formula as text.

The figure walks one setup from inputs to price. Three details make the text work. State the units, such as price per answer or per 1,000 users. Say what is already included before the bands begin. And spell out the rounding, because engines will otherwise round at different steps and land a dollar apart.

This fix does reveal your rates. We chose to publish all of them, including the Revenue Intelligence bands. Anyone with patience could read them off the sliders already, and partial rates only leave engines estimating.

Then publish pricing page examples for the setups buyers ask about most: the base plan, a mid-size setup, a high-volume setup and an agency case. Ten to fifteen rows is enough, and an engine can quote a table row with no arithmetic. That is fix 3.

Publishing your rates can also change what the answer looks like. When we asked ChatGPT what 10 client brands would cost, it built a small price calculator inside its answer, with choices for prompts, cadence and engines. A buyer could price a setup right there in the chat.

ThriveStack citedby
ChatGPT built a price calculator inside its answer
Recreated from one ChatGPT answer with web search on, Nov 1, 2026. One dash changed to fit our style.
Web search  How much would ThriveStack citedby cost per month for an agency managing 10 client brands?
For an agency managing 10 client brands, ThriveStack citedby costs approximately $280 to $350 per month before agency discounts, assuming the standard tracking configuration.
10 CLIENT BRANDS · STANDARD CONFIGURATION
Monthly billing
$350/mo
Annual billing equivalent
$280/mo
Agency Mode offers additional volume discounts of up to 20%, depending on the configuration. The exact 10-brand discount isn't publicly specified.
What's included per brand?
FeatureStandard allowance
AI engines3 (ChatGPT, Perplexity, Gemini)
Tracked prompts25
Tracking frequencyWeekly (4 runs/month)
Countries1
AI answers300/month
Content audits5 pages/month
SeatsUnlimited
The pricing is usage-based, so additional prompts, daily tracking, engines, countries, audits, or content generation increase the cost. AI Visibility ... +1
Estimate your agency configuration
Prompts per client brand
25 prompts50 prompts125 prompts
Tracking cadence
Weekly
Daily
AI engines per brand
3 engines5 engines
Calculate my agency cost →
You can also use the official ThriveStack pricing calculator ↗ and select Agency Mode to get a live quote.
ChatGPT said: $350 a month, or $280 billed annually.
Real price: $322 a month, or $258 billed annually, after the 8% discount.
ChatGPT wrote every control in this answer itself.

The price in that answer was still wrong. ChatGPT said $350 a month, or $280 billed annually, and said the 10-brand discount is not public. Our page lists that 8% discount, and the real price is $322, or $258 billed annually. So a calculator in an answer is only as good as the rates the engine finds. We saw this once, on one engine, and we did not test its button.

Read more: our published pricing formula.

Try ThriveStack citedby: Check what AI says my price is →

05 · Fix 4: FAQs

How should FAQ schema match the way buyers ask?

FAQ schema should match the way buyers ask by naming an exact setup in the question and an exact price in the first sentence of the answer. “How does pricing work?” invites a vague reply. “How much to track 125 prompts daily?” gives an engine one self-contained passage to lift and quote.

ThriveStack citedby Write FAQs in the words buyers type into AI Each buyer prompt maps to one question that holds an exact price A BUYER ASKS YOUR FAQ ANSWERS 1 How much to track 125prompts every day? How much to track 125 prompts daily? $773 a month, $618 billed annually 2 What would it cost formy 10 client brands? How much for an agency with 10 brands? $322 a month, $258 billed annually 3 Pricing for 50K usersand $5M ARR? How much for 50,000 MTUs and $5M ARR? $2,076 a month, $1,661 billed annually 4 Is there a free trial? Is there a free trial? 7 days and 14 days, by product Source: ThriveStack pricing page FAQ, Nov 2026
Four of the FAQs now on our pricing page.

Each row in the figure maps a buyer's words to one FAQ. Keep the visible FAQ and the schema word for word the same, and write them both from your pricing file. Add the plain questions too: annual savings, free trials and what each unit means. Our old FAQ said answers were billed “down to $0.03”, and Perplexity quoted that line while saying it could not reach a total. A partial rate invites a partial answer.

Try ThriveStack citedby: Track the buyer questions AI answers about me →

06 · Fix 5: one file

How do you keep offer schema in sync with your prices?

Keep offer schema in sync by generating it from the same file your calculator uses, then failing the build if any output disagrees. Our conflicts all came from people updating prices in one place and missing the rest. A single source of rates removes that job, and a check catches the cases it misses.

ThriveStack citedby One pricing file feeds every place a price appears Change a rate once and every output changes with it One pricing filerates, bands, rounding The live calculators The formula and tables FAQ text and FAQ schema Offer prices in schema The llms.txt pricing line A build check fails if any output disagrees with the file ThriveStack citedby Research
Every price on the page comes from one file.

The figure shows our setup. One file holds the rates, and it feeds the calculators, the formula text, the FAQs, the schema and the llms.txt line. The check also compares a few hand-worked prices, such as $171 and $137, so a change to the maths has to be deliberate. You do not need the same stack. A spreadsheet that exports to your CMS does the same job, as long as one place owns the numbers.

Try ThriveStack citedby: Monitor AI answers after every price change →

07 · Fixes 6 to 8

How to get cited by ChatGPT on price after the basics?

To get cited by ChatGPT on price after the basics, make the text easy to fetch and add ways for agents to ask directly. These three extras are worth doing only when fixes 1 to 5 are live. An engine that opens a clean file with wrong prices still gives a wrong answer.

ThriveStack citedby Three extras help agents after the text is right Add these once fixes 1 to 5 are live and matching 1 FIX 6 Clean copies pricing.md, pricing.json Link from llms.txt Treat as a supplement 2 FIX 7 Quote links Setup in the URL Price in the HTML Canonical stays /pricing 3 FIX 8 Quote API GET a quote as JSON Expose an MCP tool Connected agents only ThriveStack citedby Research
Each extra reaches fewer readers than the page text, so they come last.
  1. Clean copies. Publish /pricing.md and /pricing.json, and link them from llms.txt. Treat this as a low-cost supplement. Google's own guide says you can ignore “creating unnecessary AI text files (like llms.txt)” for Google Search. Even so, Perplexity's search returned ours in our test, which is why a stale line is worth fixing.
  2. Quote links. Make a URL like /pricing?engines=3&prompts=125&runs=daily return that price in the HTML, with the canonical still on /pricing. Sales can share these too. Some engines may only open links from search results or from the user, so a link the model builds itself might never load. We have not tested this.
  3. A quote API or MCP tool. This gives exact answers, but only for agents that are connected or allowed to call it.

Try ThriveStack citedby: Track AI answers about my pricing →

08 · Testing

How do you measure answer engine optimization on price questions?

Measure answer engine optimization on price questions by asking each engine the same exact setups before and after your fixes, then scoring every answer against your own calculator. Correct, wrong and no price are the only three scores you need. One run per prompt is a start, but answers vary, so repeat it.

ThriveStack citedby Run the same prompts before and after each fix A five-step test any team can repeat with a sheet and an hour Write the prompts Exact setups a buyer would ask about · sheet STEP 1 Record a baseline Each engine, web search on · engine answers STEP 2 Ship the fixes Formula, examples, FAQs, schema · your site STEP 3 Wait for a recrawl Check server logs for AI bots · logs STEP 4 Retest and compare Score against your calculator · same sheet STEP 5 ThriveStack citedby Research
The same test, repeated on the same prompts, is the only fair comparison.

Run each step in the figure with the same sheet. Write prompts that name a setup, because “How much is it?” proves little. Turn web search on, and note the date and model. After you ship, check your server logs for AI bots on the pricing page before you retest, since an engine cannot reflect a page it has not fetched. Our live retest is still to come for that reason, and we will publish the result on this page.

Our own test has limits. It used one run per cell through each vendor's API (gpt-5.5, sonar-pro and claude-sonnet-5-5). Perplexity kept its search on during the text test, though its answers still came from the rates we gave it. Your results will differ by product and by day.

Try ThriveStack citedby: Track my own prompts on 10+ AI engines →

09 · Experiments

Which pricing page experiments have we run, and what did they show?

We have run two experiments on our own pricing page and scored 18 engine answers in total. On the live page, ChatGPT, Perplexity and Claude got 0 of 9 prices right. With the rates pasted in as text, they got 9 of 9. A third test, a retest of the live page, has not run yet.

ThriveStack citedby Pricing Page AEO Experiments: 2 tests run, 1 planned, and what each one shows Each card is one experiment on the same 3 prompts. A dashed card has not run yet. Nov 1, 2026. EXPERIMENT 1 · NOV 1 Ask the live page 0 of 9 3 prompts, 3 engines, web search on, 1 run each SHOWS Engines did not return our price from the page EXPERIMENT 2 · NOV 1 Rates as plain text 9 of 9 Same prompts, with the rates pasted into the prompt as text SHOWS The text is enough to calculate the price EXPERIMENT 3 · PLANNED Retest the live page Not run Once bots refetch /pricing, repeat test 1 with 3 or more runs SHOWS Whether engines have read the fixed page AUDIT Four places on our own site disagreed on price: schema, llms.txt, agency page, calculator. Source: ThriveStack citedby tests and site audit, Nov 1, 2026. One run per cell.
Two experiments are done and one is planned. A dashed card has not run yet.

Experiment 1 asked each engine three exact setups. Row 1 was 125 prompts a day on 3 engines in 1 country. Row 2 was an agency managing 10 client brands. Row 3 was Revenue Intelligence for 50,000 users and $5M ARR. No answer matched our calculator (section 2 lists every answer).

Experiment 2 is the weaker proof, and we say so. We gave the engines our rates as text, so we know the text is enough. We do not yet know that they have read the fixed page. Experiment 3 answers that, and we will add its result here.

An audit ran alongside the tests. Four places on our own site disagreed on price: the schema, llms.txt, the agency page and the calculator code. That is why fixing facts comes first (section 3).

The limits are real. Each cell is one run through the vendor's API (gpt-5.5, sonar-pro and claude-sonnet-5-5), and we did not save the raw answers for experiments 1 and 2. We will save them from experiment 3 on. Treat 0 of 9 and 9 of 9 as a small test. A benchmark would need many more runs. We keep a cell-by-cell log of every run and will add each new experiment to this page.

Try ThriveStack citedby: Run my own pricing test →

10 · Pricing page best practices (checklist)

What are the pricing page best practices (checklist)?

The pricing page best practices for AEO start with fixing conflicting facts, then publishing your formula, examples and FAQs as text, all generated from one file. Clean copies, quote links and an API come later. The 14 checks below follow that order, and nine of them are drawn on the wireframe in section 1. Tick each box as you pass it.

ThriveStack citedby Fix your pricing page in this order Work top to bottom. The first five change what engines can read today 1 Fix conflicting prices Schema, llms.txt and other pages must match FIRST 2 Publish the formula as text Every rate, band and rounding rule CORE 3 Add a table of worked examples Engines can quote a row with no maths CORE 4 Write FAQs the way buyers ask Exact setups with exact prices CORE 5 Generate it all from one file A build check stops prices drifting CORE 6 Add clean copies for agents Markdown, JSON and an llms.txt link LATER 7 Make quote links work on the server A URL returns that setup's price LATER 8 Offer a quote API or MCP tool Exact answers for connected agents LATER ThriveStack citedby Research
The eight fixes, explained one by one in sections 3 to 7.
  1. Fix conflicting prices. An engine trusts whatever it finds, so wrong facts come first. See fix 1.
  2. Publish the formula as text. This gives an engine what it needs to calculate. See fix 2.
  3. Add worked examples. A table row needs no maths at all. See fix 3.
  4. Write FAQs the way buyers ask. Match the question to a setup. See fix 4.
  5. Generate it from one file. A build check stops prices drifting apart. See fix 5.
  6. Add clean copies, quote links and an API. These three come last. See fixes 6 to 8.

Pricing page best practices (checklist): 14 checks that help AI engines quote your exact price

Tick each box as you go. Source: ThriveStack citedby pricing page tests and audit, Nov 1, 2026.

AAre your facts the same everywhere?

Why: engines repeat whatever they find, so one wrong line can become the answer.

BCan an engine work out the price from text?

Why: crawlers read the HTML and do not move sliders.

CCan you prove it worked?

Why: one run can swing with no change on your site.

Print this page to keep a copy of your ticked list.

Your fail count tells you where to start. Any fail in group A comes first, because an engine repeats whatever it finds. Our own page failed check 2 when we tested it, since four places disagreed on price (section 3). Then work down to group B, and run group C before and after each change.

Try ThriveStack citedby: Score my pricing page with a free trial →

See how AI engines answer questions about your product

ThriveStack citedby runs your prompts on the engines your buyers use, shows what they say and where they cite you, and recommends what to fix first.

Start free trial →
Frequently asked questions

Pricing page AEO: FAQ

What is pricing page AEO?

Pricing page AEO means making your prices readable and calculable by AI answer engines. You write your rates, formula and worked examples as plain text in the HTML, so an engine can quote an exact price for a buyer's setup without using your sliders.

How many experiments did you run on pricing page AEO?

We ran two so far and scored 18 engine answers. The live page got 0 of 9 prices right. With the rates pasted in as text, the engines got 9 of 9. A retest of the live page is planned. Each cell is one run, so treat it as a small test.

What should a pricing page AEO checklist include?

It should cover one set of facts everywhere, a formula and worked examples as plain text, FAQs that give an exact price, and a test you can repeat. Our checklist has 14 checks in three groups, listed in section 10.

Can ChatGPT use a pricing calculator on my website?

Usually no. ThriveStack found that none of the major AI bots use JavaScript, so sliders do nothing for them. ChatGPT can build its own calculator inside an answer, as it did in our Nov 1 test. ChatGPT can do the arithmetic itself once the rates are written as text on the page.

Do I have to publish all my rates?

Publish as much as you want engines to quote. We published every rate because partial rates left engines estimating. If you keep rates private, publish a table of example prices instead, and accept that engines cannot price setups outside that table.

Does llms.txt fix AI pricing answers?

Not by itself. Google's guide says you can ignore it for Google Search, so it will not fix Google answers. It still needs correct facts, because Perplexity's search returned our old llms.txt line in our test.

How long until AI engines show the new price?

We do not know yet, and it varies by engine. An engine can only reflect a page after it fetches it again. Check your server logs for AI bot visits to your pricing page, then retest the same prompts.

Should the price in schema be 0 if I have a free trial?

No. Google's software app guidance says to set the price to 0 when the app is available without payment. A trial on a paid plan is a paid product, so use your real starting price and mention the trial in the description.

Sources

  1. Google Search Central, Software app structured data. Read Nov 1, 2026. offers.price is required; set it to 0 when the app is free.
  2. Google Search Central, AI optimization guide. Last updated Jul 10, 2026. Says to ignore unnecessary AI text files for Google Search.
  3. Kyle Poyar and Nikolas Laskaris, Growth Unhinged, “What AI agents really think about your pricing”. Sep 2, 2026. 7,600 AI responses on Cloud 100 pricing, run with Profound, which also sponsors the newsletter.
  4. ThriveStack pricing page and formula. Nov 2026. Real prices used to score every answer.
  5. ThriveStack citedby tests. Nov 1, 2026. Experiment 1: three prompts on gpt-5.5, sonar-pro and claude-sonnet-5-5 through the vendor APIs, one run per cell. Experiment 2: the same prompts with the rates pasted in as text.