AI assistants quote FAQ answers that give the answer in the first sentence, back it with specific facts, and sit on the page about the service being asked about. The markup no longer matters much: Google stopped showing FAQ rich results in Search from 7 May 2026 and says no special structured data is needed for its AI features. What assistants lift is plain, checkable text.
Key takeaways
- Google's FAQ rich result is gone (deprecated from 7 May 2026, documentation removed 15 June 2026). The value of an FAQ is now in the words, not the schema.
- The best questions come from your phone, your inbox and Google's People also ask box.
- Answer in the first sentence, then add a price, a time, an area or a condition. Aim for 40 to 80 words with no sales language.
- Put questions on the service page they belong to. One giant FAQ page is harder for an assistant to match to a specific question.
- Check which questions assistants already answer without naming you, and write those first.
Does FAQ schema still work in 2026?
No, not as a Google search feature, and no AI platform documents a bonus for it. Google's Search Central changelog records a deprecation notice added on 8 May 2026 stating that the FAQ rich result "will no longer appear in Google Search starting May 7, 2026", and on 15 June 2026 Google removed the FAQ rich result documentation because "the FAQ rich result feature is no longer shown in Google Search results" (Google Search Central, 2026).
For AI features the position is the same. Google says "structured data isn't required for generative AI search, and there's no special schema.org markup you need to add", and that "you don't need to create new machine readable files, AI text files, markup, or Markdown to appear in Google Search" (Google Search Central, 2026).
If you already have FAQPage markup, you can leave it, provided it "must be a true representation of the page content" and you don't "mark up content that is not visible to readers of the page" (Google Search Central, 2026). Just don't add it expecting a result.
FAQs still matter for a simpler reason. When an assistant searches on a customer's behalf, it reads pages and writes an answer with links: Perplexity's fetcher "might visit a web page to help provide an accurate answer and include a link to the page in its response" (Perplexity, 2026), and with Claude's web search "every response includes citations" (Anthropic, 2026). A clear question with a clear answer beneath it is the easiest thing on the web for that process to lift.
How do I find the questions customers actually ask AI?
Start with the questions you already answer every week, then check them against what Google and the assistants show. Four sources:
- Your phone and inbox. Write down the last twenty questions customers asked before booking: "Do you charge a call-out fee?", "Can I get an appointment on a Saturday?", "Do you cover Harrogate?" (illustrative examples). People ask assistants what they would ask you, in the same words.
- Google's People also ask box. Search your main service and town, and open the box of related questions. Google's own documentation describes this as the "related questions group, also known as 'People Also Ask'" (Google Search Central, 2026). Each question you expand reveals more; note the ones about price, timing, qualifications and what's included.
- The sub-questions behind a broad request. Assistants don't search for the customer's sentence as typed. OpenAI says ChatGPT "typically rewrites your query into one or more targeted queries", and gives the example of "What are some good restaurants near me?" becoming "top restaurants San Francisco" (OpenAI Help Center, 2026). Google's AI features use "query fan-out", "issuing multiple related searches across subtopics and data sources" (Google Search Central, 2026). So "a good emergency plumber in Leeds" (an illustrative example) may become separate searches about call-out costs, response times and Gas Safe registration, and each is a question your page can answer.
- The questions assistants already answer without you. Ask ChatGPT, Perplexity and Google AI Mode the questions from steps 1 to 3 and note which ones return competitors with you missing. Those are the pages to write first. A free AI visibility check does this for five questions in about 30 seconds.
How do I write an answer an assistant can quote?
Put the answer in the first sentence, add the facts that make it usable, and stop. A good target is 40 to 80 words: long enough to stand alone when quoted, short enough to be lifted whole. That range is practical guidance, not a published rule; no platform documents a required length.
Google's advice for its AI features works just as well for the models reading your page: "write content for your human audience and make sure the content is well written and easy to follow", and make sure "important content is available in textual form" (Google Search Central, 2026). Its helpful-content questions ask whether a page gives "a substantial, complete, or comprehensive description of the topic" and whether it leaves readers "feeling like they need to search again to get better information from other sources" (Google Search Central, 2026). "It depends, call us for a quote" fails both tests.
Five rules for each answer:
- First sentence answers. "Yes, we work on Saturdays, 8am to 1pm." Not "At Example Plumbing we understand that weekdays aren't always convenient."
- Use numbers. A price, a range, a time, a distance, a date. "A standard boiler service costs £85 and takes about an hour" gives an assistant something to quote; "competitive rates" gives it nothing.
- State the conditions. Who it applies to, where, when, and what is excluded. Conditions keep an answer accurate when it's repeated out of context.
- No marketing. Drop "leading", "trusted", "passionate" and "tailored". Google asks whether content is "primarily made to attract visits from search engines" (Google Search Central, 2026); an answer stuffed with slogans reads that way to a model too.
- Make it checkable. For a qualification or registration, name the register and give the number. Google values content that "clearly demonstrate[s] first-hand expertise" (Google Search Central, 2026); a checkable fact is the plainest form of that.
A before-and-after (illustrative):
Before: Do you offer emergency call-outs? We pride ourselves on being there when you need us most. Our friendly team is always happy to help with any plumbing emergency, big or small. Get in touch today!
After: Do you offer emergency call-outs? Yes. We take emergency calls 24 hours a day across Leeds and Bradford. Between 8am and 6pm on weekdays the call-out fee is £60, which covers the first half hour; evenings, weekends and bank holidays are £95. We aim to arrive within two hours of your call, and we tell you if we can't.
The "after" answer is 54 words, every sentence is a fact, and an assistant can repeat it without misleading anyone.
One technical point: keep the question as visible text, usually an H3 heading, with the answer in a normal paragraph beneath it. Google says it "is able to process content within JavaScript as long as it isn't blocked" (Google Search Central, 2026), but the safest FAQ has its text in the page from the start rather than loaded when an accordion is clicked.
Where should FAQs go on my website?
On the page about the service the question concerns, not on one FAQ page for the whole business. Because assistants split a request into related searches by subtopic, a page covering one service, its price and its common questions matches those searches better than a long general page where boiler servicing sits next to bathroom fitting. Google's advice for AI features includes "organizing content in a way that helps your readers" and making it easy "to distinguish your main content from other elements on the page" (Google Search Central, 2026).
A layout that works for most small businesses:
| Page | Questions that belong there (illustrative) |
|---|---|
| Each service page | Price or price range, what's included, how long it takes, who does the work and their qualifications, what to do before and after |
| Areas page or home page | Which towns and postcodes you cover, travel charges, parking or access notes |
| About or contact page | Opening hours, how to pay, deposits, cancellation terms, insurance, registrations |
| Product pages (shops) | Delivery times and costs, returns, sizing, stock, whether an item is made to order |
Keep a short general FAQ (five to eight questions) for business-wide answers and put the rest with the service. For the business facts themselves, LocalBusiness markup that matches the visible text is still worth having: see our LocalBusiness schema guide and the AI visibility checklist.
What do good FAQ answers look like for different trades?
The pattern is the same in every trade: a direct answer, a number, a condition. These are illustrative examples, not measured search volumes.
| Trade | Question customers ask (example) | What the first sentence should do |
|---|---|---|
| Plumbers | How much is an emergency call-out? | Give the fee, the hours it applies to and what it covers |
| Dentists | Are you taking on NHS patients? | Say yes or no today, and what the private alternative costs |
| Accountants | What do you charge for a sole trader tax return? | Give a from-price and what's included |
| Restaurants | Can you cater for a nut allergy? | Say what you can and can't guarantee, and how to tell you |
| Solicitors | How long does a house purchase take? | Give a typical range in weeks and what delays it |
| Independent shops | How long does delivery take? | Give days, cost and the cut-off time for same-day dispatch |
None of these answers is clever. They are the things you say on the phone ten times a week; writing them down once, clearly, is what gets them quoted.
What is a simple 10-question FAQ template?
Use this as the starting list for each service page, cut what doesn't apply, and add the questions you hear most.
- How much does [service] cost? From £[X]; what's included; what changes the price.
- How long does it take? Typical time on site or turnaround, and what can extend it.
- Which areas do you cover? Towns or postcodes, and any travel charge beyond them.
- Can you do it this week / at the weekend / in an emergency? Real availability and hours.
- Who will do the work, and are they qualified? Names or roles, registrations and where to verify them.
- Do I need to do anything before you arrive? Access, clearing space, switching something off.
- Is there a guarantee or warranty? Length, what it covers, how to claim.
- How do I pay, and do you take a deposit? Methods, when payment is due, deposit amount.
- What happens if something goes wrong? Insurance, your complaints process, who to call.
- How do I book? Phone, form, online booking, and how quickly you reply.
Each answer: first sentence answers, 40 to 80 words, at least one number, no slogans. Date the page when prices change so a reader, or a model, can see it's current.
How SearchCrow helps
SearchCrow asks ChatGPT, Perplexity, Gemini, Claude, Copilot, Google AI Overviews and Google AI Mode the questions your customers ask, and shows which ones name competitors but not you. The "create content" actions in its plan turn those gaps into questions to answer, with a draft to start from, so you write the FAQ that fills a real hole. The free check covers five questions; everything in this guide works without it.
FAQ
Does FAQ schema still work in 2026? Not as a Google search feature. Google's documentation changelog says the FAQ rich result stopped appearing in Google Search from 7 May 2026, and the documentation was removed on 15 June 2026. Google also says no special structured data is needed for its AI features. Leave existing markup in place if it matches the visible text, but spend your time on the questions and answers themselves.
How long should an FAQ answer be for AI assistants? Long enough to stand alone, short enough to lift whole: 40 to 80 words is a good target. Put the answer in the first sentence, then add the facts that make it useful, such as a price, a time, an area or a condition. No platform publishes a required length; this is a practical range that keeps answers quotable and complete.
Where do I find the questions customers ask AI about my business? Start with what people ask you by phone and email, because they ask assistants the same things. Then search your main service on Google and open the People also ask box, which lists related questions. Add the sub-questions an assistant would need to answer a broad request, such as price, area, timing and qualifications. A free AI visibility check shows the questions assistants are already answering without naming you.
Should FAQs go on one page or on each service page? On each service page. Assistants break a customer's request into several targeted searches, so a page that covers one service and its common questions is easier to match than a single FAQ page covering everything. Keep a short general FAQ for questions about the business as a whole, such as areas covered and how to pay, and put service-specific questions with the service.
Should I mark my FAQ answers as 'AI-friendly' or add an AI text file? No. Google says you don't need new machine-readable files, AI text files, markup or Markdown to appear in Google Search, and that structured data isn't required for its generative AI features. What assistants need is plain text that can be read without clicking, scrolling or expanding, written in the words customers use.
Sources
- Google Search Central, Latest Google Search documentation updates (entries of 8 May 2026 and 15 June 2026)
- Google Search Central, AI features and your website
- Google Search Central, Optimizing for generative AI features on Google Search
- Google Search Central, Creating helpful, reliable, people-first content
- Google Search Central, Featured snippets and your website
- Google Search Central, General structured data guidelines
- OpenAI Help Center, Searching the web with ChatGPT
- Perplexity, Perplexity crawlers
- Anthropic, Enabling and using web search