8 Types of Schema Markup That Help Your SEO
Schema markup is one of the few technical SEO moves where the payoff is visible in the search result itself. Done right, it turns a plain blue link into a richer, more clickable listing. Done wrong, or skipped entirely, you hand that real estate to a competitor who did the work.
Here are the eight types that actually move the needle.
Quick answer:
- Organization / LocalBusiness sets your entity identity in Google's Knowledge Graph
- FAQ schema adds expandable Q&A accordions to your search result
- Review / AggregateRating enables star ratings and review counts
- Product schema unlocks Google Shopping eligibility and price/availability data
- Article schema feeds headline, author, and freshness signals to Google
- Breadcrumb schema replaces raw URLs with readable site paths in the SERP
- How-To schema renders numbered steps directly in search for task-based queries
- Service / Event schema targets local intent and date-specific search behavior
1. Organization and LocalBusiness for Identity
Schema markup is structured data added to a page that tells search engines what your content means, not just what it says.
Organization schema (and its more specific child type, LocalBusiness) is the foundation. It tells Google your legal name, website, logo, social profiles, and contact details in a format the algorithm can read without guessing. For businesses with a physical address or service area, LocalBusiness adds fields for address, hours, and geographic coordinates.
LocalBusiness schema anchors your business entity in Google's Knowledge Graph, reducing the risk of incorrect information appearing in your Knowledge Panel.
Without this markup, Google infers your identity from unstructured text across your site and third-party directories. That inference can go wrong, populating your Knowledge Panel with outdated addresses or mismatched phone numbers. The Organization structured data documentation from Google covers the required and recommended fields.
Practical takeaway: implement Organization or LocalBusiness schema on your homepage and About page first. It is the single highest-priority schema implementation for any business that wants Google to represent its identity accurately.
2. FAQ Schema for Expandable Answer Results
FAQ schema lets Google render expandable question-and-answer pairs directly in the search result, increasing your listing's visual footprint without requiring a higher ranking position.
Google retired FAQ rich results in Google Search (deprecated as of May 2026), so FAQPage markup no longer displays expandable questions beneath your blue link, which means a user can read your answer before they click. That increased visual footprint tends to lift click-through rate on the result even when the ranking position itself has not changed.
Google's FAQ structured data documentation specifies that this markup is intended for pages where a single entity provides the questions and answers. It is not appropriate for community forums or user-generated Q&A.
The most effective use is on service pages, product pages, or landing pages where you already answer common objections. Mark up the questions you know buyers ask before they convert. That is also the content that tends to surface in AI Overviews and generative search summaries, which makes FAQ schema one of the better dual-purpose investments in technical SEO right now.
Practical takeaway: add FAQ schema to pages where you already have a question-and-answer section. If you do not have one yet, adding it is a content and schema win at the same time.
3. Review and AggregateRating for Star Snippets
Review and AggregateRating schema enable star ratings in search results, but Google's guidelines prohibit site owners from rating their own business or products.
Star ratings in the SERP are one of the highest-visibility rich results available. AggregateRating schema tells Google the average score and total review count for a product, service, or business. The rich result displays that data as a visual star row beneath the title.
Google's Review snippet documentation is explicit on one critical constraint: self-serving ratings are not allowed. The ratings must come from real users, not from the site or business themselves. Implementations that inflate ratings or apply AggregateRating to content that has no genuine user reviews risk a manual action.
For ecommerce, this schema belongs on product pages where you collect verified purchase reviews. For service businesses, it belongs on a reviews or testimonials page that aggregates feedback from a third-party platform like Google Reviews, pulling in real reviewer data. The schema signals the data; the data still has to be honest.
Practical takeaway: implement AggregateRating on product or service pages only when you have a real pool of user reviews to draw from. The schema amplifies the signal; it does not manufacture it.
4. Product Schema for Ecommerce Listings
Product schema is required for any ecommerce page that wants to appear in Google Shopping rich results within organic search. It gives Google structured access to the fields that matter at the moment of purchase intent: price, currency, availability, condition, and product identifiers like GTIN or SKU.
Google's Product structured data documentation lists both required and recommended fields. Missing required fields like offers, price, or availability silently disqualifies the listing from rich result eligibility even if everything else validates.
The practical implication for an online store: every product page needs schema that reflects live inventory status. A product marked InStock in schema but sold out on the page creates a data conflict Google will notice. Schema accuracy is not a one-time setup; it needs to stay in sync with your product database. That is one reason product schema is typically deployed via a template or a feed integration rather than hand-coded page by page.
Practical takeaway: deploy Product schema through a template that pulls live price and availability data. Static schema that goes stale is worse than no schema because it sends conflicting signals.
5. Article Schema for News and Blog Content
Article schema tells Google a page is editorial content and provides structured metadata: headline, author, datePublished, dateModified, and the publishing organization. Google's Article structured data documentation covers three subtypes: Article, NewsArticle, and BlogPosting. Use the one that matches your content type.
The fields that matter most for SEO value are datePublished and dateModified. Providing accurate dates helps Google understand content freshness, which is a ranking factor for queries where recency matters. If you update a piece of content, update dateModified in the schema to match. Leaving a stale date signals that the page has not been touched even when it has.
Author markup also connects to Google's E-E-A-T (Experience, Expertise, Authoritativeness, Trustworthiness) framework. Marking up author data with a link to a verified author profile page gives Google a structured signal about who produced the content, not just what the content says.
For the RGDM content pipeline, Article schema is standard on every insights post. It is table stakes for a blog that wants to compete in knowledge-heavy queries.
Practical takeaway: always include datePublished, dateModified, and a linked author profile in Article schema. Those three fields do the most SEO work.
6. Breadcrumb Schema for Cleaner SERP Paths
Breadcrumb schema replaces the raw URL string in a search result with a readable site hierarchy. Instead of displaying https://example.com/services/seo/technical-seo-audit, the result shows Services > SEO > Technical SEO Audit. That is easier to scan, more trustworthy-looking, and communicates site structure at a glance.
Breadcrumb schema replaces the raw URL line in a search result with a readable site path, making the listing easier to scan and more likely to be clicked.
Google's Breadcrumb structured data documentation confirms this is an eligible rich result and describes the BreadcrumbList and ListItem types used to mark it up.
From a UX standpoint, breadcrumb display in the SERP also communicates to the user that a site has organized, navigable content, not just a single landing page. For sites with layered service or product architectures, it is a low-effort implementation with a consistent presence in results.
Practical takeaway: implement BreadcrumbList schema site-wide through your CMS template. It is one of the lower-cost schema types to deploy and it improves every result across the site simultaneously.
7. How-To Schema for Step-Based Queries
How-To schema marks up content that walks a user through sequential steps to complete a task. Google previously rendered this markup as a rich result that displayed steps, images, time estimates, and supply lists directly in the SERP, but it deprecated the How-To rich result in September 2023, and it no longer appears in Search on any device.
Google's How-To structured data documentation specifies that this type is appropriate for content where the goal is task completion. A guide on how to set up a Google Tag Manager container, how to configure a conversion action, or how to audit a Google Ads campaign structure are all legitimate use cases.
Where this earns its place in an SEO strategy is on informational content targeting procedural queries. Those queries, "how to do X," are also exactly the queries that AI Overviews and generative search engines pull from when a user asks an AI assistant for instructions. Marking up the steps in a machine-readable format increases the probability that your content gets cited and structured in the response.
Practical takeaway: use How-To schema on any page built around a multi-step process. Do not force it onto content that is really an article or an FAQ; the schema type should match the actual content format.
8. Service and Event Schema for Local Intent
Service schema describes what a business offers: the service type, the provider, and the area served. Event schema gives Google structured data for in-person or virtual events including name, date, time, location, and ticket availability. Both types serve queries where the user is looking for something to do or use within a specific context.
Google's Event structured data documentation confirms that Event schema can surface in the Events rich result and in Google Search features for local event discovery. For service businesses, Service schema supports the entity relationship between a LocalBusiness and the specific services it provides.
For any business running local SEO, Service schema is the natural extension of LocalBusiness. It tells Google not just who you are but what you do and where you do it. For marketing agencies, law firms, home services companies, and any other service provider targeting a geographic market, this is the structured data layer that makes service-level pages machine-readable rather than just human-readable. RGDM's tracking and automation work often includes schema implementation as part of the technical setup, because schema accuracy is part of what makes a campaign's landing pages perform.
Practical takeaway: implement Service schema on each service page and link it to the LocalBusiness schema on your homepage. That connection gives Google a coherent entity map of your business.
One Thing That Blocks All of It
Every schema implementation should be validated with Google's Rich Results Test before going live, because syntax errors silently block rich result eligibility.
Schema that contains errors does not throw a visible warning on the page. It just fails to render as a rich result, and you may never know why without testing. Google's Rich Results Test checks any URL or code snippet and tells you which rich result types are eligible and which fields have errors.
Run every implementation through it before deploying. Fix errors before adding new schema types. A single broken JSON-LD block can invalidate the entire schema output on a page.
If you want structured data built into your pages as part of a system, not as a one-off task, that is what we do. Book a strategy call and we will audit what your pages are missing and what it would take to deploy it at scale.
Frequently Asked Questions
What schema markup should I use?
Start with Organization or LocalBusiness to establish your entity identity, then add the schema types that match your actual content: FAQ schema for question-and-answer sections, Article schema for blog posts, Product schema for ecommerce listings, and Breadcrumb schema site-wide. The right types are the ones that match what your pages already contain, schema should describe real content, not manufacture it.
Does schema markup help SEO?
Schema markup does not directly increase rankings, but it increases eligibility for rich results, which are enhanced search listings that take up more visual space and often attract higher click-through rates. Google confirms in its structured data documentation that rich results are only available to pages that implement valid schema. More clicks from the same position means more traffic without needing to rank higher.
What is structured data?
Structured data is code added to a web page, usually in JSON-LD format, that describes the page's content in a vocabulary search engines can read programmatically. Schema.org is the shared vocabulary that Google, Bing, and other search engines recognize. Instead of Google guessing that a block of text is a product price, structured data explicitly labels it: this is the price, this is the currency, this is the availability status.
Which schema types get rich results?
Google maintains a list of structured data types that are eligible for rich results. As of 2026, types that can render rich results in Google Search include FAQ, How-To, Product, Review and AggregateRating, Breadcrumb, Article (via Top Stories), Event, and LocalBusiness (via Knowledge Panel). Eligibility requires both valid markup and content that meets Google's quality guidelines. The Google Search Central documentation maintains the current full list.
Is JSON-LD the right format for schema markup?
Yes. Google recommends JSON-LD as the preferred format for structured data because it is easier to implement, maintain, and update without modifying visible page content. Microdata and RDFa are also supported but are harder to manage at scale. Most modern CMS platforms support JSON-LD schema injection through plugins or theme templates.
Can schema markup hurt my SEO?
Incorrect or misleading schema can trigger a manual action from Google. Specific violations include applying AggregateRating schema to self-generated ratings, marking up content that is not visible to the user, and using schema to misrepresent what a page contains. Schema that simply has syntax errors will not hurt rankings; it just will not generate rich results. Schema that actively misrepresents the content is the risk.
How do I know if my schema is working?
Use Google's Rich Results Test to validate markup and Google Search Console's Enhancements reports to see which rich result types Google has detected across your site and whether any pages have errors or warnings. Search Console also shows when a rich result type was first detected, which helps you confirm a deployment landed correctly.