What FAQPage schema is for now#
FAQPage is a schema.org type that marks up a list of questions and their answers in a structure machines can parse directly, instead of having to infer it from an <h3> followed by a paragraph. Google retired the FAQ rich result from search results entirely on May 7, 2026 — for every site, including the government and health properties that had kept it the longest — so the reason to use FAQPage today is no longer "it might earn a dropdown snippet."
The schema itself is still valid and Google has said leaving it in place causes no harm; it simply stopped rendering as a visual search feature. What it still does is give any machine reader — an AI assistant summarizing your page, a crawler trying to understand its structure — an unambiguous signal of which text is a question and which is its answer, which is the actual value this tool is built around now.
It only makes sense on a page that already contains the same questions and answers, visible to a human reader. Schema describes content; it does not create content. Marking up FAQs that are not actually on the page is a policy violation, not a shortcut.
Google's allowed-HTML rule, and why this tool enforces it#
Google's FAQPage documentation specifies a small, closed set of HTML tags it will render inside an answer: <a>, <p>, <strong>, <b>, <em>, <i>, <ol>, <ul>, <li> and <br>. Anything outside that list — a stray <div>, a <span> carrying a CSS class, a heading tag — gets silently discarded by Google's parser, not rejected outright.
That silence is the trap: your schema still validates, still shows no error in most checkers, and quietly renders worse than you wrote it. This tool strips disallowed tags at generation time and tells you exactly which ones it removed, so you find out before publishing instead of never.
One question, one direct answer#
The pattern that tended to get quoted by Google's old FAQ rich result is the same one that gets quoted by an AI answer engine today: a question phrased the way a person would actually type or say it, followed by an answer that states the point in its first sentence. "It depends, but generally speaking..." is the shape of answer that gets skipped over either way.
Two to six FAQs per page is a reasonable range. A handful of genuinely distinct questions, each answered directly, does more than twenty near-duplicates padding out a "content depth" checklist.
What this tool does not do#
It does not check whether the questions and answers you enter actually appear as visible text on your page — that verification is yours to make, and it is the one Google enforcement action actually targets: FAQPage markup that does not match the page's real content.
It also generates FAQPage only. Organization, Article and Product schema follow different rules and are not what this tool is for — use it specifically for a Q&A section.