Schema markup is structured data code you add to a page so machines can read what the content means, not just what it says. The vocabulary comes from Schema.org, a project the major search engines maintain together, and Google uses it to power rich results like star ratings, prices, and event dates. The word "Avatar" could be a film, a profile picture, or a spiritual concept; schema is how you remove the guesswork. In 2026 the audience for that clarity includes AI engines deciding whom to cite, not just search crawlers deciding what to rank.
The short version
- Schema markup describes your content to search engines and AI systems.
- It is not a ranking factor. It earns richer listings and better understanding.
- Use JSON-LD, validate before shipping, and mark up only visible content.
- Some rich results have been retired, so aim at the types that still pay.
The types worth adding in 2026
- Article and BlogPosting for editorial content: headline, author, dates, image.
- Product for ecommerce, feeding price, availability, and ratings into shopping-eligible listings. The highest-impact type on any store.
- LocalBusiness for physical locations: address, phone, hours, service area.
- Organization for the company itself, supporting Knowledge Panel eligibility and entity recognition.
- BreadcrumbList to show your site hierarchy in listings.
- Review where genuine reviews exist. Fabricated ratings are a manual-action magnet.
- VideoObject, Event, Recipe where that content genuinely lives on the page.
Two honest corrections to what older articles promise, this one's previous version included. Google retired HowTo rich results in 2023, and since the same year FAQ rich results display only for well-known government and health sites. FAQPage markup still helps machines parse your questions and answers, but the dropdown in the listing is gone for most sites, so stop choosing schema types for a visual reward that no longer exists.
Why JSON-LD won the format war
Schema can be written as JSON-LD, Microdata, or RDFa. JSON-LD sits in a single script tag in the head, separate from your visible HTML, so it cannot break your layout and stays easy to edit and validate. Microdata and RDFa weave attributes through the markup itself, which is exactly as pleasant to maintain as it sounds. Google recommends JSON-LD, and there is no modern reason to pick anything else.
How to add schema to a blog post
Blog posts are the best first project because one template covers every post. Here is the walkthrough we used to publish separately, folded in where it belongs.
-
Gather the post's facts
Headline, author name, publish and modified dates, featured image URL, publisher name, and the post's canonical URL.
-
Build the JSON-LD block
Start from the template below. BlogPosting is the specific subtype; Article works identically for Google's purposes.
-
Add it to the page head
Hand-coded sites paste the script tag into the template. WordPress users get Article schema generated automatically by Yoast or Rank Math, which is worth checking before writing any code.
-
Validate before publishing
Run the URL through Google's Rich Results Test and the Schema.org validator. Syntax errors kill the whole block silently.
-
Watch Search Console
The enhancements reports flag structured data errors across the site and confirm when rich results start appearing.
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "Your Post Title",
"image": "https://example.com/featured.jpg",
"datePublished": "2026-01-11",
"dateModified": "2026-07-27",
"author": { "@type": "Person", "name": "Author Name" },
"publisher": { "@type": "Organization", "name": "Company Name" },
"mainEntityOfPage": "https://example.com/blog/your-post/"
}
</script>A LocalBusiness example for comparison
{
"@context": "https://schema.org",
"@type": "LocalBusiness",
"name": "Business Name",
"telephone": "+1-555-555-5555",
"address": {
"@type": "PostalAddress",
"streetAddress": "123 Main Street",
"addressLocality": "City",
"addressRegion": "State",
"postalCode": "12345",
"addressCountry": "US"
},
"priceRange": "$$"
}The pattern is the same for every type: name the type, fill its properties with facts that appear on the page, nothing more.
The mistakes that cost sites their rich results
- Marking up content that is not visible on the page, which violates Google's guidelines outright.
- Fake reviews and inflated ratings, the fastest route to a manual action.
- The wrong type for the content, like a service page marked as an Article.
- Missing required properties, which makes the type ineligible rather than partially eligible.
- One missing comma, because JSON fails as a block, not a line.
- Never validating, so all of the above ships unnoticed.
Why schema matters more as AI reads the web
Structured data is also how you state who wrote your content and what entity stands behind it, which feeds the experience and trust signals Google evaluates. Person schema ties authors to their credentials, Organization schema ties the site to a real company. The same clarity serves AI engines choosing sources to cite, which is the territory of generative engine optimization, and it is one reason we treat schema as standing infrastructure. On our own builds it is generated per template as part of technical SEO, so it can never drift from the visible content.
Questions people ask about schema markup
Does schema markup directly improve rankings?
No. Google has confirmed structured data is not a ranking factor. The payoff comes from richer listings that win more clicks, from search engines understanding your content correctly, and from AI systems citing you accurately.
Which schema format should I use?
JSON-LD, in every new build. It lives in a script tag separate from your visible HTML, which makes it easier to add, maintain, and validate, and it is the format Google explicitly recommends. Microdata and RDFa still work but offer nothing extra.
What schema type should a blog post use?
Article or BlogPosting. BlogPosting is the more specific subtype and Google treats the two essentially the same, so either is fine. NewsArticle is only for actual time-sensitive news.
Can I use several schema types on one page?
Yes, and most real pages should. A post typically carries BlogPosting plus BreadcrumbList, and a product page might carry Product, Review, and Organization. Bundle them in one graph and make sure each type describes content actually on the page.
How long until schema shows up in search results?
Google has to recrawl and revalidate the page first, which usually takes days to a few weeks. Valid markup makes you eligible for rich results; it never guarantees them. Google decides per query.
