Most skincare product pages cover the same three things: ingredients, size and directions. The questions a first-time buyer actually has are more than just those. How does it feel on the skin? Does it layer under sunscreen? How long does a jar last? Who is it not for?
Your repeat customers already know those answers, and a lot of them have written them down in your reviews. A short FAQ on the product page is how that knowledge reaches the next buyer.
Skincare adds one catch. What you say about a product helps decide whether it's treated as a cosmetic or a drug, and your FAQ is part of what you say. This guide covers how to find the right questions, how to answer them in your own voice, and how to keep the answers on the cosmetic side of the line.
This is practical guidance for small brands, not legal advice. For questions about your specific products or claims, speak to a regulatory professional.
Why skincare FAQs need extra care
In the US, the FDA defines a cosmetic by what it's for: cleansing, beautifying, promoting attractiveness or altering appearance. A product meant to treat or prevent disease, or to affect the structure or function of the body, is a drug. The FDA says that "intended use" can be set by the claims a company makes, including on its website and in other promotional material. Its own examples of claims that make a product a drug include treating acne or dandruff and restoring hair growth.
A product-page FAQ is promotional material. So the question isn't only "is this answer true?" but also "what is this answer claiming the product does?"
This is where reviews get tricky. A customer can write that a cleanser cleared up their chin. That's their experience. If your FAQ repeats it, it becomes your claim. Putting it in quotation marks, starting with "customers say" or adding "results may vary" doesn't change what the sentence is claiming.
In a 2024 warning letter, the FDA quoted a brand's own Instagram posts, alongside its website, as evidence that its products were being sold as unapproved drugs. The FTC separately expects health-related claims in advertising to be backed by competent and reliable scientific evidence. Neither is a reason to avoid FAQs. Both are reasons to write them deliberately.
Step 1: Find the questions in your reviews
Don't brainstorm your FAQs. Read for them. Your reviews, DMs, emails and market-stall conversations already show what people wonder about before they buy.
Read a product's reviews with one question in mind: what keeps coming up? Note each topic and how many reviews mention it. Anything that shows up in two or more reviews is a theme worth answering. The usual ones are:
- texture and finish, and how it feels going on
- how it layers under SPF or makeup
- scent, including "fragrance-free but not smell-free"
- where it goes in a routine, and how to apply it
- size, how long it lasts and packaging
- who it may not suit
Pay the most attention to themes where reviewers disagree. When one person says a balm rinses clean and another says it leaves a film, a new buyer wants to know which one they'll get. Those are your most useful FAQs.
Step 2: Sort each theme before you write
Not every theme belongs on the page. Before writing anything, put each one in a bucket.
| Theme type | What it looks like in reviews | What to do |
|---|---|---|
| Feel, texture, scent, finish | "Melts on contact", "faint nutty smell" | Answer it directly |
| How to use it | "Only rinses clean with lots of water" | Answer it directly |
| Size, value, packaging | "Lasted four months", "lid cracked in transit" | Answer it, and promise only what you already do |
| Fit | "Too rich for my oily skin" | Answer it: who it suits and who it may not |
| Results on a skin condition | Breakouts, redness, dark spots, wrinkles | Don't restate it. Reframe to what the product is, or leave it off |
| Timelines | "Saw a difference in three weeks" | Leave it off |
The last two rows are where FAQs go wrong. They're also often the reviews brands are proudest of. Leaving them off the FAQ doesn't hide anything, because they're still in the reviews, in the customer's own name.
Step 3: Write each answer in your own voice
A few rules keep the answers useful and on the right side of the line.
- Answer in the first sentence. "Yes, with enough water." Then explain.
- Describe what it is and how it feels, not what it does to your skin. Texture, finish, scent, how it layers and how to use it are all fair game. So is a plain appearance statement like "skin looks and feels softer right after".
- Explain mixed experiences instead of picking a side. If results depend on how much water, how much product or which foundation, say so.
- Write as the brand, not as your customers. No quotes, no "customers say", no "many users report".
- Say who it may not suit. A short referral line, such as "if you have a skin condition, check with a professional first", makes no claim about the product.
When a draft answer drifts, these swaps help:
| Instead of | Try |
|---|---|
| "Clears breakouts" | Leave it off, or describe the product: "A lightweight, oil-free gel that sinks in fast" |
| "Repairs your skin barrier" | "A rich balm that leaves dry skin feeling comfortable" |
| "Anti-aging" or "reduces fine lines" | "Leaves skin looking smoother right after you apply it" |
| "Calms redness" | Leave it off, or state the fact: "Fragrance-free, with no essential oils" |
| "Results in two weeks" | Drop the timeline |
| "Clinically proven" or "dermatologist approved" | Drop it |
A worked example: one cleansing balm, 14 reviews
Here is how that plays out on a demo product: the Slow Melt Cleansing Balm from Terra Skincare, a demo store with 14 sample reviews. Demo product and reviews, for illustration.
The reviews settle a lot. The balm melts on contact and takes off mineral SPF and waterproof mascara. A 100ml jar lasted one reviewer four months. The spatula gets lost. They also split twice: some find it rinses clean and some get a film, and one finds it stings the eyes while another wears contacts without a problem.
One review credits the balm with clearing breakouts on the reviewer's chin over about three weeks. In the same breath, it wonders whether stopping face wipes did it instead.
This is what the three kinds of theme look like as answers. The first two are real output from a Thresh run on this demo product.
A theme where reviewers disagree: the rinse-off
Does the balm rinse away completely, or can it leave a residue?
The balm is formulated to emulsify with water once you massage it in, turning from a solid into a milky texture that rinses off. How clean your skin feels afterward can depend on how much water you use to emulsify it and how thoroughly you rinse — it's designed as a first cleanse to be followed by your usual face wash, so a light residue at that stage is part of the two-step process rather than a sign it didn't work.
It explains when each experience happens instead of siding with one reviewer.
A theme that needs a fact, not a promise: the scent
If it's fragrance-free, why does it seem to have a scent?
The formula is fragrance-free and contains no added essential oils. Natural ingredients like shea butter and sunflower seed oil carry their own faint, inherent smell, which is different from an added fragrance.
A theme to leave off: breakouts
A sentence like "helps clear breakouts in three weeks" would be a drug claim and a timeline in one. It stays off the page. If you'd like the page to speak to shoppers managing their skin, say what the product is and point them to a professional. For example: "This is a cosmetic cleanser, not a treatment. If you have a skin condition, check with a professional before use."
Where the FAQ goes on the page
Put it close to the Add to cart button, under the description. Most Shopify themes have a block for this in the product template. It's called "Collapsible row" in Dawn and many other themes, and "Accordion" (under Layout) in Horizon. Each question gets its own row. Because the answers differ from product to product, check your theme's documentation for how to give each product its own content.
Keep the list to the questions your reviews actually raise. A few strong answers beat a long list nobody opens. Three to five short "before you buy" lines next to it, such as "apply to damp skin", "a little goes further than you'd think" or "if your skin reacts easily, patch test first", catch the shopper who won't open any row at all.
Write for the shopper, not the search engine. Google stopped showing FAQ rich results in search in May 2026, so FAQ markup won't earn a special listing. A clear answer on the page is what helps the next buyer.
Revisit the FAQ when a new batch of reviews comes in. New themes show up, and old ones settle.
Before you publish: a checklist
- Every answer is about texture, feel, scent, use, size, packaging or fit, not a skin condition
- No timelines ("in three weeks", "overnight")
- No quotes, "customers say" or "users report"
- No promises you don't already keep
- Mixed experiences are explained, not hidden
- You've read every answer yourself. You know your product.
- Unsure about a claim? Ask a regulatory professional before it goes live.
Doing this faster
The slow part is reading every review to find the patterns. That's what Thresh FAQ does. It finds up to 10 recurring themes in a product's reviews, you approve the ones that matter and remove any you'd rather leave off, like the breakouts theme above, and it writes one FAQ for every theme you keep, plus before-you-buy notes, in your brand's voice.
Thresh instructs the AI not to restate medical or therapeutic claims, but it isn't a compliance check, so review every FAQ before you publish. It never connects to your store: you upload a CSV or paste your reviews, then copy the finished FAQs wherever you want them. Your first 3 runs are free, then it's $2.45 a run, with no subscription.
Your first 3 runs are free · No credit card · No subscription
— Vicky at Thresh