FAQPage
FAQPage turns a list of questions and answers into clean, labeled pairs. It used to be the most popular rich result on the web. Here's how to write it, and what it's still good for now that Google has stopped showing it.
First, the honest part
For a few years, FAQ markup was the shortcut everyone used. Add it, and your search result could grow a stack of expandable questions underneath. So everyone added it, to everything.
Google pulled it back in two steps:
- August 2023: FAQ rich results were limited to well-known, authoritative government and health websites. Everyone else stopped seeing them.
- May 2026: Google stopped showing FAQ rich results in Search altogether, and in June 2026 it removed the FAQ documentation from Search Central.
So let's be clear: adding FAQPage markup today will not change how your page looks in Google. If a plugin or an agency promises FAQ snippets, that promise is out of date.
So why learn it?
Because FAQPage is still a valid, well-defined Schema.org type, and the markup still does the thing schema does best: it removes guesswork. A page of questions and answers is easy for people to read, but a machine has to figure out which sentence is a question, where each answer starts, and where it stops. FAQPage labels every pair.
Search engines other than Google, AI assistants, and other tools that read structured data can use those clean pairs. We can't promise any particular tool does, and you shouldn't promise it to a client either. But if your page genuinely has an FAQ, accurate markup costs little and does no harm.
Our advice: add it when the FAQ is real and already on the page. Don't create an FAQ just to have somewhere to put markup.
When to use it
- Yes: a page where you wrote both the questions and the answers. A help page, a "Questions about our wedding invitations" section, a pricing FAQ.
- No: a page where visitors ask questions and other visitors answer them, like a forum thread or a product Q&A. That's
QAPage, a different type, and one Google still supports. - No: questions hidden in the markup that aren't on the page.
- No: ads or sales pitches dressed up as questions ("Why is Fern & Ink the best studio in Minnesota?").
The code
Fern & Ink's wedding invitations page ends with three common questions. Here's the markup for that page.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"@id": "https://fernandink.example/services/wedding-invitations/#faq",
"mainEntity": [
{
"@type": "Question",
"name": "How far in advance should we order wedding invitations?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Start about four to six months before the wedding. Design takes three to four weeks, and printing takes another two."
}
},
{
"@type": "Question",
"name": "Can you match our wedding colors?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. We mix every ink by hand, so we can match almost any color from a swatch or a Pantone number."
}
},
{
"@type": "Question",
"name": "Do you ship outside Minnesota?",
"acceptedAnswer": {
"@type": "Answer",
"text": "We ship anywhere in the United States. Local couples can also pick up their order at our studio on Main St SE."
}
}
]
}
Line by line
Since Google no longer documents a FAQ feature, the tags below are our advice, based on the Schema.org definitions.
| Property | Our advice | What it does |
|---|---|---|
@type: FAQPage | Recommended | Says "this page is a set of frequently asked questions." |
mainEntity | Recommended | An array (a list in square brackets) holding one Question per question on the page. |
Question.name | Recommended | The full question, word for word as it appears on the page. |
acceptedAnswer | Recommended | An Answer object. "Accepted" just means "this is the official answer." |
Answer.text | Recommended | The full answer, matching the visible text. Simple HTML like links and lists is allowed inside the string. |
@id | Optional | A name tag, handy if this FAQ sits inside a bigger @graph on a service page. |
Read it as nesting boxes: the page contains questions, each question contains one answer. That's the whole pattern. Adding a fourth question means copying one Question object, adding a comma between objects, and changing the text.
The rules that keep it honest
- Answers must be visible on the page. The full answer text should be there for a visitor to read. An accordion that opens on click is fine; text that only exists in the markup is not.
- Match the words. The question and answer in the markup should match what's on the page. Small whitespace differences don't matter. Different claims do.
- One FAQPage per page. If a page has two FAQ sections, put all the questions in one
mainEntitylist instead of writing two FAQPage blocks. - Don't repeat the same FAQ everywhere. If the same five questions appear in your footer on every page, mark them up once, on the page that's actually about them.
Common mistakes
- Leftover promises. Old SEO advice (and some plugins) still say "add FAQ schema for more space in Google." That stopped being true in 2023 for most sites, and for everyone in 2026.
- Using FAQPage for user questions. Forum threads and community Q&A belong in
QAPage. - Missing commas. With several questions, a missing comma between
}and{is the most common syntax error. A validator will catch it. - Escaping trouble. A quote mark inside an answer must be written as
\", or the whole block breaks.
Testing it
Google's Rich Results Test is built around Google's own features, so it isn't the right tool for FAQPage anymore. Use the Schema Markup Validator instead. It checks that your markup is valid Schema.org, whatever Google does or doesn't display. We'll cover both tools in the Testing lesson.
Try it
Add a fourth question to the example: "Do you offer digital proofs?" with the answer "Yes, you'll get a PDF proof to approve before anything goes on press." Then paste the result into the Schema Markup Validator. If it complains, look for the missing comma first.
Check yourself
- I know Google no longer shows FAQ rich results, and I won't promise them to anyone.
- I can write an FAQPage with a
mainEntitylist of Questions and Answers. - Every answer in my markup is visible on the page, word for word.
- I use one FAQPage per page.
- I use QAPage, not FAQPage, when visitors write the answers.
FAQ alongside Person, Event, Recipe, and Reviews: Schema Markup Explained, Part 3: FAQ, Person, Event, Recipe, and Reviews.