Structured Data Types Explained (Beyond LocalBusiness)

If you haven't read it yet, start with the structured data basics guide — it covers LocalBusiness, Service, FAQPage, BreadcrumbList, and AggregateRating, which are the types almost every service business needs first. This guide picks up where that one leaves off: the schema.org types that apply in more specific situations, what each one is actually built to describe, and — just as important — where Google's rich result eligibility has gotten stricter over the past several years. A lot of outdated SEO advice still promises rich results that schema markup alone no longer reliably produces.

Product schema

Product schema marks up a specific sellable item — its name, price, availability, and (when eligible) review data. It's built for retail and e-commerce: a specific SKU with a specific price that a visitor can buy right now. It maps poorly onto most service offerings, because a service ("emergency HVAC repair") usually doesn't have a fixed price the way a physical product does.

Where it does apply for a service business: retail add-ons sold alongside services (a HVAC company selling smart thermostats, a landscaper selling mulch by the bag), or an equipment/parts catalog. If your business is purely service-based, Service schema — covered in the basics guide — is the correct type, not Product. Using Product schema for something that isn't actually a discrete purchasable item is a common source of Search Console structured data errors.

Review and AggregateRating, revisited

The basics guide covers how to add AggregateRating markup. What it's worth understanding in more depth is Google's eligibility rules around it, because they're stricter than most business owners assume. Google's structured data guidelines restrict what it calls self-serving reviews — a business marking up reviews or ratings of itself, sourced only from its own site, generally isn't eligible for the star-rating rich result in search. Star ratings you see next to a business in search results typically come from third-party sources Google trusts directly (Google's own review data, or select aggregator platforms), not from schema a business adds to its own homepage.

That doesn't make the markup pointless — an accurate AggregateRating still gives any system parsing your page (including AI answer engines) a clean, structured data point instead of a paragraph it has to interpret. It just means you shouldn't count on it producing visible stars in Google's organic results for your own site.

HowTo schema

HowTo schema marks up step-by-step instructional content — steps, tools needed, estimated time. For a while, it produced a genuinely useful rich result: an expandable step list directly in search. Google has since scaled that feature back substantially, and HowTo rich results are no longer a reliable outcome even with complete, accurate markup.

The practical takeaway: don't build content or budget SEO strategy around HowTo schema producing a visual search feature. If you have genuinely instructional content — "how to reset a garage door opener," "how to winterize your sprinkler system" — write it clearly and use HowTo markup for the semantic accuracy it adds for AI systems and other consumers of your page, not as a rich-result play.

Article and BlogPosting

Article (and its subtype BlogPosting) marks up editorial content — a headline, author, publish date, modified date, and featured image. It's most directly tied to visibility in Google News and Top Stories features, which are mostly relevant to news publishers rather than a local service business's blog.

For a service business, the more practical value is establishing clean authorship and freshness signals: a dateModified field that's actually updated when you meaningfully revise a post (not just touched for the sake of a date change), and an author tied to a real person or your organization. See the guide to structuring a blog post for SEO for how this fits into a full post.

Event schema

If you're hosting something with a specific date, time, and location — an open house, a seasonal sale, a community workshop, a webinar — Event schema marks that up explicitly, and it's one of the more reliably useful types for producing a visible rich result, since Google has kept event listings relatively stable in search. It needs a real start date, and ideally an end date and location, to be valid; recurring or vague "ongoing" events don't map well onto the schema and are better handled as a regular page.

VideoObject schema

Marks up video content embedded on a page — its name, description, thumbnail, upload date, and duration. It can produce video-specific rich results (a thumbnail preview, key moments within longer video) and helps video content get surfaced correctly rather than being ignored. It only applies to video you're actually hosting or embedding on the page — not a page that merely mentions video content elsewhere.

Organization schema

Broader entity data than LocalBusiness: legal name, logo, founding information, and sameAs links pointing to your verified social profiles, Google Business Profile, and other authoritative mentions of the same entity across the web. LocalBusiness is technically a subtype of Organization, so most single-location service businesses only need LocalBusiness — it already carries the Organization-level fields. Separate Organization markup makes more sense for a parent brand overseeing multiple distinct LocalBusiness locations, where the brand-level entity and the individual location entities are genuinely different things.

The one rule that applies to every type on this list

• Only mark up content that genuinely, visibly exists on the page — schema is a description of the page, not a wish list of what you'd like Google to think is there.
• Test every new schema type with Google's Rich Results Test before publishing, and re-check periodically — plugin and theme updates silently break markup that worked before.
• Don't treat any of these types as a rankings lever on their own. They remove ambiguity for machines reading your page; they don't substitute for the content, links, and reputation signals that actually drive rankings.