• Content

FAQ for voice search: question in a whole sentence, answer in two lines

A block of questions and answers for a searchable site is not an "FAQ" page in the footer, but short answers where the question arises: in the product card, on the delivery page, next to the buy button. We take questions from your requests and internal search, write the answer so that it can be read aloud, and mark exactly what is visible on the page. At the same time, we do not promise an extended snippet: from 2023, Google will show it for FAQs mainly on government and medical sites.

See how it works
Price
after a free audit
Guarantee
30 days after project sign-off
Where do we get the question from?
internal search, chat, mail, reviews - not a query dictionary
Price
after a free audit
Guarantee
30
days after project sign-off
Where do we get the question from?
internal search, chat, mail, reviews - not a query dictionary
Term
7-30
working days; it is not the volume of the text that stretches it, but the comparison of answers
Before the estimate
free collection of questions from your sources, 2-3 working days
Measured example
wholesale B2B catalog for 5,830 items: FAQ is provided with micro-markup right in the layout
What we do not promise
extended snippet and mentions in the AI ​​response are the service's decision, not the contractor's
The risk we remove
markup with a rating of 4.8 with 50 reviews and zero mentions of reviews on the page
Process steps

Transparent stages with approval at every step

Total duration:7–30 days

  1. Collection of questions from your sources

    2-3 working days

    Internal search, chat, mail, reviews, query report in Search Console. We do not touch the wording: at this stage, it is the raw language of people that is valuable. At the same time, we see which topics are repeated most often.

  2. Grouping and location map

    1-3 working days

    Questions are arranged by topic, each topic receives an address: a block in the card, a block in the checkout, a block on the delivery page, a separate page. Here we screen out questions about a specific order - they live in the chat and do not go to the site.

  3. Answers and coordination with a specialist

    2-12 working days

    We write, then give it for confirmation. The longest stage and the only one we don't fully control: the speed here is set by whoever is responsible for warranty and compatibility.

  4. Placement and marking

    1-8 working days

    Blocks go into patterns, markup — on the same pattern. The question and the answer must be visible without expansion, or at least present in the HTML of the first response of the server: what is added by the script after the click, the machine may not see.

  5. Verification on live pages and replenishment rules

    1-4 working days

    The validator shows the syntax, and the discrepancy between the markup and the text is visible only with the eyes - so we go through the live pages with our hands. At the exit, we give the order of replenishment of the block, so that new questions from appeals do not remain in the chat.

Technologies & integrations

What we build on and what it connects to

Stack

  • Internal site search data is the most accurate source of wording; limitation: if the search does not write a query log, the first useful slice will have to wait two to three weeks after activation
  • Downloading requests from the chat and CRM — there the questions lie in a whole sentence; limitations: most of it concerns a specific order and does not go into the block
  • Google Search Console, query report - shows only what the site is already visible for; you won't get new topics from there
  • JSON-LD FAQPage / Question / Answer - set by default: one block in the template, does not depend on the layout
  • Micro markup right in the typesetting — when the markup needs to be firmly tied to the visible text; limitation: it goes with the theme on redesign
  • Markup at the template level, not a separate page - otherwise the next fill will lose it
  • Validation on live pages by hand - the validator sees the syntax, not the discrepancy with the text

Integrations

  • Google Search Console
  • GA4
  • chat on the site
  • CRM
  • internal site search
What's included

Complete list of work and what you get as a result

  • We collect questions from internal search, chat, mail and feedback - the output is a list of what you are really being asked, not guesses from the marketing department
  • We group the questions by topic and decide what goes as a block to the existing page, and what pulls to a separate page - this saves us from thirty empty pages "on request"
  • We write the answers so that the first one or two sentences already answer: such a paragraph can be read aloud and quoted without a page around
  • We leave the question verbatim - "how much does the parcel go to the village", not "delivery time by Ukrposhta": in the second wording, the person does not ask it
  • We check everything about compatibility, warranty and returns with your specialist, so that the site does not make promises that support can't keep later
  • We put the blocks where the question arises: card, category, delivery page, checkout, service page
  • We mark the questions and answers at the template level - the markup will not be lost the next time the catalog is filled
  • We check the markup with the visible text line by line and remove everything that is not on the page
  • We check neighboring marking blocks on declarations without reason: ratings without reviews, prices without goods, work schedule that does not coincide with the real one
  • We give the replenishment rule: three questions from support per month, ten minutes of work — and the block remains alive without us
