Should I create an FAQ page for GEO?
Short answer: Yes, but put FAQs on the pages they belong to rather than one giant FAQ page, and only include questions customers genuinely ask.
Yes, with two conditions: put the questions on the pages they belong to, and only include questions customers actually ask. A single catch-all FAQ page is better than nothing, but a three-question block at the bottom of each service page is more useful to both assistants and readers, because the answers sit next to the context they refer to.
Why FAQs work for GEO: the question-and-answer format is precisely the shape an assistant's answer takes. A well-written FAQ answer is a self-contained passage that names the business, states a fact and needs nothing else, which is what retrieval systems select. Marked up with FAQPage JSON-LD, it is also unambiguous to parse.
How to do it well:
- Source the questions from reality: enquiry emails, phone calls, reviews, and the "People also ask" box on Google for your category.
- Keep answers between 40 and 80 words, with the key fact in the first sentence.
- Be specific. "We charge £65 per hour plus parts, with a one-hour minimum" beats "our pricing is competitive".
- Name yourself in the answer where it reads naturally, so the passage carries its own attribution.
- Match the visible text and the schema exactly. Schema that says something the page does not is a trust problem.
- Do not pad. Ten real questions beat forty invented ones.
A common mistake is writing FAQs that answer the questions you wish people asked ("Why choose us?") rather than the ones they do ask ("Do you charge a call-out fee?"). The second kind gets quoted.
Seoptist's audit checks whether key pages have FAQ blocks and valid FAQPage schema, and the content tools on Growth and above suggest questions per page from your site and sector.