A Practical Guide To Schema Markup That Wins Rich Results

When Two Identical Listings Get Very Different Clicks

Picture two ecommerce pages ranking side by side for the same query, both in positions three and four. One shows a plain blue link and a gray description. The other shows a price, a star rating, an “In stock” badge, and a thumbnail image. The second listing pulls a disproportionate share of the clicks, even though it ranks lower. The difference is not the algorithm. It is the structured data feeding Google’s rich result, and the page that lost out simply never marked up its content in a way Google could trust.

That gap is what this guide is about. Schema markup is the vocabulary you add to your HTML so search engines and AI systems can read your page as data rather than guessing from text. Done correctly, it makes you eligible for enhanced listings: prices, ratings, sitelinks, recipe carousels, and the entity panels that increasingly anchor AI answers. Done carelessly, it does nothing, or worse, it triggers a manual action. Below we cover which markup still earns enhanced features in 2026, how to validate it, and where the landscape shifted after Google retired several once-popular types.

What Rich Results Actually Are, And Why They Still Matter

A rich result is any search listing that goes beyond the standard title, URL, and description. Google reads structured data on a page to understand entities like products, articles, businesses, and events, then decides whether to render a richer treatment. According to Google’s structured data documentation, markup alone never guarantees a rich result. You have to include every required property for a given type, follow the content guidelines, and earn the placement. As Google puts it, you must include all the required properties for an object to be eligible for an enhanced display.

The business case has only strengthened. Controlled testing matters here, because correlation studies overstate the effect. The most credible evidence comes from SearchPilot’s split tests, which ran schema changes as true experiments. Adding an FAQ-style markup question produced a roughly 9 percent uplift in organic traffic, while swapping Microdata for JSON-LD showed no detectable impact and a dateModified change was inconclusive. The lesson is not that schema is magic. It is that the right markup, on the right page, measurably moves clicks, and the format you choose is far less important than whether the markup makes you eligible for a visible feature.

There is also a second audience now reading your structured data: generative engines. Both Google and Microsoft have stated that they use schema markup to power their AI features, and that signal has become central to how content gets surfaced in AI Overviews and chat answers. This is why we treat structured data as foundational to both classic SEO and AI search optimization, not a niche technical chore.

The Four Schema Types Worth Your Attention In 2026

You do not need all twenty-plus supported types. For most businesses, a small set carries nearly all the value. Here is where to focus, and what each one earns you.

Product And Merchant Listing Markup

If you sell anything online, Product markup is the highest-leverage schema you can implement. It powers the price, availability, and review stars that make ecommerce listings stand out, and it feeds Google’s Shopping surfaces. Google splits this into two experiences. Product snippets apply to pages where a shopper cannot directly buy, such as editorial review pages, and emphasize ratings and pros and cons. Merchant listings apply to pages where the shopper can actually purchase.

Per Google’s merchant listing documentation, an eligible page needs, at minimum, a product name, an image, and an offers object containing a price greater than zero and a priceCurrency in ISO 4217 format. None of the global identifiers are strictly mandatory for eligibility, but Google recommends including every applicable identifier and using the most specific GTIN that applies to your product. In practice, supplying GTIN, MPN, and brand is what separates a listing that performs from one that technically validates. We treat clean product identifiers as part of broader technical SEO hygiene, because they also reconcile your site data with Merchant Center.

One gotcha worth flagging: pricing and availability that change frequently should be present in the server-rendered HTML wherever possible. Google can read JSON-LD injected by JavaScript, but for fast-moving data like stock status, dynamically generated markup can make crawls less reliable.

Organization Schema

Organization markup is the most underrated item on this list. It defines your brand as an entity: legal name, logo, address, contact points, and your official social and web profiles via the sameAs property. This is the markup that helps populate knowledge panels and, increasingly, the entity recognition that AI systems lean on to decide whether your brand is a credible source. For B2B and service businesses that will never have a price or a star rating, Organization schema is often the single most valuable type to get right. Place it on your homepage and key about pages, keep the details consistent with the rest of the web, and treat it as the backbone of your entity presence.

Review And Aggregate Rating Markup

