FAQ Schema
SEOAlso: FAQPage Schema · FAQ Structured Data
Quick definition
FAQ Schema is a type of structured data that marks up question and answer content in code so search engines can read it as a distinct format. It uses Schema.org's FAQPage type to tell Google exactly which text is a question and which text is its answer.
How it varies across Australia
Eligibility for FAQ rich results narrowed sharply after Google's 2023 update, and that change applied globally including to Australian sites. Most commercial pages lost the expandable snippet in the search engine results page (SERP), while government and well-established health sites kept it. The gap between businesses that still mark up FAQs properly and those that gave up entirely is wide.
See technical SEO scores across Australian industries →What it actually means
Think of FAQ Schema as labelling a filing cabinet. Without labels, a search engine sees a page of text and has to guess what's a question and what's an answer. With FAQ Schema, every drawer is labelled. The question goes here, the answer goes there, no guessing required.
Most teams adopted FAQ Schema for one reason. It used to make your listing bigger in the SERP, with expandable questions sitting right under your title and meta description. That reason mostly disappeared in 2023, when Google restricted the visual rich result to a small set of authoritative government and health sites.
The schema itself didn't stop working. It stopped paying off the way people expected. What it still does is make your content easier for machines to parse, which matters more now than it did before, because those machines include AI overviews and voice assistants, not just the classic blue links.
This is technical SEO in its purest form. Invisible to the average visitor, structural to how the page gets read.
FAQ Schema stopped being a rich-result trick in 2023. It's now a machine-readability habit that pays off somewhere else entirely.
How it shows up
FAQ Schema shows up as JSON-LD code in a page's head or body, invisible on the rendered page itself. You'll see it in Google's Rich Results Test as either eligible or ineligible for the FAQPage rich result. It also shows up indirectly in how AI-generated answer boxes and voice assistants phrase responses, since well-structured question and answer pairs are easier for those systems to lift and quote directly.
The Australian context
Australian government and health sites (think Services Australia, health.gov.au) are among the few site categories still eligible for the visual FAQ rich result under Google's tightened rules. For everyone else in the Australian market, including most ecommerce and professional services sites, the rich result is effectively gone regardless of how well the markup is implemented.
That doesn't make the exercise pointless. It shifts the payoff away from SERP real estate and toward how well your content answers questions when an AI system or voice assistant is doing the reading instead of a human scanning a results page.
Where people get this wrong
Related terms
Common questions
Is FAQ Schema still worth implementing in 2026?
Yes, but for a different reason than before. The rich result in Google's search results is largely restricted to authoritative sites, but the structured content still helps AI overviews and voice assistants parse and quote your answers accurately.
Why did my FAQ rich results disappear?
Google tightened eligibility for the FAQPage rich result in 2023, limiting it mostly to government and well-established health sites. If your business isn't in one of those categories, the visual snippet is unlikely to return regardless of markup quality.
Does FAQ Schema affect rankings directly?
Schema.org markup is not a direct ranking factor on its own. Its value is in helping search engines and AI systems understand and correctly surface your content, which can influence visibility indirectly through richer answer features.
Where should FAQ Schema be placed on a page?
It should mark up genuine, visible question and answer content already on the page as JSON-LD, typically in the page head. It shouldn't be added invisibly to content that doesn't actually appear for human visitors, since that risks a manual action.
Debrief
Get the next one
No spam. No fluff. Just the next article, straight to your inbox.
Keep exploring
About New Rebellion
New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.
How we think →