So you've heard that adding FAQ schema to your pages can get you those sweet rich results in Google Search — the expandable Q&A dropdowns right in the SERP. You Google "FAQ schema generator", paste in your questions, copy the JSON-LD, and drop it in your <head>. Done, right?
Sort of. There's more going on here than most tutorials explain.
Let's break it down properly.
What Is FAQ Schema, Actually?
FAQ schema is a type of structured data — machine-readable metadata you embed in your HTML to tell search engines what kind of content is on your page.
It uses the is just a UI wrapper around a template. You fill in fields, it writes the JSON-LD for you. Nothing more.
The output of every single FAQ schema generator in existence looks like the block above. They differ only in:
- Whether they let you add multiple Q&A pairs (most do)
- Whether the
textfield allows HTML (more on this in a second) - Whether they validate the output before showing it to you
- Whether they minify or pretty-print the JSON
They do not:
- Check if your questions match actual content on your page
- Verify whether your page is eligible for rich results
- Guarantee you'll get a rich snippet
- Update automatically if you change your FAQ content
That last point trips people up constantly.
The HTML-in-answers Question
Google's documentation says the text property of an Answer does support a limited subset of HTML — specifically: <a>, <b>, <br>, <em>, <i>, <li>, <ol>, <strong>, <ul>.
Some generators strip all HTML from the answer field. Some preserve it. Some encode it incorrectly (double-escaping & instead of &, breaking the output).
If your answers need links or lists inside them, test your generator's output manually. Paste the result into — tests whether Google can parse your schema and whether your page is eligible for rich results
Schema.org Validator — validates against the schema.org spec directly, independent of Google's interpretation
These aren't interchangeable. Google's validator tells you what Google will do with your schema. The schema.org validator tells you if your markup is technically correct per the open standard. Run both.
When Rich Results Don't Appear (and It's Not the Generator's Fault)
Even perfectly valid FAQ schema doesn't guarantee a rich result. Google treats rich results as optional enhancements, not entitlements. Common reasons you won't see them:
- The page doesn't have enough authority or trust signals yet
- Google already shows a competitor's FAQ snippet for the same queries
- The SERP layout for those queries doesn't include FAQ features (Google has been reducing FAQ rich results for high-authority sites since 2023)
- The page was crawled but not yet re-indexed since you added the schema
Structured data is an input signal to Google's rendering pipeline. What comes out the other end is Google's decision.
TL;DR
| Thing | What It Does | What It Doesn't Do |
|---|---|---|
| FAQ Schema Generator | Writes valid JSON-LD for you | Validates content match, guarantees rich results |
JSON-LD in <head> | Makes schema parseable by crawlers | Make questions visible to users |
| Google Rich Results Test | Shows if schema is parseable | Guarantees SERP appearance |
| FAQPage schema type | Signals Q&A structure to search engines | Work on pages without actual FAQ content |
Structured data is one of those areas where the tooling is simple but the judgment required to use it correctly is non-trivial. Generators handle the syntax. Understanding when and how to apply the schema — that part is still on you.
SOCIAL SHARE CARD GENERATOR