Structured Data in SEO: How It Improves SERP Visibility in 2026

Structured data is a standardized format, usually based on the Schema.org vocabulary, that describes a page and classifies its content so that search engines can understand it. In SEO, its main visible benefit is eligibility for rich results in Google Search. Eligibility is not a guarantee, and the list of supported rich results has shrunk since 2023.

This guide reflects Google’s documentation as of October 2026, including what structured data can and cannot do for AI-powered search.

Illustration of structured data: linked content blocks organized as a hierarchy

What is structured data?

Google defines structured data as “a standardized format for providing information about a page and classifying the page content” (Google Search Central, updated December 2025). For example, a recipe page can state its ingredients, cooking time and calories explicitly. Google no longer has to infer them from the text alone. Google says it also uses structured data to gather information about the web and the world in general, such as the people, books or companies named in the markup.

Structured data is code added to the page. Visitors do not see it, but it must describe content that they can see.

Schema.org, JSON-LD, Microdata and RDFa: who does what?

Schema.org and JSON-LD are often confused, but they play different roles. Schema.org is the vocabulary: it names the types (Article, Product, Organization) and their properties (headline, price, address). Version 30.1, released on September 16, 2026, contains 826 types and 1,540 properties (Schema.org, 2026). JSON-LD, Microdata and RDFa are the formats used to write this vocabulary into a page.

FormatHow it worksGoogle’s position
JSON-LDA JavaScript notation in a <script> tag, separate from the visible textRecommended: the easiest format to implement and maintain at scale
MicrodataHTML attributes nested inside the visible content, usually in the <body>Supported
RDFaHTML5 attributes that map visible content to linked dataSupported

Google says all three formats are “equally fine” if the markup is valid, and recommends JSON-LD because it is less prone to errors. Schema.org also contains many types that Google does not use: for Google Search, the Search Central documentation is the reference (Google Search Central, 2025).

Structured data vs metadata and Open Graph

Metadata is a broader term: the title tag and meta description shape the search snippet, while Open Graph tags control how a page looks when shared on social networks. Neither is a Schema.org structured data format. Google does note that it uses both Schema.org markup and the og:image tag as sources when choosing a page’s thumbnail image (Google changelog, March 2, 2026).

How does structured data improve SERP visibility?

Structured data improves SERP visibility by making a page eligible for rich results: stars, prices, event dates, breadcrumbs, video details and other enhancements. These enhancements can make a result more informative than a plain blue link. Google decides, query by query, whether to show them. Valid markup is a precondition, not a promise.

Google “does not guarantee that your structured data will show up in search results”, even when the Rich Results Test validates it. Common reasons include markup that does not represent the main content, markup that describes hidden content, or Google judging a plain text result more appropriate (General structured data guidelines, updated July 2026).

What about rankings? Google does not document structured data as a ranking boost. A structured data manual action removes rich result eligibility but “doesn’t affect how the page ranks in Google web search”. When it announced the retirement of seven rich result types in 2025, Google also said the change “won’t affect how pages are ranked” (Google Search Central Blog, June 2025). Our reading: structured data works on how a result looks and how well Google understands the page, not on its position.

Google does publish case studies on its introduction page. Rotten Tomatoes measured a 25% higher click-through rate on 100,000 pages enhanced with structured data. Nestlé measured an 82% higher click-through rate for pages shown as rich results (Google Search Central, page updated December 2025). Google gives no measurement dates, so treat these figures as illustrations, not benchmarks.

Which rich results does Google still support in 2026?

Google’s search gallery listed 25 structured data features on its June 15, 2026 update, across content, commerce and specialized verticals. FAQ and HowTo rich results are no longer among them. Several other types were retired between 2024 and 2026, so a markup plan written before 2024 needs a review.

Features listed in Google’s search gallery

Use caseFeatures listed by Google
Content and publishersArticle, Breadcrumb, Carousel, Discussion forum, Image metadata, Profile page, Q&A, Speakable, Subscription and paywalled content, Video
Businesses and commerceEvent, Employer aggregate rating, Job posting, Local business, Organization, Product, Review snippet, Software app, Vacation rental
Education, food and entertainmentCourse list, Dataset, Education Q&A, Math solver, Movie, Recipe

Source: Structured data markup that Google Search supports, updated June 15, 2026. Dataset markup serves only Google Dataset Search, and Breadcrumb rich results are documented for desktop (Google, updated September 2026). Local business markup, which describes details such as opening hours, is relevant to local SEO, as our local SEO guide for e-commerce brands in Saudi Arabia explains.

Rich results Google has retired or restricted

