Technical SEO
Intermediate
11 min read

Structured Data and Schema.org

Structured data is one of the few SEO levers that directly produces visible SERP changes. Add Recipe schema and you might get a recipe carousel. Add FAQPage schema and you might get expandable FAQs in the SERP. Beyond rich results, structured data is also the most efficient way to communicate exactly what your page is about to search engines and AI assistants. This guide explains how it works and which schemas matter most.

Last reviewed April 19, 2026|By Toronto SEO Editorial
TL;DR

Structured data is machine-readable markup (using the Schema.org vocabulary, in JSON-LD format) that tells search engines and AI assistants exactly what your page is about. It powers rich results in Google (stars, FAQs, breadcrumbs, recipes), enables knowledge-graph entity recognition, and makes your content far easier for AI assistants to cite accurately.

Structured data is one of the few SEO levers that directly produces visible SERP changes. Add Recipe schema and you might get a recipe carousel. Add FAQPage schema and you might get expandable FAQs in the SERP. Beyond rich results, structured data is also the most efficient way to communicate exactly what your page is about to search engines and AI assistants. This guide explains how it works and which schemas matter most.

What structured data is

Structured data is machine-readable markup that describes the content of a page. It uses the Schema.org vocabulary — a shared, search-engine-supported set of types and properties (Article, Product, Recipe, LocalBusiness, etc.) — and is typically embedded as JSON-LD in a script tag in the page head.

JSON-LD is Google's recommended format. Microdata and RDFa are also supported but harder to maintain. Stick to JSON-LD unless you have a strong reason not to.

The most valuable schema types

Some schema types unlock rich results; others communicate entity information used by AI assistants and the knowledge graph. The schemas with the most universal value:

  • Organization (or LocalBusiness for local businesses): your brand entity. Always implement on the homepage at minimum.
  • Article (or NewsArticle): for blog posts, news, and editorial content. Powers the Google News carousel.
  • Product: for product pages. Powers price, rating, availability rich results.
  • Recipe: for recipes. Powers cook time, ratings, ingredient cards.
  • FAQPage: for pages with genuine FAQs. Powers expandable FAQ rich results (though Google has reduced this since 2023).
  • BreadcrumbList: for breadcrumb trails. Replaces URL fragments with readable hierarchy in the SERP.
  • Person: for author bios and team pages. Critical for E-E-A-T signal.
  • HowTo: for tutorials with discrete steps.

Avoiding common implementation mistakes

Most structured data bugs fall into a few patterns:

  • Marking up content that isn't visible on the page (a violation of Google's guidelines and grounds for manual action).
  • Marking up unrelated content (e.g., FAQ schema on a non-FAQ page).
  • Missing required properties for the schema type (Google's Rich Results Test catches these).
  • Using fake review markup with star ratings nobody actually gave (manual action territory).
  • Implementing JSON-LD that doesn't validate (silently ignored by Google).

How AI assistants use structured data

AI assistants love structured data because it removes ambiguity. A page with Article schema (with author, datePublished, headline, image, publisher) is far easier to cite confidently than one without. A LocalBusiness schema with NAP, hours, and services makes accurate citation trivial.

Practical rule: every page should have at minimum a sitewide Organization schema and a page-specific schema (Article, Product, Service, etc.) that matches its content type. That covers ~90% of the AI-citation benefit.

Validation and monitoring

Validate every schema implementation with Google's Rich Results Test (rich result eligibility) and Schema.org's Validator (syntax and vocabulary correctness). Monitor in Search Console under Enhancements — Google reports errors and warnings per schema type.

If you ship a schema change, re-validate in Rich Results Test before deploying, and re-check Search Console a week later for new errors.

Key takeaways

Use JSON-LD with Schema.org types — that's Google's recommended format.
Implement Organization schema sitewide and page-type schemas per page.
Don't mark up content that isn't visible or relevant — that's grounds for manual action.
Validate with Rich Results Test before deploying.
AI assistants use structured data to cite accurately.

Frequently asked

Ready to apply this to your site?

Toronto SEO works with ambitious businesses across the GTA on the exact playbooks taught in this hub. Get a free, senior-led audit of where your SEO program stands today.