Schema Markup Generator
Build valid JSON-LD structured data for Article and FAQ pages. Unlocks rich snippets (star ratings, sitelinks, FAQ accordions) in Google search results.
How to use this tool3 quick steps
Choose Article or FAQ schema
Article schema enables author-attributed rich results in Google News. FAQPage schema can show expandable Q&A blocks directly in search results.Fill in the form fields
Headline and URL are required for Article. For FAQ, each question and answer pair must be complete. The output updates live as you type.Copy and paste into <head>
Paste the <script> block anywhere in your page's <head>. Then validate with Google's Rich Results Test to confirm eligibility.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article"
}
</script>Use this with
Related schema & structured data tools
Structured Data Guide
Why schema markup unlocks rich snippets
Schema.org is a shared vocabulary Google uses to understand what your page is about — not just what words it contains. Proper schema unlocks rich results: FAQ accordions, star ratings, breadcrumbs, sitelinks, and more. Those expanded listings take more SERP real estate and typically 2–3× click-through.
JSON-LD is the recommended format
Google supports microdata, RDFa, and JSON-LD, but JSON-LD is preferred because it ships as a single <script> block in your <head> — no HTML restructuring, no template gymnastics.
Article schema
Use on blog posts and news articles. Provides Google with headline, author, publish date, and hero image — which can trigger Top Stories carousel placement (for news) and richer snippets for evergreen articles.
FAQ schema
Use on any page with a Q&A section. Google renders the questions as an accordion directly in the SERP — hugely expanding your listing's vertical space and dominating attention. Also works on product pages with genuine FAQs.
Validation is mandatory
Invalid schema is silently ignored by Google, which means you get zero benefit and never know why. Always validate at search.google.com/test/rich-results before deploying — the link is right above the output.
Don't fake FAQs
Google requires the Q&A content to be visible on the page. Adding FAQ schema with content users can't see is a policy violation that can get your rich snippets suppressed site-wide.
Multiple schemas per page
You can ship multiple <script> blocks on one page — e.g., Article + FAQ on a blog post with a FAQ section. Generate each separately here and paste both into your <head>.
Pro Tips
Use ISO 8601: YYYY-MM-DD (or full timestamp). Our date pickers produce this format natively. Non-ISO dates get parsed unreliably or rejected entirely.
For Article author, use Person when a human wrote it, Organization only when the piece is genuinely anonymous/staff-written. Google prefers Person schema for E-E-A-T (Experience, Expertise, Authority, Trust).
After deploying, check Search Console → Enhancements. Google reports which pages have valid FAQ/Article schema and flags errors. Fix errors within 48 hours — unfixed errors can disable rich snippets for months.
Frequently Asked Questions
- Will schema guarantee my rich snippets show up?
- No. Valid schema makes you eligible for rich results. Google still decides whether to show them based on relevance, quality signals, and SERP layout. Expect 2–8 weeks from deployment to seeing rich snippets — and not every page gets them.
- Where do I put the JSON-LD script?
- Inside the <head> element, or anywhere in the <body>. Google parses both locations. <head> is cleaner and the standard convention. If your CMS only lets you inject into <body>, that works too.
- Do I need to regenerate schema when I update my post?
- Update the `dateModified` field when you make substantive changes. You do not need to change anything else unless the headline, author, URL, or image changed. Rebuilding schema every time you fix a typo is unnecessary.
- Can Google penalize me for bad schema?
- Yes. Deceptive schema (marking up content that isn't actually on the page, fake reviews, etc.) triggers a manual action that suppresses all your rich snippets — sometimes site-wide. Keep it honest.