Structured Data Beyond FAQ and HowTo: Schema Types Worth Implementing

A client selling handmade furniture had strong product photography, detailed descriptions, and genuinely good reviews — but their listings showed up in Google’s results as plain blue links with no price, no rating stars, no stock status. A competitor selling similar pieces showed up directly below them with a rating snippet, a price, and an availability indicator visible right on the search results page, without clicking through. The content wasn’t better. The competitor had simply implemented Product and Review schema, and Google was using it to display extra information directly in the search result. We added the same markup, and within a few weeks our client’s listings carried the same rich result — same products, same prices, just now visible before the click instead of after it.

What Structured Data Actually Does

Structured data (schema markup) is code added to a page that explicitly labels what different pieces of content actually are — this number is a price, this text is a rating, this date is a publish date — rather than leaving Google to infer it from context. Most sites that have implemented any schema at all have stopped at FAQ and HowTo markup, since those are the most commonly discussed types. But a much wider set of schema types exists, and for many sites — especially e-commerce, content publishers, and local businesses — these underused types offer a more direct path to richer, more clickable search results.

Product Schema

Marks up price, availability, brand, and aggregate rating for a product page, and is the schema type most directly tied to the visible rich results — star ratings, price, and stock status — that show up directly in search results for product pages.

• Price and currency, kept in sync with what’s actually displayed on the page (Google has specifically flagged mismatches between schema and visible price as a quality issue)
• Availability status (in stock, out of stock, preorder)
• Aggregate rating and review count, pulled from genuine, existing customer reviews — never fabricated, which Google actively checks for and penalizes

On a site with hundreds of product pages, manually adding this to each one isn’t practical — it’s almost always implemented as a template that automatically pulls the relevant fields from the product database, which also keeps it accurate as prices and stock levels change.

Review Schema

Distinct from Product schema’s aggregate rating, Review schema marks up individual written reviews and is what allows star ratings to appear next to a result even for content that isn’t a traditional product page — a review article, a service comparison, a roundup post. The most important constraint here: Google’s guidelines require that review schema only be used for genuine, visible reviews actually present on the page, not a rating the page owner invented to make the result look more attractive in search.

Organization and Local Business Schema

Organization schema establishes core facts about the business itself — name, logo, official social profiles, contact information — and feeds into how Google represents the brand across search, including the knowledge panel that can appear for branded searches. LocalBusiness schema (a more specific version) adds location-based fields like address, hours, and geographic coordinates, and works alongside — not instead of — a properly optimized Google Business Profile, since they serve overlapping but distinct purposes in how Google understands and displays the business.

Article and BreadcrumbList Schema

Article schema marks up publish date, author, and headline information for blog posts and news content, and can influence whether a date appears directly in the search result, along with supporting how the content is categorized for News or Discover-related surfaces. BreadcrumbList schema marks up the page’s position within the site’s hierarchy, and commonly results in the breadcrumb trail (Home > Category > Page) displaying directly in the search result URL line instead of the raw URL path — a small but genuine improvement to how clean and trustworthy a result looks.

Implementation: JSON-LD Is the Practical Standard

Schema can technically be implemented in a few different formats, but JSON-LD is the format Google explicitly recommends and the one most modern CMS plugins default to. It sits as a self-contained script block in the page’s code, separate from the visible content, which makes it easier to manage and update without touching the page’s actual layout or copy.

• Use Google’s Rich Results Test to validate markup before publishing, and to confirm Google can actually parse it as intended
• Use Search Console’s Enhancements reports to monitor for errors across the site over time, since a template-level mistake can silently break schema across hundreds of pages at once
• Keep schema data genuinely in sync with the visible page content — mismatches between what’s marked up and what’s actually shown are a documented cause of manual rich-result suppression

Rich Results Are Not Guaranteed

Implementing schema correctly makes a page eligible for a rich result. It doesn’t guarantee one will display — Google ultimately decides whether and how to show enhanced results, and eligibility is a necessary but not sufficient condition. Treat correct implementation as removing a barrier, not as purchasing a guaranteed outcome.

The Bottom Line

FAQ and HowTo schema get most of the attention because they’re the easiest to explain, but Product, Review, Organization, and Article schema often have a more direct, visible impact on click-through rate for the sites that actually have the underlying content to support them — real prices, real reviews, real publish dates. The technical lift is usually smaller than people expect, and the upside is a search result that simply shows more before the click, which tends to outperform an identical result that shows less.