When this service isn't right

What's not included — so there are no surprises at delivery

  • Making up questions that no one asked you
  • Markup of content that is not on the page
  • Setting up chat bots and voice assistants
  • Promises to get into selected answers or reviews from artificial intelligence
Who it's for

Situations where this service delivers results

Scenario 1 of 4

They ask the same thing every day in the chat

For the third year, the manager answers whether it is possible to return the goods without packaging and how much the parcel is going to the village. People type the same wordings in the search — it's just that no one has transferred them to the site. Transferred: the question remains verbatim, the answer becomes a visible text, and not a verbal agreement in correspondence.

We'll review your situation in a free audit
Block in the place of the question vs. a separate section "Questions and answers"

How this option differs from the alternative

One general FAQ sectionOur approach
Where a person meets the answeron a separate page, where you have to guess firstin the card, at the checkout, on the delivery page — at the moment of doubt
What goes into the blockeverything in a row, because there is one page, but there are many topicsfive to eight questions strictly on the topic of the page
What the machine seesone markup block for the entire site; nothing is announced to the machine on the rest of the pagesmarkup on each page where the answer is really visible
What happens to appealsthe question still goes to the chat — the page was not foundsome questions are closed before the person opens the chat
The life of the block continuesthe section is written once and not opened againthree new questions from support every month, ten minutes of work
Free audit

A free collection of questions that are already being asked

We take your existing question sources — internal search, chat, inquiries, feedback — and show you which ones are the most frequently asked questions. This is the preparation of the FAQ: you do not have to invent questions, they have already been asked.

What we measure

  1. What is asked in the internal searchPeople's wording is the most accurate source. Often there are questions that are not in any query dictionary.
  2. Questions from appeals and reviewsWhat is repeated in the chat and on the phone is almost always typed in the search as well - only in different words.
  3. Blocks of questions are available on the websiteAre they, or are they not, made up of questions invented by a marketer, and are they declared in structured data.
  4. Question marking statusDoes the markup match what is visible on the page. Marking up questions that aren't on the page is a rule violation, not a trick.
  5. Other declarations in the markupAt the same time, we check the neighboring blocks. Real find: The markup advertises 50 reviews and a 4.8 rating, and the page has zero mentions of reviews, a direct reason for manual sanctions.
  6. Format of available answersLength, location, does the first line answer the question. An answer that starts with a preface doesn't work in conversational search.

What you get

  • A list of questions you're actually asked, grouped by topic.
  • Estimate which ones are worth a separate page, and which ones are worth a block on the existing one.
  • Findings based on existing markings, including risky ones.
  • Conversation for 30 minutes on the document.

Timeline: 2-3 working days

Why is it free

Because the collection of questions is a mechanical part, and it is fast with us. And also because after it it often turns out that there are enough questions for two blocks, not thirty pages, and it is more honest to say it right away.

What's next

Next, we write the answers, coordinate them with your specialist and mark exactly what is visible on the page.

Short form: your contact and site URL

Did not find your case?

Describe how it works on your side — we will tell you whether “FAQ for voice and spoken search” fits and what it means in your situation. No brief and no call: one question, one answer.

Contract and paperwork

We work officially

Contract, act and invoice — for every project, not just large ones.

Trusted by6 brands

Trusted by: Kvant Energy, GYPSUN, Naturel Cosmetics, Pancer Protection, LUGI, BeeTech

Terms fixed in writing8 points

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

  • Contract, act and 30-day warranty

    Every project gets a written contract: scope, deadlines, amount, acceptance procedure. After delivery — act and invoice, then 30 calendar days of warranty.

  • Sole proprietor & bank transfer

    The contractor is a registered sole proprietor. Payment by invoice with closing documents.

  • Rights & access — yours

    Code, design and materials transfer to you after full payment. Domain, hosting, repository and analytics are registered to you.

  • Client portal instead of email chains

    During the project you get access to a portal: contracts, invoices, acts and project status in one place.

  • Sites in nine countries

    Our sites run in nine countries: besides Ukraine — Poland, Germany, Austria, England, Norway, Bulgaria, Moldova and Spain.

  • Verifiable numbers

    Every case in the portfolio comes with a link to a live site and a technical measurement.

  • Audit first, then pricing

    There is no price list on the site intentionally: the scope of the same work differs multiples between clients.

  • We say "no" when unsure

    If the task isn't ours or the deadline is unrealistic — we tell you upfront.

