Schema Markup for SEO in 2026: What Still Earns a Rich Result, and What Only Helps Google Understand You

What schema markup is, in plain English

Schema markup is a set of labels you add to a page's code so machines can read it without guessing. A person can see that a page shows a plumber's phone number and hours. Markup states it outright: this is a Plumber, here is its telephone, here are its openingHours.

The labels come from schema.org, a shared vocabulary that Google, Microsoft and other search engines support. The format Google prefers is JSON-LD. Its introduction to structured data says: "In general, Google recommends using JSON-LD for structured data if your site's setup allows it." JSON-LD sits in a script block, separate from the visible HTML, which makes it easier to build into templates and maintain.

Two other formats exist, Microdata and RDFa, which weave labels into the HTML itself. Google accepts all three when they are valid. We use JSON-LD on every site we build because it keeps the markup in one place.

What schema markup for SEO does, and what it doesn't

Markup helps search engines understand a page and can make it eligible for enhanced displays. It is not a ranking boost on its own, and eligibility never means a rich result will show.

What it does

• Makes pages eligible for rich results such as product prices, review stars, event dates and video thumbnails.
• Removes ambiguity about who you are. Google's Organization markup documentation says it can help Google "disambiguate your organization in search results" and influence which logo appears.
• Supports product and merchant experiences with price, availability, shipping and returns.

What it doesn't do

• Promise a feature. Google's documentation says markup "can enable" richer results, and items missing required properties are not eligible at all.
• Fix a weak page. Markup describes content. It doesn't replace it.
• Override what the page shows. Google's structured data guidelines say: "Don't mark up content that is not visible to readers of the page."

Google has published case studies of sites that gained from structured data. On its introduction page it reports Rotten Tomatoes measured a 25% higher click-through rate on pages with structured data, and Nestlé measured an 82% higher click-through rate for pages that showed as rich results. Those are Google's reported examples from large publishers, not a forecast for a local business.

The rich result cleanup: what Google retired, and when

Since 2023, Google has steadily removed rich result types it says few sites used or that no longer added value. If your markup strategy was built around FAQ and HowTo snippets, it needs an update. These dates come from Google's own Search documentation updates log.

The lesson is not that markup is dead. It is that a visible feature is something Google lends you and can take back. The markup that describes who you are and what each page covers keeps its value, because it doesn't depend on any one display.

Should you delete old FAQPage markup? There is no need to rush. It still describes the questions on the page accurately. Just stop adding it for the sake of a snippet that no longer shows, and never mark up questions that aren't visible.

Schema types that still matter, by job

Sort every type into one of two jobs: types that can still earn a visible feature, and types that add meaning. Google's search gallery lists the features it currently supports, including Article, Breadcrumb, Event, Local business, Organization, Product, Review snippet, Video and Job posting.

That is twelve types, and most businesses need five or six of them. A local service company needs Organization, LocalBusiness per location, WebSite, BreadcrumbList and Article for its guides. A store adds Product and reviews. An event venue adds Event.

The review markup rule that catches most businesses

You cannot mark up reviews of your own business and expect stars. Google's review snippet guidelines say that if the entity being reviewed controls the reviews about itself, its pages using LocalBusiness or any other Organization structured data "are ineligible for star review feature."

In practice that means the testimonials on your own home page will not produce stars in search, no matter how they are marked up. Plugins that add a five-star AggregateRating to every page of a service business are wasting code at best, and creating a mismatch at worst.

Review markup still works for products you sell when the reviews are genuine and shown on the page, and for review sites writing about someone else's product or business. For a local business, the review signal that matters is on your Google Business Profile. Our guide to getting more Google reviews covers that side.

Build one connected graph, not scattered snippets

Give every entity an @id and reference it everywhere else. Then your organization, its locations, its pages and its services form one connected description instead of a dozen disconnected blocks that each repeat your name and phone number.

