Two articles. Same topic. Same search intent. Similar content quality.
One shows up in Google with star ratings, a publication date, an author name, and an FAQ section that expands directly in the search results — before the user has clicked anything.
The other shows a URL, a title, and a meta description. Standard issue. Invisible by comparison.
Both are on the first page. But one is visually twice the size of the other. One has social proof baked directly into the listing. One gives users information before they even arrive.
Which one gets the click?
This is what structured data does. It doesn’t just tell Google what your page is about — it tells Google what kind of page it is, what specific entities appear on it, and how to display it as a rich result in ways that make your listing stand out from everything around it.
The technology is not new. The adoption is still surprisingly low. Which means right now, implementing it correctly is still a genuine competitive advantage.
Table of Contents
What Is Structured Data?
When you write content, you’re communicating with humans. Humans understand context, implication, and meaning. When you write “Subu has been doing SEO since 2012,” a human reader understands that Subu is a person, that SEO is a professional field, and that 2012 marks the beginning of a career.
Google’s crawlers are improving at understanding natural language — but they’re not humans. They read code and infer meaning from signals. The more explicitly you communicate what things are, the more confidently Google can classify, display, and rank your content.
Structured data is a standardised way of communicating that explicit information to search engines. Instead of writing about a recipe and hoping Google figures out it’s a recipe — you tell Google directly: “This is a recipe. The name is X. The ingredients are these. The cook time is 45 minutes. The calorie count is this. The author is this person.”
Google now knows exactly what it’s looking at. And it can do far more interesting things with the listing as a result.
What Is Schema Markup?
Schema markup is the specific vocabulary used to implement structured data. It’s a shared standard created and maintained by Schema.org — a collaborative project involving Google, Bing, Yahoo, and Yandex.
Schema.org defines hundreds of entity types — Person, Organisation, Article, Product, Recipe, Event, LocalBusiness, FAQPage, HowTo, and many more — and the specific properties each entity can have.
The most common implementation format today is JSON-LD (JavaScript Object Notation for Linked Data). It’s a block of code added to the <head> of your page — separate from your visible content — that describes the page’s entities in a machine-readable format.
A simple Article schema looks like this:
json<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Your Article Title Here",
"author": {
"@type": "Person",
"name": "Subu"
},
"datePublished": "2026-04-09",
"publisher": {
"@type": "Organisation",
"name": "SEO by Subu"
}
}
</script>
Google reads this, understands the page is an Article, knows who wrote it, knows when it was published, and knows which organisation published it — all from structured, explicit code rather than inferred from content.
What Rich Results Actually Look Like
Here’s what schema markup can unlock in Google search results:
FAQ Rich Results — accordion-style questions and answers that expand directly in the SERP, below your main listing. Users get answers before clicking. Your listing takes up significantly more vertical space than standard results. Click-through rates on FAQ-enhanced listings are typically higher — both from the extra space and from the pre-click engagement.
Star Ratings (Review Rich Results) — gold stars below your title and URL, with an average rating and review count. For product pages, service pages, and local businesses, these are trust signals that directly impact click-through rate.
Article Rich Results — enhanced article listings showing publication date, author, and publisher logo. Particularly prominent in Google Discover and Top Stories.
Product Rich Results — price, availability (in stock / out of stock), and review stars directly in the search result. For e-commerce, this information changes purchase intent before a user has visited the page.
How-To Rich Results — step-by-step instructions displayed directly in search results, including images per step.
Event Rich Results — event name, date, location, and ticket availability surfaced in search and Google Events.
Breadcrumb Rich Results — your URL replaced with a navigational breadcrumb trail showing page hierarchy. Cleaner, more informative, and typically preferred by users over raw URL strings.
Sitelinks Searchbox — a search bar appearing directly beneath your brand name in branded searches, allowing users to search your site from the SERP.
Not all schema types guarantee rich results — Google decides whether to display them based on page quality, relevance, and its own discretion. But correctly implemented schema gives Google the option. Without it, the option doesn’t exist.
The Schema Types That Matter Most for SEO
Article / BlogPosting — for all editorial content. Establishes the piece as a formal publication with an author, date, and publisher. Directly supports E-E-A-T signals by making authorship explicit and machine-readable.
FAQPage — marks up question-and-answer content. One of the highest-value schema implementations for most content sites because the visual impact in search results is immediate and significant.
Product — for e-commerce. Name, description, price, currency, availability, aggregate rating. Essential for any site selling products online.
LocalBusiness — name, address, phone number, opening hours, geo coordinates, price range. Critical for local SEO. Directly feeds into Google’s understanding of your business entity.
Person — name, job title, affiliation, social profiles. Used for author markup on articles and for the primary subject of personal brand websites. Supports E-E-A-T by establishing the author as a real, identifiable person with credentials.
BreadcrumbList — your page hierarchy expressed as a structured list. Replaces the ugly URL in search results with a clean navigation path.
HowTo — for instructional content with discrete steps. Eligible for the step-by-step rich result display.
VideoObject — for pages featuring video content. Name, description, thumbnail, upload date, duration. Enables video rich results and increases visibility in video search.
Review / AggregateRating — structured review data. Must be a genuine review of a specific item — Google explicitly prohibits using Review schema on self-promotional content.
How to Implement Schema Markup
There are three main approaches, in order of elegance:
Method 1: JSON-LD in the <head> (Recommended)
Add a <script type="application/ld+json"> block directly in your page’s <head> section. This is Google’s preferred method. It’s clean, maintainable, and completely separate from your visible page content — so changes to the schema don’t risk changing what users see.
Method 2: WordPress Plugin
If you’re on WordPress, Rank Math and Yoast SEO both include schema markup tools. Rank Math in particular has a comprehensive schema builder that handles Article, FAQ, HowTo, Product, and more — with a UI-based implementation that doesn’t require writing JSON-LD manually.
Method 3: Google Tag Manager
Inject schema markup via GTM without touching the site code. Useful when you don’t have direct access to the codebase. The implementation is slightly less clean than inline JSON-LD and there’s a minor rendering delay, but it works reliably for most schema types.
Generate Your Schema Markup in Seconds
Writing JSON-LD from scratch is fiddly. The syntax is specific, the nesting has to be exact, and a single missing bracket breaks the whole thing.
I built a Schema Markup Generator specifically to remove that friction. Select your schema type, fill in your details, and get clean, validated JSON-LD code ready to paste directly into your page’s <head>.
No manual JSON writing. No syntax errors. No “why isn’t this working” at 11 PM.
Supports the schema types that matter most — Article, FAQPage, LocalBusiness, Product, BreadcrumbList, Person, HowTo, and more. Use it before every new page type you build.
How to Test Your Schema Markup
Google’s Rich Results Test (search.google.com/test/rich-results)
Enter a URL or paste your schema code directly. Shows you which rich result types Google detects, whether they’re eligible to display in search results, and any errors or warnings. This is the definitive test — if it passes here, Google can read it.
Schema Markup Validator (validator.schema.org)
Google’s own tool for validating schema.org syntax. Shows all detected entities and their properties. More technical than the Rich Results Test but useful for verifying complex or nested schema implementations.
Google Search Console → Enhancements
Once your schema is live and Google has crawled the pages, Search Console shows enhancement reports for each implemented schema type — including how many pages have valid schema, how many have errors, and which specific pages have issues. This is your ongoing monitoring dashboard.
Browser DevTools → Search Console URL Inspection
For individual pages, the URL Inspection tool in Search Console shows detected structured data items alongside other page analysis. Useful for checking that schema deployed via CMS or plugin is actually appearing in the rendered page.
Common Schema Mistakes and How to Avoid Them
Marking up content that isn’t on the page. Schema must accurately reflect visible page content. Adding 5-star review markup to a page that doesn’t display reviews, or adding a price to a schema block when the price isn’t on the page, violates Google’s structured data guidelines. This can result in manual actions — actual penalties applied by a human reviewer.
Using Review schema on your own content. Self-reviews, testimonials presented as third-party reviews, or aggregate ratings that aren’t based on real user-submitted reviews — all of these violate Google’s guidelines. Google has gotten better at detecting this.
Broken JSON-LD syntax. One missing comma, one extra bracket, one mismatched quotation mark — the entire schema block becomes invalid. Always validate with the Rich Results Test before deploying. Always.
Implementing FAQ schema on pages with very low content quality. Google decides whether to display FAQ rich results based on page quality, not just schema presence. A 300-word page with FAQ schema doesn’t reliably get the rich result. The schema needs good content behind it.
Forgetting to update schema when content changes. Your article schema says the publication date is 2023, but the page has been significantly updated since. Your product schema shows a price that changed six months ago. Stale schema isn’t a penalty — but it creates inconsistencies between what Google sees in the markup and what it sees in the content, which reduces confidence in both.
Not implementing schema on the most eligible pages first. FAQ schema on product pages with genuine Q&A sections. Article schema on every blog post. LocalBusiness schema on your contact or about page. Start with the highest-value, highest-eligibility combinations rather than randomly applying schema across the site.
The TL;DR
- Structured data tells Google explicitly what your content is — not just what it says
- Schema markup (JSON-LD format) is the vocabulary used to implement it — Schema.org defines hundreds of entity types
- Rich results are the payoff: star ratings, FAQ accordions, product pricing, article authorship, all displayed before a user clicks
- Highest-value schema types for most sites: Article, FAQPage, LocalBusiness, Product, BreadcrumbList, Person
- Use Subu’s Schema Markup Generator to generate clean JSON-LD without writing it manually
- Test everything with Google’s Rich Results Test before deploying and monitor via Search Console’s Enhancements reports
- Never mark up content that isn’t visible on the page — that’s a guideline violation, not just bad practice
Structured data is one of the few technical SEO implementations where the upside is immediately visible in search results. Do it correctly and your listings look fundamentally different from everyone else’s.
Questions about which schema types make sense for your specific site? Drop them in the comments. Subu will point you in the right direction.
— Subu, SEO by Subu