Star ratings remain one of the most clickable enhancements available, and Review and AggregateRating markup is what produces them across products, local businesses, and certain other content types. The rule that gets sites into trouble is self-serving review markup. Google explicitly prohibits marking up reviews you write about yourself or sourcing ratings from a third party that you do not display on the page. The ratings must be genuine, visible to the user, and tied to the specific entity. Get that right and review stars deliver some of the most reliable click-through gains of any feature.

FAQ And HowTo: What Changed

For years, FAQ and HowTo were the go-to schema types because they expanded your listing with extra real estate. That era has ended, and you need to know it. HowTo rich results were phased out across desktop and mobile in 2023 and 2024. FAQ rich results then followed. According to Search Engine Journal and confirmed in Google’s FAQ documentation, FAQ rich results stopped appearing in Google Search on May 7, 2026. Google is removing the FAQ search appearance filter, the rich result report, and Rich Results Test support in June 2026, with Search Console API support discontinued in August 2026.

The practical takeaway is twofold. First, you can leave existing FAQPage markup in place. Google has confirmed that unused structured data does not cause problems for Search. Second, stop building content strategy around the visual reward, because the dropdown is gone. The pattern here is instructive: when a rich result gets aggressively scaled by tooling and stops faithfully describing the page, Google narrows eligibility and eventually removes the feature. Markup chasing a SERP gimmick is fragile. Markup that genuinely describes your content endures.

The Types Google Retired, And The Lesson In Them

FAQ and HowTo are not isolated. In 2025, Google retired seven additional structured data features, including Course Info, Estimated Salary, Special Announcement, Vehicle Listing, and Claim Review. Google’s gallery of supported types remains the single source of truth, and the supported set has narrowed steadily across recent years. Before you invest engineering time in any schema type, check it against that gallery. A type that earned a feature two years ago may now do nothing in Search. This is also why we audit existing markup during a technical SEO and GEO audit: stale schema is common, and removing dead features clarifies what is actually driving results.

How To Validate Your Markup Without Guesswork

Validation is where good intentions either become rich results or quietly fail. Use the right tool for the right job.

Rich Results Test: Google’s primary validation tool for development. Paste a URL or code snippet and it tells you which rich result types the page is eligible for and flags errors and warnings. Errors block eligibility; warnings are recommended fields you should usually add.
Schema Markup Validator (schema.org): Use this to confirm your syntax is valid Schema.org, including types that Google does not render as rich results. It checks correctness rather than Google eligibility.
Search Console rich result reports: The only tool that shows behavior at scale across your live site, including impressions, errors, and which pages actually earned features. Treat this as your monitoring layer after deployment.

A reliable workflow looks like this: build the markup in JSON-LD, which Google recommends as the easiest format to implement and maintain at scale, validate the template in the Rich Results Test, deploy to a sample of pages, then watch the Search Console report for ten to fourteen days to confirm Google is parsing and crediting it. If the Rich Results Test shows eligibility but Search Console never reports the feature, the issue is usually content quality or guideline compliance, not syntax. Pairing accurate markup with strong on-page optimization is what consistently converts eligibility into real placements.

A Practical Implementation Checklist

If you are starting from scratch or cleaning up an inherited mess, work in this order:

Inventory every schema type currently on the site and check each against Google’s supported gallery. Remove or stop maintaining anything that no longer earns a feature.
Standardize on JSON-LD. Mixed Microdata and JSON-LD across templates creates conflicts and makes audits painful.
Implement Organization schema sitewide via a single source, with logo, sameAs profiles, and accurate contact details.
Add Product or merchant listing markup to every commercial page, including price, currency, availability, and all applicable identifiers, rendered in server HTML where data changes often.
Add Review and AggregateRating only where ratings are genuine and visible on the page.
Validate templates, deploy in batches, then monitor Search Console rather than assuming success.

The Strategic Picture

Schema markup in 2026 is less about chasing every available SERP decoration and more about building a clean, accurate data layer that both Google and AI engines can trust. The features that survive are the ones that faithfully describe what is on the page: products people can buy, businesses that exist, reviews that are real. The features that disappeared were the ones that became gimmicks. If you mark up your content honestly, keep it valid, and validate before you ship, you will keep earning enhanced listings even as Google continues to prune the list. That is the durable version of winning rich results, and it is the approach we bring to every technical engagement.

Sources

See where you are cited today

A free snapshot audit of your rankings and AI citations before we ever talk.

Schedule a free consultation