FAQ JSON-LD in 2026: visible answers first

A lot of sites panicked when Google reduced FAQ rich results.

Some removed every FAQ block. Some left the markup in place and hoped it would still do something. Some kept adding hidden accordions to pages because an old SEO checklist said FAQ schema was an easy win.

The better answer is less dramatic.

FAQ rich results are no longer a regular search feature for most sites. Google announced in August 2023 that FAQ rich results would only be shown for well-known, authoritative government and health websites going forward. For everyone else, FAQPage markup is not the shortcut it used to be.

But FAQs are not dead.

Visible questions and answers can still be useful for users. They can still help a page match real search intent. They can still support internal linking. They can still make complex pages easier to scan. And when the visible Q&A content is genuinely present, FAQ JSON-LD can still describe that structure cleanly.

The mistake is chasing markup instead of answering questions.

The rich-result era changed

FAQPage markup used to be abused because the incentive was obvious. Add questions and answers, get larger search results, take up more space, attract more clicks.

That incentive produced a lot of junk.

Sites added generic questions. Plugins generated boilerplate. Marketers hid FAQs in collapsed sections. Pages with weak content bolted on FAQ blocks at the bottom. Some answers were written for snippets, not users.

Google’s 2023 change removed most of that immediate reward. FAQ rich results became limited mainly to well-known, authoritative government and health sites.

That means ordinary SaaS, ecommerce, affiliate, agency, and local business sites should not treat FAQ schema as a SERP real-estate tactic anymore.

If your only reason to add FAQs is “maybe Google shows the rich result,” skip it.

What FAQ content is still good for

FAQ content still has a job when it is based on real user questions.

A pricing page may need answers about billing, cancellation, plan limits, and trials.

A support page may need answers about setup, compatibility, permissions, and troubleshooting.

A service page may need answers about process, timelines, guarantees, locations, and what is included.

A product page may need answers about shipping, returns, materials, sizing, integrations, or data handling.

A blog post may need a short FAQ if the main article covers a topic where users clearly ask follow-up questions.

The value is not the markup. The value is reducing uncertainty.

Search Console question queries can be especially useful here. If people already find your site through queries starting with “how,” “what,” “why,” “can,” “does,” or “is,” those are clues. Some deserve full sections in the article. Some deserve a short FAQ. Some deserve their own page.

SEO Perception can surface these as possibilities because crawl data and GSC data together are more useful than either one alone. A crawler can see whether a page has visible FAQ structure. GSC can show whether the page already attracts question-style queries.

Visible content first, JSON-LD second

Google’s structured data guidelines are clear that structured data should represent the page content. Content described in structured data should not be hidden from users.

For FAQPage, this means the questions and answers must exist on the page.

Do not add FAQ JSON-LD for questions that users cannot see.

Do not add answers that are different from the visible answers.

Do not use FAQPage markup for testimonials, sales claims, fake objections, or keyword stuffing.

Do not use it on a page where the main content is not a set of questions and answers or a page section that includes genuine FAQs.

Callout: FAQ JSON-LD should match visible FAQ content. If the visible answer is weak, fix the answer. Do not expect the markup to make it useful.

A good FAQ answer is short, direct, and specific. It should usually answer the question in the first sentence, then add context if needed.

Bad FAQ answers dodge the question, repeat marketing copy, or exist only to include a keyword.

For example:

Bad:

“SEO software is important because many companies need SEO software to improve SEO software outcomes.”

Better:

“SEO software helps you find technical issues, content gaps, and search performance changes faster than manual checks. It does not replace strategy, but it can show you where to look first.”

That is the difference between content and clutter.

FAQPage, QAPage, and normal headings

FAQPage is for pages or page sections where the publisher provides both the questions and answers.

QAPage is different. It is for pages where users submit answers to a single question, such as a forum or community Q&A page.

Most business sites that add FAQ sections are dealing with FAQPage, not QAPage.

But you do not always need FAQPage markup. Sometimes normal headings are enough:

## Common questions

### Can I cancel anytime?

Yes. You can cancel from your account page, and the subscription will not renew after the current billing period.

That structure is already useful. It is visible, scannable, and easy for users to understand.

If you add JSON-LD, it should reflect that visible structure. The markup should not become a second, hidden FAQ with different wording.

AI search and FAQ structure

AI Overviews, AI Mode, ChatGPT search, Perplexity, and other AI-style systems reward clarity in different ways, but there is no public “FAQ schema gets you cited” rule you can rely on.

Google’s AI features documentation says there are no additional requirements to appear in AI Overviews or AI Mode and no special schema.org structured data that must be added. It also says existing SEO fundamentals remain worthwhile, including crawlability, internal links, textual content, page experience, and structured data that matches visible text.

That is the sensible line.

FAQ structure can help because questions and direct answers are easy to parse. JSON-LD can support that structure. But the core asset is still the visible answer.

Do not promise clients that FAQ JSON-LD will make ChatGPT recommend them. That is hype.

A better promise is: clear questions and answers make the page more useful to users and easier for machines to interpret.

That is honest, and it is enough.

How to decide whether to add FAQ JSON-LD

Use this checklist:

Does the page contain real visible questions and answers?
Are the answers useful without the markup?
Do the questions match actual user concerns or GSC queries?
Is the FAQ section relevant to the main page topic?
Are the answers specific, current, and non-deceptive?
Is the page not trying to mark up hidden content?
Does the site have a way to maintain the answers over time?

If yes, FAQ JSON-LD can be reasonable.

If no, write better content first.

The practical workflow

Start with the page, not the schema.

Look at the page’s purpose. Look at Search Console question queries. Look at support tickets, sales objections, live chat logs, and customer emails. Pick questions that actually matter.

Write visible answers.

Group them under clear headings.

Add internal links where a short answer needs a deeper explanation.

Then generate FAQ JSON-LD that matches the visible questions and answers exactly.

Finally, test the structured data and monitor the page over time.

FAQ markup is no longer a cheap SERP trick. Good.

The web has enough tricks.

Useful answers still matter.

Frequently asked questions

Is FAQ schema still worth using in 2026?

Sometimes. It is not a regular rich-result tactic for most sites anymore, but it can still describe useful visible FAQ content accurately.

Should I remove all FAQ markup from my site?

Not automatically. Remove FAQ markup that does not match visible content or exists only for rich-result chasing. Keep or improve FAQs that genuinely help users.

Does FAQ schema help AI search?

There is no reliable guarantee. Clear visible Q&A content can help users and machines understand the page, but no special FAQ schema promises AI visibility.

Can FAQ answers be hidden in accordions?

Accordions can be fine when the content is accessible to users, but the markup must match the visible content and should not describe answers users cannot access.

Read the companion piece Google killed FAQ rich results. Your FAQs are not dead., plus FAQ schema in the docs and AI discoverability overview.