Updated · Built and checked by the PlinzoTools team, formulas tested against published sources
Generate JSON-LD schema markup for Article, FAQ, How-To, Product, Local Business, Organization and Breadcrumbs, checked against Google's requirements.
Ready to paste
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to Proof Sourdough at Home",
"image": [
"https://example.com/images/sourdough.jpg"
],
"datePublished": "2026-03-01",
"author": {
"@type": "Person",
"name": "Sam Lee"
},
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/blog/proof-sourdough"
}
}
</script>Schema markup is structured data, written in the schema.org vocabulary, that tells search engines exactly what a page is about: an article with an author and a date, a product with a price, a business with an address and opening hours. This tool builds that markup as JSON-LD -- the format Google recommends -- for seven common types: Article, FAQ Page, How-To, Product, Local Business, Organization and Breadcrumbs. Pick a type, fill in the fields, and copy clean, ready-to-paste code. As you type, each field is checked against Google's documented required and recommended properties.
Choose a schema type from the menu. The form changes to show that type's fields, filled in with an example so you can see the shape of the output; replace the sample values with your own. Anything you leave empty is left out of the code rather than written as an empty value. Errors (missing required fields, malformed URLs or dates) and recommendations appear above the code. When the status line reads "Ready to paste", copy the code or download it. Untick "Wrap in a script tag" if your CMS or plugin asks for the raw JSON only.
| Type | Use it for | Google rich result today |
|---|---|---|
| Article | Blog posts, news stories, guides (choose Article, BlogPosting or NewsArticle) | Yes -- a better title, image and date display in results and Discover |
| Product | A page selling one specific product | Yes -- price and availability in results and Google Shopping surfaces |
| Local Business | A business with a physical location customers visit | Supports business details in Search and Maps |
| Organization | Your company's home or About page | Supports logo and company details in knowledge panels |
| Breadcrumbs | Any page with a category trail | On desktop -- the trail replaces the raw URL (Google stopped showing it on mobile in 2025) |
| FAQ Page | A page of questions and answers written by the site | Only for well-known government and health websites (since 2023) |
| How-To | Step-by-step instructions | No longer shown by Google (since 2023) |
FAQ Page and How-To are still valid schema.org types. Other search engines and AI systems can read them, and they don't hurt anything, but most sites shouldn't expect them to produce a special Google result. The tool shows this notice when you select either type.
Errors are things Google requires before the markup can qualify for a rich result -- a headline for an Article, a name and an address for a Local Business, a price and currency for a Product -- or values in the wrong format. Recommendations are properties Google says improve the result, such as an image or a publish date. Fix every error; add recommendations whenever you have genuine values for them.
The Article form opens with a sample blog post: the headline "How to Proof Sourdough at Home", its URL, one image, a publish date of 2026-03-01 and the author Sam Lee. Every required and recommended field is filled, so the status reads "Ready to paste". The output contains @context and @type, the headline, the image as a one-item list, the date, an author object of type Person, and mainEntityOfPage pointing at the article's URL. The optional description, modified date and publisher were left empty, so they don't appear at all.
Mo-Fr 09:00-17:00 or Sa,Su 10:00-14:00. Each line becomes a structured OpeningHoursSpecification with full day names.Name | URL, numbered automatically. Only the last crumb, the current page, may leave its URL off.Star ratings in markup must come from genuine reviews that visitors can see on the same page. Google also doesn't show review stars for reviews a business publishes about itself (LocalBusiness and Organization). A field that invites typing in "4.8 stars from 120 reviews" mostly produces markup that breaks those rules and can lead to a manual action. So this tool leaves ratings out entirely. A Product still qualifies through its offer, its price and availability. If you collect real reviews, add aggregateRating using the actual numbers from your review system.
Paste the script tag into the page's HTML -- inside <head> or anywhere in <body>; both work. In WordPress, use your SEO plugin's custom schema field or a header-code plugin. Then test the live URL in Google's Rich Results Test, which shows which rich results the page is eligible for, and in the Schema Markup Validator at validator.schema.org, which checks the vocabulary itself. After launch, Google Search Console's enhancement reports flag errors across the site.
Three rules matter more than any single property. The markup must describe what is actually visible on the page. It must be about that page, not the whole site (Organization markup belongs on the home or About page, not every post). And if your CMS or SEO plugin already outputs schema, extend that rather than adding a second, competing block of the same type.
Any < character in your text is written as a Unicode escape. The JSON means exactly the same thing, but a value such as "</script>" can't accidentally close the script tag and break the page.
To sanity-check markup you already have, paste it into the Structured Data (JSON-LD) Validator. To complete the rest of a page's head, use the Meta Tags Generator & Analyzer.
Not directly. Google has said structured data isn't a general ranking factor. What it does is make a page eligible for rich results -- prices, breadcrumbs, article images -- which can make the listing more useful and more likely to be clicked.
All three are supported, but Google recommends JSON-LD because it sits in one block, separate from the visible HTML, which makes it easier to add, read and maintain.
No. Valid markup makes a page eligible, but Google decides whether to show a rich result based on the query, the page's quality and its own policies.
Yes. A blog post can carry Article and BreadcrumbList markup, for example. Generate each type separately and paste both script tags, or combine them into one array of objects.
Since August 2023, Google shows FAQ rich results only for well-known, authoritative government and health websites. For other sites the markup is still valid, but the dropdowns won't appear.
A plain date is accepted. A full date-time with a timezone, such as 2026-03-01T09:00:00+00:00, is more precise and is what Google recommends when you know the exact time.
Reference: Google Search Central