How many questions should an FAQ page have?

Better 4-8 excellent questions per page or topic than a giant page of 40 generic ones. The rule: every question must be one a real customer asked or would type into Google, and the answer must deliver real value rather than dodge ("contact us for details"). Quality beats quantity here too.

What is FAQ Schema and why does it matter?

A standard code layer marking for search engines: this is a question, this is its answer. It lets Google understand and feature the content, and hands AI engines ready-to-quote answers in a format they parse unambiguously. On a well-built site the Schema is added automatically for every question.

Where should FAQs live: a dedicated page or inside each page?

Both, split sensibly: general business questions (payment, availability, service areas) on a dedicated page, and service-specific questions at the bottom of the relevant service page. This serves the visitor in the right context and gives every page its own content depth.

Where do I get ideas for questions?

The best source: the questions you actually get on the phone and in WhatsApp, word for word. Then: Google's "People also ask" box, autocomplete, and questions raised in industry Facebook groups. One week of logging conversations yields months of material.

FAQ Sections: The Secret Weapon of Both SEO and GEO

There is one element on a website that works three shifts: in the morning it pulls traffic from Google, at noon ChatGPT quotes it, and in the evening it reassures the hesitant customer who almost called but had one more small doubt.

It’s called the FAQ. And it’s probably the most underused part of small business websites.

Why the question-and-answer format?

Because it is the format humans search in - and the format machines answer in.

Look what happened to search: people no longer type “dental bridge cost”. They ask, on Google and even more on AI: “how much does a bridge cost for a 12-year-old?” An engine hunting for an answer to a question instantly recognizes content shaped as a question and answer: a perfect match.

And as we saw in the GEO post, AI engines compose answers from quotable sentences. A question and answer is a ready-made quote, wrapped and labeled.

The three shifts of a good FAQ

The Google shift: well-covered questions can win rich results, capture spots in “People also ask”, and catch long-tail searches your service pages miss.

The AI shift: when a customer asks ChatGPT “how long does building a website take?”, the engine looks for exactly that question-answer pair. If it lives on your site, clearly written with numbers, your odds of being quoted jump.

The conversion shift: the customer who almost reaches out always gets stuck on the same worries: how much does it cost, how long does it take, what if I’m not satisfied. An honest answer on the site dissolves the objection before it stops them. Sales people have known this for a century; your website can do it around the clock.

How to write FAQs that work

Real questions, in the customer’s words. Not “What is our work methodology?” (nobody ever asked that) but “How does it actually work?”. Best source: your WhatsApp.
Answers that actually answer. The great enemy of FAQs is the dodge: “It depends, contact us.” Give a range, a rule of thumb, something. “Most of our projects run between X and Y” is an answer; “it depends on your needs” is a waste of a click.
2-4 sentences per answer. Enough to deliver value, short enough to be read and quoted.
Mark it with Schema. An FAQPage tag tells the engines “these are official questions and answers”. On our builds it happens automatically for every question. (Hint: the post you are reading right now does exactly that with the questions at its end.)
Distribute wisely. General questions on a dedicated page; service-specific ones at the bottom of that service’s page.

Bottom line

FAQs are the highest-ROI content investment for a small business: easy to write (the material is already in your WhatsApp), loved by Google, quoted by AI engines, and they handle hesitant customers’ objections. Two hours of work, an asset for years.

Want a site where every Q&A is automatically marked with Schema and served to both Google and AI? That’s how we build by default ↗