How to Make Your Prices and Services Readable for AI Assistants

What "AI-readable" actually means

AI assistants and the crawlers behind them are, at their core, reading text. They don't reliably read text that's baked into an image, and most of them can't open and parse a PDF the way a person skims one — even when they technically can access the file, what they extract from it is often garbled, incomplete, or just skipped in favor of a competitor's page that's easier to read. Making your site AI-readable isn't a redesign project. It's confirming that the facts a customer would ask about — price, hours, service area, policies — exist somewhere on your site as actual, selectable text.

This is also the first step behind how Tailwind's own AI product works: before it can publish a catalog AI can quote to a customer's assistant, it has to read your website and find real prices and services to work from. If that information isn't there in readable text, there's nothing accurate to publish — not for Tailwind, and not for any other AI tool trying to answer a question about your business. Everything below is about fixing that at the source.

Why this is worth fixing now

A growing share of the questions people used to type into a search bar — "how much does a brake job cost," "does this clinic take new patients," "what's the cancellation policy at this studio" — are now being asked inside a chat window instead. The assistant on the other end doesn't visit your site the way a person does, scrolling past a hero image and skimming for the number they need. It's trying to extract a specific fact from your page's underlying content, and if that fact isn't there in a readable form, the assistant has three options: guess, say it doesn't know, or surface a competitor whose site gave it a clean answer. None of those outcomes work in your favor.

Rule 1: Put your prices in text, not images or PDFs

The single most common reason an AI assistant can't tell a customer what something costs at your business is that the price only exists inside a photographed menu board, a scanned price sheet, or a PDF price list meant to be downloaded and read by a person. All three are hard or impossible for most AI crawlers and assistants to reliably read:

• Images. A price list saved as a JPEG or PNG — even a clean, well-designed one — is just pixels to a crawler unless it runs the image through OCR, which most general-purpose AI crawlers don't do reliably, if at all.
• PDFs. Some PDFs contain real, selectable text; plenty of others are scanned images wrapped in a PDF container, which puts you right back in the image problem. Even when the text is real, PDFs sit off to the side of your normal page structure, so they're more likely to be missed or deprioritized entirely.
• Infographics and pricing graphics. The same logic as images — if the price is part of the artwork rather than part of the page's text, it's effectively invisible to a machine reader.

The fix is simple, if a little unglamorous: have an actual web page with an actual HTML table or list that states your services and prices in plain text. You can still show the nicely designed graphic alongside it for human visitors — just don't let it be the only place the price lives.

Rule 2: Keep a plain-text FAQ page

Customers — and increasingly, the assistants acting on their behalf — ask the same handful of questions over and over: Do you offer free estimates? Is there a cancellation fee? Do you work weekends? Can I book same-day? If the answers only exist in a video, an Instagram caption, or a graphic pinned to your homepage, they're effectively unanswerable for anything trying to read your site as text. A plain FAQ page, with the question written out and the answer in a sentence or two underneath it, is one of the highest-value, lowest-effort pages you can add.

Rule 3: State your policies in text, somewhere

Booking, cancellation, returns, deposits, warranty terms — these details often live only in a sign on the shop door, a line in a contract a customer signs after they've already booked, or a verbal explanation from staff. None of that is readable before the fact, by a person or an assistant. Put the policies that actually matter to a buying decision — can I cancel without a fee, is a deposit required, what's your return window — on a page as text. It doesn't need to be a legal document. A short, honest paragraph is enough.

Rule 4: Consider adding Service and Offer schema markup

Once your prices, FAQs, and policies exist as visible text, there's one more layer worth considering: structured data, sometimes called schema markup. This is a small block of code added to a page that doesn't change anything a visitor sees — it sits quietly in the page's source — but it labels specific facts (a service name, a price, a currency) in a format that machines can parse without ambiguity, as a backup to the visible text. A simplified example for a single service might look like this:

{
  "@type": "Service",
  "name": "Standard Oil Change",
  "offers": {
    "@type": "Offer",
    "price": "49.99",
    "priceCurrency": "USD"
  }
}

