An FAQ page is useful for AI search when it is useful for humans: the same questions you already type back on WhatsApp. It is not a magic citation engine. A model can quote a clear answer. It can also ignore the page.
What else the site needs: content AI search needs. Full company checklist: optimize for AI search. Acronyms: what GEO is.
Yes, add an FAQ if you already have repeat questions. Write five to eight. Keep them visible. Mark them up only if the text matches. No, do not build a 200-question silo for machines.
When an FAQ page earns its URL
You sell a service with rules: area, deposit, what is included. You sell products with dispatch and return questions that do not fit every PDP. You are tired of typing the same paragraph. Those answers belong on the site once.
When it does not: you are inventing questions around keywords. You are duplicating the homepage. You added an app that injects twenty generic lines.
| Question type | Where it should live |
|---|---|
| Do you serve this city? | Service page or FAQ |
| How long to start? | Service page |
| How do I pay? | Contact or checkout policy |
| Product fit / material | PDP, not a giant FAQ dump. See store AI search |
Write them like a person
Use the customer’s words in the question. Answer in two or three sentences. If the rule changes, edit the page the same day. Stale FAQs are worse than none because they get quoted.
This journal uses a visible FAQ band for the same reason. Schema follows the visible text, not the other way around.
That is your outline. We can place it on the site. Send the list.
