The price question: why your prices belong in plain text
"What does it cost?" decides bookings. If the price only lives in your booking widget, neither your website nor an AI assistant can answer it.
Most local businesses have a price that decides the first visit: a first appointment, a trial session, a starter package, a standard service. It is the number that turns a curious person into a customer standing at your door. Yet on many business websites that number is nowhere in the page text.
Where the price usually hides
Booking and reservation systems are good at selling, so businesses let them. The schedule, the offer and the price live in an embedded widget or a link to the vendor’s checkout. Most booking vendors offer a snippet you paste into your site, and the widget then draws its content from their servers. The result looks fine to a visitor with a fast connection and a mouse.
It looks different to anything that reads your site rather than looks at it.
What a crawler sees
Content that appears inside an embedded frame belongs, technically, to the vendor’s page, not yours. Google can index some embedded content, and it added the indexifembedded instruction specifically for the case where a page is only meant to be seen inside another site (source 2). But that content is attributed to the frame’s own URL. A prospect asking an assistant about your business gets an answer built from your pages.
Content built by JavaScript is a second layer. Google renders JavaScript, though with delays and limits it documents itself (source 1). Several AI crawlers fetch the raw HTML only. If your price is only written to the page by a script, or only fetched into a widget, the raw HTML does not contain it. My check flags this as “limited text in the fetched HTML; rendering not tested”, because a non-rendering fetch cannot prove what a rendering one would see. It can prove that the price was not in the HTML.
What this does to the question that matters
When I ask an assistant “what does a first appointment at [business] in Rotterdam cost and how do I book it?”, the good outcome is a sentence with the price and a link to your booking page, citing your site. The common outcome is one of three worse things: “prices are not listed on the website”, a guess drawn from a directory that is out of date, or a competitor’s offer because their page had the answer.
None of those is a problem with the assistant. The page did not contain the sentence.
The fix takes one sentence
Write the offer as text, near the booking button and on the pricing page, in the language of the site:
Een eerste afspraak kost €45 en duurt 30 minuten. Daarna betaal je €35 per behandeling. Maak je afspraak via de knop hieronder.
Include what it is, what it costs, what it includes, and any condition such as “for new customers only”. Keep the widget; just stop letting it be the only place the fact exists. When the price changes, change both.
While you are there, do the same for the two other facts that hide in widgets: your opening hours, and which services you actually offer.
Twenty-minute action
Open your pricing page, press Ctrl-U (or View Source), and search the code for your price. If it is not there, it is not on your website in any sense a machine understands. Add the sentence, and check again.
The free check looks for exactly this and shows you what the assistants currently say when asked the price question about your business.
Sources
- Google Search Central: Understand JavaScript SEO basics (checked 2026-09-13)
- Google Search Central Blog: Robots meta tag: indexifembedded (2022) (checked 2026-09-13)
