The questions worth adding to a Shopify product page are the ones support already answers. Open the last stretch of product email, about twenty threads if you have them, and group the repeats. Founders staring at a blank FAQ often invent objections the product does not have. A waterproof claim on a product that was never asked about, and is not waterproof, creates a new problem. Start from the inbox.
Typical groups are fit, materials, shipping window, returns, and compatibility. Skip a question that repeats the title. "Is this the blue mug?" is not worth a row when the title and the photo already say it. This list is useful with or without an app. You can type it into a theme accordion. An app such as Product FAQs for AI Crawler helps when you want the answers assigned per product, drafted from the description, and edited before you save.
Pull the questions from the inbox
Export or skim recent mail and write down the question in the shopper's words, not in your brand voice. "Will this shrink?" is a better heading than "Garment longevity." Count repeats only well enough to see a pattern. You do not need a formal study. Three notes about the same zipper are a FAQ. One note about a lost package is a support case, unless lost packages are the pattern.
Separate product facts from store rules as you go. Fit and materials usually differ by item. A shipping window that is true for every in-stock product can live in a shop-wide FAQ. If you use the app, that split is an assignment choice: products attached, or no products attached. If you use the theme, it is a choice of which template holds the text.
Five groups that show up often
Fit covers measurements, what "runs small" means in numbers, and who the cut is for. Replace the adjective with a dimension and a size label. Materials cover fiber, fill, hardware, and what the item is not, such as "the strap is leather and the body is coated canvas." Shipping covers handling time and the carrier's role after pickup, in business days if that is how you operate. Returns cover the window, who pays postage, and final-sale exceptions. Compatibility covers the plug, the phone, the bulb, the mattress size, or the software version the product works with.
- Fit: a measurement for a named size, including the unit and how you measured.
- Materials: the actual fiber or surface, by part if parts differ.
- Shipping: handling time, and what happens after the carrier has it.
- Returns: the window and who pays, matching the policy page.
- Compatibility: the device, size, or version the product works with, and a known mismatch.
You will not need all five on every product. A digital gift card does not need a fiber answer. A sofa may need a doorway measurement more than a wash instruction. Add the group the inbox proves. Leave the others off until a real question arrives. Empty categories on the page look like you had nothing to say, which is worse than a short list.
Questions to skip
Skip anything answered by the title, the price, or the variant picker. Skip a question you cannot answer yet. "When will this be back?" belongs in inventory messaging if you have it, not in a permanent FAQ that will be wrong next week. Skip legal or medical claims you are not prepared to support. A skincare FAQ that implies a medical result is a different risk from a tee FAQ that states an inseam.
Skip a store policy copied onto every product when the policy page already states it and the product is not an exception. The product page can link to that policy. The FAQ row should be the exception, or a one-sentence reminder that matches the policy word for word. Two versions of the return window are how chargebacks start.
Where a global FAQ is the better home
Shipping, wholesale minimums, and "do you ship to this country" are often global. Put them on a store FAQ page. On the product, add only the exception: freight, made to order, or a hazmat limit. Compatibility can be global when you sell one system and every accessory shares it. It is a product question when each SKU differs.
If you generate drafts, the model will happily write a generic shipping answer onto a product group. Move that answer to the shop-wide group after you check it, or delete it. Generated text is editable before save, and a saved group can be edited again. There is no accuracy score. The inbox is the score that matters: if the new FAQ is live and the same question still arrives, the heading or the first sentence missed the shopper's words.
How an AI draft goes wrong
A draft goes wrong when it fills a gap. The description says "canvas tote" and the draft adds a liter capacity, a washing instruction, or a waterproof lining nobody wrote down. Reject that sentence. A draft also goes wrong when it repeats the title as a question and answers with a slogan. Replace it with one of the five groups, or delete it.
A useful generated question sounds like the inbox. "Will the tote fit a 15 inch laptop?" is worth keeping if you know the answer and you put the measurement in the first sentence. If you do not know, do not publish the question. The app can ask clarification questions in description mode before it finishes. Use that step to supply the laptop measurement, or cancel the question. The widget can later show which groups people open. Opens are still not orders. They tell you which of these five groups earned a click.
Questions about what to add
How many questions should a product have?
As many as the inbox repeats, and no decorative extras. Three accurate answers beat twelve soft ones.
Should shipping be on every product?
Put the shared rule in a store FAQ. Put only the exception on the product.
What if I have no support email yet?
Use the questions you would ask before buying the item, then delete any you cannot answer from the spec. Add real mail later and revise.
The listing is Product FAQs for AI Crawler.
Turn the next real support thread into one product question, and use Product FAQs for AI Crawler if you want that question assigned to the product and editable before it is saved.