How to write FAQ answers people actually read
- Use real questions from calls, emails and DMs, in the customer’s words.
- Answer in the first sentence: "Yes, we service all of Geelong and the Bellarine." Then add detail.
- Be specific: times, areas, what’s included. Vague answers make people call anyway.
- Keep it current: update hours, prices and policies when they change.
FAQ schema in 2026: what changed
Google limited FAQ rich results to well-known government and health websites in 2023, and stopped showing them in Search on 7 May 2026 (Google Search Central: documentation updates). The FAQPage type is still part of schema.org, so the markup remains a valid way to label questions and answers on a page. The real value is the visible FAQ itself: it helps customers decide.
More: how to get recommended by AI assistants, small business website checklist and the free Google Business description generator.
Quick answers
Does FAQ schema still get rich results on Google?
No. Google stopped showing FAQ rich results in Search on 7 May 2026, after limiting them to government and health sites in 2023. FAQPage is still valid schema.org markup that describes the page, but don’t add it expecting extra space in Google results.
Then why have an FAQ on my website?
Because customers ask the same things every day: do you service my area, are you licensed, can I bring the dog. Answering them on your site saves you calls and helps people decide. Plain, specific answers are also the kind of text search engines and AI tools can read and quote, though nobody can promise what they’ll show.
Where do I put the code?
Most website builders (WordPress, Wix, Squarespace, Shopify) have a "custom HTML", "code" or "embed" block. Paste the HTML there. The schema can go in the same block, or in your site’s header code settings.
How many questions should I have?
Five to ten real ones is plenty. Use the questions you get on the phone and in messages, and keep each answer to a few sentences.