FeatureWhat changedDate
HowToLimited to desktop, then removed from desktop too: the result type is deprecatedAugust 8 and September 13, 2023
FAQRestricted to well-known, authoritative government and health websites, then no longer shown in Google Search; documentation removed on June 15, 2026August 2023, then May 7, 2026
Sitelinks search boxRemoved from search results worldwideFrom November 21, 2024
Course Info, Claim Review, Estimated Salary, Learning Video, Special Announcement, Vehicle ListingPhased out of Search; removed from Search Console reports and the Rich Results Test on September 9, 2025Announced June 12, 2025
Book ActionsAnnounced for retirement in June 2025, then kept because a feature still uses the markupNovember 5, 2025
Practice problemDeprecated; documentation removedNovember 5, 2025, then January 6, 2026

Sources: Google Search Central Blog, 2023, Google Search Central Blog, 2024, Google Search Central Blog, 2025 and the Search Central documentation changelog.

Unused structured data “does not cause problems for Search”, says Google: old FAQPage or HowTo markup can stay, but brings no Google rich result.

How do you add structured data with JSON-LD?

To add structured data with JSON-LD, choose the Schema.org type that matches the main purpose of the page. Then check Google’s documentation for that feature and write only properties that describe visible content. Place the block in a <script type="application/ld+json"> tag and test it before and after publishing.

  1. Pick the main type, as specific as possible: BlogPosting rather than a generic CreativeWork.
  2. Read the feature documentation: items missing a required property are not eligible.
  3. Describe only visible information: if the markup names a price or a rating, the page shows it.
  4. Insert the JSON-LD in the <head> or the <body> of the page it describes.
  5. Test, publish, then monitor with the tools described below.

The three examples below are deliberately minimal and use example.com.

Example 1: BlogPosting for an article

Article markup has no required properties in Google’s documentation. Google recommends adding those that apply, such as headline, image, datePublished, dateModified and author (Google Search Central, updated September 2026).

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to choose a running shoe",
  "image": ["https://www.example.com/images/running-shoe-16x9.jpg"],
  "datePublished": "2026-09-15T08:00:00+01:00",
  "dateModified": "2026-10-01T09:30:00+01:00",
  "author": {
    "@type": "Person",
    "name": "Jane Doe",
    "url": "https://www.example.com/authors/jane-doe/"
  }
}
</script>

Example 2: Organization for your brand

Organization markup also has no required properties. Google suggests useful details such as the name and an indication of real-world presence, like an address or telephone (Google Search Central, updated September 2026).

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Example Agency",
  "url": "https://www.example.com/",
  "logo": "https://www.example.com/images/logo.png",
  "telephone": "+216-00-000-000",
  "address": {
    "@type": "PostalAddress",
    "streetAddress": "10 Example Street",
    "addressLocality": "Tunis",
    "postalCode": "1000",
    "addressCountry": "TN"
  },
  "sameAs": ["https://www.linkedin.com/company/example-agency/"]
}
</script>

Example 3: BreadcrumbList for site hierarchy

BreadcrumbList requires itemListElement, an ordered list of ListItem entries (Google Search Central). Each entry gives a position, a name and the URL of the page it represents. The last entry, the current page, can omit its URL.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {"@type": "ListItem", "position": 1, "name": "Blog", "item": "https://www.example.com/blog/"},
    {"@type": "ListItem", "position": 2, "name": "SEO", "item": "https://www.example.com/blog/seo/"},
    {"@type": "ListItem", "position": 3, "name": "Structured data in SEO"}
  ]
}
</script>

CMS plugins, JavaScript and Google Tag Manager

On a CMS such as WordPress, Shopify or Wix, you may not be able to edit the HTML directly. Google points instead to the CMS’s search engine settings or to a plugin that lets you specify structured data (Google Search Central, updated December 2025). Google can also read JSON-LD injected with JavaScript, including through Google Tag Manager, if it is present in the rendered page. In Tag Manager, Google advises building the markup from page variables rather than retyping content, to avoid mismatches (Google Search Central, updated December 2025).

How do you test and monitor structured data?

Test structured data with Google’s Rich Results Test before publishing. Then monitor it in Search Console’s rich result reports and the URL Inspection tool. The Schema Markup Validator checks generic Schema.org syntax, but it does not tell you whether a page is eligible for a Google rich result.

ToolWhat it checksWhen to use it
Rich Results Test (Google)Which Google rich results the markup can generate, with errors and warningsBefore publishing and after every template change
Schema Markup Validator (schema.org)Syntax and use of Schema.org types and properties, including types Google does not useFor markup aimed at other platforms, or for types outside Google’s gallery
URL Inspection (Search Console)Structured data detected on the indexed version and on a live test of one URLTo check a specific page as Google sees it
Rich result reports (Search Console)Valid and invalid items per rich result type, counted by item, not by pageOngoing monitoring across the whole site
Manual Actions report (Search Console)Whether a structured data manual action applies to the siteWhen rich results disappear without an obvious technical cause

