Schema Markup: Complete Implementation Guide

Schema markup tells search engines and AI engines what your content means. Here is which schemas matter, how to implement them, and the common mistakes to avoid.

Schema markup (structured data) is how you explicitly tell search engines and AI engines what your content is. It's no longer optional in 2026 — rich results, FAQ snippets, AI Overview source selection, and increasingly LLM citations all depend on it.

What is structured data?

Structured data is metadata embedded in your HTML that describes the page's content in a machine-readable format. The vocabulary is schema.org; the recommended syntax is JSON-LD (embedded in a <script type="application/ld+json"> tag).

Why it matters more than ever

Rich results in Google. Stars, prices, FAQ accordions, recipe cards — all schema-driven.
AI Overview source selection. Pages with valid FAQPage / Article schema are preferred.
Entity recognition. Organization + sameAs schema builds your brand entity in Google's Knowledge Graph.
LLM citations. ChatGPT, Perplexity, Claude all weigh structured data when picking sources.

Most important schemas (priority order)

1. Organization (homepage)

{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Your Company",
  "url": "https://example.com",
  "logo": "https://example.com/logo.png",
  "sameAs": [
    "https://twitter.com/yourcompany",
    "https://linkedin.com/company/yourcompany",
    "https://wikidata.org/wiki/Qxxxxxx"
  ],
  "contactPoint": {
    "@type": "ContactPoint",
    "email": "hello@example.com",
    "contactType": "Customer Service"
  }
}

2. WebSite with SearchAction (homepage)

Enables the sitelinks search box in Google search results.

{
  "@context": "https://schema.org",
  "@type": "WebSite",
  "url": "https://example.com",
  "potentialAction": {
    "@type": "SearchAction",
    "target": "https://example.com/search?q={query}",
    "query-input": "required name=query"
  }
}

3. BreadcrumbList (every non-home page)

{
  "@context": "https://schema.org",
  "@type": "BreadcrumbList",
  "itemListElement": [
    {"@type": "ListItem", "position": 1, "name": "Home", "item": "https://example.com"},
    {"@type": "ListItem", "position": 2, "name": "Blog", "item": "https://example.com/blog"}
  ]
}

4. Article (every blog post)

Include author (Person), datePublished, dateModified, image, publisher.

5. FAQPage (any Q&A content)

The single biggest win for AEO. Use for FAQ sections, service pages with Q-A blocks, product FAQs.

6. Product / Service (e-commerce / services)

Include name, description, price, currency, availability, aggregateRating, review.

7. Person (author bios)

jobTitle, worksFor, sameAs to LinkedIn/Twitter. Strengthens E-E-A-T signals.

Implementation methods (ranked)

JSON-LD in <head> or <body> — recommended by Google. Cleanest separation from content.
Microdata — embedded in HTML attributes. More verbose, harder to maintain.
RDFa — similar to microdata. Rarely used.

Always use JSON-LD unless you have a specific reason not to.

How to deploy

Two approaches:

Hand-coded (recommended for small sites)

Write the JSON-LD blocks directly into your templates. Pros: full control, no plugin overhead. Cons: requires care to keep in sync with content.

Plugin / framework (for CMSes)

WordPress: Yoast SEO, Rank Math, Schema Pro
Shopify: Shopify Schema App, JSON-LD for SEO
Webflow: Custom Code embeds
Next.js / Nuxt: next-seo, schema-org-graph-js

Common mistakes

Schema mismatch. The schema must match what's visible on the page. Don't mark up a 4.9-star rating if no reviews exist.
Invalid JSON. A missing comma kills the entire block. Always validate.
Multiple primary types. Don't mark a single page as Article AND BlogPosting AND NewsArticle. Pick one.
Spammy FAQ schema. Don't use FAQPage for content that isn't actually Q-A — Google penalises this.
Missing required fields. Each schema type has required properties; check Google's docs.
Outdated schemas. Some schemas (e.g., HowTo for non-recipe content) have been deprecated or restricted.

Validation tools

Google Rich Results Test — tells you which rich results your page can earn
Schema.org Validator — checks JSON-LD syntax and schema compliance
Search Console Enhancement reports — surfaces schema errors at scale

Schema audit checklist

✓ Organization + WebSite on homepage
✓ BreadcrumbList on every internal page
✓ Article on every blog post (with author, dates)
✓ FAQPage on every Q-A section
✓ Product / Service / Event / Recipe where applicable
✓ Person bio for every recurring author
✓ All validated against Rich Results Test
✓ Search Console shows no schema errors

What schema won't do

Schema is not a magic ranking boost. It enables rich results, which improve CTR, which can improve rankings. But adding schema to a poor page won't make it rank — fix the content first, then mark it up.

Want it done?

Our On-Page SEO Optimization (€69) includes full schema deployment across 5 pages, validated and Rich Results Test-passing.