Correct JSON-LD is valid JSON inside a <script type="application/ld+json"> element. It starts with @context and @type, and it describes only facts that appear on the page. Pick the example below that matches your page, replace every fictional value with your own, add one block, and test the published URL.
Before you paste anything, look at what your theme, SEO plugin or platform already adds to that page. If it already describes the same business, product or article, edit that output instead of adding a second description of the same thing.
Bing Webmaster Tools says Bing supports JSON-LD, so one correct block serves more than one search engine. For AI search, see whether AI systems use schema markup.
Check what the page already outputs
Open the published page, view the source and search for ld+json. Themes, SEO plugins and site builders often print blocks of their own. Yoast SEO's schema settings describe a connected schema graph, and Rank Math's schema templates support custom schema. Squarespace generates structured data for blog posts, events, local businesses, organizations, products and websites, and Shopify's help center says themes may already include structured data such as product information.
If a block already covers the entity, change its values in the plugin, theme or platform settings. Two blocks that describe the same entity differently hand a crawler two sets of facts to choose between. When nothing covers your page, choose the most specific type that fits, such as Restaurant rather than the general LocalBusiness, as Google's local business documentation recommends.
Replace every fictional value
All the examples below use example.com and invented names. Nothing in them is true of your site, so each value needs a replacement from the page itself. Change these in any example:
- Every
example.comURL, including image, logo, video and registration URLs. - Names such as Example Bakery, Example Publishing and Example Goods.
- Addresses, telephone numbers, opening hours, prices, dates, ratings and review counts.
- Authors, publishers, sellers, providers and organizers.
- Social profile URLs, SKUs and other product identifiers.
Google's general structured data guidelines say the markup should represent content visitors can see. A rating, price, event or author that appears only in the code does not belong there. If you also need the steps for installing a block on your site, how to add schema markup to any website covers the routes in order.
The check works well with two people. One reads the page aloud while the other reads the block, and each value either matches the page or gets changed.

