Structured data SEO: schema markup guide

What structured data is and what it does

Structured data (commonly implemented with schema.org vocabulary in JSON‑LD) is machine‑readable markup added to a page so search engines can interpret entities, attributes and relationships more explicitly than by parsing the visible text alone.

It is a clarity tool: structured data signals that a block of content represents an Article, Product, Event, Person, FAQ, BreadcrumbList, Review, or other defined type. That clarity can improve eligibility for rich results, make entity relationships explicit for knowledge systems, and help search features understand which text corresponds to which property.

Structured data is not a shortcut to rankings. It does not replace high‑quality content, good information architecture, or crawlable pages. It helps search engines interpret what is on a page; search engines still decide (via crawling, indexing and ranking) whether and how that page appears in results.

How structured data works (mechanics)

Formats and placement

JSON‑LD is the recommended and most widely used format today. Schema can also be expressed as Microdata or RDFa, but JSON‑LD keeps the markup separate from the visible DOM and is easier to manage for modern templates and CMSs.

Typical placement is inside a <script type="application/ld+json"> tag in the page head or body. Example minimal Article snippet:

<script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","headline":"Your headline here","author":{"@type":"Person","name":"Author name"}}</script>

Crawling, indexing and ranking: where schema plays a role

Structured data is consumed during crawling and indexing stages: crawlers can read JSON‑LD during fetch; indexers can store properties or use them to qualify a page for a SERP feature. Whether a page appears in Search and how it ranks is still determined by the search engine's algorithms using many signals.

Note that Google uses the mobile version as its primary basis for crawling and indexing. Since July 2024, Google crawls sites for Search with Googlebot Smartphone by default; ensure the structured data present on mobile matches the desktop semantics (parity), not necessarily pixel‑for‑pixel layout.

Where structured data helps (use cases)

Common benefits and eligible features

Rich results: FAQs, How‑tos, recipe previews, product snippets, reviews and event cards may be eligible when markup follows the documented requirements.

Knowledge graph and entity linking: schema can make entity relationships explicit (publisher → article → author → organization). This helps systems that build entity graphs.

Sitelinks and breadcrumb interpretation: BreadcrumbList markup clarifies navigation hierarchy so search features can surface the correct trail.

Eligibility signals for specialized search experiences (e.g., product availability, event dates, job postings) where structured properties convey machine‑readable facts that are hard to extract reliably from free text.

Even when markup is present, appearance of a rich result is not guaranteed. Search engines use markup as a signal and may ignore it or require additional quality signals (content quality, indexability, site reputation).

Implementing schema: practical checklist

Plan and map

Decide which page types need structured data. Map each page template to schema.org types and required properties (for example, Product requires name and offers; FAQ requires mainEntity with Question/Answer pairs). Use the schema.org documentation as the authoritative vocabulary reference.

Authoring and templating

Generate JSON‑LD from your CMS or build it into your server templates. Keep markup synchronized with visible content: dates, prices, availability, and text used inside structured properties should match what users see.

Testing and staging

Test generated JSON‑LD in staging with the Rich Results Test and Schema Markup Validator (schema.org). For pages you own, use Google Search Console URL Inspection to check how Google sees the page and whether structured data is detected as valid or contains errors.

Deployment and monitoring

Deploy to production and verify live pages with Rich Results Test.

Monitor Search Console for structured data reports and coverage issues on pages you own; use server logs and crawler‑emulation (curl) to ensure bots receive the same markup.

If you need a quick way to see what HTML a specific user agent gets, use curl with a UA string. To fetch headers only: curl -I https://example.com. To fetch the HTML as a given UA: curl -A "Googlebot" https://example.com

Verification and troubleshooting

Step‑by‑step verification for pages you own

1) Use the Rich Results Test to validate syntax and required properties. 2) In Google Search Console, run URL Inspection to confirm Google detects structured data and to review any errors or warnings. 3) Check the page's rendered HTML in Chrome DevTools > Elements to confirm the JSON‑LD script is present after any client rendering. 4) Monitor Search Console reports to catch newly surfaced issues after deployment.

What to do if rich results don’t appear

If markup validates but a rich result does not appear, check these areas: 1) Is the page indexable? Use URL Inspection to confirm index coverage. A page that isn’t indexed is unlikely to show rich results. 2) Does the visible content match the structured properties exactly? Discrepancies can cause engines to ignore markup. 3) Is the site’s overall quality and reputation sufficient for the feature — engines often require trust signals in addition to markup. 4) Confirm you are using supported types and properties for the feature (see Rich Results Test documentation).

Common mistakes and how to avoid them

Marking up content that is not visible to users or that contradicts on‑page text — structured data should reflect visible facts.

Using types or properties that are unsupported for the intended rich result; consult the Rich Results Test for the current eligibility matrix.

Relying on structured data to fix content quality or site architecture issues. Schema helps clarity but cannot compensate for thin or unhelpful content.

Not keeping markup in sync with dynamic content changes (dates, prices, availability) — avoid stale structured values.

Advanced patterns and governance

Design a schema governance process: include schema ownership in your content or engineering teams, version control JSON‑LD snippets, and add tests to your CI pipeline that validate schema syntax and required fields before deploy.

For large sites, generate structured data from canonical source fields rather than copying rendered HTML. Where localized content exists, ensure language and regional properties reflect the page audience and avoid mixing languages in a single property.

Structured data can also support downstream systems beyond search — internal knowledge bases, voice assistants, and analytics. Define a minimal, stable core of properties needed for both search and internal consumption to reduce maintenance overhead.

If you want a refresher on technical foundations that work with schema (indexability, canonicalisation, Core Web Vitals), Read the Technical SEO Guide

FAQ