Anthony FAQ Pages That Google And AI Actually Use
An FAQ page that Google and AI tools use is one where each question is a real question a customer asks, the answer starts with the actual answer in the first sentence, and the page sits on the topic it belongs to instead of a dumping ground called "FAQ." Schema helps a little. The writing does the work.
We audit a lot of local business sites. The typical FAQ page is a list of eight questions nobody asked, with answers that dodge the point, stuffed with the business name and the city. It reads like it was written to impress a search engine, and the search engine is not impressed.
Key points
- Start from real questions: phone calls, texts, reviews, your own search console, not guesses.
- Answer in the first sentence. Put the nuance after.
- Put each FAQ block on the page where the question comes up, not only on one master page.
- FAQ schema is fine but optional. It must match the visible text exactly.
- Google stopped showing FAQ rich results for most sites in 2023. The value now is in being quoted and being clear.
What Changed With FAQ Rich Results
In August 2023, Google announced it would show FAQ rich results only for well known, authoritative government and health sites. For everyone else the little expandable questions under the blue link went away. Google also deprecated HowTo rich results around the same time.
So if someone sold you "FAQ schema" as a way to take up more space in the results, that was a trick with an expiry date. The schema itself still validates, and Google still reads it. It just does not produce the visual bonus it used to.
What did not change is that people ask questions, search engines try to answer them, and AI tools that summarize the web look for short, clear, self contained answers to quote. That is the target now.
Step 1. Collect The Questions People Really Ask
Do not brainstorm in a conference room. Pull the questions from places where customers already said them.
| Source | What you get |
|---|---|
| Call notes and voicemail | The raw wording, including the worry behind it |
| Text threads and chat | Short questions, usually about price and timing |
| Your Google reviews | What people were nervous about before they hired you |
| Search Console queries | Questions already typed into Google that hit your site |
| "People also ask" box | Neighbors of the question you started with |
| Competitor pages | Gaps, because they skip the hard questions |
At Supercanic, our customers asked the same few things over and over: can you fix it at my house, how much before you start, do you need a tow. Those became FAQ blocks on the pages for each repair, not a general page. You will find the same pattern in your own phone log if you read it for an hour.
Step 2. Write The Answer First
Open with the answer, then add the conditions. Compare two answers to the same question.
Weak: "At our company, we pride ourselves on transparent pricing and offer competitive rates on all services. Please contact us for a custom quote."
Strong: "The price depends mostly on the battery size and your vehicle. We give you the exact price by text before we drive out."
The strong version has a first sentence that stands alone. If a search engine or an AI model pulls only that sentence, it is still useful and still true. Keep these rules:
- First sentence is the answer. Yes, no, a number, a time frame.
- Second and third sentences are the "it depends" and the next step.
- Keep the whole thing under 80 words for a short question.
- Never answer a price question with "call for a quote" only. Give a range or a way to get one fast.
Do not invent numbers to sound confident. If you cannot give a real range, say what drives the price. That is more honest and more useful than a fake figure.
Step 3. Put The Question Where It Belongs
A single FAQ page with forty questions is a junk drawer. Break it up.
- Service pages get questions about that service: cost, time, what is included.
- Location pages get questions that are local: service area, parking, hours.
- Pricing or quote pages get questions about payment and guarantees.
- A short main FAQ gets only the general questions about the business.
This helps in two ways. A visitor sees the answer exactly when the doubt arises, and a search engine sees a page about "brake repair" that also answers "how long does a brake job take." That is relevant, not stuffed.
If you want a step by step setup, my guides section has an FAQ guide you can follow.
Step 4. Add Schema, Honestly
FAQPage markup is a small block of structured data that matches the questions and answers on the page. Use it if you like. Three rules:
- The text in the schema must match the text on the page, word for word. Hidden FAQ markup that is not visible to users is against Google's structured data guidelines.
- Do not mark up ads or promotions as questions.
- Do not repeat the same FAQ block on 50 pages. That is duplicate content with a bow on it.
Do not expect it to produce a visual change in search. Expect it to give machines a clean, labeled copy of what the page already says.
What AI Answer Engines Look For
I cannot tell you how any single AI tool picks its sources, and anyone who claims to know is guessing. What I see across sites is consistent with common sense: pages that are clear, specific and easy to quote get quoted more often than pages that are vague.
A page is easier to quote when:
- It names the thing in the heading, in plain words ("How long does a brake job take?")
- The answer sits right under the heading, not three paragraphs down.
- It states facts that can be checked: hours, area, license numbers, prices where you can.
- It has a real author or business behind it, with contact details.
- It does not contradict itself across pages.
That last one trips people up. If your home page says "open 24 hours" and your contact page says "8 to 5," a machine does not know which to trust, and neither does a customer.
The Questions Most Sites Skip
These are the ones that actually close sales, and almost nobody writes them:
- Do you charge to give a quote?
- What happens if the price changes after you start?
- Are you licensed and insured? Can I see it?
- What do you not do?
- How do I pay and when?
- What if I am not home?
"What do you not do" is my favorite. It builds trust fast, because it shows you are not trying to sell everything to everyone.
A Quick FAQ Audit You Can Do In 20 Minutes
- Open your top five service pages.
- For each, write down the three questions a customer asked you last week.
- Check whether each question is answered on that page, in the first sentence of the answer.
- Add what is missing. Delete anything that is not a real question.
- If you add schema, copy the visible text exactly.
If you want me to look at your pages, book a strategy call.
Questions
Does FAQ schema still help SEO?
It does not produce the expandable rich results for most sites anymore, since Google limited them in 2023. It is still valid markup that labels your questions and answers. Treat it as a small bonus, not a ranking trick.
How many questions should an FAQ section have?
Three to six per page is plenty. Choose the questions people actually ask, and put them on the page where the question comes up. A forty question list on one page is harder to use and harder to quote.
Should I write FAQs with AI?
You can use AI to draft, but the answers have to come from your real knowledge: your prices, your process, your area. Generic AI answers sound like every other site and can state things that are wrong for your business. Edit hard or write it yourself.
Can I put the same FAQ on every page?
No. Repeating the same block across many pages adds duplicate text and little value. Give each page the questions that fit its topic.