We sign NDAs on request. After completing the work, we delete our access to your services ourselves.

What affects the price

Why two seemingly identical tasks are priced differently

  • How many questions and where to get themTwenty questions about shipping and returns are written quickly. Twenty hardware compatibility questions are a different job: each answer is checked against the documentation, and the pace is set by your technical expert, not a copywriter.
  • Who on your side says "yes"One person has the right to confirm the answer - the approval cycle is a day. The answer, which goes through three departments, stretches the stage of writing twice. This is the most common reason why the term reaches the upper limit.
  • Number of page types and access to templatesOne block on the delivery page is hours. Blocks in the card, category, checkout and service pages are work in templates. Without access to the templates, the markup has to be put by hand, and the next filling of the catalog erases it.
  • Status of existing markupA clean site is marked up from scratch. The site with other people's blocks must first be analyzed: in our own dimension, we encountered a markup that announced a rating of 4.8 out of 50 ratings with zero mentions of reviews on the page. Such places are removed before putting new ones.
  • Language versionsEach language has a separate set of questions and a separate marking. In the wholesale catalog, we deliberately gave two language versions of 6,234 addresses each: questions are asked in pairs, because the blindly translated wording ceases to be the way a person speaks.
Cases

Tasks and results in numbers — all metrics measured by us

LUGI

wholesale supplier of goods from China, B2B catalog of almost 6,000 items

Task
Check that the questions and answers have already been given to the machine on the pages of the catalog and whether the marking matches the visible text.
Solution
Inventory of structured data on live pages, analysis of site maps by language versions, measurement of the volume of the catalog using two independent methods.
Result
5,830 products - the number was confirmed twice: the regular search of the engine gave 58 pages of 100 positions plus 30, the site maps - 6,234 addresses for each of the two languages, a total of 12,468. Questions and answers are given with the FAQPage/Question/Answer micromarkup right in the layout, breadcrumbs and the WebSite/SearchAction search action work nearby. First server response 506.9ms with 333.1KB markup. The case is rare: the block of questions is not simply written, but announced to the machine — and announced in such a way that it cannot physically break up with the visible text. Measured on 07/31/2026.

Ukrainian platform for automatic rewriting of product descriptions

Task
Check the landing page markup with its content before tackling the content.
Solution
Parsing all JSON-LD blocks, matching each declared entity with visible text, checking service files and measuring speed.
Result
A block of questions and answers is given in JSON-LD together with application, proposal, organization and site; it is from the markings of the FAQPage that the terms of payment are read - non-cash transfer to the FOP's IBAN with a minimum top-up of UAH 50. First server response of 220.6ms with 140.8KB of markup, the fastest result among the sixteen sites measured. There is also a risk: in the markup a rating of 4.8 out of 50 ratings is announced, and on the page there is zero mention of the words "feedback" and "rating" - this is a ready reason for manual measures. Separately: robots.txt links to a sitemap that returns a 404. Measure 07/31/2026.
What we need from you

We can't start without this — best to prepare in advance

  1. Download or access requests: chat, mail, feedback, call records. Three months is enough.
  2. Internal search log, if maintained. If not, turn it on at the start, the first useful cut will be in two or three weeks.
  3. A specialist who confirms answers about compatibility, warranty and returns. Without it, the writing stage stops.
  4. Access to CMS or to templates: we put the markup in the template, otherwise it lives until the next filling of the catalog.
  5. The applicable terms of delivery, payment and return as they may be published.
If something is missing — let us know, we'll help you gather it or do it as a separate task.
FAQ

Most frequently asked questions — with concrete answers

Does FAQ markup give a rich snippet in Google?

Mostly not anymore. Starting in 2023, Google shows these enhanced results mostly for government and medical sites, so we don't sell markup as a way to get a snippet. It has another benefit: it provides questions and answers in a machine format — both for search and for services that collect answers from text. And the block of questions itself is primarily useful for a person who is on the verge of "buying" and has doubts.

