Put the Real Questions on the Product Page
Your FAQ page answers questions about your business. The questions that decide a sale are about one product. How to collect them and answer them where shoppers look.
Most stores have an FAQ page. Very few have an FAQ for the questions that actually decide a sale.
Two different lists
The FAQ you wrote: return policy, shipping times, international delivery, payment methods, order tracking. Questions about your business.
The FAQ your shoppers write: Will a 15-inch laptop fit? Does the medium run small? Can I wear this to an outdoor wedding? Is the green closer to olive or sage? Questions about one product and her own situation.
The first list stops support emails. The second decides purchases.
Why the FAQ page can’t hold the second list
Policy questions apply to the whole store, so one page works. Purchase questions apply to one product. Does the medium run small only means something about a particular garment.
So the real FAQ belongs on the product page, next to the add-to-cart button, and not on a separate page she has to go looking for.
Where to find the real questions
You don’t need to guess. Shoppers have already written them down:
- Pre-purchase messages: chat, email, DMs. Each one is a question that stood between someone and a purchase.
- Reviews that start “I wish I’d known.” A question answered after purchase, by disappointment.
- Return reasons. Smaller than expected. Didn’t fit my laptop. Questions the page didn’t answer.
- Phone or in-store questions, if you take them.
This is different from reading your site search log, which shows the words shoppers type when they’re looking for something. Here you’re collecting the questions people ask about a specific product once they’ve found it.
Build a product FAQ in an afternoon
1. Pick your ten most-visited products.
2. Gather a month of questions for each from the sources above.
3. Find the three or four that recur. For most products, a handful of questions account for most of what people ask.
4. Answer them on the product page, in a short section near add-to-cart.
5. Answer like a person, not a policy.
Does the medium run small? Yes, a little. If you’re between sizes, go up.
Not: “Sizing may vary. Please consult our size guide.”
6. Keep your FAQ page for policy. It still has a job. It just isn’t the job of selling.
The answers are probably already known by whoever answers your inbox. Writing them down is the same work as capturing what the founder knows: it moves judgment out of one person’s replies and onto the page where every shopper can see it.
Keep it current
Questions change. New products bring new ones, seasons shift them, a new batch brings is this the same shade as before? Read new questions once a month and update the answers when they move.
What stays
None of this is an argument against the FAQ page. Policy questions are real, and a shopper who wants to know about returns deserves a clear answer in one place. The point is narrower: a policy FAQ isn’t where a purchase gets decided, so it can’t be the only place your store answers questions.
What to measure
- Recurring questions per product. The shorter and more stable the list, the more a product FAQ will help.
- Conversion on product pages before and after adding a real-questions section. Count your own; don’t borrow anyone else’s number.
- Pre-purchase messages per product. These should fall for questions now answered on the page.
- “I wish I’d known” reviews and “not as expected” returns on the products you’ve covered.
Where Immerss fits
Some questions will only ever be asked once. For those, a shopper needs somewhere to ask on the page and get an answer straight away.
Immerss puts an AI sales agent on your store that answers from your catalog and your own store knowledge, at any hour. You can see every conversation, so the questions shoppers actually ask are in front of you. The agent’s setup includes Library knowledge and FAQ answers, so what you learn goes straight back into what it says. The Shopify setup guide shows where both are added. When a shopper needs to see the product, one tap brings a real person onto live video.
Immerss installs on Shopify, WooCommerce, Salesforce or any store by script, and it’s free to start. See how other stores use it in our customer stories, or get started.
The FAQ you wrote is about you. The questions that decide the sale are about her, and she’s already written them down.
Questions
What is the difference between an FAQ page and a product FAQ?
An FAQ page answers questions that apply to the whole store: returns, shipping, payment, order tracking. A product FAQ answers questions that only mean something about one product, such as whether a size runs small or whether a laptop fits in a bag. The first stops support emails. The second decides purchases.
Where should product questions be answered?
On the product page, in a short section near the add-to-cart button. A question about one product is asked while the shopper is looking at that product, so an answer on a separate FAQ page is an answer she has to go looking for.
Where do I find the questions shoppers really ask?
In what they have already written: pre-purchase messages in chat, email and DMs, reviews that start with "I wish I'd known", return reasons such as "smaller than expected", and questions asked by phone or in store if you take them.
How many questions does a product FAQ need?
Usually three or four per product. Gather a month of questions for a product and look for the ones that recur. For most products a handful of questions account for most of what people ask.