You don't need to understand every property to get value from this — a developer or a website platform's built-in schema plugin can usually add it in an afternoon. The important point is that schema markup is a supplement to clear, visible text, not a replacement for it. A site with perfect schema markup and no visible prices is still a site most AI tools will struggle to quote accurately.

Common mistakes that quietly block AI from reading your site

• Prices that only live on social media. An Instagram post or Facebook caption with your rates is invisible to most website crawlers entirely — it's not even on your site.
• A "Contact us for pricing" page with no range at all. If an assistant can't find any number, it generally won't invent one — but it also won't recommend you for a price-sensitive search when a competitor's page states a real figure.
• Policies buried in a long terms-of-service document. A cancellation policy stated on page 11 of a legal document, written in legal language, is technically text but practically unreadable for the purpose of answering a simple customer question.
• Out-of-date text left over from a previous pricing structure. A clearly worded old price is arguably worse than no price at all, since it gets quoted as current when it isn't.

A quick win: llms.txt

While you're making these changes, it's also worth adding an llms.txt file — a short, plain-text summary file some AI tools look for at the root of a website. It's not a confirmed ranking signal and won't substitute for the fixes above, but it's a five-minute addition with no downside. Our free llms.txt generator builds one from a short form if you want to add it while you're already working on this.

A related but different problem

Everything above is about preparation — making sure the facts about your business are in a form AI can actually read in the first place. That's a different problem from an AI assistant already having read something about you and gotten it wrong — outdated hours, an incorrect price, a review summary that misstates what you offer. That's a real issue worth solving, just not the one this guide covers.

A quick self-check

Before moving on, it's worth testing your own site with a few honest questions:

1. Can you select and copy your prices with a mouse, or are they locked inside an image or PDF?
2. Does a real FAQ page exist with questions and answers written out as text?
3. Are your booking, cancellation, and return policies stated in a sentence or two somewhere a visitor can read before contacting you?
4. Does your site have any Service or Offer schema markup, and if not, is that something your website platform can add easily?

Common questions

Do AI assistants ever read PDFs correctly?

Sometimes, if the PDF contains real selectable text and the assistant's crawler chooses to open it. It's inconsistent enough that you shouldn't rely on a PDF as the only place a price or policy lives — treat it as a nice-to-have download, not your source of truth.

Do I need schema markup if my prices are already visible as text?

Visible, selectable text is the foundation and matters more than schema markup on its own. Schema is a worthwhile next step once the basics are in place, not a substitute for them.

Will this guarantee an AI assistant recommends my business?

No — being readable is necessary but not sufficient. An assistant also needs a reason to choose you over a competitor, which is where your reviews, reputation, and the completeness of your catalog come in. This guide is about removing the readability barrier so that, when an assistant does look at your site, it finds accurate information instead of nothing at all.

Does this mean I should get rid of my downloadable price list PDF?

Not necessarily — a downloadable PDF is still convenient for customers who want to print it or save it for later. The point isn't to delete the PDF, it's to make sure the same information also exists as plain text on an actual page, so a human-friendly download isn't also your only machine-readable source.

How long does this actually take to fix?

For a typical small-business site, converting a price list from an image or PDF to a text page is an afternoon's work, writing a basic FAQ page is another, and stating your core policies in text is usually a matter of pulling language you already have from a contract or a sign and rewriting it in plain sentences. Schema markup takes longer if you're adding it by hand, but many website platforms (Shopify, WordPress plugins, Squarespace) offer built-in or plugin-based ways to add it without writing code yourself.

Where this leads

Making your website AI-readable is unglamorous, mostly text-formatting work — but it's the prerequisite for anything more ambitious, including letting AI assistants quote your real prices and send booking requests on a customer's behalf. If you'd rather have that catalog built and kept current for you, see how Tailwind's pricing works — plans start at $5/month per tool or $50/month for everything on the Full plan, with the first month free, no credit card and no contract.