Schema type · FAQPage FAQ schema generator
Paste questions and answers as plain text and get valid FAQPage JSON-LD. Be aware before you spend time on it: Google stopped showing FAQ rich results for every site on 7 May 2026. The markup is still valid schema.org; it just no longer changes how your result looks in Google.
- Required and recommended checks
- Rich-result status as of 2026
- Runs locally
Generate FAQPage JSON-LD
Write each question on one line and its answer on the lines below; leave an empty line between pairs. The answer can contain simple HTML such as links or lists.
One question per block: first line is the question, the lines below are the answer. Separate blocks with an empty line.
BlogPosting for blog posts, NewsArticle for news, Article for anything else.
The title as shown on the page.
One per line. Google suggests 16:9, 4:3 and 1:1 versions.
ISO 8601, e.g. 2026-11-02T09:00:00-05:00.
Only change it when the content really changed.
Just the name, no "by" or job title.
A profile page that identifies the author.
One per line.
Your own stock code.
8, 12, 13 or 14 digits from the barcode. Leave empty if the product has none.
Number only, dot for decimals: 59.00. Symbols are removed automatically.
ISO 4217: USD, EUR, GBP…
YYYY-MM-DD. Leave empty if the price has no end date.
Only if real customer reviews are shown on the page.
A short name or acronym people search for.
At least 112×112 px, readable on a white background.
One URL per line: LinkedIn, X, YouTube, Wikipedia…
With country code: +1-415-555-0100.
Two letters: US, GB, DE…
One level per line: Name | URL. The last line is the current page and can omit the URL.
Pick the most specific one.
A photo of the place.
With country and area code.
e.g. $$ or $10–20 (under 100 characters).
e.g. Ramen, Japanese
Two letters.
At least 5 decimals.
At least 5 decimals.
One rule per line: Mo-Fr 09:00-18:00, Sa,Su 10:00-16:00. Closed days: just leave them out.
Google’s list of applicationCategory values.
e.g. Windows, macOS or Android 10+.
0 for free apps.
Required when the price is above 0.
Google requires a rating or a review for this rich result.
Minutes (45), 1:30, or ISO 8601 (PT1H30M).
One per line (things used up).
One per line (things you need but keep).
One step per line. Optional short title: Title | what to do.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "How long does shipping take?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Orders ship within 1 business day. Standard delivery takes 3–5 business days in the continental US."
}
},
{
"@type": "Question",
"name": "Can I return an item?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Unworn items can be returned within 30 days for a full refund. Return labels are free."
}
},
{
"@type": "Question",
"name": "Do you ship internationally?",
"acceptedAnswer": {
"@type": "Answer",
"text": "We ship to 40 countries. Duties and taxes are calculated at checkout, so there are no surprise fees on delivery."
}
}
]
}
</script>Paste it into the page’s <head> or <body>. The values must match what visitors can see on that page.
Checks
Errors break eligibility; warnings are recommended properties or likely mistakes.
- NoteFAQPage: valid markup, but Google stopped showing FAQ rich results on 7 May 2026 for all sites. Keep it only if it helps other consumers.
Version v1.0Updated Update history
What the generator gives you
A code block, a list of checks and three links. Each answers a different question.
The JSON-LD block
A <script type="application/ld+json"> tag with one object. It can go anywhere in the HTML; the head is the usual place. If your CMS already outputs schema for the same thing (many SEO plugins do), replace theirs rather than adding a second, conflicting copy.
Errors
A required property is missing or a value has the wrong format: a date like 11/09/2026, a price written as $59, a currency written as usd. Google ignores an item with errors for rich results, though the page itself still ranks normally.
Warnings
Recommended properties you left out, or things that are valid but risky, such as a relative image URL or a time without a time zone. Add a recommended property only when the information really appears on the page.
Eligible is not the same as shown
“All required properties present” means the item can qualify. Google still decides per query whether to show a rich result, and some types (FAQ, HowTo) are no longer shown at all. The tool says so on those types instead of pretending.
The checks follow schema.org and Google Search Central’s structured data pages as of November 2026. Google’s own Rich Results Test is the final word on eligibility; test the live URL after publishing.
Four steps from form to rich result
Most of the work is copying facts that are already on the page.
-
1
Choose the type
Match the main content of the page: a product page gets Product, a blog post Article, the home or about page Organization. One page can carry several types, each in its own block.
-
2
Fill in the visible facts
Copy names, prices, dates and ratings exactly as visitors see them. Markup that describes content not on the page breaks Google’s guidelines.
-
3
Clear the errors
Work down the checks list until there are no errors. Warnings are optional but usually worth fixing.
-
4
Publish and test
Paste the block into the page template, deploy, then run the live URL through the Rich Results Test and watch the Enhancements reports in Search Console.
FAQPage rules, and its status in Google
FAQPage itself has not changed: a page of questions with one accepted answer each. What changed is Google’s use of it.
- August 2023: FAQ rich results limited to well-known government and health sites
- 7 May 2026: FAQ rich results no longer shown in Google Search
- June 2026: Google removed the FAQ structured data documentation
- Use QAPage instead when users submit several answers to one question
| Property | On | Required | Notes |
|---|---|---|---|
| mainEntity | FAQPage | Yes | Array of Question objects |
| name | Question | Yes | The full question text |
| acceptedAnswer | Question | Yes | One Answer object |
| text | Answer | Yes | The full answer; simple HTML allowed |
A shipping-policy FAQ
Three questions from a store’s help page. The answers in the markup match the visible text word for word.
| Question (name) | Answer (acceptedAnswer.text) | Fine as FAQ? |
|---|---|---|
| How long does shipping take? | Orders ship within 1 business day… | Yes: a fixed answer written by the site |
| Can I return an item? | Unworn items can be returned within 30 days… | Yes |
| Which size should I buy? | Answers from 14 customers | No: several user answers belong in QAPage |
None of these produce an FAQ rich result in Google any more. The markup still documents the Q&A for any system that reads schema.org.
Why valid-looking markup gets ignored
Most structured data that never produces a rich result fails for one of these reasons.
Marking up what visitors cannot see
Ratings with no reviews on the page, FAQs that only exist in the code, or prices that differ from the page. Google treats this as spam and can apply a manual action.
Local date and price formats
09/11/2026, 1.299,00 € and ¥199 are normal on a page and wrong in JSON-LD. Use ISO dates and plain numbers.
Two plugins, two copies
A theme and an SEO plugin both output Product or Organization with different values. Keep one source of truth.
Chasing retired rich results
FAQ and HowTo markup no longer produce rich results in Google. Adding them to every page is wasted effort.
See whether search traffic follows
Structured data is a means; clicks are the result. TapCub puts search performance, crawler activity and page behaviour next to each other, so you can see what happened after you shipped the markup.
Search Console and Bing in one view
Clicks, impressions, CTR and position by query and page, with content-decay alerts for pages losing traffic.
Learn moreSearch engines and AI crawlers counted apart
Googlebot, Bingbot and AI crawlers are kept out of human reports and shown on their own lines.
Learn morePage reports
Entry and exit pages, 404s with the referrer that sent people there, and pages that used to rank and now slip.
Learn moreSchema markup generator questions
Still have a question?
Chat with the team behind TapCub — we usually reply within a few hours on business days.
Does FAQ schema still work in Google?
Not for rich results. Google stopped showing FAQ rich results on 7 May 2026 and removed the documentation in June 2026. Since August 2023 they had already been limited to well-known government and health sites. Valid FAQPage markup does no harm, but it no longer adds the expandable questions under your result.
Should I remove existing FAQ markup?
There is no penalty for keeping valid markup, so removing it is not urgent. Do not spend time adding it to new pages for Google’s sake. Keep it where your CMS outputs it automatically and it matches the visible text.
What is FAQ markup still useful for?
It states unambiguously which text is a question and which is the answer. Other search engines, site-search tools and AI systems can read schema.org, but none of them publicly promise a feature for it, so treat any benefit as a bonus.
FAQPage or QAPage?
FAQPage is for questions the site answers itself, with one answer each. QAPage is for a single question where users post answers, like a forum thread. Using FAQPage for user-generated answers was never allowed.
Update history
New features, fixes and data refreshes for this tool, newest first.
-
· v1.0
LaunchedFirst release.
Missing something or found an error? Tell us — requests that come up often go into the next update. All tool updates
Check the result, then the rest of the page
Validate the published page, then make sure the title and description earn the click.