Schema markup: what it is and why it matters

Overview

Schema markup (structured data) is machine-readable annotations you add to page HTML to describe people, products, events, reviews, articles and other entities. In 2026, search engines use structured data to better interpret page content, decide eligibility for rich results and surface content in AI-driven SERP features, but structured data does not guarantee a rich result or change rank by itself.

Common formats are JSON-LD (recommended by Google), Microdata and RDFa. JSON-LD keeps markup separate from visible HTML and is the easiest to maintain for most sites; Microdata/RDFa embed properties inline with elements. Use schema.org vocabularies or provider-specific schemas when available.

Step-by-step

1) Choose the right type — identify the schema.org type that matches the content (Article, Product, Event, LocalBusiness, Recipe, FAQPage, etc.). Use the most specific type available.

2) Pick a format — prefer JSON-LD for easier deployment and separation from markup. If your platform or CMS only supports Microdata/RDFa, ensure required properties are present and accurate.

3) Add required properties — follow the specification for the type. For example, a minimal Article example in JSON-LD can look like: <script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","headline":"Example title","datePublished":"2026-01-01"}</script>.

4) Test before publishing — use the Rich Results Test and the Schema Markup Validator (schema.org) to confirm syntax and required properties, and review any warnings.

5) Monitor performance — use Google Search Console’s Performance report to watch impressions and CTR for pages eligible for rich results. Use the URL Inspection tool to check how Google last indexed a specific URL and whether structured data was detected.

Format comparison: JSON-LD vs Microdata vs RDFa

JSON-LD — Pros: easier to inject and maintain, keeps markup separate from visible HTML, preferred by many search engines. Cons: you must ensure the script is present on the final rendered page (not removed by client-side rendering).

Microdata — Pros: ties properties directly to elements, can be useful in legacy systems. Cons: harder to maintain and more intrusive to HTML structure.

RDFa — Pros: powerful for semantic web use cases and linked data. Cons: greater complexity and less common for standard SEO tasks.

Verification: technical checklist

Use these checks to verify structured data is present, valid and discoverable. Each check is something you can perform from outside the publisher site.

**Structured data present** — where to verify: view-source or curl of the published URL — passes when the page contains a valid <script type="application/ld+json"> block or inline Microdata/RDFa with the expected properties.

**Syntax & required fields** — where to verify: Rich Results Test and Schema Markup Validator — passes when the tools report no errors and only permissible warnings for your markup type.

**Rendered availability** — where to verify: Chrome DevTools Elements panel or a curl request emulating a user-agent — passes when the structured-data script or attributes appear in the final rendered DOM.

**Indexation signal** — where to verify: Google Search Console URL Inspection (for your site) or public indexation indicators such as site: queries — passes when URL Inspection shows the page indexed and the inspection detects structured data; note: site: is only indicative, not definitive.

Practical commands and tools

Fetch the raw HTML as a typical browser: curl -L "https://example.com/page". To inspect what a specific user-agent receives, use curl -A "Mozilla/5.0 (compatible; Googlebot/2.1; +http://www.google.com/bot.html)" "https://example.com/page" (do not use -I if you want the HTML body).

Run the page through Google’s Rich Results Test (https://search.google.com/test/rich-results) and the Schema Markup Validator (https://validator.schema.org). For your own URLs, use Google Search Console URL Inspection to see how Google last crawled and indexed the page and whether structured data was detected.

Common problems

Invalid JSON syntax — missing commas or quotes break JSON-LD. Fix with a JSON validator or the Rich Results Test.

Missing required properties — some rich result types require specific fields (e.g., price for Product). Without them, a page may be ineligible for a rich result even if schema exists.

Script removed by client-side rendering — if your site injects JSON-LD via JavaScript, confirm the final rendered DOM contains the script tag; otherwise search engines may not see it.

Structured data on non-indexed pages — a page Google does not index is unlikely to surface rich results. Indexation and eligibility are separate stages: structured data affects interpretation and eligibility; indexation determines whether the page can appear in results; ranking order is determined by many signals beyond structured data.

Conflicting or duplicate types — avoid marking the same content with contradictory types or duplicate, inconsistent values that confuse parsers.

Manual action or policy issues — structured data that misrepresents content to gain richer display may be treated as spam. Follow provider guidelines and avoid marking up content that isn’t visible to users.

Read the Technical SEO Guide

Frequently asked questions

Technical SEO is one part of organic growth. Building topical authority requires high-quality backlinks in addition to correct structured data and on-page signals. Build authority with quality backlinks