Do You Still Need an FAQ Page If You Have a Chatbot?
Yes. Your chatbot answers from it, search and AI engines read it, and many visitors would rather skim than type. Here's why, and how to structure one now.
Published Updated 7 min read
Yes, keep your FAQ page. A good chatbot answers from it, search engines and AI answer engines can read and cite it, and plenty of visitors would rather skim a page than type a question. What has changed is the old reason to bother with FAQ markup: Google stopped showing FAQ rich results in its search results on May 7, 2026, so the page is now for people and for AI answers, not for extra space in Google.
I build ChatBento, an AI chatbot that answers from a business's website. You might expect me to say the chatbot makes the FAQ page unnecessary. It doesn't. The two do different jobs, and the chatbot works better when the FAQ page is good.
Why your chatbot needs the FAQ page
A support chatbot that's built properly answers only from your content. ChatBento trains on your website pages, Q&As you add, and any text you paste in. If an answer isn't in any of those, it says it doesn't know and offers a contact form instead of guessing.
That makes the FAQ page one of the most useful pages it can read. It's usually the one place on your site where the awkward, specific answers live: the returns window, whether you take a particular insurer, what happens if a delivery is missed. Delete the page and those answers have to live somewhere else, or the bot stops knowing them.
There's a second reason. You can give a chatbot private Q&As that never appear on your site, and for exact wording that's useful. But anything that exists only inside your chatbot is invisible to Google, ChatGPT and Perplexity. They can't crawl a conversation. If an answer matters, it should be on a public page too.
Why search and AI engines still read it
AI answer engines search the web, read a few pages and quote passages. A page of plain questions with direct answers is easy to quote. I covered how to get cited in detail in How a Small Business Gets Cited by ChatGPT, Perplexity and Google AI Overviews, so I won't repeat it here. The short version: crawlers need to be able to read the page, and each answer should be clear in its first sentence.
A chatbot can't do this job for you. The answers it gives in a chat window aren't pages that an engine can find, rank or cite.
What happened to FAQ rich results?
For years, adding FAQPage structured data could get your questions shown as expandable dropdowns under your Google result. That's gone, in two steps:
- August 2023. Google's Search Central blog announced that FAQ rich results would only be shown "for well-known, authoritative government and health websites." Everyone else lost them.
- May 2026. Google's Search Central changelog recorded that the FAQ rich result feature would no longer appear in Google Search from May 7, 2026, and in June 2026 Google removed the documentation for it.
What about the markup already on your pages? Google's 2023 post said there was no need to remove FAQPage structured data proactively, and that structured data Google doesn't use causes no problems for Search. So you don't need to rip it out. Just don't add it expecting a visible change in Google results.
The takeaway: the FAQ page was never really about the dropdowns. It's about answering questions for people, for your chatbot and for AI engines.
Why people still read FAQ pages
Not everyone wants a conversation. Some visitors:
- Don't know what to ask yet. A list of questions shows them what they should be thinking about, like whether there's a cancellation fee.
- Want to compare quickly. Skimming ten answers is faster than typing ten questions.
- Don't trust chatbots, or don't want to start a chat on a site they're only browsing.
- Arrive from search on the FAQ page itself, looking for one specific answer.
Nielsen Norman Group's guidance on FAQs (Susan Farrell, 2014) makes similar points: base the questions on what users really ask, group large FAQs by topic so they can be scanned, and link to fuller pages when an answer needs more room.
FAQ page vs chatbot: what each does better
| FAQ page | AI chatbot | |
|---|---|---|
| Visitor doesn't know the right words | Weak: they have to find the matching question | Strong: they ask in their own words |
| Visitor wants to skim | Strong | Weak |
| Found and cited by Google and AI engines | Yes, if crawlable | No |
| Follow-up questions | No | Yes |
| Exact, approved wording | Yes | Yes, if you add Q&As for it |
| Shows you what people actually ask | No | Yes, in the conversation history |
| Works if someone won't use chat | Yes | No |
| Upkeep | Edit when facts change | Same, plus reading conversations |
They aren't competitors. The FAQ page is the source; the chatbot is a way of asking it questions.
How to structure an FAQ page now
1. Start from real questions
Take questions from your inbox, your phone notes and, if you have one, your chatbot's conversation history. Use the visitor's words: "Can I get my money back?" beats "Refund policy information". If you're starting from nothing, our FAQ generator drafts ten FAQs from a page on your site. Check every answer against what you actually do before publishing.
2. Group questions by topic
Five to eight groups is plenty for most small businesses. For an online shop:
- Ordering and payment
- Shipping and delivery
- Returns and refunds
- Sizing and product care
- Contacting us
For a dental clinic it might be: new patients, insurance and payment, appointments and cancellations, treatments, emergencies.
3. Use headings for groups and questions
A clean skeleton looks like this:
FAQ (page title, H1)
Shipping and delivery (H2)
Do you ship to Canada? (H3)
How long does delivery take? (H3)
Returns and refunds (H2)
How long do I have to return an item? (H3)
Who pays for return shipping? (H3)
Headings help people scan, and they give crawlers and your chatbot clear boundaries between answers.
4. Answer in the first sentence
"Yes, we ship to Canada. Delivery takes 5 to 8 working days and costs $15." Then add detail if needed. Specific beats vague: times, prices, places and limits. If an answer needs more than a short paragraph, give the short answer and link to the full page.
5. Keep one version of the truth
If your FAQ says 30-day returns and your returns page says 14, both a chatbot and an AI engine may quote either one. When a policy changes, update every page that mentions it on the same day.
6. Include the awkward questions
What you don't do, where you don't deliver, what isn't covered. These are the questions visitors most want answered and the ones businesses most often leave out. They also stop a chatbot from saying "I don't know" to a question you could have answered.
7. Keep answers in the page's HTML
If you use expand-and-collapse sections, make sure the answer text is in the page itself and not fetched only when someone clicks. Some crawlers miss text that loads that way.
8. Link to it where questions happen
Footer, contact page, checkout, booking page. The FAQ page shouldn't depend on people finding it from your menu.
When you could skip a separate FAQ page
If your site is a single page that already states your hours, prices, area and policies plainly, a separate FAQ page may only repeat it. The same goes for a site where every product or service page already answers its own common questions. In those cases, put the answers on the pages people already visit and let the chatbot answer from them. The goal is that every common question has a clear public answer somewhere, not that a page called FAQ exists.
How the two work together
- Add your FAQ page, along with the rest of your site, as a source for the chatbot.
- Add Q&As for answers that must be worded exactly, and keep them identical to the FAQ page.
- Once a month, read the chatbot's conversations. Questions it couldn't answer are missing FAQ entries; questions asked over and over may deserve a more prominent answer.
- Add the new answers to the public page first, then make sure the chatbot has the updated version.
The short checklist
- Questions taken from real customers, in their words
- Grouped by topic, with headings for groups and questions
- Each answer clear in its first sentence, with specifics
- No answer that contradicts another page
- Awkward questions included
- Answer text in the HTML, not loaded on click
- Linked from the footer, contact page and checkout
- Chatbot trained on the page, with matching Q&As for exact wording
To draft a first version, try the free FAQ generator, then see how FAQ automation with ChatBento turns the same answers into replies visitors can ask for.