# What should an HVAC FAQ page include so AI assistants quote it? | HVACDiscoverable Source: https://hvacdiscoverable.com/blog/2026-09-26-hvac-faq-page-ai-assistants-quote.html HVACDiscoverable field guide September 26, 2026 **Direct answer:** Put the questions customers actually ask your dispatchers on the page, answer each one in two to three sentences with concrete numbers where possible, and keep every question and answer as plain crawlable text. AI assistants quote FAQ pages more than any other page type because the question matches the user's phrasing and the answer is already self-contained. Pages that bury answers in accordions with no text fallback, or that answer every question with "call for details," never get quoted. ## Why FAQ pages get quoted first When someone asks an AI assistant "how often should I service my furnace" or "why is my AC freezing up," the assistant looks for an answer that already matches that phrasing and can be lifted in full. An FAQ page built from real customer questions is shaped exactly like that. The question on your page and the question in the user's message share vocabulary, and the answer underneath is complete enough to stand alone. Few other page types satisfy both conditions at once. Service pages usually explain what you sell. Review pages prove you did the work. The FAQ page answers the worries and confusions that come before the purchase, which is the stage where most AI-mediated research happens. A customer choosing between two contractors often starts with "is a heat pump worth it in my climate" or "do I need to replace my ducts with the new system." The company whose FAQ answers those questions is the one the assistant names. ## Write the questions people actually ask The best source of FAQ content is your own call log. Ask the dispatchers and techs which questions they answer every week: cost of a tune-up, whether the tech can fix it in one visit, how long an install takes, whether financing is available, what the warranty covers. Those are the queries reaching AI assistants too, phrased in plain language rather than industry jargon. Ten questions from the phones beat fifty written from a marketing outline. Write each question in the customer's words, not the industry's. "How much does AC repair cost?" beats "What is the typical investment range for residential cooling remediation?" Assistants match phrasing, and your customers do not talk like a spec sheet. Read the question aloud. If nobody has ever said it to a dispatcher, rewrite it. Keep answers short and self-contained. Two to four sentences is the range. The first sentence should answer directly ("A standard tune-up runs $89 to $149 in our market"), and the rest can add conditions. Every answer should make sense if an assistant lifts it without the surrounding page, so avoid references like "as noted above" that break when quoted out of context. ## Concrete beats clever The FAQ answers that get quoted contain numbers. Prices, ranges, timeframes, and limits are the specifics assistants reach for when a user asks for specifics. "We answer emergency calls within two hours in our core towns" is quotable. "We provide fast, reliable emergency service" is not. Where you cannot give an exact figure, give a range and name the variables that move it. Name your limits honestly. "We cannot service systems over 20 years old for safety reasons" or "same-day appointments end at 2 PM on weekdays" are answers that build trust and prevent mismatched expectations. Assistants treat stated boundaries as evidence the company is deliberate about its claims, and customers who find the limit on the FAQ page are better leads than customers who discover it on the phone. Link from answers to the relevant service or pricing pages. A short answer that links to a full tune-up page gives the crawler a path and the customer a next step. The FAQ page should function as a hub: quick quotable answers on the surface, full detail one click deeper. ## The markup that matters Plain HTML is the baseline: a heading for each question and paragraph text for each answer. Assistants handle this layout well. FAQ structured data (schema.org FAQPage markup) adds a clear signal about which text is the question and which is the answer, and it is worth adding if your pages do not already carry it. But markup is the second step. A plain-text FAQ with great questions and specific answers outperforms a perfectly marked-up page of vague answers every time. Watch out for accordion interfaces that hide answers until clicked. They are fine for humans if the content is also present in the HTML source, but many implementations load the answers with scripts that crawlers never run. If your FAQ answers live only behind a click, verify that the raw page source contains the full answer text. A quick check: disable JavaScript in the browser and reload the page. If the answers disappear, so do your quotes. ## Keep it current Prices change, service areas shift, and policies get revised. An FAQ page with last year's tune-up price is a small trust problem for a customer and a stale-signal problem for assistants. Put a "last updated" line on the page and review it quarterly at minimum, more often for anything price related. Add questions as they arrive. When a new one lands on the phones repeatedly, it belongs on the page within the month. A living FAQ page compounds: each real question you add is one more answer an assistant can quote with your company attached. ## Sources * [Google Search: FAQ structured data](https://developers.google.com/search/docs/appearance/structured-data/faq) * [Google: Guidelines for representing your business](https://support.google.com/business/answer/3038177) A strong FAQ page helps systems quote a business, but it does not guarantee inclusion, ranking, citation, or a particular AI answer.