Here is a simplified example for a fictional plumbing company's service page. It defines the organization once, defines the location and links it to the organization, then says the page is about that location.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@graph": [
    {
      "@type": "Organization",
      "@id": "https://example.com/#org",
      "name": "Example Plumbing Co.",
      "url": "https://example.com/",
      "logo": "https://example.com/logo.png",
      "sameAs": ["https://www.facebook.com/exampleplumbing"]
    },
    {
      "@type": "Plumber",
      "@id": "https://example.com/#location-morristown",
      "name": "Example Plumbing Co.",
      "parentOrganization": { "@id": "https://example.com/#org" },
      "telephone": "+1-973-555-0100",
      "address": {
        "@type": "PostalAddress",
        "streetAddress": "12 Sample St",
        "addressLocality": "Morristown",
        "addressRegion": "NJ",
        "postalCode": "07960",
        "addressCountry": "US"
      },
      "openingHours": "Mo-Fr 07:00-18:00"
    },
    {
      "@type": "WebPage",
      "@id": "https://example.com/water-heater-repair/#webpage",
      "url": "https://example.com/water-heater-repair/",
      "name": "Water Heater Repair in Morristown",
      "about": { "@id": "https://example.com/#location-morristown" },
      "breadcrumb": { "@id": "https://example.com/water-heater-repair/#crumbs" }
    },
    {
      "@type": "BreadcrumbList",
      "@id": "https://example.com/water-heater-repair/#crumbs",
      "itemListElement": [
        { "@type": "ListItem", "position": 1, "name": "Services", "item": "https://example.com/services/" },
        { "@type": "ListItem", "position": 2, "name": "Water Heater Repair" }
      ]
    }
  ]
}
</script>

Three details make this work:

1. Stable IDs. https://example.com/#org means the same organization on every page of the site.
2. The most specific type. Plumber is a subtype of LocalBusiness. Use the closest subtype schema.org offers.
3. Every value matches the page. The phone number, address and hours in the markup are exactly what the visitor sees.

Generate this from your templates and your business data, not by pasting blocks into each page. When the hours change, they should change everywhere at once.

Schema markup for SEO and AI search

Treat structured data as a consistency layer for AI search, not a shortcut into it. Google's guidance on AI features says there are no special optimizations needed for AI Overviews or AI Mode, and lists "making sure your structured data matches the visible text on the page" among its best practices.

That is the honest position. Engines read the page. Markup confirms facts the page already states: your business name, your locations, your hours, what the page covers. When the two agree, and when your Business Profile and directory listings say the same thing, you give every engine fewer reasons to doubt you.

What markup cannot do is make an AI engine cite a page that doesn't answer the question well. For that side, see our guides to generative engine optimization and answer engine optimization.

How to add schema markup without a mess

The right method depends on how your site is built. Whatever you choose, there should be exactly one source for each block of markup.

Duplicate markup is the most common problem we find: a theme adds Organization, a plugin adds another, and a reviews widget adds a third with different details. Pick one owner and switch the others off. Our web development team builds markup into templates for exactly this reason.

Test, then monitor

Validate before launch and monitor after. Use two validators and two Search Console tools, because each catches different problems.

• Rich Results Test shows whether a page is eligible for Google's features and flags missing required properties.
• Schema Markup Validator checks any schema.org markup, including types Google doesn't display.
• URL Inspection in Search Console confirms Google actually found the markup on the live page.
• Rich result reports in Search Console show errors and warnings across the whole site over time.

Then add one step most teams skip: compare the markup with the visible page. Validators confirm the code is well formed. Only a person, or a careful crawl, confirms the phone number in the markup is the one on the page.

Our schema markup for SEO audit checklist

This is the checklist we run when we audit structured data on a site. It takes about an hour on a small site and finds something on almost every one.

1. Is there exactly one Organization block, defined once and referenced by @id?
2. Does each physical location have its own LocalBusiness block, using the most specific subtype?
3. Do name, address, phone and hours match the page, the Google Business Profile and major directories?
4. Does every page below the home page have a BreadcrumbList that matches the visible trail?
5. Do product pages carry price, currency and availability that match the page today?
6. Is any review markup self-serving on a LocalBusiness or Organization? Remove it.
7. Is any markup describing content that is not visible? Remove it.
8. Are there retired types still being added for a feature that no longer shows, such as FAQ for snippets or HowTo? Stop adding them.
9. Are two plugins or a theme and a plugin outputting competing blocks?
10. Do Rich Results Test and Search Console show zero errors on key templates?

Structured data is one part of a wider check. Our technical SEO checklist covers crawling, indexing and speed, and our technical SEO audit service runs all of it for you.

Markup by business type: where to start

If you only do one thing this month, do the row that matches your business.

Then measure. Track rich result impressions in Search Console and fold them into the monthly report described in our SEO reporting guide.

How Unified handles structured data

We build schema markup for SEO into the templates of every site we make, connected by @id and generated from the same data that fills the page, so it can't drift. On Nusbaum Medical Centers, that matters at scale: 3,066 pages live, and one template change updates the markup on all of them.

UnifiedIQ, our own platform, scores every page for SEO, which is how we kept all 50 landing pages for Joe Sale Photography scoring 99 to 100. Our SEO team handles the strategy. If you want your current markup audited against the checklist above, get in touch.

Schema markup questions, answered