What FAQ schema markup is
It is a description of a question-and-answer block written in the Schema.org vocabulary using the FAQPage type. Visitors see ordinary text: a question heading and a paragraph beneath it. Crawlers also receive a structured copy of the same block, with each question and each answer clearly labelled.
The markup usually goes on service pages, product cards and blog articles, because that is where customers ask about timing, payment, delivery and warranty.
What changed in Google
A few years ago, marked-up questions could expand right inside the search snippet, so site owners added the markup everywhere. Google has since cut back on showing these results, and they now appear mainly for well-known government and health websites.
For a typical business site, such as a Tashkent online shop, a clinic or a renovation studio, the markup remains valid, but an expanded snippet is unlikely. This is Google's decision about how results look. It is not a penalty and not an error. Just do not promise yourself or your boss a jump in clicks from FAQ code alone.
Why add it if there is no rich result
The reasons are quieter but real. The biggest value is not in the code but in the block itself: good answers remove doubts before a customer messages you on Telegram or picks up the phone.
- Search engines understand the structure of the page more precisely.
- Yandex and other systems read the Schema.org vocabulary, so a structured block helps them too.
- Clean question-and-answer pairs are easier for AI answer systems to quote.
- It is cheap to add, especially if your CMS or plugin generates it.
What the code looks like
JSON-LD is the most convenient format: a separate script in the page code. Every question is a Question object inside the mainEntity array, and the reply sits in acceptedAnswer. A simplified example for an online shop:
<script type="application/ld+json">{"@context":"https://schema.org","@type":"FAQPage","mainEntity":[{"@type":"Question","name":"Do you deliver to the regions?","acceptedAnswer":{"@type":"Answer","text":"Yes, we ship to regional centres. The manager confirms the terms when you order."}}]}</script>
The wording is illustrative. Write what is actually true for your business.
Rules you should not break
Breaking the structured data guidelines can lead to manual actions, so keep the markup inside the rules.
- Every question and answer in the markup must be visible to visitors on the page.
- The marked-up text must match the page text in meaning.
- One question, one answer from the site. For forums where users answer, the QAPage type exists.
- Do not use FAQ for advertising or for questions nobody really asks.
- Do not repeat the same questions across dozens of pages.
Which questions to include
Take questions from real practice: what managers hear on the phone and in Telegram, what people write in Instagram comments, and what Google suggests in the People Also Ask box. For a shop, that means delivery, warranty, returns and paying with Click or Payme. For a clinic, preparation for a procedure and contraindications.
Put the answer in the first sentence and the detail after it. One template block copied to every service page is a weak choice, since each page has its own questions.
Common mistakes and how to test
The usual slips: markup without a visible block, a hidden accordion whose text only loads after a click, many questions in the code but three on the page, HTML tags that break the JSON, and duplicate markup from two plugins.
Test the code in Google's Rich Results Test, the Schema.org validator and Yandex Webmaster's markup validator. Test the published page, not just the code, so you can see your CMS outputs it where intended. A missing FAQ report in Search Console is not an error.
If you want help with the technical side, markdev works on SEO optimisation in Uzbekistan: structure audits, markup and content. Tell us about your project and we will say honestly where FAQ markup helps and where strong copy is enough.
FAQ
Does FAQ schema still give rich results in Google?
For most commercial sites, usually not. Google shows them mainly for authoritative government and health websites. The markup itself stays acceptable.
Can I put the FAQ inside an accordion?
Yes, as long as the answer is in the page code and a visitor can open it. It is a problem if the text loads only after a click through a script, or is missing.
Which markup format should I use?
JSON-LD is usually easiest. It sits in a separate script, stays apart from your layout and is simple to add through a CMS or plugin.
Can one FAQ block go on every page?
It is not advisable. Repeated questions add little value. Build each block around a specific service or product and mark it up only there.
Let’s look at your task for free
Leave your contact — in a 15-minute call we’ll show where leads get lost and what to fix first.