12 Schema Types Every Website Should Consider Adding

Schema markup is one of those things that most site owners keep putting off — right up until they see a competitor's listing in Google showing star ratings, FAQ dropdowns, and breadcrumbs while theirs sits there looking completely naked. Structured data doesn't directly move your rankings, but it absolutely changes how Google understands your content and how your listing looks in search results. That second part matters a lot.

This isn't a guide about every schema type in existence (there are hundreds). Instead, here are twelve that cover the widest range of real websites — from e-commerce to local services to editorial blogs — and actually have visible payoffs in search.

1. Organization

This is table stakes. If you have a website for a company, brand, or project, you need Organization schema on your homepage. It tells Google your official name, logo, website URL, social profiles, and contact information. Google uses this to power Knowledge Panels and to understand brand identity across the web.

Best fit: Every business site, startup landing page, nonprofit, agency. Add it once on the homepage and you're done.

2. WebSite (with SearchAction)

Often overlooked because it sounds too generic, WebSite schema with a SearchAction property is what enables the Sitelinks Search Box — that small search field that sometimes appears directly under a brand's main result in Google. You're essentially telling Google: "Hey, our site has a search function at this URL pattern." Not every site gets the box even with this markup, but you can't get it without the markup.

Best fit: Content-heavy sites, e-commerce stores, platforms with internal search.

3. Article (and BlogPosting)

If you publish written content — articles, guides, opinion pieces, news — Article schema is non-negotiable. It signals authorship, publication date, headline, and thumbnail image. Google's Top Stories carousel in mobile results specifically favors marked-up articles from publishers using this schema. BlogPosting is a subtype of Article and works the same way; use whichever matches your content more precisely.

Best fit: Blogs, news sites, content marketing pages, editorial publications.

4. Product

Product schema is where structured data gets genuinely powerful for e-commerce. When done right — including offers, price, availability, and aggregateRating — your product listings can show price, stock status, and star ratings directly in organic search results. This is free real estate that paid ads can't replicate.

One thing people get wrong: the aggregateRating inside Product needs to reflect actual user reviews. Faking or inflating review counts gets you a manual action from Google fast.

Best fit: Any e-commerce product detail page.

5. Review / AggregateRating

Standalone review schema works for sites that review products, services, books, restaurants, or anything else. If your site aggregates scores from real users or provides editorial ratings, AggregateRating can show those gold stars in search results. The click-through rate lift from visible star ratings is real — studies consistently put it somewhere between 10% and 35% depending on the niche.

Best fit: Review sites, comparison platforms, service directories, recipe sites.

6. FAQ

FAQPage schema was the darling of SEO for a few years, and for good reason — properly marked-up FAQ sections used to expand directly beneath search listings, effectively doubling your SERP real estate. Google pulled back on showing these as prominently in 2023, but they still appear for some queries, especially on mobile. More importantly, FAQ content feeds directly into Google's AI Overviews.

Implementation is straightforward: any page with a genuine question-and-answer section can use this. Don't stuff it with keyword-targeted questions that read like a robot wrote them; write actual questions your users ask.

Best fit: Product pages, service pages, help centers, landing pages with genuine Q&A sections.

7. HowTo

If your content walks someone through a process step by step, HowTo schema can unlock rich results that display individual steps in Google Search and Google Assistant. Think tutorials, DIY guides, recipes that aren't food-related (yes, Recipe has its own type), technical walkthroughs.

The schema requires each step to have a name and description, and optionally an image. Google is fairly strict about this one — if your "how-to" is really just a paragraph pretending to be steps, expect nothing.

Best fit: Tutorial sites, DIY and home improvement content, technical documentation, fitness and cooking guides.

8. Recipe

Food content is one of the most competitive niches online, and Recipe schema is one reason some sites dominate it. The rich result for recipes is unusually information-dense: cook time, prep time, calorie count, star rating, and a thumbnail — all visible before anyone clicks. It also feeds Google's recipe carousel, which appears for almost any cooking query.

If you run a food blog and you're not using Recipe schema on every post, you're leaving meaningful traffic on the table.

Best fit: Food and cooking blogs, recipe databases, meal planning sites.

9. LocalBusiness

LocalBusiness schema (and its many subtypes like Restaurant, MedicalBusiness, AutoDealer) is the foundation of local SEO structured data. It captures your address, hours, phone number, geo-coordinates, price range, and more. While Google My Business (now Google Business Profile) handles most of this for local packs, having LocalBusiness schema on your actual website reinforces your NAP (name, address, phone) consistency — a known local ranking factor.

Best fit: Any business with a physical location or service area. Restaurants, clinics, gyms, law firms, retail stores.

10. BreadcrumbList

Breadcrumb schema is subtle but valuable. It replaces the raw URL in your Google search listing with a clean, readable breadcrumb path (Home > Category > Subcategory > Page). Users can tell at a glance where a page sits in your site structure, which builds trust and relevance signals before they even click.

This one is especially useful for large sites with deep category structures — e-commerce, content hubs, documentation sites. Implementation is simple: you're just mapping your page hierarchy into a JSON-LD list.

Best fit: E-commerce sites, blogs with category hierarchies, documentation, news sites.

11. Event

If you host or promote events — live or virtual — Event schema gets those events into Google's event rich results. This includes the event name, date, location (or virtual event URL), ticket price, and organizer. For the right type of business, this is genuinely one of the highest-ROI schema implementations possible because event searches have strong commercial intent.

Post-COVID, Google added solid support for eventAttendanceMode to distinguish in-person, online, and hybrid events. Make sure to use it.

Best fit: Venues, ticketing platforms, conference organizers, music promoters, webinar hosts, community organizations.

12. VideoObject

Video results have their own carousel in Google Search, and VideoObject schema is how you get into it for videos hosted on your own site (not just YouTube). The schema captures the video title, description, thumbnail URL, upload date, duration, and embed URL. Google needs this metadata to index and surface your videos — without it, a video embedded on your page is mostly invisible to search crawlers.

If you're already uploading videos to your own CMS or hosting them on a CDN, adding VideoObject schema to those pages is one of the easiest wins in technical SEO.

Best fit: Media companies, course platforms, tutorial sites, product demo pages, any site with self-hosted video content.

A Few Things Worth Knowing Before You Start

JSON-LD is the format Google prefers. Don't use Microdata or RDFa for new implementations unless your CMS forces you to. JSON-LD sits in a <script> tag and doesn't tangle with your HTML structure.

Validate everything. Google's Rich Results Test (search.google.com/test/rich-results) will tell you exactly which types your page qualifies for and flag any errors. Schema.org's own validator catches structural issues. Run both.

You can stack multiple schema types on one page. A product page can simultaneously carry Product, BreadcrumbList, and FAQPage markup. A blog post can carry Article, BreadcrumbList, and HowTo if the content genuinely matches. Just don't add schema that doesn't reflect what's actually on the page — Google will ignore it at best, penalize it at worst.

Schema doesn't fix bad content. It's a signal layer on top of content that Google already understands. If your product descriptions are thin, your FAQ answers are vague, or your "recipe" is three sentences and a photo, schema markup won't save you. Get the content right first, then add the structured data layer.

The twelve types above cover the majority of real use cases. Pick the ones that match your site type, implement them in JSON-LD, validate them, and monitor your Search Console for rich result impressions over the following weeks. The payoff isn't always instant, but it is consistent.