Does the markup have to match what is on the page?

Yes, and this is the rule most often broken. Google’s structured data policies say not to mark up content that is not visible to readers of the page, and markup that misrepresents a page can lead to a manual action.

Where do I put the JSON-LD?

In a script tag with type="application/ld+json", anywhere in the head or body. The most reliable approach is to render both the visible accordion and the JSON-LD from the same array in your code, so the two cannot drift apart as the copy changes.

Free tool · Structured data

FAQ Schema Generator

Turn a page’s questions and answers into valid FAQPage JSON-LD.

No sign-up. We read the page to fill this in. Nothing is stored.

In the output

What you get

Valid FAQPage JSON-LD, ready to paste
One answer per question, as the spec requires
Escaped text that will not break the block
A warning when the markup will not validate

That every question has exactly one answer, which is the constraint FAQPage markup enforces and hand-written JSON-LD most often breaks.
That the markup validates as FAQPage before you paste it into a page.
That the answer text carries no HTML that would invalidate the block.
That the questions match what is visible on the page, which Google’s structured data policies require.

Three steps

How to use the FAQ Schema Generator

Enter the page your FAQ is on

We read existing FAQ markup and open accordions, so the wording already matches what a visitor sees.

Review the generated JSON-LD

It is emitted as a single script block, ready to paste.

Add it to the page’s head

One FAQPage block per page. Two competing blocks is a common and silent error.

Why it matters

Why FAQ markup is worth the five minutes

It describes your answers unambiguously.

A question paired with exactly one answer is a clear structure for any system that reads the page, even though Google no longer shows FAQ rich results.

It has to match the visible page.

Google’s structured data policies say not to mark up content readers cannot see. Use the wording already on the page.

One block per page.

Two competing FAQPage blocks is a common and completely silent failure.

It ages badly if nobody watches it.

The copy changes, the markup does not, and the mismatch stays invisible until someone checks.

After you run it

What to do with the result

Google stopped showing FAQ rich results in May 2026, so this markup no longer earns a special search display. What it still does is describe your questions and answers in an unambiguous, machine-readable form that matches the visible page. The catch is keeping it matched as the copy changes. Veritas scores structure as you write, so the markup and the page do not drift apart.

Content optimization tool

Frequently asked questions

No. Google limited FAQ rich results to well-known government and health sites in September 2023, announced that the feature would stop appearing in Search from 7 May 2026, and removed its documentation on 15 June 2026. The markup can still be worth adding as an accurate, machine-readable description of a page’s questions and answers, but not for a search display.

Same cluster

More free tools

Article Schema Generator

Build Article JSON-LD from a post URL, with the author fields that carry E-E-A-T.

Organization Schema Generator

Define who your company is, once, in the markup search and answer engines read.

SERP Snippet Preview

See how your title and description render in Google results, and where they get cut off.

See where you actually stand.

A free tool checks one thing once. Veritas watches all of it, continuously, across every engine that decides whether you get cited.

GOOGLE · CHATGPT · PERPLEXITY · GEMINI · AI OVERVIEWS