Put a customer question in an FAQ when a precise answer fits in a few sentences and rarely depends on the reader’s situation. Give it a full guide when answering it properly needs steps, trade-offs, examples, or conditions that change the advice. The test is the work the reader must do after reading the answer, not how often the question is asked.
That choice also shapes what an AI assistant can find. If a buyer asks how to migrate from another system and your only answer is one line in an accordion on the pricing page, the assistant has little to retrieve and less to cite. If a buyer asks whether you offer a free trial and you have written a 1,400-word article about it, the plain answer is buried.
Seenvero lets you track the questions that matter to your business as prompts and see, per question, whether answers name your brand and which pages they cite. That makes it easier to notice when a question deserves more than the space you gave it.
Two kinds of customer question
Sales and support teams hear both kinds every week, often in the same call.
A clarification has one answer that is true for almost everyone. Do you invoice in euros? Can I cancel monthly? Do you integrate with a particular calendar? The reader wants a fact and a link to the details.
A decision question has an answer that depends on the reader. How should we move our records across? Which plan suits a team with seasonal staff? Should we take payment upfront or after the appointment? The reader needs to understand options, steps, and consequences before acting.
A clarification forced into a long article wastes the reader’s time. A decision question squeezed into an FAQ gives them an answer they cannot use, and often a reason to ask a competitor.
A placement test you can run in a meeting
Ask five questions about each customer question before choosing where it lives.
| Check | Points toward an FAQ | Points toward a full guide |
|---|---|---|
| Length of a correct answer | Two to four sentences | Several sections, steps, or a table |
| Does the answer depend on the reader? | Rarely | Often: size, setup, market, or goal changes it |
| What happens after reading | The reader moves on | The reader has to do or decide something |
| How often the facts change | Seldom, and in one place | Workflows, screenshots, or examples need upkeep |
| Is it a separate search? | Mostly asked in context, while evaluating you | People ask it before they know your brand |
No single row decides the outcome. A question that is asked before people know your brand and needs several steps is a strong candidate for its own page. A short, stable fact asked while comparing plans belongs in an FAQ next to that comparison.
Eight fictional questions, placed
The business below is invented for illustration. Northpeak is a fictional appointment-booking tool for physiotherapy clinics; the questions, answers, and features are not Seenvero product information or real customer data.
| Customer question | Placement | Reason |
|---|---|---|
| Do you offer a free trial? | Pricing-page FAQ | One stable fact with plan terms; nothing to explain beyond it. |
| Can we export patient records if we cancel? | Brand FAQ, linked to the export help article | Short answer, but the caveat about attachments matters. |
| Can patients book in Latvian and English? | Product-page FAQ | A yes or no with a short note on which screens are translated. |
| What happens to bookings if our internet connection drops? | Brand FAQ | Two or three sentences on what still works and what syncs later. |
| How do we move from another booking system without losing history? | Full guide | Steps, a checklist, timing, and what to test before switching. |
| How should a clinic choose between prepayment and pay-at-visit? | Full guide | A trade-off between no-shows, cash flow, and patient experience. |
| Does it suit three locations sharing therapists? | Section on a multi-location use-case page, plus a short FAQ entry | The FAQ gives the direct answer; the page shows the setup. |
| How do we cut no-shows without annoying patients? | Full guide | Many clinics ask it before they know the brand, and the advice varies. |
Notice that two of the eight sit in both places. A short FAQ entry that answers directly and links to the detailed page serves the visitor who wants the fact and the one who needs the method. Keep both answers consistent; contradictory versions are worse than either one alone.
Rewrite a weak FAQ answer
Many FAQ entries answer a question nobody asked in words nobody uses. Here is a fictional before-and-after for Northpeak.
Before
Is my data safe with Northpeak? Absolutely. Security and privacy are at the heart of everything we do, and we use industry-leading practices to keep your information protected.
After
Can we export patient records if we cancel? Yes. A clinic administrator can export appointments, patient details, and treatment notes as CSV files at any time, including for 30 days after cancellation. Uploaded attachments such as referral letters are downloaded separately as a ZIP file. After 30 days the account and its data are deleted. The full export steps are in the help centre.
The rewritten version uses the question a clinic manager actually asks, answers it in the first word, gives the specific conditions, and states the limit a buyer would otherwise discover later. Every fact in it is something the company can check and must keep current. If any detail is uncertain, confirm it with the product team before publishing rather than softening it into a reassurance.
Make sure the answer is actually on the page
An accordion is a display choice, not a problem in itself. What matters is whether the answer text is part of the page that systems receive. Some accordions place every answer in the HTML and simply hide it visually until a click. Others fetch the answer with a script only after someone opens the item, which means anything that reads the page without clicking may never see it.
Google says it can only index content that is visible in the rendered HTML, and recommends using the URL Inspection tool to check what was rendered. See Google’s JavaScript SEO guidance. In Search Console’s URL Inspection tool, View crawled page shows the HTML Google received. For a simpler check that does not involve Google, open the page source in a browser and search for a sentence from one of your answers. Systems that do not run your scripts get roughly what that source shows.
If the answer is missing from the source, either render it on the server or make sure it is present before anyone interacts with the page. That benefits screen-reader users and people on slow connections as well as crawlers.
What FAQ markup does and does not do now
Google no longer shows FAQ rich results in Search. Its documentation changelog says the feature stopped appearing from May 7, 2026, and the FAQ rich result documentation was removed in June 2026. See Google’s Search documentation updates.
Google’s current guidance on generative AI features also says that structured data is not required to appear in them and that there is no special schema.org markup to add. The same page says you do not need to break content into small chunks or write in a special way for AI search, and that there is no ideal page length. Read Google’s AI optimization guide.
If you keep FAQPage markup for other systems that may use it, it must describe questions and answers readers can see on the page. Google’s structured data policies say not to mark up content hidden from readers. See Google’s structured data policies.
The practical conclusion is simple: write the answer well and make it visible. Markup cannot make a vague answer useful.
How this connects to AI visibility
Kevin Indig’s Growth Memo describes AI search in three stages: a page has to be retrieved, then cited, then trusted by the reader. Read the framework’s introduction. Placement touches the first two. A clear page with a heading that matches the question is easier to find for that question. A direct, specific answer is easier to quote accurately.
None of this guarantees that an assistant will cite or recommend you. Answers vary by product, model, wording, and location, and a later change in what you observe does not prove your edit caused it. What you can do is track the questions over time.
In Seenvero, add the decision questions you moved into full guides to your prompt list, grouped into a topic. Per-prompt visibility shows which ones you still lose, and the list of pages cited instead shows who is being read on those questions. These are questions you chose, not measured search demand, so treat them as a panel that represents your buyers rather than a count of them.
Start with your last ten sales questions
Collect ten questions from recent sales calls or support tickets. Run each through the placement test, rewrite the FAQ answers so they answer in the first sentence, and list the questions that need a full guide. Write the guide for the one that most often stalls a deal.
Explore Seenvero’s sample report to see prompts, cited pages, and brand roles laid out on an explicitly fictional brand. For the measurement basics, read how to tell whether AI is recommending your brand.
Common questions
Should we build a separate FAQ page for the whole brand?
It can be a useful place for the short, stable facts buyers ask about across products, such as billing, contracts, data handling, and support hours. Keep each answer specific, link to the detailed pages, and avoid duplicating long explanations that will drift apart.
How many questions should an FAQ section have?
As many as real customers ask and you can answer precisely. Google says it has no preferred word count, and padding a section with invented questions makes the useful ones harder to find. See Google’s guidance on helpful content.
Will a standalone guide always beat an FAQ answer?
No. A dedicated guide is often a better match for a broad decision question, but results depend on the question, the competition, and the quality of each page. For a simple fact, a direct FAQ answer may be the most useful format.