Iron Goo - AI Upgrade Agency for Ambitious Companies

---
title: "How to Get Your Prices and Hours Into the Answer AI Gives"
seoTitle: "Get Your Prices and Hours Into AI's Answer"
description: "When a customer asks AI about your services, it answers from whatever it can read. How to make sure your prices, hours, and offers are what it actually finds."
datePublished: "2026-09-01T18:17:00Z"
dateModified: "2026-09-01T18:17:00Z"
category: ai
imageAlt: "Iron Goo blog featured image on getting a business's real prices and hours into the answer an AI assistant gives a customer."
tags: [structured-data, ai-search, machine-readable, smb-ai, citations]
faq: true
---

A man sitting in his driveway asks an assistant what a full detail costs for a car like his, somewhere near him, and gets a clean answer: a named local detailer, "around ninety dollars," open till six. He calls. The detailer has not charged ninety in two years; a full detail is one-forty now, and on a Saturday they are booked till the afternoon and the phone goes to voicemail at five. The assistant did not lie. It read a stale figure off a directory page the owner forgot existed and repeated it with total confidence, because that was the only price about this business it could actually find as a number. The owner's real price was on his own site the whole time. It just was not in a form a machine could lift, which is the gap this whole piece is about: the unglamorous work of getting your **prices into answers** the assistant actually gives, so the number it quotes about your business is yours and current instead of someone else's guess from a page you abandoned.

Here is the part that stings, because it feels like it cannot be true. The owner did have his pricing online. He had a tidy page reading "every detail is tailored to your vehicle, contact us for a quote," with a button. He had a downloadable service menu, a nice PDF, with the real numbers in it. To him, the price was right there; anyone could get it. But the someone now answering on the customer's behalf is not anyone. It is an AI platform, ChatGPT or Claude or Gemini or Perplexity or one of several others, and it does not fill in a quote form and it does not open a PDF to read you a price. It answers from facts it can extract cleanly and corroborate, and a price hidden behind "contact us" or sealed in a download is, to that machine, a price that is not there. So it reached past the owner's site to the one number it could read, and the number was wrong.

## How do you get your prices and hours into the answer AI gives?

State them plainly as facts an assistant can extract, not buried in prose, an image, a PDF, or a "call for a quote" form. Mark them up so a machine reads them as price and as hours. Then keep them consistent everywhere they appear.

That is the whole shape of it, and the rest here is each part made concrete, because every step of that sentence is a place owners quietly lose the answer without ever knowing the gap was there.

## "On the website" is not "in the answer"

The assumption underneath almost every wrong AI answer about a small business is this: the facts are on the site, so the assistant has them. It does not work that way. An assistant does not read your site the way a customer does, lingering, scrolling, clicking the button that says "get a quote," downloading the menu out of interest. It assembles an answer from facts it can pull off your surface as plain, stated values and then confirm against other places you appear. What it cannot extract, it does not use. What it cannot find from you, it finds somewhere else.

So "on the website" splits into two very different things. A price a person can read and a price a machine can extract are not the same fact, even when they are the same number on the same page. A human reads the one inside the sentence "most full details run a little under one-fifty depending on your vehicle" without effort. A machine reading for a clean, repeatable price value gets a hedge, not a number it can stand behind. The fact is visible. It is not extractable. And the assistant answering a buyer's "how much" question needs the extractable kind, because it is going to repeat it as a claim.

This is exactly where the correct number quietly disappears. Not because it was missing, but because of the form it was in.

::::comparison{title="Same price, two different facts"}
:::side{label="A fact a human can read"}
"Every detail is priced to your vehicle. Contact us for a quote." A person understands instantly: prices vary, ask and they will tell you. The button works. The PDF menu, two clicks away, has the real figures. To a customer browsing, the pricing is right there and perfectly clear.
:::
:::side{label="A fact a machine can extract"}
A full detail is "$140." It is written as a price, on the page, in text, not behind a form or inside a download. An assistant reading the page lifts one clean number it can repeat and corroborate. Same business, same price the owner would quote on the phone, but now it exists in the one form the machine can actually use in an answer.
:::
::::

The "contact us for a quote" form deserves a special mention, because it is the cleanest example of a fact that is not there. To the owner it feels like the responsible choice: prices depend on the vehicle, so why pin a number that might be wrong. To a machine it is a closed door. There is no price on the page to extract, no number to repeat, nothing to corroborate. The assistant asked "how much for a full detail near me" cannot answer from a form it would have to fill out, so it does what it always does with a fact it cannot get from you. It reaches for one it can get elsewhere, and elsewhere is rarely current.

## What makes a price or an hours-block usable

Three things have to be true about a fact before an assistant can use it in an answer, and they are easiest to see against the two facts a buyer asks about most: the price and the hours.

It has to be **stated plainly**, as the fact it is. A price is a number, written as a price, on the page, in text. Not "starting in the low hundreds," not painted into a graphic of a price list, not living only inside a PDF a person downloads. Hours are the same: "Mon to Fri, 8 to 6; Sat, 9 to 2," as text, not a styled image of an opening-hours card that a human reads at a glance and a machine reads as a picture. The single most common way a small business hides a price from a machine without meaning to is putting it somewhere a person can see it and a parser cannot: an image, a PDF, a form, a hedge.

