Turn pre-purchase questions into content Google and AI can cite
Every question you answer over WhatsApp or email before a sale is a question someone already typed into Google. Answered once, with FAQ markup, it can be cited both by the classic search engine and by an AI assistant — and along the way, link to the product page that closes the question.
This is the Pre-purchase questions (FAQ) recipe: it identifies the real questions people ask on Google before buying — shipping, warranty, differences between models, «does this work for…?» — and answers them with marked-up FAQ (FAQPage) so both search engines and AI assistants can read them. Each short answer links to the page in your catalog that resolves the question. It's informational content with a BOFU destination: it ends on the product page, not in the blog's infinite scroll.
The problem: every question gets answered by hand, one at a time
Most stores already have the answer to these questions. The problem is where it lives.
The same question, typed out by hand every time
Ten people ask if the product works for a specific use, and ten times someone on the team types out the same answer over WhatsApp or email. The work repeats because the answer never ends up living anywhere public.
Without FAQ markup, neither Google nor AI can find it
An answer written in a private chat isn't indexed by anyone. And a loose answer on a page, without FAQPage markup, is much harder for a search engine or an assistant to extract than a short, well-tagged answer.
An unanswered question leaves before it converts
Someone who doesn't find the answer in time doesn't always write in to ask: sometimes they just close the tab. A question left unanswered at the right moment is, often, the real reason behind an abandoned cart.
The recipe, step by step
Four steps. The first is the one almost no one does with any method.
Identify the real questions
They aren't invented: they come from Google's «people also ask» section around your products (PAA, People Also Ask — the related questions the search engine shows) plus the signals from your own catalog — variants, features that raise questions, what people ask over WhatsApp.
Google + your catalogAnswer short first, detail after
The direct answer goes on top, in two or three lines: if an AI assistant copies only that part, the citation still holds. Conditions, measurements or exceptions go below, for whoever wants to go deeper.
on top, in 2-3 linesMark it up with FAQ schema
Each question and answer gets marked up with FAQPage — the same format this very page uses for its own. It's what lets a search engine or an assistant extract the answer without having to interpret the rest of the text.
FAQPage, not just visualLink each answer to the page that resolves the question
«Does this work for X?» ends on the product page that works for X. Not the homepage, not the blog index: the specific page where that person can already buy.
one link per answerWhat no generic FAQ guide tells you
Search «how to build an FAQ section for SEO» and you'll find dozens of guides that explain the schema and stop there. None of them know which page in your catalog each answer should link to, because none of them know your store. That intersection — the real question people search for and the exact product that answers it — is the work that turns a generic FAQ into content that sells, and it's exactly what a generic article can't do for you.
Not every question deserves its own piece of content. If the question is specific to a single product — a size, a color, a specific measurement — it's better placed directly on the product page than in a separate blog post. FAQ content makes sense for questions that repeat across several products or that someone searches on Google before reaching your store. Confusing the two just fills the blog with content no one will read or cite.
Frequently asked questions
(This section, incidentally, carries the same FAQPage markup described in step 3 — it's the example done in practice.)
Does this replace the product page?
No. The product page still holds the technical details and the buy button. The FAQ content answers the question before the person gets there, and links to the right product page: it comes before it, it doesn't replace it.
Where do the questions come from?
From two sources: the «people also ask» section of Google around your products (PAA, People Also Ask) and the signals from your own catalog — variants, repeated questions, what people ask over WhatsApp or email. They're never made up.
Does this work if I already have an FAQ section?
Depends on how it's built. If the questions don't carry FAQPage markup or none of them link to a specific product page, there's real work to do. If it already covers both, there's nothing to touch.
Do all the questions go on the blog?
No. The ones specific to a single product are better placed directly on its page. The blog is for questions that repeat across several products or that someone searches before reaching the store.
How do you measure whether it's working?
In the clicks that go from each answer to the catalog, not in the visits to the post. An FAQ that gets read a lot and sends no one to a product page hasn't done its job.
Start with the questions people already ask you
The diagnosis of your blog is free: which pre-purchase questions repeat, whether you already have FAQ markup and how many answers link to the catalog today. Before writing a single new line.
Get my diagnosisno card required · the diagnosis is free · we'll only reach out once