FAQ schema can earn rich FAQ snippets in Google. Limit to 5–8 most-asked questions per page for the best result.
A short, practical explanation — no jargon.
Schema markup (also called structured data) is code added to your website's HTML that describes its content to search engines in a standardised vocabulary defined at schema.org. Think of it as labelling: instead of leaving Google to guess that "$49.99" on your page is a product price, you explicitly tell it via schema. Instead of letting Google interpret a list of questions as just text, you label it as an FAQ.
Google, Bing, Yandex, and other search engines use this structured information to display rich results directly in the search listing — star ratings, prices, FAQ accordions, event dates, recipe images, breadcrumb trails, and much more. Pages with rich results take up more space in search results, look more credible, and get measurably higher click-through rates than plain results in the same position.
Three formats are supported: JSON-LD, Microdata, and RDFa. Google explicitly recommends JSON-LD because it lives in a single script tag in your page head, separate from the visible HTML. That makes it easy to add, easy to maintain, and impossible to break the page layout. This generator outputs JSON-LD only.
Not every schema type produces a visible enhancement in search results. Here's what actually pays off.
| Schema Type | Rich Result? | Use When |
|---|---|---|
| FAQPage | Yes — FAQ accordion | You have a real FAQ section with 3+ questions answered on the page |
| Article / NewsArticle / BlogPosting | Yes — Top Stories carousel, dates, author | Blog posts, news articles, editorial content |
| Product | Yes — Price, availability, ratings | E-commerce product pages with price and stock data |
| Review / AggregateRating | Yes — Star ratings | Reviews of products, books, businesses, software, events |
| LocalBusiness | Yes — Knowledge panel, map results | Any business with a physical location and serving area |
| Recipe | Yes — Recipe carousel | Cooking recipes with ingredients, instructions, and ratings |
| Event | Yes — Date, location, ticket panel | Concerts, conferences, classes, online events |
| VideoObject | Yes — Video carousel | Embedded videos that are key content of the page |
| BreadcrumbList | Yes — Breadcrumb display | Any page deeper than the homepage in your site hierarchy |
| HowTo | Reduced in 2024 | Step-by-step tutorials — Google still crawls but rarely shows rich results now |
| Organization | Knowledge graph signal | Homepage of any business — feeds Google's knowledge panel |
| Person | Knowledge graph signal | Author bios, About pages — supports E-E-A-T |
The top six in this table — FAQ, Article, Product, Review, LocalBusiness, and Event — produce the most visible CTR lift. The bottom three don't trigger flashy rich results but support Google's understanding of your site, which strengthens E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) signals — especially important for affiliate, financial, and health content.
Three ways, ranked by ease.
1. WordPress with an SEO plugin (easiest): If you use RankMath or Yoast, common schema types (Article, Product, BreadcrumbList, Organization) are added automatically based on your post type and settings. RankMath also includes a custom schema builder for less common types. You usually don't need this generator at all if you're using RankMath — but it's still useful for non-WordPress pages or specialised schemas.
2. Manual paste (universal): Use this generator to build the JSON-LD, then paste it inside the page <head> wrapped in a <script type="application/ld+json"> tag. This works on any platform — Webflow, Squarespace, custom HTML, static site generators. Just paste, save, deploy.
3. Tag manager (for non-developers): Use Google Tag Manager to inject schema markup as a Custom HTML tag firing on specific page paths. Useful if you can't access your site's HTML directly. Note that Google does process tag-manager-injected schema, but on rare occasions it can take longer to be picked up than schema in the source HTML.
After adding schema, always validate it:
All five are easy to avoid once you know to check for them.
1. Marking up content that isn't visible to users. Google penalises sites that include FAQ, Review, or Product schema for content that doesn't actually appear on the page. If your FAQ schema has five questions but only three are visible, Google will flag it as deceptive markup and may issue a manual action. Rule: schema describes what's on the page, not wishful thinking.
2. Fake or self-generated reviews. Adding Review/AggregateRating schema with star ratings you made up is one of the fastest ways to get a manual penalty. Reviews must be genuine first-party reviews on your site or from a recognised review platform. Don't add five-star Review schema "just because."
3. Marking up irrelevant content as the main entity. If your Article schema's headline doesn't match the actual H1 of the page, or your Product schema's name differs from the visible product title, Google ignores the schema or flags it. Keep them consistent.
4. Missing required properties. Each schema type has required fields (Product needs name + offers; Recipe needs name + recipeIngredient + recipeInstructions; Event needs name + startDate + location). Skipping required fields prevents rich results entirely. This generator includes all required fields by default — don't delete them.
5. Forgetting to update schema when content changes. If your Product schema says price $49 but the visible price is now $69, your schema is out of date and Google may stop honouring it. For any frequently-changing data (price, stock, ratings, dates), make sure your schema updates automatically when the underlying data does.
This generator builds one schema at a time. The tools below add schema to entire WordPress sites automatically — no copy-pasting required. They also handle dynamic content (prices, ratings, stock) so your schema stays accurate as data changes.
Schema markup (also called structured data) is code added to your website's HTML that describes its content to search engines in a standardised vocabulary defined at schema.org. Google, Bing, and other search engines use this data to display rich results — star ratings, prices, FAQs, event dates, recipe images, and more — directly in search results.
Google explicitly recommends JSON-LD (JavaScript Object Notation for Linked Data) as the preferred format for schema markup. JSON-LD is added inside a single script tag in the page head and does not require modifying the visible HTML, making it easier to maintain than Microdata or RDFa formats.
The most common schema types that trigger rich results in 2026 are: FAQ (FAQ rich snippets), Article (top stories carousel), Product (price, rating, availability), Recipe (recipe carousel), HowTo (step-by-step displays, though Google has reduced these), Event (event details panel), LocalBusiness (knowledge panel data), Review (star ratings), Video (video carousels), and BreadcrumbList (breadcrumb display in SERPs).
Generate the JSON-LD code with this tool, then paste it inside a <script type="application/ld+json"> tag in the head section of your page. On WordPress, plugins like RankMath or Yoast SEO add common schema types automatically, but custom schemas still need manual implementation. After adding schema, test it with Google's Rich Results Test or the schema.org validator.
Schema markup is not a direct ranking factor, but it indirectly helps in two ways: rich results increase your click-through rate from search results (often 20–30% higher CTR), and structured data helps Google understand your content better, which improves topical relevance signals. The biggest impact is on CTR, not ranking position itself.
Use Google's Rich Results Test (search.google.com/test/rich-results) for the most accurate check of which rich results your schema is eligible for. Use the schema.org validator (validator.schema.org) for syntax-level validation against the full schema vocabulary. Both are free. After deploying, also check Google Search Console under Enhancements for any structured data warnings or errors.
Yes. You can include multiple JSON-LD blocks on a single page, and they should describe different aspects of the page. For example, an article page might include Article schema for the post itself, BreadcrumbList for navigation, Person schema for the author, Organization schema for the publisher, and FAQPage if there is an FAQ section. Each schema goes in its own script tag.