How to Write FAQ Pages That Get Cited by AI Answers | How-to Guide

What makes a frequently asked questions page useful to customers, Google and AI assistants: real questions, direct answers, specific facts, honest structured data, and a layout crawlers can read.

AI assistants love a direct answer to a direct question, which makes a good FAQ page one of the easiest things for them to quote. A bad one, padded with questions nobody asked and answers that say nothing, gets ignored by people and machines alike. The difference is mostly in the writing.

Start with questions customers really ask

Pull questions from your inbox, booking calls, reviews and the "People also ask" boxes on Google for your service and town. Good FAQ questions tend to sound like this:

  • "Do you charge for a quote?"
  • "How long does a full rewire take in a three-bed semi?"
  • "Can I bring my dog to the grooming appointment and wait?"
  • "Do you work weekends, and is it more expensive?"

Questions written by the marketing team ("Why are we the best?") are not FAQs. Leave them out.

Answer in the first sentence

Open each answer with the answer: yes, no, a number, a range, a time. Then add the condition or detail. "Yes, quotes are free within 15 miles of Norwich; beyond that we charge a travel fee that is deducted if you book." An assistant can lift the first sentence and still be accurate. Keep most answers between two and five sentences.

Be specific, and be local

Specifics are what make a page citable. Prices or price ranges, timeframes, the towns you cover, brands you service, certifications you hold with their registering body. Vague phrases like "competitive rates" give an assistant nothing to repeat. If prices vary, say what they depend on and give a typical range.

Group and link

A single FAQ page with sections (booking, pricing, the service itself, aftercare) is easier to scan than one long list. Where a question deserves a longer answer, give a short answer on the FAQ page and link to a full guide. Also put the two or three most relevant questions on each service page itself, since a page about boiler servicing that answers boiler questions is a stronger source than a general FAQ.

Make it readable to crawlers

Accordions are generally fine if the answer text is in the HTML when the page loads. Problems arise when answers are fetched by a script only after a click, because crawlers that do not run JavaScript may never see them. Check with View Page Source.

What about FAQ structured data?

Google announced in August 2023 that FAQ rich results would be shown only for well-known, authoritative government and health websites, so most businesses will not see the expandable FAQ display in results. FAQPage markup is still valid Schema.org and does no harm when it matches the visible questions and answers exactly. Google's structured data guidelines are clear that markup must reflect content on the page; never mark up questions that are not shown. The visible text, not the markup, is what AI assistants quote.

Keep it current

An FAQ with last year's prices does more damage than no FAQ, because assistants repeat it confidently. Review answers whenever prices, hours or services change, and add new questions as they come up in calls.

Mistakes to avoid

  • Copying another business's FAQ, which is both unhelpful and a duplicate content problem.
  • Stuffing town names into every answer.
  • Answers that end with "call us to find out", which answers nothing.

Turning one customer question into one well-answered page each week is the routine SEO God Mode runs for We.Inc sites, with a quality check on every draft before it reaches your inbox.

Frequently asked questions

Does FAQ schema still get rich results?

Since 2023 Google shows FAQ rich results mainly for well-known government and health websites. The markup is still allowed if it matches the visible questions and answers.

How many questions should an FAQ page have?

As many as customers genuinely ask. Ten to twenty real questions with direct answers beat fifty padded ones, and the best can also sit on the relevant service pages.

Can AI read answers inside an accordion?

Yes, if the answer text is in the page HTML when it loads. If answers are fetched by a script only after a click, crawlers that do not run JavaScript may miss them.

More in Guides

Website builders for the businesses in this article

Related guides and tools

Start building

Product

Who It's For

Features

Resources

Company

View Sitemap