Skip to content
SEO and AI search

Schema Markup Generator

Pick a Schema.org type, fill in a short form, and copy a ready JSON-LD script tag, with checks for the fields Google requires or recommends.

Last checked

Schema type

Blog posts and news. Google has no required fields; the recommended ones help it read the title, image, dates and author.

Article details

Recommended
Recommended
Recommended
Recommended
Recommended
Recommended

JSON-LD

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to size an Open Graph image",
  "image": "https://example.com/og/cover.png",
  "datePublished": "2026-10-01",
  "dateModified": "2026-10-18",
  "author": [
    {
      "@type": "Person",
      "name": "Jane Doe",
      "url": "https://example.com/about/"
    }
  ],
  "publisher": {
    "@type": "Organization",
    "name": "Example Studio"
  }
}
</script>
  • OKRequired and recommended fields are filled in.
Schema Markup Validator

The test page has no way to receive code in a link, so the button copies the script first; paste it into the Code tab.

Search preview Approximation

A rough sketch of how Google could show the Article item, not Google's real layout. Google decides whether to show any rich result.

Example Studiohttps://example.com

How to size an Open Graph image

Oct 1, 2026 — By Jane Doe. The description comes from the page's meta description or its text, not from the markup.

Google picks the date, image and title it shows; it can use other parts of the page and may show none of them.

Validate existing JSON-LD

  • Paste the JSON-LD from any page to check it
  • Every object in a @graph or array is checked
  • Edit in generator loads known types into the form

How to use it

  1. Choose the type that matches what the page is: Article for a post, Product for a product page, Local business for a place people visit, Event, Recipe, Video or Software app for those pages, Breadcrumbs for the path, Organization or WebSite for the home page.
  2. Fill in the fields. Lists take one item per line; FAQ and breadcrumbs take Question | Answer or Name | URL. Empty fields are left out of the output. The preview under the form sketches how the result could look.
  3. To describe more than one thing on the page, press Add another item: the current item is saved and the script switches to a single @graph that holds them all.
  4. To check markup a page already has, paste its JSON-LD or HTML into Validate existing JSON-LD, read the checks per item, and press Edit in generator to fix it in the form.
  5. Copy the script tag into the page, keep it in line with what the page shows, and test the URL with Google's Rich Results Test or the Schema Markup Validator.

What it checks and why

JSON-LD is the structured data format Google recommends. It sits in a script tag of type application/ld+json and describes the page with Schema.org types, so search engines can read who wrote an article, when it changed, what the breadcrumb path is, or which organization runs a site.

Google lists no required properties for Article; headline, image, datePublished, dateModified and author are recommended. BreadcrumbList needs a name and a position for each item and a URL for every item but the last. FAQPage needs each question with its accepted answer. Since August 2023 Google shows FAQ rich results only for well-known government and health sites, so for most sites FAQ markup no longer earns a rich result in Google.

Google retired the sitelinks search box worldwide on 21 November 2024, so a SearchAction in WebSite markup no longer adds a search field to results. Google says leftover markup causes no errors; the tool leaves it out. WebSite markup still feeds the site name Google shows above the URL.

For the rich result types the tool follows Google's feature docs. Product snippets need a name plus offers, a review or an aggregate rating. LocalBusiness needs a name and an address; geo (at least 5 decimal places), opening hours, phone and URL are recommended. Event needs a name, a startDate and a location with a name and address. Recipe needs a name and an image, and calories need recipeYield. VideoObject needs a name, thumbnailUrl and uploadDate. SoftwareApplication needs a name, offers.price (0 for free) and a rating or review. JobPosting needs a title, an HTML description, datePosted, hiringOrganization and jobLocation; a fully remote job uses jobLocationType TELECOMMUTE and lists the countries applicants may live in with applicantLocationRequirements. An aggregate rating needs ratingValue plus ratingCount or reviewCount.

Google's current event docs do not list eventAttendanceMode; it is a Schema.org property, and the tool writes it when you pick one. For an online-only event it writes a VirtualLocation with the join URL and warns that Google's event docs describe venues with an address.

Markup has to match the visible page. Google's structured data guidelines say not to mark up content that readers cannot see, and a page with misleading markup can lose rich result eligibility.

Specs and sources

Limits

  • It covers thirteen common types and their main properties, not every Schema.org type or property (no Course, merchant listing shipping and returns, or nested Recipe video yet). The validator lists the properties of other types but has no form for them.
  • Product, Recipe and SoftwareApplication take one aggregate rating and Product one review; more reviews, AggregateOffer and pros and cons need hand editing.
  • Valid markup does not guarantee a rich result. Google decides what to show, and some types have no rich result at all.
  • The search preview is an approximation drawn in the page, not Google's real layout, and it never loads your images.
  • It does not fetch or test a live URL: paste the page's HTML instead, or use the Rich Results Test or the Schema Markup Validator.

Questions

What is schema markup?
Structured data, usually JSON-LD, that describes a page with Schema.org types such as Article or Organization, so search engines can understand its content and show rich results.
Where do I put JSON-LD on a page?
In a script tag with type application/ld+json, in the head or the body. Google reads both. Add one script per item, or combine several items in an array.
Does FAQ schema still work?
Since August 2023 Google shows FAQ rich results only for well-known government and health sites. The markup is still valid Schema.org, and other systems can read it.
Does HowTo schema still work?
Not in Google. Google stopped showing HowTo rich results on mobile in August 2023 and on desktop on 13 September 2023, and calls the type deprecated. That is why this tool has no HowTo form; the markup is still valid Schema.org.
What does JobPosting schema need?
Google requires title, description (HTML), datePosted, hiringOrganization and jobLocation. For a fully remote job, set jobLocationType to TELECOMMUTE and list the countries applicants may live in. validThrough, employmentType, baseSalary, directApply and identifier are recommended.
How do I test schema markup?
Paste the code or the page HTML into Validate existing JSON-LD for field checks here, then paste the page URL or the code into Google's Rich Results Test to see which rich results it can get, or into the Schema Markup Validator to check it against Schema.org.
Can I put several schema types on one page?
Yes. Use one script per item, or one script whose @graph array holds all of them under a single @context. Every item should describe something the page actually shows.
What fields does Product schema need?
Google's product snippet docs require a name and at least one of offers, review or aggregateRating. An offer needs a price; priceCurrency and availability are recommended. An aggregate rating needs ratingValue and ratingCount or reviewCount.
How do I write cook time in recipe schema?
As an ISO 8601 duration such as PT30M for 30 minutes or PT1H15M for 1 hour 15 minutes. Google asks to use cookTime together with prepTime, or totalTime on its own. Type 1h 15m in the tool and it writes the ISO form.
What date format does schema markup use?
ISO 8601: 2026-10-21 for a date, or 2026-10-21T09:00:00+02:00 for a date and time. Google recommends adding the time zone; without it Google uses Googlebot's time zone.
Is the sitelinks search box markup still needed?
No. Google stopped showing the sitelinks search box on 21 November 2024. Existing SearchAction markup does no harm, but it no longer changes the result.
Is JSON-LD better than Microdata?
Google supports JSON-LD, Microdata and RDFa and recommends JSON-LD because it is the easiest to add and maintain: it sits in one block and does not change the visible HTML.