Generate valid FAQ and Article JSON-LD schema for any page
FreeTurn any page's content into valid, error-free FAQ and Article JSON-LD that passes the Schema.org validator and marks up only what is visible on the page.
Get copy-paste-ready, validation-passing JSON-LD structured data for a page's FAQs and article metadata, without hand-writing schema or shipping invalid markup.
Your details
saved for every promptThis prompt
You are a technical SEO engineer who specializes in structured data (JSON-LD). Generate valid, error-free schema markup for the page below that passes the Schema.org validator, follows Google's structured-data guidelines, and describes only content that is actually visible on the page.
Page details:
- Publisher / organization name: {{company}}
- Canonical page URL: {{page_url}}
- Publisher logo URL (used for Article markup): {{publisher_logo_url}}
- Schema type(s) to generate: {{schema_type}}
Page content (paste the visible copy: headline, body, author, publish and updated dates, and every FAQ question and answer shown on the page):
"""
{{page_content}}
"""
Follow these steps:
1. Read the pasted content and identify the fields each requested schema type needs. An Article/BlogPosting needs: headline, description, main image, datePublished, dateModified, author, and publisher. An FAQPage needs every question and its answer that appears on the page.
2. Pull each value directly from the content above, and keep the wording of questions and answers exactly as it appears on the page.
3. Choose the most specific valid type: use BlogPosting for blog posts, NewsArticle for news, otherwise Article. Use FAQPage only when the page shows a genuine list of questions and answers.
4. Format every date as ISO 8601 with a timezone offset (for example, 2026-07-15T14:30:00+05:00). Model the author as a Person with a name, and a profile url when the page shows one. Model the publisher as an Organization with a name and a logo ImageObject.
5. Nest properties correctly: put each FAQ answer inside an acceptedAnswer object of type Answer with a text property, and list all questions inside the FAQPage mainEntity array.
6. Assemble the markup as JSON-LD, one script block per schema type.
7. Self-check the result: confirm it is valid JSON (double-quoted keys, no trailing commas, special characters escaped), that every required property is present, and that each marked-up value matches the visible page content.
Output in this format:
1. Each schema type as its own fenced <script type="application/ld+json"> block, ready to paste into the page <head>.
2. A short validation checklist confirming: valid JSON, required properties present, headline within 110 characters, dates in ISO 8601, and every FAQ answer matching the page verbatim.
3. A "Missing inputs" list naming any required property you could not fill from the content provided.
Constraints:
- Mark up only content that a visitor can see on the page. When the content above lacks a required value such as an author name or a publish date, list it under "Missing inputs" and ask for it rather than inventing one.
- Keep the Article headline at 110 characters or fewer and match the page's visible H1.
- Treat FAQPage as valid Schema.org that search engines and AI answer engines still parse for page understanding, and include it for that reason; note in a single line that it no longer triggers FAQ rich results in Google Search.
- Return the JSON-LD and the checklist only. Add explanation only for values you flag as missing.5 fields still empty — the {{like_this}} slots fill in as you type.
See it in action
What this prompt produces with example details filled in:
Block 1 — BlogPosting
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://webinnoventix.com/blog/faq-schema-guide"
},
"headline": "FAQ Schema in 2026: Does It Still Help Your SEO?",
"description": "Google retired FAQ rich results in 2026, but FAQPage markup still shapes how search engines and AI assistants read your page.",
"image": "https://webinnoventix.com/assets/blog/faq-schema-2026.jpg",
"datePublished": "2026-07-10T09:00:00+05:00",
"dateModified": "2026-07-15T14:30:00+05:00",
"author": {
"@type": "Person",
"name": "Salman Ahmad",
"url": "https://webinnoventix.com/author/salman-ahmad"
},
"publisher": {
"@type": "Organization",
"name": "Web Innoventix",
"logo": {
"@type": "ImageObject",
"url": "https://webinnoventix.com/assets/logo.png"
}
}
}
</script>
Block 2 — FAQPage
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "FAQPage",
"mainEntity": [
{
"@type": "Question",
"name": "Do FAQ rich results still show in Google in 2026?",
"acceptedAnswer": {
"@type": "Answer",
"text": "No. Google fully retired the FAQ rich result in May 2026, so FAQ pages no longer display expandable question snippets in Search for any site."
}
},
{
"@type": "Question",
"name": "Is FAQPage schema still worth adding?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. FAQPage is still valid Schema.org markup that Google and AI answer engines parse to understand your page, so it can help your content surface in AI Overviews and assistant answers even without the SERP feature."
}
}
]
}
</script>
Validation checklist
- Valid JSON: both blocks parse cleanly — double-quoted keys, no trailing commas, no unescaped characters.
- Required properties present: BlogPosting has headline, image, datePublished, dateModified, author, publisher; FAQPage has mainEntity with Question + acceptedAnswer/Answer.text.
- Headline length: 47 characters (within 110) and matches the visible H1.
- Dates: ISO 8601 with +05:00 offset.
- Content match: both FAQ questions and answers are reproduced verbatim from the page.
Missing inputs
- None required are missing. Optional upgrades: add image width/height, and an author jobTitle, to strengthen E-E-A-T signals.
Note: FAQPage markup no longer produces FAQ rich results in Google Search, but it is valid Schema.org that Google and AI answer engines still parse — kept here for machine understanding.Tips
- Paste the real, visible page copy — including the exact FAQ questions and answers — so the markup describes what users actually see.
- After generating, run the output through validator.schema.org to confirm zero errors before you ship it.
- Give the author a real profile URL (and a jobTitle when relevant) so the Person markup carries genuine E-E-A-T authority signals.
- FAQ rich results are gone, but the markup still feeds Google's page understanding and AI Overviews — keep it whenever you have genuine Q&A content.
Best for: Bloggers and SEOs adding Article or BlogPosting schema to posts, Adding FAQPage markup for AI answer engines and search understanding, Generating structured data without hand-coding JSON-LD, Producing schema that passes the Schema.org validator on the first try
json-ldfaq schemastructured dataschema markuparticle schemaschema generatorrich resultsseoaieo
Built by Web Innoventix
Want the work done, not just prompted? We design, build and rank websites that get found on Google and cited by AI.
Get a free quoteMore prompts
Browse all →SEO & AIEO
Article brief that ranks and gets cited by AI
Produce a content brief optimised for Google rankings AND citations in ChatGPT, Gemini and Perplexity answers.
3 fieldsseoaieo
SEO & AIEO
Title tags and meta descriptions that win clicks
Generate three SERP-ready title tag + meta description options for any page — each under Google's character limits, working in your keyword, and written to earn the click — plus a recommendation on which to use and why.
3 fieldsseometa-description
SEO & AIEO
Write an answer-first block that wins the featured snippet
A fill-in prompt that turns your verified facts into an answer-first block — paragraph, list, or table — engineered to win Google's featured snippet and get quoted by AI answer engines.
5 fieldsfeatured snippetposition zero
SEO & AIEO
Build a topic-cluster and pillar-page plan that wins topical authority
A paste-and-go prompt that interviews you, then builds a complete topic-cluster content strategy — pillar page, cluster map, internal-linking spine, and publishing roadmap — to win topical authority on Google and AI answer engines.
Paste & gotopic clusterspillar page
SEO & AIEO
Write a Google Business Profile post that ranks in local search
A fill-in-the-blank Google Business Profile post prompt that front-loads your local keyword, reinforces local relevance signals, and drives one clear action — ready to paste.
9 fieldsgoogle business profilelocal seo
SEO & AIEO
Audit old posts and decide what to refresh, merge, or kill
An agentic prompt that runs a content refresh audit: paste your aging posts and it gives each one a verdict — Refresh, Merge, Keep, or Kill — with the evidence behind it and a prioritized 90-day action plan.
Paste & gocontent refresh auditcontent decay