How do voice search questions differ from regular keys?

Length and shape. Type "delivery by Ukrposhta term", and pronounce "how long does the parcel by Ukrposhta go to the village". The second wording almost does not make it into the standard query lists, but it is constantly found in your requests and in internal searches. That's why we start from there, and we take the query dictionary later - as a check, not as a source.

What should be the answer?

Direct answer in first one or two sentences, details below. Our work test is simple: read the first paragraph alone, without a question on it. If it is so clear, the answer is ready; if it begins with "our company strives" - it can neither be read aloud nor quoted. Assistants cite the paragraph itself, not the question-answer pair.

Where to put a block of questions?

Where the question arises. About compatibility - on the product card, about delivery - on the delivery page and in the checkout, about returns - next to the buy button. One large section "Questions and answers" collects everything in a row and almost does not work: a person does not go there, he asks in the chat. The section makes sense only as a summary, when the blocks on the pages are already there.

JSON-LD or micro-markup directly in layout?

By default, JSON-LD: one block in the template, does not stick to the layout, survives a change of theme. Micro-markup has its own advantage — it hangs on the same elements that a person sees, so it cannot break with the text of the page by construction. This is exactly how it was done in the wholesale catalog from our measurements. The price for this is that the markup goes along with the layout during the redesign. One more detail: if the questions are expanded by clicking, the content should still be in the HTML of the first answer, and not be added with a script.

Is it possible to mark questions that are not on the page?

No. This directly violates the rules and ends up with manual actions. An example from my own measurement of a nearby type of markup: the page announced a rating of 4.8 out of 50 ratings, and the words "review" and "rating" were not on it at all. With questions, the logic is the same - and, unlike the rating, here the check takes a minute: markup against visible text, line by line.

Does a wholesale catalog need an FAQ?

Often more necessary than retail. In wholesale, the questions are specific: minimum batch, shipping conditions, documents, deadlines. We measured a wholesale catalog with 5,830 items, where the micromarkup of questions and answers already worked on the pages together with breadcrumbs, with the first server response of 506.9 ms. The block there is short - and that's why it works.

And are voice assistants and AI responses already a visible channel?

No, and selling it as a mainstream channel would be an exaggeration. The volume of transitions from assistants is still small compared to classic search, and no one guarantees a mention in the answer - vendors have neither guarantees nor transparent selection rules. It's a lead-in job with an unknown payoff, and we talk about it like that. Technically, what is required of you is the same as for a search: the response is rendered in HTML immediately, rather than compiled in the browser.

How to keep the block alive?

By rule, not by force of will. Once a month, someone from support writes out three questions that were repeated most often, and they go to the site. Ten minutes of work — and the block does not become obsolete along with the terms of delivery. We give this order together with the work in writing, so that it does not depend on us.

Demo

Your catalogue on a phone screen

This is how your store can look on a phone: a collection banner, popular products and a cart one tap away. Tap “Add to cart” and the counter in the header updates, just like in a real store.

  • Collection bannerThe first screen shows what is new, not a logo.
  • Product cardsPhoto, price and a button — no extra page to open.
  • One-tap cartThe counter in the header updates instantly, like in a real store.
Stores in the portfolio
This is a demo interface, not a client's store. Live projects are in the portfolio.
SHOP
New collectionAutumn / WinterExplore
PopularAll products ›
  • Essentials Hoodie1 290 ₴
  • Urban Backpack1 490 ₴
  • Classic Cap690 ₴
  • Basic Tee590 ₴
  • Street Sneakers2 390 ₴
  • Active Shorts890 ₴

Send a three-month request dump — or just tell me where your chat is.

The answer is a list of questions that you have already been asked, grouped by topic, with a mark that goes as a block to the existing page, and that pulls to a separate page. If there are enough questions for two blocks, and not for thirty pages, you will hear it in the first email.

View cases
  • Reply within 2 hours
  • No commitment
  • We work under a contract

There is no price list on the site on purpose: the same work differs several times over between two clients, and a “from” figure explains nothing in that case. First a free audit — we count your pages, duplicates and speed — then we name the sum and the deadline and fix both in the contract.