Why do AI assistants quote Q&A content first?
Assistants don’t read your site the way a person does. When someone asks a question, the system breaks your pages into passages, scores each passage against the question, and hands the best few to the model. The model then writes its answer from those passages and, in most tools, cites where they came from.
A passage wins that scoring when it looks like the question and answers it immediately. A heading that reads “How long does a bathroom remodel take?” followed by a paragraph that opens with “Most full bathroom remodels take three to five weeks” is about as close to a perfect match as a system can find. A paragraph buried in a 900-word “About Our Process” section that eventually mentions timelines is not.
Q&A sections work because they pre-chunk your content into exactly the units these systems retrieve. You are doing the model’s work for it, and it rewards you by using your words.
Where do the questions come from?
The most common mistake is writing questions nobody asks. “Why choose us for HVAC service?” is a marketing question. Nobody types it into an assistant. Real questions come from five places you already have access to:
Your phone and inbox. Ask whoever answers the phone to keep a running list for two weeks. The questions that repeat are your first ten.
Your Google Business Profile. The Q&A tab and the reviews are full of the language customers actually use, including the words they get wrong. Keep their phrasing.
Sales objections. Every reason a prospect hesitates is a question: “Do you charge for estimates?”, “Are you licensed for commercial work?”, “What happens if it rains on install day?”
Google’s own suggestions. Type your service plus your city into Google and read the “People also ask” box and the autocomplete list. These are aggregated from real searches.
The assistants themselves. Ask ChatGPT, Gemini, and Perplexity what people want to know before hiring your type of business. Then ask the follow-up questions they suggest. You are reverse-engineering the questions the models already expect to answer.
Aim for six to ten questions per service page. More than that and the section becomes a dumping ground. Fewer and you are leaving obvious questions unanswered.
How do you write an answer that gets quoted?
An answer gets lifted when it can stand on its own. The model may only see your paragraph, not the page around it. Write each one as if that is true.
Answer in the first sentence. Not “Great question, and it depends on several factors.” Start with the answer: “A standard roof replacement on a 2,000 square foot home in the St. Louis area typically runs $12,000 to $18,000.” Add the nuance after.
Use specifics. Numbers, ranges, timelines, brand names, neighborhoods, license types. Specifics are what make a passage worth citing. “Pricing varies” gives the model nothing to work with. “$150 to $350 for most residential drain cleanings, with camera inspection adding $200 to $400” gives it a quote.
Keep it to 40 to 80 words. Long enough to be complete, short enough to be pulled whole. If an answer needs 300 words, it is really a section of the page, or its own article.
Name yourself and your area once. “At Posted Social we…” or “for homeowners in Kirkwood and Webster Groves…” helps the model connect the answer to your business and your service area when it is deciding who to recommend.
Write like you talk to a customer. Contractions are fine. Jargon is not, unless you define it. The assistant is going to paraphrase you for a homeowner, so meet it halfway.
Here is the shape, using a question a St. Louis plumber might field:
Do you charge for a plumbing estimate in St. Louis?
No. Estimates for repairs and installations within St. Louis City and County are free, and we give a written price before starting work. The exception is diagnostic work that requires a camera inspection or opening a wall, which is billed at $189 and credited toward the repair if you hire us.
Direct answer, a number, a location, a named exception. That is a quotable paragraph.
Where on the site should Q&A sections live?
Not on one giant FAQ page. A standalone /faq/ page is fine to have, but it is the weakest place for this content because it lacks context. A question about drain cleaning prices on a page that also covers your warranty, your hiring, and your holiday hours tells the system less than the same question on your drain cleaning service page.
Put the questions where the topic already lives:
- Service pages get the service-specific questions: cost, timeline, process, what’s included, what’s not.
- Location pages get area-specific questions: service radius, travel fees, permits in that municipality.
- The homepage or about page gets the business-level questions: licensing, insurance, how long you’ve been around, who shows up.
- Blog posts get one or two questions at the end that the post didn’t fully answer.
Each question gets its own heading (H3 under a “Common questions” H2 works well). Keep the answer text in the page HTML. Accordions are fine as long as the content is in the source, not loaded on click. If your site builder hides the answer until someone taps, check the page source to confirm the text is actually there.
Does FAQPage schema still matter?
Yes, with a caveat. In 2023 Google stopped showing FAQ rich results for most businesses, so the little expandable answers in search results mostly disappeared. That led a lot of people to remove the schema. Don’t.
Structured data doesn’t add information the page lacks, but it removes ambiguity. FAQPage markup tells any system reading your page “this is a question, this is its answer, they belong together.” That is useful to a retrieval system trying to decide where a passage starts and ends. It also travels: assistants that build on Bing or Google’s index inherit that clarity.
Rank Math and most SEO plugins have an FAQ block that outputs the markup automatically. Use it, and make sure the visible text and the schema text are identical. Marking up questions that don’t appear on the page is a fast way to lose trust with both search engines and assistants. FAQPage is one of four types of schema markup for local businesses worth having.
Should you also answer questions on Google Business Profile?
Yes, and this is the step most businesses skip. The Q&A tab on your profile is public, indexed, and pulled directly into assistants that lean on Google’s data. It is also one of the few places a customer can post a wrong answer about your business and have it sit there.
Seed it yourself. Post your top eight questions as the business owner and answer them. Match the wording on your website so the two sources corroborate each other. Then check it monthly for questions from customers and answer those within a day or two.
How do you know if it worked?
There is no dashboard yet that says “you were quoted 14 times this month.” Testing is manual, and that is fine, because it takes ten minutes.
Once a month, ask ChatGPT, Gemini, Perplexity, and Google’s AI Mode the six to ten questions you built the section around, with your city attached. Note three things: whether your business is mentioned, whether your wording is quoted or paraphrased, and which page is cited. Keep it in a spreadsheet. Expect nothing for the first four to eight weeks after publishing. Retrieval indexes update on their own schedule.
Two leading indicators show up sooner. In Google Search Console, look for impressions on long, question-shaped queries you didn’t previously appear for. In your analytics, watch for referral traffic from chatgpt.com, perplexity.ai, and gemini.google.com. Both usually move before the manual checks do.
What not to do
Don’t stuff keywords into the questions. “What is the best affordable emergency plumber in St. Louis MO near me?” is not a question a person asks. Assistants are trained on human language and score it accordingly.
Don’t answer with a sales pitch. “Call us today to find out!” is a non-answer. The model skips it and finds a competitor who gave the number.
Don’t duplicate the same block across every page. Ten identical questions on twelve service pages dilute all of them. Write to the page.
Don’t hide answers behind tabs loaded by JavaScript. If the text is not in the HTML, it does not exist to a crawler.
Don’t set it and forget it. Prices, timelines, and service areas change. A quoted answer with last year’s pricing is worse than no answer.
Where Posted Social fits
Most of what’s in this article is a writing job. If your team has the time, this is the piece of AI visibility work you can absolutely do in-house, and the question-gathering step alone will improve your sales conversations.
If you would rather hand it off, Q&A sections are built into every service page we write, with schema, GBP seeding, and monthly assistant checks included. That conversation starts with our team. Contact Our Team
Common questions
How many FAQs should a service page have?
Five to eight. Enough to cover cost, timeline, process, and what’s included, without turning the section into a dumping ground. If you have more real questions than that, the extras probably belong on a different page or in a blog post.
Should FAQs be on a separate page or on service pages?
On service pages. A standalone FAQ page is fine to keep, but a question about a specific service is worth more to a search engine or AI assistant when it sits on that service’s page, surrounded by related content.
Does FAQPage schema still matter in 2026?
Yes. Google stopped showing FAQ dropdowns for most sites in 2023, but the markup still labels each question and answer for anything that reads the page, including AI assistants. Add it to every FAQ block, and keep the schema text identical to the visible text.
How long until AI assistants start quoting a new FAQ?
Usually four to eight weeks. Retrieval indexes update on their own schedule. Search Console impressions on question-style queries and referral traffic from chatgpt.com or perplexity.ai tend to move first, before a manual prompt test shows your business by name.