Schema Markup for Beginners: The JSON-LD Worth Adding
Schema markup helps search engines understand your pages and can earn rich results. Here are the JSON-LD types most sites should add first, with examples.

Schema markup is structured data that describes what a page is about in a format search engines can read reliably, and JSON-LD is the format Google recommends for adding it. For most sites, the markup worth adding is Organization (or LocalBusiness) on the home page, Article on blog posts, Product on product pages and BreadcrumbList site-wide. It can make pages eligible for rich results, but it does not guarantee them and Google does not treat it as a direct ranking boost.
Key takeaways
- Use JSON-LD in a script block; it is easier to maintain than microdata or RDFa and is Google's recommended format.
- Only mark up content that is actually visible on the page.
- Start with Organization or LocalBusiness, Article, Product and BreadcrumbList.
- Skip types Google has restricted or retired for rich results unless you have another reason to use them.
- Validate with Google's Rich Results Test and the Schema.org validator, then monitor Search Console.
What schema markup actually does
Search engines are good at reading text, but they still have to guess some things: is "19.99" a price, is "Jane Doe" the author, is this page a recipe or a review of a recipe? Schema.org vocabulary removes the guesswork by labeling those facts explicitly.
In practice it does three useful things:
- Rich result eligibility. Product prices and ratings, breadcrumbs, recipe details, event dates and similar enhancements in Google results rely on structured data.
- Entity clarity. Organization markup helps connect your site to your brand name, logo and official profiles.
- Machine readability in general. Other search engines and systems that parse pages can use the same data.
What it does not do: make a weak page rank, or force Google to show a rich result. Google decides whether to display an enhancement based on its own criteria, and eligibility is all you can control.
Why JSON-LD instead of microdata
There are three syntaxes for schema.org markup: JSON-LD, microdata and RDFa. Microdata and RDFa are woven into your HTML attributes, so a template change can silently break them. JSON-LD sits in its own script block, usually in the head, which makes it easy to read, generate from a CMS and debug. Google supports all three but recommends JSON-LD where your setup allows it.
A JSON-LD block looks like this in your page source (shown escaped here):
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Organization",
"name": "Example Co",
"url": "https://www.example.com/",
"logo": "https://www.example.com/images/logo.png",
"sameAs": [
"https://www.linkedin.com/company/example-co",
"https://www.youtube.com/@exampleco"
]
}
</script>
The four types worth adding first
1. Organization or LocalBusiness (home page)
Use Organization for online businesses and publishers. Use LocalBusiness, or a more specific subtype such as Dentist, Restaurant or Plumber, if customers visit you or you serve a defined area. LocalBusiness adds address, phone and opening hours:
{
"@context": "https://schema.org",
"@type": "Plumber",
"name": "Example Plumbing",
"url": "https://www.example.com/",
"telephone": "+1-555-010-0199",
"address": {
"@type": "PostalAddress",
"streetAddress": "100 Main St",
"addressLocality": "Springfield",
"addressRegion": "IL",
"postalCode": "62701",
"addressCountry": "US"
},
"openingHours": "Mo-Fr 08:00-18:00"
}
Keep these details identical to your Google Business Profile and your contact page. Inconsistent phone numbers or addresses across the web are a common local SEO problem.
2. Article or BlogPosting (posts and news)
Article markup helps Google understand the headline, dates, author and images. The fields that matter most are accurate dates and a real author:
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to Fix a Slow Drain",
"datePublished": "2026-10-01T09:00:00-05:00",
"dateModified": "2026-10-20T14:30:00-05:00",
"author": {
"@type": "Person",
"name": "Jane Doe",
"url": "https://www.example.com/about/jane-doe"
},
"image": "https://www.example.com/images/slow-drain.jpg",
"publisher": {
"@type": "Organization",
"name": "Example Plumbing"
}
}
Only change dateModified when the content meaningfully changes. Bumping it on every deploy without real edits is misleading and easy to spot.
3. Product (product pages)
Product markup with an Offer can make a page eligible for price, availability and review information in results. Include name, image, and an offers object with price, priceCurrency and availability. Add aggregateRating only if the ratings are genuine and shown on the page. Google's guidelines do not allow self-serving review markup for your own business on LocalBusiness or Organization pages.
4. BreadcrumbList (site-wide)
Breadcrumb markup describes where a page sits in your site hierarchy, which Google can use to display the path in results. It is easy to generate from your navigation and low risk:
{
"@context": "https://schema.org",
"@type": "BreadcrumbList",
"itemListElement": [
{"@type": "ListItem", "position": 1, "name": "Blog", "item": "https://www.example.com/blog/"},
{"@type": "ListItem", "position": 2, "name": "Plumbing tips", "item": "https://www.example.com/blog/plumbing/"},
{"@type": "ListItem", "position": 3, "name": "How to fix a slow drain"}
]
}
Types to think twice about
Google has narrowed or dropped several rich result types over the years, so check the current documentation before investing time:
- FAQPage: since 2023, FAQ rich results are shown only for well-known, authoritative government and health sites. The markup is still valid schema.org, but most sites will not get the visual enhancement.
- HowTo: HowTo rich results were deprecated in 2023.
- Sitelinks search box: Google stopped showing this feature in late 2024, so WebSite SearchAction markup no longer triggers it.
Leaving valid markup in place does no harm, but do not expect a visual result from these. Google's structured data search gallery lists the features it currently supports.
Rules that keep you out of trouble
- Mark up what users can see. Prices, ratings, authors and FAQs in your markup must match the visible page. Hidden or invented data can lead to a manual action for spammy structured data.
- Be specific. Use the most specific type that fits (BlogPosting, Plumber) rather than a generic Thing.
- Use absolute URLs for
url,imageandlogo. - Use ISO 8601 dates with a time zone, as in the examples above.
- One source of truth. If a plugin and your theme both output Organization markup, you may end up with conflicting duplicates. Pick one.
How to check your markup
- View what is actually served. Plugins and tag managers sometimes inject markup you did not know about, or fail to inject it at all. Use Get Source Code of Webpage to see the raw HTML and search for
application/ld+json. - Test for Google features with the Rich Results Test, which reports which rich results a page is eligible for and any errors or warnings.
- Validate the vocabulary with the Schema Markup Validator at validator.schema.org, which checks against schema.org itself rather than Google's subset.
- Monitor at scale in Search Console, where the enhancement reports list valid items and errors across the site.
While you are in the source, check the basics too. Structured data complements, but does not replace, a good title tag and meta description; a Meta Tags Analyzer shows both in one pass.
Common mistakes
- Copying a JSON-LD example and forgetting to replace placeholder values.
- Invalid JSON: trailing commas and smart quotes pasted from a word processor break the whole block.
- Adding review stars to every page in the hope that they appear.
- Marking up content on one URL that only exists on another.
- Expecting a ranking jump after adding markup to thin pages.
Next steps
- Add Organization or LocalBusiness markup to your home page.
- Configure your CMS or SEO plugin to output Article and BreadcrumbList on posts.
- Add Product markup with accurate offers to product pages.
- Test a sample of each template in the Rich Results Test.
- Check Search Console enhancement reports after Google recrawls the pages.