Types of Schema Markup: A Practical Guide to the Ones That Actually Matter

Schema.org lists well over 800 types and thousands of properties. Most of them are irrelevant for practical SEO purposes. After years of implementing structured data professionally, I have a clear picture of which types Google actually uses, which ones generate rich results, and which ones exist mainly for semantic completeness that search engines largely ignore. This guide covers the ones that matter.

Organization and LocalBusiness

Every business site should have an Organization block, and if you serve customers in a physical area, it should be LocalBusiness (a subtype of Organization). This is foundational — it tells Google the name, address, phone, website, logo, social profiles, and founding details of the entity behind the site.

LocalBusiness also has dozens of more specific subtypes: Dentist, Attorney, Plumber, Restaurant, and so on. Always use the most specific subtype available. A dental office should use Dentist, not just LocalBusiness. A more specific type tells Google exactly what kind of business you are, which improves entity disambiguation in the Knowledge Graph.

Key properties to include: name, url, logo, address (as a nested PostalAddress), telephone, openingHoursSpecification, geo, areaServed, and sameAs pointing to your Google Business Profile, Yelp, LinkedIn, and other authoritative profiles.

Person

If there is a named professional whose expertise is core to the brand — a consultant, an author, a speaker, a practitioner — Person schema matters a lot for E-E-A-T. I use it on my own site to establish my professional identity, credentials, and affiliations. Properties worth including: name, jobTitle, url, image, sameAs (LinkedIn, speaker bios, media appearances), worksFor pointing to the Organization, and alumniOf if applicable.

When a Person is marked as the author of an Article, and that Person has a well-documented sameAs profile, Google can establish authorship signals that support content credibility — this is increasingly relevant as AI-generated content floods the web.

Article, BlogPosting, and NewsArticle

Content pages benefit from Article or its subtypes. BlogPosting is appropriate for editorial blog content; NewsArticle is for current-events journalism. The critical properties are headline, author (nested Person), datePublished, dateModified, image, and publisher (nested Organization with logo). These support Google Discover eligibility and can contribute to AI Overview citations.

dateModified is often skipped, but it matters. It tells Google the content has been reviewed and updated, which factors into freshness signals.

Product, Offer, and AggregateRating

E-commerce and product pages use Product schema for rich results — the price, availability, and star ratings that appear in search results. The nesting matters: Product contains offers (an Offer with price, priceCurrency, availability) and optionally aggregateRating (from an AggregateRating with ratingValue and reviewCount).

Google is strict about review schema: Review and AggregateRating may only be used on pages where the actual review content is visible to users. Do not add AggregateRating to a product page that has no visible reviews — Google will eventually catch this, and it can trigger a manual action.

For more detail on e-commerce implementation, see my post on product schema markup.

FAQPage

FAQPage schema allows individual questions and answers to expand directly in search results, giving your listing a significantly larger SERP footprint. Each question must be visible on the page and match the marked-up text exactly. This is one of the more impactful schema types for service pages and informational content — I cover the full implementation in my FAQ schema markup post, including Google’s eligibility rules and common mistakes.

HowTo

HowTo schema is designed for step-by-step instructional content. It can generate a rich result showing the steps directly in the SERP. Properties include name, step (each a HowToStep with name, text, and optionally image), totalTime, and estimatedCost. It works best when the page is genuinely procedural — tutorials, installation guides, DIY instructions. Do not shoehorn it onto pages that are not actually step-by-step in structure.

BreadcrumbList

Breadcrumb schema is one of the highest-adoption schema types because it is simple, universally applicable, and produces a visible rich result (the breadcrumb trail replacing or supplementing the URL in the SERP). Every site with more than one level of hierarchy should implement it. The BreadcrumbList contains ListItem elements with position, name, and item (the URL).

Most well-configured SEO plugins handle breadcrumbs automatically, but verify with Rich Results Test that the output is clean.

Event

If you run conferences, workshops, or webinars, Event schema generates rich results with date, location, and ticket links. I use it for SEOST / SEO Spring Training. Required properties: name, startDate, location (nested Place), and eventStatus. offers with ticket URL and price, plus performer or organizer, round out a complete implementation.

Review and AggregateRating (Standalone)

Beyond product pages, standalone Review schema is valid for review-focused content: comparison posts, best-of roundups, and service reviews where a single item is the subject. AggregateRating can appear on local business pages that aggregate client reviews. Both carry the same requirement: visible review content must match the markup.

SiteLinksSearchBox

This type enables a search box within your Google Knowledge Panel result. It requires a potentialAction pointing to a search URL with a query-input parameter. It is only worth implementing for large sites where users would plausibly search within the domain from a Google result. For most service businesses, it is low priority.

VideoObject

If you publish video content — tutorials, case studies, webinar recordings — VideoObject schema enables video rich results including thumbnail, duration, and description directly in search. Required: name, description, thumbnailUrl, uploadDate, and either contentUrl or embedUrl.

The Entity Graph: How Types Connect

The real power of schema is not in individual types — it is in connecting them. An Article has an author who is a Person who worksFor an Organization that has a logo and sameAs links. When these entities are connected and consistent across a site, Google builds a coherent knowledge graph around your brand. That graph supports Knowledge Panel appearance, AI Overview citations, and E-E-A-T scoring in a way that isolated schema blocks simply cannot.

I teach this connected-entity approach in detail in my SEO University cohorts, because it is the thing most practitioners get wrong — they implement types in silos rather than as a graph.

Prioritizing What to Implement

Not every type needs to be implemented at once. A practical priority order for most service or content sites: (1) Organization or LocalBusiness with sameAs links, (2) BreadcrumbList, (3) Article or BlogPosting with Person author, (4) FAQPage on service pages, (5) HowTo on instructional pages, (6) Product or Event where applicable. Then layer in additional types as pages warrant.

The format debate between JSON-LD and Microdata is covered in detail in my post on JSON-LD vs Microdata. Short answer: use JSON-LD for everything new.

If you want a full assessment of your current schema coverage and a prioritized roadmap, that is the kind of work I do through my schema markup consultant practice — reviews, implementation, and validation across all the types that matter for your specific site.