In short
State an amount or range in euros for your standard services as a visible full sentence in the HTML, with scope, VAT status and an as-of date. AI answers can quote your price correctly only if they can read it. Lab tests support this; we found no comparable study for service businesses. No one can promise a mention.
Key takeaways
- AI answers can quote your price correctly only if they can read it. In a lab test, six models cited sources with a price first more often.
- In one test, none of five AI systems named a price that appeared only in JSON-LD. The amount belongs in the HTML as visible text.
- On November 9, 2026, only 4 of 35 providers dated their prices. 16 showed no date on the page, and 15 didn’t say if VAT was included.
- GEO audits we reviewed mostly have a fixed price, retainers a starting price. Six of nine SaaS developers give an MVP range in a cost guide.
- We found no study showing that published prices bring service businesses more AI mentions. No one can promise that.
Why do prices end up in AI answers?
An AI answer to a cost question needs a number, and it takes that number from sources it can read. In a lab experiment with product reviews, six language models cited sources with a price first more often than sources without one. We haven’t found a comparable study for service businesses.
Four findings from three studies offer clues about how prices and dates work. All of them have limits you should keep in mind.
| Study | Result | Limit |
|---|---|---|
| Vishwakarma et al., May 2026, price | In an experiment with 252,000 runs in total and six language models, a source with a price was cited first more often than a source without one, in every model. | 100 product reviews with invented brand names, only two sources per run, no real web search |
| Vishwakarma et al., date | With a 2026 date instead of 2019, a source won in all six models. Against a source with no date at all, the advantage appeared in only two or three models. | same as above |
| Fang et al., 2025, revised 2026 | An artificially added newer date alone moved passages by up to 95 positions when seven language models ranked them. | ranking of research test collections, no web search |
| searchVIU, test of Oct 30, 2025 | None of five AI systems named a price that appeared only in the JSON-LD. The prices they found were mostly in the visible text. | one test page with fictitious products, not repeated since |
Source: Vishwakarma, Kumar, Jamidar (SIGIR 2026) (external site), · sections 3 and 5
Source: Fang, Tao, Chen, Chang, Sakai (external site), · first version 2025
Source: searchVIU (external site), · vendor study · test of Oct 30, 2025
During our research on October 24, 2026, we used an AI model’s web search tool to ask what custom software costs. We didn’t use a consumer chat app for this. The figures in its answer came from a single provider’s cost guide. One run in one system proves little. It does show the path a number can take.
AirOps looked at the pages ChatGPT retrieved for commercial prompts and analyzed which ones it cited. For prompts that check a detail such as price, pages with many price points were more likely to be cited. That’s a correlation. It doesn’t show cause. Our guide to service pages puts the study in context in the section How do prospects find out your price?
Source: AirOps (external site), · vendor study · ChatGPT only, correlations
For service businesses in Germany, we found no study showing that published prices lead to more mentions in AI answers. Google’s guide to generative AI features (external site) doesn’t address prices either. So publish prices primarily for your prospects. Showing up in AI answers is a possible bonus. Our guide to GEO (generative engine optimization) reviews the overall evidence in the section What’s proven about GEO, and what isn’t?
Which price format fits which service?
State a fixed amount when the scope is set, a starting price with an upper limit for packages that grow, and a range with cost drivers for projects. In our review, GEO audits mostly have a fixed price and retainers a starting price; only one provider gives an upper limit. “Price on request” gives an AI answer no figure.
| Service | Fixed amount | Starting price | Range | Total |
|---|---|---|---|---|
| GEO audit or quick check | 7 | 1 | 0 | 8 |
| GEO retainer with implementation | 2 | 13 | 0 | 15 |
| GEO setup | 2 | 2 | 0 | 4 |
| Website, smallest package | 3 | 5 | 0 | 8 |
| SaaS MVP | 1 | 1 | 7 | 9 |
Source: our own survey, · 44 offerings from 35 providers; we counted the price stated for each package
This gives you a simple rule:
- Fixed amount, when scope and result are set. This suits audits and fixed packages. Seven of eight GEO audits have a fixed price.
- Starting price, when the package grows with the scope. A starting price alone only says where prices begin. So give an upper limit or say what pushes the price up. One provider in our survey states explicitly: from €1,500 up to €10,000 a month.
- Range, when every project is different. Seven of nine providers give a range for a SaaS MVP. For six of them, the range appears in a cost guide and describes the market in general. Say what your range depends on, for example the number of integrations or user roles.
Whether to use “price on request” is your decision. But an AI answer finds no figure there, and neither do prospects. Our GEO cost guide and our SaaS MVP cost guide show how such ranges come about and what they include.
Common mistake: A starting price that doesn’t say what it includes. Then there’s nothing to compare the amount with.
Done when every service on your website has an amount or a range, or you’ve deliberately chosen “price on request.”
What does a citable price statement look like?
A citable price statement is a full sentence that makes sense on its own. It names the service, scope, amount or range, time period, VAT status, target customers and as-of date. An AI answer can then use the sentence without knowing the rest of the page.
Fixed price:
[Service] from [Company] costs €[amount] excl. VAT [one-time / per month] for [scope in numbers]. This offer is for [target customers]. As of [Month D, YYYY].
Starting price:
[Service] from [Company] starts at €[amount] excl. VAT per month for [smallest scope]. The price rises with [cost driver], up to about €[amount]. As of [Month D, YYYY].
Range:
[Service] from [Company] costs €[low amount] to €[high amount] excl. VAT. The price depends mainly on [cost drivers]. We give the exact amount after [step, for example an intro call or analysis]. As of [Month D, YYYY].Each element has a reason. The figures come from our review of 35 providers in the section “From our work.”
- Service and scope in numbers: pages, questions, hours or roles. An amount without a scope can’t be compared.
- Amount or range with a time period: “one-time” or “per month.”
- Excl. or incl. VAT: On the page with the amount, 15 of 35 providers don’t say. German pages use netto for excl. VAT and brutto for incl. VAT, and readers abroad may know neither term. If an answer picks up the amount without this detail, no one can tell which figure it is.
- Target customers: businesses, freelancers or consumers.
- As-of date right next to the statement: Only 4 of 35 providers do this.
- Cost drivers for starting prices and ranges.
Write the statement as a full sentence in your body text, even if you also have a pricing card. A number on a card only makes sense in the context of the page. A sentence still makes sense when it’s lifted out. Our guide Service pages for AI search shows how the price fits with the other details on a service page.
Common mistake: The page says only “from €[amount],” with no service, time period or date. Fragments like that are hard to cite.
Done when someone with no background knowledge can read the sentence and name the service, amount, time period, VAT status and date.
Where should the price appear on your website?
The price belongs in the delivered HTML as visible text, on the service page and on a pricing overview, with the same value everywhere. In one test, no AI system named a price that appeared only in the JSON-LD. Calculators that show amounts only through JavaScript aren’t enough on their own.
How to do it:
- State the amount on the service page and on a pricing overview. All 35 providers in our review have their amount in the delivered HTML, so it’s doable.
- Check the page source. Our guide shows the method in the section Are your services visible in the HTML?
- Check whether AI crawlers are allowed to read your website. An amount no search crawler can fetch won’t reach an answer.
- Keep the values the same on every page. One provider in our survey shows two different figures for a SaaS MVP on two guide pages: €10,000–25,000 and €15,000–30,000.
Markup is an extra. Google doesn’t require any special markup for its AI features (Google Search Central, AI guide, Jul 10, 2026 (external site)). If you use JSON-LD, it has to match what’s visible: Google says not to mark up content that readers can’t see (Google Search Central, structured data guidelines, Jul 10, 2026 (external site)). Of our 35 providers, 12 include the amount as a number in their JSON-LD, and 5 of those also include the VAT status. None sets a validity date. You’ll find the fields for this at Schema.org (external site), and our article on structured data explains the limits.
{
"@context": "https://schema.org",
"@type": "Offer",
"name": "[Service]",
"priceSpecification": {
"@type": "PriceSpecification",
"minPrice": [low amount],
"maxPrice": [high amount],
"priceCurrency": "EUR",
"valueAddedTaxIncluded": false,
"validFrom": "[YYYY-MM-DD]"
}
}Common mistake: The price appears only in a calculator that shows it through JavaScript after someone enters their details. In searchVIU’s test, only Gemini found a price added by JavaScript when fetching the page directly. Perplexity and Google’s AI Mode knew it only after indexing.
Done when you can find the amount in the page source and it’s the same on every page.
How do you keep prices up to date?
Put an as-of date right next to the price statement, check your prices on a fixed schedule and change the date only after a real check. When a price changes, update every place at the same time, including the JSON-LD.
The date has to be accurate. Google asks you to show the date prominently and to use the same date in your markup (Google Search Central, byline dates, Dec 10, 2025 (external site)). In its self-assessment for helpful content, Google explicitly asks whether you’re changing the date of pages to make them seem fresh when the content hasn’t substantially changed (Google Search Central, helpful content, Oct 5, 2026 (external site)). So the lab finding that a recent date shifts rankings is no reason to change dates without a real update.
How to do it:
- Set a regular date for checking your prices, for example once a quarter.
- Change “as of” only when you’ve actually checked the prices.
- Keep a list of every place a price appears: service page, pricing overview, FAQs, JSON-LD, directories.
- Once a year, check what third-party comparisons say about you and ask for corrections.
Third-party overviews go out of date. On November 9, 2026, one GEO provider listed only “price on request” for all its packages. On that same day, another provider’s price comparison from August 17, 2026, still showed it with euro amounts.
Common mistake: The date in the footer changes automatically with every page view. Then it says nothing about the prices.
Done when the next check is on your calendar and the as-of date shows the day of the last real check.
What are the arguments against public prices?
The main arguments against public prices are that competitors can see them and that prospects may read a figure as a fixed amount when their project costs more. Ranges and cost drivers soften both. For highly customized services, “price on request” can remain the better choice.
Prices matter to prospects. In 2013, Nielsen Norman Group called pricing the information business customers need most online, and for complex offerings it advised showing prices for typical cases or ranges. That finding is old, and we haven’t found newer, reliable figures for service businesses. In 2019, Forrester pointed out the downside: for offerings that need explaining, public prices can turn a conversation into one about price too early, and highly customized offerings are a poor fit for them.
Source: Nielsen Norman Group (external site), · vendor study
Source: Forrester (external site), · vendor study
| Objection | What’s true | What you can do |
|---|---|---|
| Competitors will see our prices | True. We found no reliable data on the consequences. | Publish ranges and cost drivers in place of detailed calculations. |
| The figure will be read as a commitment | A number looks firm even when it’s meant as a guide. | Say what’s included and when the amount becomes binding. |
| Our projects are too individual | True for highly customized services, and Forrester says so too. | Give prices for typical cases or a range, or deliberately stay with “price on request.” |
| Prices go out of date quickly | True. An outdated figure creates false expectations. | Add an as-of date and schedule regular price checks. |
The German-language guides on this question that we read make similar arguments but don’t back them with data. They don’t address AI answers.
What should you check before you publish prices?
Before you publish, establish whether you sell only to businesses or also to consumers, because that determines how you have to state prices. This is a legal question this guide does not answer, and the rules vary by country. Have a local lawyer review your pricing page.
In practice, it helps to name your target customers right next to the price. At least two providers in our survey state, right next to their net prices, that their offers are for businesses only. If you don’t charge VAT, say that too, so no one has to guess.
From our work: how do 35 providers state their prices?
On November 9, 2026, we fetched the pages of 35 providers based in Germany as a server delivers them, without JavaScript, and counted how they state prices there. They are the 18 GEO providers, 8 web designers and 9 SaaS developers from our GEO cost guide, our website cost guide and our SaaS MVP cost guide. The GEO providers and web designers state the price of their own packages on their pages; for six of the nine SaaS developers, the page we reviewed is a cost guide that gives a range. All 35 state their amount in the HTML. Only four date it.
| Feature | GEO (18) | Website (8) | SaaS MVP (9) | Total (35) |
|---|---|---|---|---|
| Amount in the delivered HTML | 18 | 8 | 9 | 35 |
| VAT statement | 13 | 6 | 1 | 20 |
| Visible date on the page | 7 | 6 | 6 | 19 |
| of which: date on the price statement | 3 | 0 | 1 | 4 |
| No visible date | 11 | 2 | 3 | 16 |
| Amount as a number in JSON-LD | 8 | 3 | 1 | 12 |
| of which: VAT status in JSON-LD | 2 | 3 | 0 | 5 |
Source: our own survey, · 35 providers, one page with prices each, delivered HTML without JavaScript
On method: a VAT statement means netto (excl. VAT), zzgl. MwSt. (plus VAT), inkl. MwSt. (incl. VAT) or a note that no VAT is charged. A date on the price statement means an as-of date that refers to the prices or the price table; one of these four providers gives only the year there. A date in an author line, in an article’s header or in the footer counts as a date on the page, even when it sits in the same box as the price. Dates only in the JSON-LD don’t count as visible here. For the count, we read exactly one page per provider; only one GEO provider’s audit price comes from its cost guide. One web designer says nothing about VAT on the page we reviewed but does on its pricing page. If its pricing page counts too, the number of web designers with a VAT statement rises from 6 to 7 of 8, as in our review of website packages.
The review has limits. We included only providers that publish prices, so it doesn’t show how many don’t. Two other counts give a rough indication. In our review of 17 software providers on November 9, 2026, eight published euro amounts for their own services. Of 12 GEO providers on our shortlist, six published no prices as of October 24, 2026. The review also covers only how prices are stated. It says nothing about their effect in AI answers.
As a rule, we don’t name competitors, so you can’t check the individual details here directly. The review contains no Datafalke prices. We sell websites, GEO services and software ourselves, so we have a stake in this topic.
Frequently asked questions
Is a minimum budget enough instead of a price?
As the smallest citable statement, yes. One provider in our survey gives only a minimum budget of €1,000 excl. VAT a month. That tells prospects when a conversation is worthwhile. Say what the budget covers.
How do I check whether AI systems mention my price?
Use fixed questions in several systems, with several runs per question. Ask your cost question the way customers ask it, and note which figure the answer gives and which source it comes from. Our guide How to measure AI search visibility shows how to set this up.
What should I do if a portal lists the wrong price?
Ask the operator to correct it, and point to the page with your current price and its date. Portals and comparisons don’t update themselves. That’s why it pays to maintain your own page as a dated source you can point to.