The most useful schema types — FAQ, Product, LocalBusiness, Article, Breadcrumb & more — with what each does and when to use it.
The schema types worth adding for most sites are: Organization, Website, BreadcrumbList, LocalBusiness, Product, Article, FAQPage, HowTo, Review, Event, VideoObject, Recipe, and JobPosting — each one unlocks a specific rich result or clarifies a specific kind of content for search engines. This is the complete schema types list, with what each one does, exactly when to use it, and a worked JSON-LD example for the ones you're most likely to actually need on your own site.
Why Not Just Add Every Type?
Before the list: more schema isn't automatically better, and it's worth saying so plainly before diving into thirteen types. Google's guidelines require the markup to accurately reflect content that's actually visible on the page — marking a page as a Product when it's really a blog post about products, or adding Review schema when there are no visible reviews anywhere on that page, is treated as a mismatch, not a clever shortcut. The right approach throughout this list is to match schema to what the page genuinely already is, not to add every available type hoping something eventually sticks.
The 13 Types
1. Organization
Your brand's name, logo, URL, and social profiles (via sameAs). This is typically added site-wide — once, on every page, or via a global template — rather than per-page. It's foundational for how Google's Knowledge Graph understands your brand as an entity, independent of any single page's content.
{ "@context": "https://schema.org", "@type": "Organization", "name": "Your Brand", "url": "https://example.com", "logo": "https://example.com/logo.png" }
2. WebSite (with Sitelinks Searchbox)
Declares your site's name and URL as a whole, and — combined with a potentialAction of type SearchAction — can make Google show a search box directly beneath your homepage's search result, letting users search your site without clicking through first.
3. BreadcrumbList
Shows the click-path to a page (Home → Category → Page) directly in the search result's URL line, replacing a raw URL string with a readable trail. Worth adding to nearly every page beyond the homepage, since it's low-effort and reliably improves how a listing looks.
{ "@context": "https://schema.org", "@type": "BreadcrumbList", "itemListElement": [
{ "@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com" },
{ "@type": "ListItem", "position": 2, "name": "Blog", "item": "https://example.com/blog" }
] }
4. LocalBusiness
Name, address, phone number, opening hours, and geo-coordinates. This is essential for any business with a physical location or a defined service area — it's what feeds Google Maps and local pack results, and it's the single highest-priority schema type for local SEO.
{ "@context": "https://schema.org", "@type": "LocalBusiness", "name": "Example Clinic",
"address": { "@type": "PostalAddress", "streetAddress": "12 MG Road", "addressLocality": "Bengaluru", "addressCountry": "IN" },
"telephone": "+91-80-1234-5678", "openingHours": "Mo-Sa 09:00-19:00" }
5. Product
Name, price, currency, availability, and rating. On e-commerce pages, this is what unlocks the price-and-star rich snippet directly in search results — arguably the single highest-CTR-impact schema type available for online stores.
{ "@context": "https://schema.org", "@type": "Product", "name": "Wireless Headphones",
"offers": { "@type": "Offer", "price": "4999", "priceCurrency": "INR", "availability": "https://schema.org/InStock" },
"aggregateRating": { "@type": "AggregateRating", "ratingValue": "4.6", "reviewCount": "212" } }
6. Article / BlogPosting / NewsArticle
Headline, author, publish date, and featured image, for blog posts and news content. This is what makes a post eligible for "Article" rich results and helps establish authorship and freshness signals search engines use for news and blog content specifically.
{ "@context": "https://schema.org", "@type": "Article", "headline": "How to Add Schema Markup",
"author": { "@type": "Organization", "name": "Scult Team" }, "datePublished": "2026-08-17" }
7. FAQPage
Marks up a list of questions and their answers as machine-readable Q&A pairs, rather than one undifferentiated block of prose. See what is FAQ schema for the full explanation, including the one rule that matters most: the Q&A in your JSON-LD has to match text that's actually visible on the page.
{ "@context": "https://schema.org", "@type": "FAQPage", "mainEntity": [
{ "@type": "Question", "name": "Do you ship internationally?",
"acceptedAnswer": { "@type": "Answer", "text": "Yes, to over 40 countries." } } ] }
8. HowTo
Step-by-step instructions, each with a name and description, structured so search engines (and increasingly, AI assistants) can present them as a numbered sequence rather than a wall of prose.
9. Review / AggregateRating
Star ratings and review counts. This is what puts a star rating directly beneath a search result — one of the most visually attention-grabbing rich results available, and one of the most tightly policed by Google's guidelines against fake or unverified ratings.
{ "@context": "https://schema.org", "@type": "AggregateRating", "itemReviewed": { "@type": "Product", "name": "Wireless Headphones" },
"ratingValue": "4.6", "bestRating": "5", "reviewCount": "212" }
10. Event
Dates, venue, ticket availability, and pricing for events — conferences, concerts, webinars — which can surface as an event rich result with a "get tickets" style action directly in search.
{ "@context": "https://schema.org", "@type": "Event", "name": "Annual SEO Summit",
"startDate": "2026-11-14T09:00", "location": { "@type": "Place", "name": "Bengaluru Convention Centre" },
"offers": { "@type": "Offer", "price": "999", "priceCurrency": "INR", "availability": "https://schema.org/InStock" } }
11. VideoObject
Thumbnail, duration, and upload date for video content, which helps a video appear correctly in both regular search results and Google's dedicated video search results, including a timestamp preview where relevant.
12. Recipe
Ingredients, cook time, and rating for recipe content — one of the richest, most visually distinct rich result types available, showing a photo, star rating, and prep time directly in the listing.
13. JobPosting
Title, location, salary range, and employment type for job listings, which is what makes a posting eligible to appear in Google for Jobs — a dedicated jobs search surface that sits above normal organic results for job-related queries.
Not Every Type Gets a Google Rich Result
It's worth separating two ideas that get conflated: Schema.org defines hundreds of valid types, but Google's rich results gallery only supports a specific, documented subset — Article, Product, Event, LocalBusiness, BreadcrumbList, FAQPage (in limited contexts), HowTo, Recipe, JobPosting, Review/AggregateRating, and a handful of others. Marking up a type outside that gallery (a CreativeWork subtype Google doesn't have a rich result for, say) is still valid schema.org markup, and can still help general machine understanding and AI citation — it just won't change how your listing visually looks in classic search, because there's no matching rich result defined for it.
Combining Multiple Types on One Page
Real pages almost always carry more than one schema type at once, layered as separate <script type="application/ld+json"> blocks. A typical e-commerce product page might carry Product, AggregateRating, BreadcrumbList, and Organization together; a typical blog post might carry Article, FAQPage, and BreadcrumbList. There's no penalty for multiple blocks on one page — each one just needs to accurately describe content genuinely present on that specific page.
Which Do You Need? By Site Type
| Site type | Priority schema | Why |
|---|---|---|
| Local business (clinic, restaurant, salon) | LocalBusiness, Organization, Review, FAQPage | Powers Maps/local pack results and builds trust via visible ratings |
| E-commerce store | Product, Review/AggregateRating, BreadcrumbList, Organization | Product rich snippets are the single highest-CTR-impact type for online stores |
| Blog / media site | Article, FAQPage, BreadcrumbList, VideoObject (if applicable) | Article schema plus FAQ coverage for informational search intent |
| Services / agency | Organization, FAQPage, Service, Review | No physical storefront to anchor LocalBusiness around, so entity clarity and trust signals matter more |
| SaaS / software | Organization, FAQPage, SoftwareApplication | Establishes product identity and answers pre-purchase questions directly in search |
| Recruiter / careers page | JobPosting, Organization | Unlocks Google for Jobs, a dedicated high-intent search surface |
| Events / ticketing | Event, Organization, BreadcrumbList | Event rich results directly support ticket-buying intent |
Schema Markup for Local Businesses, in Detail
A local business — a clinic, restaurant, salon, gym, or law firm with a physical address or a defined service area — gets the most direct, measurable value from schema markup of any site category, because LocalBusiness schema feeds directly into Google Maps and the local pack, both of which are high-intent, high-conversion surfaces. Beyond the basics (name, address, phone, hours), it's worth adding priceRange, geo coordinates, and — critically — Review/AggregateRating schema pulling from genuine, verifiable reviews, since star ratings are one of the strongest trust signals in a local-intent search result. FAQPage schema addressing the questions a front-desk staff member fields most often ("do you take walk-ins," "is parking available") rounds out a strong local schema setup.
Schema Markup for E-Commerce, in Detail
For an online store, Product and Review/AggregateRating schema are doing most of the commercial work — they're what unlocks the price-and-star rich snippet that tends to outperform a plain listing at the same position for a shopping-intent query. Beyond individual product pages, BreadcrumbList schema across category and product pages reinforces your site's taxonomy, and Organization schema at the site level supports brand-level trust, particularly for newer stores without an established reputation yet. For stores running promotions, the Offer object's priceValidUntil and availability fields matter more than they might seem — stale availability claims are a common source of user complaints and, at scale, of Google treating your Product markup as unreliable.
Schema Markup for Blogs and Media Sites, in Detail
A content-first site's highest-value schema is Article (or BlogPosting), paired with FAQPage wherever a post genuinely answers a cluster of related questions, and BreadcrumbList to reinforce category structure across a large content library. Sites publishing video content alongside articles should add VideoObject to make embedded or linked videos independently discoverable in video search results, not just as an afterthought inside a blog post. Author-level schema (a Person type linked via the Article's author property, ideally with a sameAs link to a genuine author bio or social profile) increasingly matters for both classic E-E-A-T signals and AI citation, since it gives search and AI engines a real entity to attribute the content to rather than an anonymous byline.
Schema Markup for Agencies and Service Businesses, in Detail
A services business without a single physical storefront to anchor LocalBusiness schema around should lean on Organization (for entity clarity), a Service type describing each distinct offering, and FAQPage schema addressing pre-sales questions directly — pricing ranges, typical timelines, what's included. Review/AggregateRating schema, sourced from genuine client testimonials, does more trust-building work for a services business than almost anywhere else, since prospective clients typically can't physically inspect the "product" before buying.
How to Test Which Types Actually Apply to You
Rather than guessing, the fastest honest test is to look at your own page and ask: what is this page actually about, in one sentence, and does a Schema.org type exist that matches that sentence directly? A product listing page is a Product. A page answering five common questions is an FAQPage. A page introducing your company is best served by Organization. Where the answer isn't obvious, it's a signal you may be looking at a page that's trying to do too many things at once — which is worth addressing in the content itself, not by forcing a schema type that doesn't cleanly fit.
Two More Types Worth Knowing: SoftwareApplication and Speakable
Beyond the core 13, two additional types are worth knowing for specific use cases. SoftwareApplication describes an app or piece of software directly — its category, operating system, and pricing — and is the natural fit for a SaaS product's homepage or pricing page, distinct from a generic Product type built more around physical goods.
{ "@context": "https://schema.org", "@type": "SoftwareApplication", "name": "Example App",
"applicationCategory": "BusinessApplication", "operatingSystem": "Web",
"offers": { "@type": "Offer", "price": "0", "priceCurrency": "USD" } }
Speakable marks specific sections of a page as suitable for text-to-speech, aimed at voice assistants reading a short summary aloud rather than a full article — a narrower, more experimental type than the rest of this list, but worth knowing if voice-driven discovery matters for your content specifically.
A Note on Deprecated and Changing Rich Result Support
Google periodically changes which rich results it supports — FAQ and HowTo rich results, for instance, have had their eligibility scope reduced over time for most sites, even though the underlying FAQPage and HowTo schema types themselves remain entirely valid Schema.org vocabulary and still support AI-citation and general machine-understanding benefits. This is worth knowing so you don't conclude a schema type has "stopped working" when what's actually changed is Google's specific rich-result display policy for that type — the markup itself, and its value beyond that one specific visual enhancement, hasn't gone away. Checking Google's Search Central documentation periodically for which types currently support which rich results (rather than relying on older articles, including this one, staying current indefinitely) is the safest way to know what's actually true today.
Schema Types Worth Knowing for Specific Niches
Beyond the general-purpose list above, a handful of niche types are worth knowing if your content fits them specifically. Course describes an educational course's provider, duration, and format, relevant for training providers and online education platforms. Dataset describes a downloadable or queryable data collection, useful for research organizations, government data portals, and companies publishing open data. PodcastEpisode and PodcastSeries cover audio content the same way VideoObject covers video, feeding podcast-specific discovery surfaces. ClaimReview is used specifically for fact-checking content, marking a claim and its verified accuracy rating — a narrow but important type for publishers doing dedicated fact-checking work. None of these apply broadly, but each is the correct, most specific type for its niche — falling back to a more generic type like Article when a more specific one genuinely fits your content is a missed opportunity for clarity, not a safer default.
Why Specificity Matters More Than Coverage
A recurring theme across this list: picking the most specific type that accurately matches your content generally serves you better than a broader type that technically still applies. A recipe page marked up as Recipe (with ingredients, cook time, and rating) is more useful to both search engines and readers than the same page marked up as a generic Article that happens to be about cooking — the specific type carries structured fields (prepTime, recipeIngredient, nutrition) that a generic Article type simply doesn't have anywhere to put. The same logic applies throughout: JobPosting over Article for a careers page, Event over Article for an event announcement, Product over Article for something you're selling. When in doubt, search Schema.org's own type hierarchy for a more specific match before defaulting to something broad and generic.
Keeping Up with New Schema Types Over Time
Schema.org's vocabulary isn't frozen — new types and properties get added as genuine use cases emerge across the industries that rely on it. A list like this one is accurate as of when it's written, but it's worth periodically checking whether a new type has appeared that matches your specific content better than what was available when you last reviewed your schema — particularly for niche content categories (courses, datasets, podcasts) that didn't always have a dedicated type in earlier versions of the vocabulary.
Schema Type Selection: A Worked Decision Walkthrough
Take a concrete, ambiguous-seeming case: a page that's technically a blog post, but the post is entirely a step-by-step tutorial for using a product. Is it an Article, or a HowTo? The honest answer is often both, layered as separate schema blocks — Article for the authorship, publish date, and headline (the "this is a piece of content by this author, published on this date" facts), and HowTo for the actual step sequence within it (the "here are the numbered instructions" facts). This layering pattern — one type for the content's identity, a second for its specific structural shape — comes up often enough that it's worth having as a default instinct rather than treating every page as needing exactly one type.
A second common ambiguous case: a services page that also functions as a landing page with pricing. Organization or Service schema covers "who we are and what we offer"; FAQPage covers the pre-sales questions answered on the same page; neither substitutes for the other, and most well-built service pages carry both together rather than picking one.
How to Audit Your Existing Schema Markup
If you've inherited a site rather than building its schema from scratch, a quick audit beats guessing at what's already there. View the source of a handful of representative pages (one per major page type — homepage, a product or service page, a blog post) and search for application/ld+json to see every schema block currently live. Run each through Google's Rich Results Test to confirm it's still valid — schema that was correct when added can become stale or broken after a theme update or CMS migration without anyone noticing, since broken schema doesn't produce a visible error on the page itself. Cross-check what you find against the "by site type" table below to spot the highest-value gaps, rather than trying to add every type at once.
The Most Important Schema Types, If You Can Only Add a Few
If you're prioritizing rather than doing everything at once: start with Organization (site-wide, foundational), BreadcrumbList (low-effort, broadly applicable), and whichever single type matches your core content — Product for a store, Article for a blog, LocalBusiness for a physical location. Those three or four cover the majority of the visible benefit most sites will see from schema markup.
Add the Ones You Need
Generate FAQ, Product, LocalBusiness, Article, and six more schema types with the Schema Markup Generator — it builds valid, correctly nested JSON-LD from a typed form for each type above, so you don't have to hand-write the JSON snippets shown here. For adding the code to your specific platform, see how to add schema markup.
Frequently Asked Questions
How do I decide between two schema types that both seem to fit my page?
Pick the more specific one — a more specific type nearly always carries more relevant structured fields than a broader, more generic type would for that same content.
What are the most important types of schema markup?
Organization and BreadcrumbList as a foundation, plus whichever type matches your core content — Product for e-commerce, Article for a blog, LocalBusiness for a physical location.
How many schema types can one page have?
As many as accurately describe content actually present on that page — an article page commonly carries Article, BreadcrumbList, and Organization together, for example.
Which schema is best for local SEO?
LocalBusiness, supported by Organization and Review/AggregateRating — this trio covers what Google Maps and local pack results draw from most directly.
What schema markup should an e-commerce site use?
Product and Review/AggregateRating are the highest-impact types, since they unlock the price-and-star rich snippet. BreadcrumbList and Organization round out the set.
Does every website need FAQPage schema?
No — only pages with a genuine, visible FAQ section. Adding FAQPage schema without matching visible Q&A content on the page violates Google's guidelines.
What's the difference between Article and BlogPosting schema?
BlogPosting is a more specific sub-type of Article aimed specifically at blog content; both are valid, and Google treats them equivalently for most practical purposes. Article is the safer default when in doubt.
Can I use more than one schema type per page?
Yes — this is normal and expected. A typical page carries 2–4 schema types together (for instance, Article + BreadcrumbList + FAQPage on a blog post).
What schema type should a SaaS or software company use?
SoftwareApplication for the product itself, plus Organization and FAQPage — SoftwareApplication is the more accurate fit than a generic Product type, since it covers operating system and application category rather than physical-goods fields.
How do I know if my existing schema markup is still valid?
Run representative pages through Google's Rich Results Test periodically, especially after a theme update, CMS migration, or redesign — broken schema doesn't produce a visible error on the page itself, so it can go unnoticed for a long time without an explicit check.
Does adding more schema types always improve my search appearance?
No — only types that accurately describe content genuinely present on the page help. Adding types that don't match your actual content risks a guideline violation rather than an improvement.
Do all 13 schema types need to be added by the same person or team?
Not necessarily — Organization and other site-wide types are usually a one-time setup task, while content-specific types (Article, Product, Event) are often best templated directly into whatever system already creates that content, so new pages get correct, matching schema automatically rather than needing someone to remember to add matching schema by hand separately, every single time a new page or product gets published on the site.
Which schema type should I add first if I'm starting from zero?
Organization, since it's foundational and site-wide, followed immediately by whichever single type most obviously matches your core content — Product, Article, or LocalBusiness in most cases.
Not sure which of these schema types your specific site actually needs, or where to start? Ask Scult's SEO team for a free structured-data audit and a prioritized implementation plan.