Required for a Google feature, recommended, and optional
The word "required" means different things depending on who is asking. Valid JSON syntax is one level. Valid schema.org vocabulary is a second. The requirements of one Google feature are a third, and whether anything is indexed and shown is a fourth. None of these implies the next.
A property can be required for Google's Product snippet and optional in the wider schema.org vocabulary. Types such as Offer, Person, Service and FAQPage are valid schema.org vocabulary even though no Google rich result is attached to them. Google says correct markup does not guarantee a rich result (Google's general structured data guidelines).
Recommended properties are useful when they represent real information, and optional ones add clarity without being necessary. For help choosing among all the types, types of schema markup that matter for search sorts them by purpose.
Organization and LocalBusiness examples
Use Organization for a company, publication or brand with no storefront. Google lists no required properties for Organization markup. Google recommends name, url, logo, sameAs, telephone and address as well (Google's Organization documentation). Replace the @id with your own home page URL followed by #organization, and keep that identifier unchanged wherever you refer to the company later.
{
"@context": "https://schema.org",
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Bakery",
"url": "https://example.com/",
"logo": "https://example.com/images/logo.png",
"sameAs": [
"https://social.example.org/examplebakery",
"https://photos.example.net/examplebakery"
],
"telephone": "+1-555-010-1000",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Example Avenue",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78701",
"addressCountry": "US"
}
}The Organization schema generator builds this block from your own details. A business with a physical location can use a LocalBusiness type. Required for this Google feature: name and address. Recommended: url, telephone, image, geo, openingHoursSpecification and priceRange (Google's local business documentation).
Swap LocalBusiness for a subtype that describes the place, such as Restaurant, Store, Dentist or AutomotiveBusiness. A restaurant can also add servesCuisine. Geographic coordinates should come from a geocoder, not from a guess, and the hours must match the hours printed on the page.
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"@id": "https://example.com/#localbusiness",
"name": "Example Bakery",
"image": "https://example.com/images/storefront.jpg",
"url": "https://example.com/",
"telephone": "+1-555-010-1000",
"priceRange": "$$",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Example Avenue",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78701",
"addressCountry": "US"
},
"geo": {
"@type": "GeoCoordinates",
"latitude": 30.2672,
"longitude": -97.7431
},
"openingHoursSpecification": {
"@type": "OpeningHoursSpecification",
"dayOfWeek": ["Monday", "Tuesday", "Wednesday", "Thursday", "Friday", "Saturday"],
"opens": "07:00",
"closes": "18:00"
}
}The local business schema generator covers the same fields. An online-only publication has no storefront, so Organization is the right type there.
Product and review examples
A product page needs the Product type with facts that match the visible page. Required for this Google feature (Product snippet): name, plus at least one of review, aggregateRating or offers. Recommended: image, description, brand and sku (Google's product snippet documentation).
Price and availability sit inside the nested Offer. Replace the price, currency and availability value with what the product page shows today, and update them whenever the page changes.
{
"@context": "https://schema.org",
"@type": "Product",
"@id": "https://example.com/products/example-mug#product",
"name": "Example Ceramic Mug",
"image": [
"https://example.com/images/mug-front.jpg",
"https://example.com/images/mug-side.jpg"
],
"description": "A fictional 12-ounce ceramic mug.",
"sku": "EX-MUG-001",
"brand": {
"@type": "Brand",
"name": "Example Goods"
},
"offers": {
"@type": "Offer",
"url": "https://example.com/products/example-mug",
"priceCurrency": "USD",
"price": "18.00",
"availability": "https://schema.org/InStock"
}
}Google separates product snippets from merchant listings in its product structured data documentation. Merchant listings use further properties inside offers, such as shippingDetails and itemCondition, and Google recommends gtin and hasMerchantReturnPolicy for them. A standalone Offer and a standalone AggregateRating are valid schema.org types, but Google uses ratings within review snippets and products, not as a separate feature.
Use the product schema generator to fill these fields in. Choose the type from the page's primary subject, so a page about one product takes Product and a page about the company takes Organization.
A Review can mark up a review that visitors can read on the page. Required for this Google feature (Review snippet): author, reviewRating and itemReviewed. Recommended: reviewBody, datePublished and publisher. Do not mark up reviews hidden from visitors, and do not mark up self-serving reviews of your own business, which Google's review guidelines restrict.
{
"@context": "https://schema.org",
"@type": "Review",
"@id": "https://example.com/reviews/example-mug-review#review",
"itemReviewed": {
"@type": "Product",
"name": "Example Ceramic Mug",
"url": "https://example.com/products/example-mug"
},
"author": {
"@type": "Person",
"name": "Jordan Example"
},
"datePublished": "2026-05-21",
"reviewBody": "The fictional mug is sturdy and comfortable to hold.",
"reviewRating": {
"@type": "Rating",
"ratingValue": "5",
"bestRating": "5",
"worstRating": "1"
},
"publisher": {
"@type": "Organization",
"name": "Example Review Journal"
}
}The review schema generator follows the same structure. Replace the reviewer, date, text and rating with a real review that appears on your page, in the same words.
Article and breadcrumb examples
An editorial page takes Article, BlogPosting or NewsArticle. Google treats all three as the Article feature. Google lists no required properties for it. Recommended for this Google feature: headline, image, author, datePublished and dateModified. Optional: publisher and mainEntityOfPage (Google's article documentation).
To switch to a blog post or a news story, change only the @type value and the facts. Set dateModified only when the page really changed. The author here is a Person with a link to an author page, and the person schema generator builds that entity if you want one.
{
"@context": "https://schema.org",
"@type": "Article",
"@id": "https://example.com/articles/example-guide#article",
"headline": "Example Guide to Better Websites",
"image": [
"https://example.com/images/example-guide.jpg"
],
"datePublished": "2026-05-04T09:00:00-05:00",
"dateModified": "2026-05-18T09:00:00-05:00",
"author": {
"@type": "Person",
"name": "Alex Example",
"url": "https://example.com/authors/alex-example"
},
"publisher": {
"@type": "Organization",
"name": "Example Publishing",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/images/logo.png"
}
},
"mainEntityOfPage": "https://example.com/articles/example-guide"
}Try the article schema generator for the same fields. BreadcrumbList describes the path from the home page to the current page. Required for this Google feature: itemListElement, with at least two ListItem objects. Recommended: position, name and item. Google's breadcrumb documentation asks for a typical path a visitor might take, so match the trail your page shows.
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"@id": "https://example.com/blog/example-post#breadcrumb",
"itemListElement": [
{
"@type": "ListItem",
"position": 1,
"name": "Home",
"item": "https://example.com/"
},
{
"@type": "ListItem",
"position": 2,
"name": "Blog",
"item": "https://example.com/blog/"
},
{
"@type": "ListItem",
"position": 3,
"name": "Example Post",
"item": "https://example.com/blog/example-post"
}
]
}The breadcrumb schema generator numbers the positions for you.
FAQPage, Event, VideoObject and Recipe examples
FAQPage is valid schema.org vocabulary for questions and answers that visitors can read on the page. Google stopped showing FAQ rich results in May 2026, so the block does not lead to a search display. Keep it only if you want machine-readable questions that match your visible text. Google also retired HowTo rich results, as its August 2023 announcement describes.
{
"@context": "https://schema.org",
"@type": "FAQPage",
"@id": "https://example.com/example-faq#faq",
"mainEntity": [
{
"@type": "Question",
"name": "What is Example Bakery's fictional delivery area?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Example Bakery delivers within the fictional Example District."
}
},
{
"@type": "Question",
"name": "Does Example Bakery offer fictional gluten-free items?",
"acceptedAnswer": {
"@type": "Answer",
"text": "Yes. Example Bakery offers a fictional gluten-free menu."
}
}
]
}The FAQ schema generator writes the same structure. Each name and text should match a question and answer shown on the page word for word.
An Event needs a date and a place. Required for this Google feature: name, startDate and location. Recommended: endDate, eventStatus, eventAttendanceMode, image, description, offers, performer and organizer (Google's event documentation). For an online event, set eventAttendanceMode to OnlineEventAttendanceMode and use a VirtualLocation with a URL as the location. The event schema generator offers both forms.
{
"@context": "https://schema.org",
"@type": "Event",
"@id": "https://example.com/events/example-workshop#event",
"name": "Example Website Workshop",
"description": "A fictional workshop about building better websites.",
"image": "https://example.com/images/workshop.jpg",
"startDate": "2026-12-05T10:00:00-06:00",
"endDate": "2026-12-05T12:00:00-06:00",
"eventStatus": "https://schema.org/EventScheduled",
"eventAttendanceMode": "https://schema.org/OfflineEventAttendanceMode",
"location": {
"@type": "Place",
"name": "Example Community Hall",
"address": {
"@type": "PostalAddress",
"streetAddress": "500 Example Lane",
"addressLocality": "Austin",
"addressRegion": "TX",
"postalCode": "78705",
"addressCountry": "US"
}
},
"organizer": {
"@type": "Organization",
"name": "Example Academy",
"url": "https://example.com/"
},
"offers": {
"@type": "Offer",
"url": "https://example.com/events/example-workshop",
"price": "25.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
}
}A video page takes VideoObject. Required for this Google feature: name, thumbnailUrl and uploadDate. Recommended: description, contentUrl, embedUrl, duration and expires (Google's video documentation). The duration value uses ISO 8601, so PT8M30S means eight minutes and thirty seconds.
{
"@context": "https://schema.org",
"@type": "VideoObject",
"@id": "https://example.com/videos/example-tutorial#video",
"name": "Example Website Tutorial",
"description": "A fictional tutorial showing how to organize a website.",
"thumbnailUrl": [
"https://example.com/images/example-tutorial-thumbnail.jpg"
],
"uploadDate": "2026-05-04T09:00:00-05:00",
"duration": "PT8M30S",
"contentUrl": "https://cdn.example.com/videos/example-tutorial.mp4",
"embedUrl": "https://example.com/videos/example-tutorial/embed"
}A recipe page takes Recipe. Required for this Google feature: name and image. Recommended: recipeIngredient, recipeInstructions, author, datePublished, description, prepTime, cookTime, totalTime, recipeYield, nutrition, aggregateRating and video (Google's recipe documentation). If you add a rating, include ratingValue and either ratingCount or reviewCount, and only when the page shows real ratings.
{
"@context": "https://schema.org",
"@type": "Recipe",
"@id": "https://example.com/recipes/example-bread#recipe",
"name": "Example Banana Bread",
"image": ["https://example.com/images/banana-bread.jpg"],
"author": {
"@type": "Person",
"name": "Alex Example"
},
"datePublished": "2026-05-06",
"description": "A fictional banana bread recipe.",
"prepTime": "PT15M",
"cookTime": "PT45M",
"totalTime": "PT1H",
"recipeYield": "1 loaf",
"recipeIngredient": [
"3 fictional ripe bananas",
"200 g fictional flour",
"100 g fictional sugar"
],
"recipeInstructions": [
{
"@type": "HowToStep",
"text": "Mash the fictional bananas."
},
{
"@type": "HowToStep",
"text": "Mix the ingredients and bake until done."
}
],
"nutrition": {
"@type": "NutritionInformation",
"calories": "220 calories per slice"
}
}Service and connected graph examples
Service is valid schema.org vocabulary for a service page, and no Google rich result is attached to a generic Service. Useful properties are name, description, serviceType, provider, areaServed and offers. The service schema generator builds it, and the provider should be the same organization you described elsewhere.
{
"@context": "https://schema.org",
"@type": "Service",
"@id": "https://example.com/services/example-consulting#service",
"name": "Example Website Consultation",
"description": "A fictional consultation service for website planning.",
"serviceType": "Website consultation",
"provider": {
"@type": "Organization",
"name": "Example Studio",
"url": "https://example.com/"
},
"areaServed": {
"@type": "AdministrativeArea",
"name": "Example County"
},
"offers": {
"@type": "Offer",
"price": "250.00",
"priceCurrency": "USD",
"availability": "https://schema.org/InStock"
}
}WebSite markup remains useful for site names, according to Google's site name documentation. The sitelinks search box it once powered was removed from Google Search beginning 2024-11-21 (Google Search Central Blog).
When one page describes several related things, put them in one @graph and link them with @id. The block below connects a company, an article it published and the breadcrumb trail. Each item keeps the required properties of its own feature, and publisher points back to the organization with a short {"@id": ...} reference instead of repeating it. The JSON-LD 1.1 specification defines identifiers and graphs, and Google's guidelines allow related items to be connected.

{
"@context": "https://schema.org",
"@graph": [
{
"@type": "Organization",
"@id": "https://example.com/#organization",
"name": "Example Publishing",
"url": "https://example.com/",
"logo": "https://example.com/images/logo.png"
},
{
"@type": "BlogPosting",
"@id": "https://example.com/blog/example-post#article",
"headline": "Example Publishing Guide",
"image": "https://example.com/images/example-post.jpg",
"datePublished": "2026-05-04T09:00:00-05:00",
"dateModified": "2026-05-12T09:00:00-05:00",
"author": { "@type": "Person", "name": "Alex Example" },
"publisher": { "@id": "https://example.com/#organization" },
"mainEntityOfPage": "https://example.com/blog/example-post"
},
{
"@type": "BreadcrumbList",
"@id": "https://example.com/blog/example-post#breadcrumb",
"itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com/" },
{ "@type": "ListItem", "position": 2, "name": "Example Publishing Guide", "item": "https://example.com/blog/example-post" }
]
}
]
}The Schema Graph Builder links entities this way without hand-typing each reference.
Add the block on your platform
Whatever the platform, the finished output is the same script element with the same JSON. Plain HTML takes the block as written, in the head or the body.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Bakery"
}
</script>On WordPress, build the data as a PHP array and let wp_json_encode() turn it into JSON (WordPress developer reference). The JSON_HEX_TAG flag keeps a stray tag inside a value from closing the script early. The snippet below is a starting point for a child theme or a code snippet plugin, so add the other Article properties from the example above before you rely on it, and turn off any duplicate output from your SEO plugin.
add_action( 'wp_head', function () {
if ( ! is_singular( 'post' ) ) {
return;
}
$data = array(
'@context' => 'https://schema.org',
'@type' => 'Article',
'headline' => get_the_title(),
);
echo '<script type="application/ld+json">' . wp_json_encode( $data, JSON_HEX_TAG ) . '</script>';
} );Wix accepts JSON-LD for manual markup and limits each block to 7,000 characters, so a long graph may need splitting. In Webflow, Page Settings hold the schema field; publish the page, then test it. On Squarespace and Shopify, check the automatic output first and add a block only for what the platform leaves out. On HubSpot, follow HubSpot's current documentation or inspect the published page source before adding custom markup.
On Next.js, render the script from layout.js or page.js, and escape the less-than sign in serialized values, as the Next.js JSON-LD guide recommends.
export default function Page() {
const jsonLd = {
'@context': 'https://schema.org',
'@type': 'Article',
headline: 'Example Guide to Better Websites',
};
return (
<script
type="application/ld+json"
dangerouslySetInnerHTML={{
__html: JSON.stringify(jsonLd).replace(/</g, '\\u003c'),
}}
/>
);
}Test the published page
Test in this order. First read the rendered source of the live page and confirm the block is present, appears once per entity and carries your values. Next run Google's Rich Results Test on the published URL. It reads JSON-LD, RDFa and Microdata, and reports errors and suggestions for supported result types.
The Schema Nova validator checks pasted code and the schema checker reads a page address. If a test shows a warning about a missing field, check whether the field is recommended or required for that Google feature before adding anything.
A passing test shows that the markup parses and, for supported features, that it may be eligible. It does not guarantee that Google will show a result. Remove any duplicate block you find, publish again and test again. Google Search Console can then report the structured data it finds on your site over time.
Questions people ask
Where should JSON-LD go in the HTML?
Put the script element in the HTML of the page it describes, in the head or the body. After publishing, view the page source and confirm the block appears in the rendered HTML.
Does valid JSON-LD guarantee a rich result?
No. Google says correct markup does not guarantee a rich result, and a Rich Results Test pass shows eligibility signals, not a promise of display. Valid JSON-LD can still help machines read the page.
Can one page carry more than one schema type?
Yes. A product page can describe a Product, a BreadcrumbList and the Organization behind it. Put related items in one @graph and connect them with @id, and keep each description consistent with the visible page.
Can I use FAQPage markup on a business site?
It is valid schema.org vocabulary for questions and answers that appear on the page. Google stopped showing FAQ rich results in May 2026, so treat the block as machine-readable text, not as a way to get a display.
How do I avoid duplicate markup from a plugin or platform?
View the source of the published page and search for ld+json before adding anything. If a theme, plugin or platform already describes the same entity, edit that output or switch the duplicate off, then test the page again.