It has to be **marked up** as that kind of fact. Plain text gets you most of the way; markup is what tells the machine, without it having to guess, that this number is a price and this block is your opening hours, not just two more lines of text on a busy page. That is the layer that turns "there is a number here" into "this is the price of this service." The how of that, which markup, written how, validated how, is its own discipline and not this post's job; [how to mark up your prices and hours so a machine reads them as facts](/guides/seo/structured-data-for-smbs) is the full procedure for it. The point to carry from here is only that markup confirms what kind of fact a stated value is, and a stated value is the thing it needs to confirm.

It has to be **consistent** everywhere it appears. Your site is not the only place an assistant reads you. It reads your map listing, your directory profiles, the pages that mention you, and it reads them together. A price stated one way on your site and another way on an old listing does not average out to "close enough." It reads as a contradiction, and a contradiction lowers the machine's confidence in the whole picture, including the parts that were right. The detailer's real problem was not only that his site had no extractable price. It was that the one number out there, the stale ninety on the directory, had no current number anywhere to overrule it. Nothing he controlled was saying one-forty in a form the machine could read, so the wrong fact won by default.

:::callout{type="warn" title="A buried fact is a missing fact"}
To you, a price inside a quote form or a PDF menu is still a price; it is right there. To an assistant answering a customer, it is simply absent, and absent does not mean it stays silent. It means it goes and finds a number somewhere else. The most likely somewhere else is a third-party page you do not control and may not have looked at in years.
:::

## The wrong answer is the symptom, not the subject

It is tempting to fix this from the wrong end. The detailer's instinct, once he saw that ninety-dollar answer, was to want to correct it, to find where the assistant got it and argue the figure down. Correcting a wrong fact an assistant already states about you is a real and separate task, and [the wrong answer an AI gives about your business](/blog/ai-gets-you-wrong) is the piece that walks through tracing it back to its source. But that is the cleanup. It treats the symptom.

The subject here is upstream of the wrong answer. The reason the assistant had a stale figure to repeat at all is that the current one was never available to it in a form it could use. Get your real price stated plainly, marked up, and consistent, and you are no longer fighting a wrong number after the fact. You are making yours the number that is actually there to be found, so the wrong one has something current to lose to. The fix is not in the conversation and it is not in the correction. It is in making the right fact extractable before the question ever gets asked.

This sits one level inside a larger idea. Prices and hours are not the only facts a customer asks an assistant about; they are the sharpest, most-asked examples of a broader job. [The machine-readable business](/blog/machine-readable) covers the full set, all the core facts an agent has to find about you in a readable form before it will put you in an answer, and how the same plain-stated-and-consistent standard applies across every one of them. This piece narrows to the two facts a buyer asks about with their wallet open, price and hours, because those are where the gap between "on my site" and "in the answer" costs you a job you had already won.

## How to find which of your own facts are invisible

You do not need a developer or a tool to find out where you stand. You need one honest pass over your own surface, fact by fact, asking a single question of each: is this stated plainly, as text a machine could lift, and does it say the same thing everywhere it appears.

Start with the two that matter most and the short list of places a fact tends to get locked away from a machine. For your price and your hours, check whether each one is hiding in any of these:

- Inside a sentence, as a hedge ("priced to your vehicle," "competitive rates") rather than a stated number.
- Painted into an image, a graphic, or a screenshot of a price list or hours card.
- Sealed inside a PDF menu or brochure a person has to download.
- Behind a "contact us for a quote" or "call for pricing" form, with no number on the page at all.
- Stated one way on your site and a different way on your map listing or an old directory entry.

Anywhere a price or an hours-block lives only in one of those forms, it is, for the assistant, either unreadable or untrusted. Then widen the same pass to the other facts a customer asks about: your service area, and what you actually offer. Are they named in plain words, or implied by photos and tone? Do they match across your site, your listing, and your profiles, or do they drift?

:::stat-grid
::stat{value="Plain text" label="the only form a machine reliably reads"}
::stat{value="Price + hours" label="the facts a buyer asks about first"}
::stat{value="Every source" label="they have to agree across"}
:::

The standard for "good" here is plain to the point of feeling too simple. A fact is in good shape when a stranger, or a machine, could lift it off your page as text without interpreting an image or filling out a form, and then find the same fact, unchanged, on every other surface where you appear. That is the bar. Not persuasive, not pretty. Extractable, and the same everywhere.

One honest caveat, so nobody oversells this to you. Making a fact extractable, marked up, and consistent does not force an assistant to quote your price; no one controls exactly when or how a given platform decides to state a number. What it does is decide which number is available to be quoted, and whether the one it finds is yours and current or a stranger's and stale. You are not buying a guarantee that it speaks your price. You are making sure that when it does, the price is right.

So the one thing to go do is the pass itself: walk your own price and hours the way that man in the driveway's assistant had to, and find the ones that are sitting on your site in a form no machine can lift. Once you know which facts are invisible, marking them up so a machine reads them as facts is the next move, and it has a procedure of its own.