In 2026 FAQ markup is no longer a way to get FAQ rich results in Google Search. Google's documentation says the feature stopped appearing on 7 May 2026 and the documentation was removed on 15 June 2026; since August 2023 it had been limited to well-known government and health sites anyway. Write FAQ sections for customers: real questions, short direct answers, placed near the decision point. Treat existing FAQPage markup as harmless but not a reason to invest.
The short history, and why many guides are out of date
If you search for FAQ schema, many top results still describe it as a way to take more space on the results page. That was true for some sites several years ago, and it is no longer true. The sequence matters for any owner or agency still selling it:
| Date | What happened | Source |
|---|---|---|
| 2019 to early 2023 | FAQ rich results could appear for eligible pages that followed the markup guidelines | Google Search Central documentation (historical) |
| August 2023 | Google limited FAQ rich results to well-known, authoritative government and health websites | Google Search Central Blog, 'Changes to HowTo and FAQ rich results' |
| 7 May 2026 | FAQ rich results stop appearing in Google Search | Search Central documentation updates, entry of 8 May 2026 |
| 15 June 2026 | The FAQ rich result documentation is removed; the page states the feature is no longer shown | Search Central documentation updates, entry of 15 June 2026 |
| June to August 2026 | Search Console reporting and testing for FAQ are reported to be retired | Industry reporting (Search Engine Journal); check Search Console for your account |
We read the Search Central documentation updates page for the first two 2026 rows and have confirmed those dates. The later reporting rows come from trade press and may change, so check your own Search Console. Anything that promises 'FAQ stars' or extra search space from schema alone is outdated.
What changed for a UAE service business
Very little changes in the work that actually generates enquiries. A clinic, a pest control firm or a gym owner never won customers because of an expanded snippet; they won them when the page answered a worry quickly. The loss is a technical shortcut, not a strategy. What still matters is the content that FAQ sections hold.
- Customers still ask the same questions before booking: price logic, safety, timing, coverage, guarantees you truly give.
- Pages that answer those questions convert better than pages that avoid them.
- Google, and assistants that summarise web pages, need clear text to understand what you offer. Plain headings and short answers are readable by both.
- Structured data in general is still useful where Google lists a feature, for example Local business, Organization and Breadcrumb in its structured data gallery. FAQ is no longer in that gallery.
For how AI-assisted search treats your content, see our AI search optimization guide. It follows the same principle: clear, accurate, customer-focused answers.
A decision framework: keep, change or remove
| Situation | Decision | Reason |
|---|---|---|
| Your CMS or plugin outputs FAQPage JSON-LD, valid and matching visible text | Keep, do not invest more | Low risk, no promised benefit in Google Search |
| You hand-code FAQPage on every page | Stop adding new markup; spend the time on the visible text | Google has retired the feature |
| Markup includes questions that are not visible on the page | Remove it | Google states that markup should describe visible content |
| Markup contains promotional or misleading answers | Rewrite or remove | Accuracy and trust matter more than format |
| You have no FAQ on key service pages | Write one | Customers need the answers |
| A health, legal or financial page has FAQ answers with advice | Review with a qualified person and regulator rules | Higher standard for sensitive topics |
The principle that markup must match visible content comes from Google's structured data introduction: Google matches markup to what users can see and says not to describe information that is not visible. It also recommends JSON-LD for implementation, and does not promise that markup will produce rich results.
How to build a FAQ that earns its place
- Collect 20 real questions from WhatsApp, calls, forms and sales conversations over the last three months.
- Group them by stage: before contact (price, coverage, trust), during service (process, timing), after service (guarantees, follow-up).
- Pick the 6 to 8 that block a decision most often. Move the rest into articles or the body of the page.
- Write each answer in three parts: a direct answer in the first sentence, the condition or exception, and the next step.
- Link to the full explanation: a section, a guide or a case study.
- Review the FAQ every quarter; delete answers that are out of date.
Use the lead qualification questions and your WhatsApp follow-up log as sources, because they hold the language customers really use.
Writing patterns that work
| Weak answer | Better answer | Why |
|---|---|---|
| 'We offer the best prices in Dubai.' | 'Price depends on property size, frequency and access. Send photos on WhatsApp and we reply with a quote logic.' | Explains, does not boast |
| 'Yes, contact us for details.' | 'Yes for villas up to the size listed on this page. For larger sites we need a visit first.' | Gives a real boundary |
| Long paragraph repeating the page | Two sentences and a link | Respects the reader |
| Generic questions copied from competitors | Questions from your chat history | Original and useful |
For regulated sectors such as clinics, avoid answers that read as medical advice or promise outcomes. Health advertising has special rules from regulators and platforms; see our medical advertising rules checklist and the clinic website checklist.
Where the FAQ belongs on the page
A FAQ at the very bottom is the last thing a mobile visitor sees. Place it after the proof and cost-factor sections, where doubts appear, and follow it with a clear action block. For long pages, place two or three decision-critical questions inside the relevant section as short answers, and keep the full list near the end. Our service page structure checklist puts the FAQ as block 10 of 12 for this reason.
Bilingual sites: write Arabic and English separately
Questions differ by audience. Arabic-speaking customers may ask about family or household access, payment methods or response time differently from English-speaking expatriates. Write each FAQ from the questions customers ask in that language, keep facts identical, and link the language versions properly. See our bilingual SEO guide.
Three myths to drop from your checklist
- Myth: adding FAQ schema makes my page rank higher. Google's documentation never described FAQ markup as a ranking factor, and the rich result feature itself has now ended.
- Myth: more questions mean more visibility. Padding a page with thirty generic questions makes it slower to read and harder to keep accurate; six to eight decisive answers serve customers better.
- Myth: an FAQ is a place to hide keywords. Readers notice stuffed answers immediately, and it damages the trust you are trying to build. Write the way you would answer a customer on the phone.
If an agency quotes you a separate price for FAQ markup alone, ask what outcome they expect and how they will measure it. A better use of the same budget is a proper content review of your three most important service pages, with the questions your team hears every week.
A hypothetical audit
This is an invented example. A physiotherapy clinic site has an FAQ plugin that outputs FAQPage markup on 40 pages, all using the same generic questions. The audit finds that the answers repeat across pages, nobody has updated them for a year, and several mention prices that have changed. The recommendation is not to remove the plugin, but to write six real questions for the three most important service pages, delete the generic ones, and add the questions to the monthly review. Any markup that remains is then at least accurate.
How we work at ZED
Our process for service businesses is research, setup, call and WhatsApp tracking, then monthly reporting. For FAQ sections, research means collecting the questions your customers ask; setup means writing and placing answers on the right pages inside our website and SEO work; tracking records calls and WhatsApp taps from those pages with our conversion tracking; and the monthly report shows which pages produce enquiries. We publish no price list. You can see our approach to sectors in the medical marketing case study, the case studies and the portfolio. Send your page link and we reply with an initial plan.
Frequently asked questions
Does Google still show FAQ rich results?
No. Google's Search Central documentation changelog says the FAQ rich result would no longer appear in Google Search from 7 May 2026, and on 15 June 2026 it removed the FAQ documentation, stating that the feature is no longer shown. Before that, from August 2023, it had been limited to well-known government and health websites.
Should I delete FAQPage markup from my pages?
You are not forced to. Reports on the change say existing markup does not cause problems, but Google's own pages no longer give guidance on it, so we cannot promise any benefit. Do not spend new budget adding it. If your site generates it automatically and it is valid and matches the visible text, leaving it is low risk; if you maintain it by hand, put that time into the visible FAQ instead.
Is a visible FAQ section still worth writing?
Yes, for readers. A good FAQ answers the questions customers ask before they contact you, handles objections, and brings useful wording to the page. It is a content and conversion decision, not a markup decision.
Where do I find real FAQ questions?
Start with your own channels: WhatsApp chats, call notes, form messages and sales conversations. Then check Search Console queries that contain question words, and the questions that appear in search results for your service. Prefer questions you hear from customers over generic lists.
How many questions should a service page have?
Six to eight is a good range for a service page. More is fine if each is real, but long lists dilute the page. Put the most important objections first and move technical detail into separate articles that you link to.
Should the FAQ answers be the same as the page text?
No. Do not repeat paragraphs that are already on the page. Use the FAQ for short direct answers, conditions and next steps, and link to the page section or article for the full detail.
Does the Arabic version need its own FAQ?
Yes. Write the Arabic FAQ from Arabic customer questions rather than translating the English list, because the worries and wording can differ. Keep the facts identical between languages.
Can ZED write and organise FAQ sections for my pages?
Yes. We collect customer questions, write the answers with you, and place them on the right pages as part of our website and SEO work. Send your page link on WhatsApp for an initial plan.
Turn customer questions into pages that convert
Send your page link and the questions customers ask most on WhatsApp. We reply with an initial plan, with no promise of rankings or rich results.
Send page link on WhatsApp Call 01097079170