The Schema Markup Validator replaced Google’s former Structured Data Testing Tool in 2021 and does not check Google rich result types (Google Search Central Blog, 2020, updated 2021). In Search Console, an invalid item has at least one critical issue that blocks the rich result. The markup lives on your site, so every fix is made in your pages or templates (Search Console Help).

Which structured data mistakes should you avoid?

Google notes that its quality guidelines are not easily testable with an automated tool: syntactically valid markup can still lose rich result eligibility or be marked as spam. Marking up hidden or misleading information, using self-serving reviews or blocking the page from Googlebot can all remove rich result eligibility. Some of these mistakes can also trigger a manual action. Google’s general guidelines list the rules that every type must follow.

  • Marking up invisible content: the page body must show what the JSON-LD describes.
  • Irrelevant or misleading markup: woodworking instructions labeled as recipes, or fake reviews.
  • Missing required properties: the item is not eligible for the rich result.
  • Self-serving reviews: review snippets for LocalBusiness and Organization are only eligible on sites that collect reviews about other businesses (Google, updated September 2026).
  • Blocking the page with robots.txt, noindex or other access controls.
  • Outdated information: Google does not show rich results for time-sensitive content that is no longer relevant.

One belief from older SEO articles is wrong: repeating the same structured data on duplicate pages does not cause a penalty. Google recommends placing the same structured data on all duplicates, not only on the canonical page (General structured data guidelines, 2026). To manage the duplicates themselves, see how canonical URLs work.

Deliberately deceptive markup belongs to the same family as other manipulative tactics. Our article on black hat techniques and Google penalties covers that wider risk.

Does structured data help with AI search?

Structured data is not required to appear in Google’s AI Overviews or AI Mode, and Google says there is no special Schema.org markup to add for them. Google still advises keeping it for rich result eligibility. Bing says it may support clearer grounding for Copilot, without any guarantee. No markup guarantees a citation in an AI answer.

Google’s guide to generative AI features lists “overfocusing on structured data” among common misconceptions (Google Search Central, updated July 2026). Its AI features page recommends making sure that structured data matches the visible text on the page. To appear as a supporting link, a page must be indexed and eligible for a snippet (Google Search Central, updated December 2025).

Microsoft’s guidelines for Bing and Copilot are similar: “Structured data may support clearer grounding but does not guarantee visibility or grounding traffic. Markup must accurately reflect visible content” (Bing Webmaster Guidelines, consulted October 2026).

Our analysis: in AI search, structured data is a clarity signal, not a shortcut. Citation in an AI answer still depends on indexing, content quality and relevance, as described in our article on where SEO is heading.

Structured data in an SEO audit

Structured data can be reviewed as part of a technical SEO audit, alongside crawling, indexing and page templates. Templates matter because an error in a page template is repeated on every page that uses it. An audit of structured data can check which types are used, whether they match visible content, and which errors Search Console reports.

At Web First Rank, our SEO audit combines a technical audit, an on-site audit and an off-site audit. It is delivered as a report with a prioritized action plan, followed by a review meeting and follow-up. If you want an outside review of your site’s search performance, it is one place to start.

FAQ about structured data

Is structured data a ranking factor?

Google does not document structured data as a ranking factor. Its guidelines say that a structured data manual action removes rich result eligibility without affecting web ranking. Google said that retiring several rich result types in 2025 would not affect rankings. Structured data mainly helps Google understand a page and makes it eligible for enhanced displays.

Should I remove FAQPage markup now that FAQ rich results are gone?

There is no urgency. Google stopped showing FAQ rich results on May 7, 2026, and states that unused structured data does not cause problems for Search. FAQPage remains a valid Schema.org type. Keep it only if the questions and answers are visible on the page, and expect no Google rich result from it.

What is the difference between the Rich Results Test and the Schema Markup Validator?

The Rich Results Test shows which Google rich results a page can generate and flags blocking errors for Google. The Schema Markup Validator, maintained by schema.org, checks general Schema.org syntax, including types Google does not use. For Google Search, rely on the Rich Results Test and Search Console reports first.

What is the difference between structured data and metadata?

Metadata is a broad term for information about a page, such as the title tag, the meta description or Open Graph tags. Structured data is a specific kind of markup, usually based on Schema.org, that classifies the page content for search engines. Open Graph tags mainly control how a page looks when it is shared on social networks.

Key takeaways

  • Structured data makes pages eligible for rich results. It does not guarantee them and is not documented as a ranking boost.
  • The list has changed. FAQ, HowTo and sitelinks search box rich results, and several other features, are no longer shown: check Google’s gallery before planning markup.
  • Accuracy beats volume. Minimal JSON-LD that matches visible content, tested and monitored in Search Console, serves both classic and AI-powered search.