Schema Markup for SEO: What to Add and How

Schema Markup for SEO: What to Add and How

A reader lands on your services page from a Google result that shows your star rating, your price range, and a line of breadcrumbs above the link. Three competitors below you show a plain blue link. That extra context came from one thing: structured data the others skipped.

Schema markup is the code that tells search engines what your content actually means. A page about "Atlas" could be a person, a product, or a mountain range. Markup removes the guesswork. For a B2B site, the payoff is concrete: more real estate in the result, better eligibility for rich features, and cleaner signals for the AI systems that now summarize answers before anyone clicks.

This guide covers what to add, what stopped working in 2026, and how to ship it without breaking anything. No theory you can't act on by this afternoon.

What schema markup does (and what it doesn't)

Structured data is a standardized vocabulary, maintained at Schema.org, that you embed in a page so machines can parse it. You describe your organization, an article, a product, an FAQ, and each property follows an agreed format.

It does not rank you higher on its own. Google has said for years that structured data is not a direct ranking factor. What it does is make you eligible for richer search appearances and help engines understand entities and relationships. Those richer appearances often lift click-through rate, and a higher CTR can move you up over time.

One more job has grown in importance. AI Overviews, ChatGPT, and Perplexity all parse pages to extract facts. Clean markup gives them structured answers to pull from, which matters if you want your brand cited in AI-generated responses. We dug into that shift in our guide to AI and SEO, and schema is a quiet part of it.

The 2026 reset: what changed

If you read an older schema tutorial, parts of it are now wrong. Google has spent three years trimming the list of structured data types that produce rich results, and 2026 brought the biggest cut yet.

FAQ rich results are gone. As of May 7, 2026, Google stopped showing the expandable FAQ accordion in search for almost all sites. The rich result report and Rich Results Test support are being retired through the summer. The FAQPage type still validates and you can leave it on the page, it just no longer earns that visual treatment for ordinary sites.

HowTo rich results were removed earlier, fully deprecated on desktop back in September 2023. A batch of seven more niche types was retired in June 2025. The pattern is consistent: a type gets widely abused, Google restricts it to trusted verticals, then pulls it entirely.

So spend your effort on the types that still pay off.

Schema type Still earns rich results (2026)? Best for B2B
Organization Yes (knowledge panel, sitelinks) Every site, the homepage
BreadcrumbList Yes Deep service and blog pages
Article / BlogPosting Yes (Top stories, article cards) Every blog post
Product + Offer Yes (price, availability) SaaS pricing, productized services
Review / AggregateRating Yes (star ratings) Case studies, testimonials pages
LocalBusiness Yes (maps, local pack) Agencies and firms with an office
Event Yes Webinars, conferences
FAQPage No longer (May 2026) Still fine for AI parsing
HowTo No (removed 2023) Skip for rich results

Figures and support status reflect Google's documentation as of June 2026. Treat any single type as worth re-checking before a big rollout, because this list keeps moving.

Pick your format: JSON-LD

Three formats exist (JSON-LD, Microdata, RDFa). Use JSON-LD. Google recommends it, it lives in a single <script> block instead of being tangled through your HTML, and you can generate it server-side or inject it with a tag manager without touching the page body.

A JSON-LD block sits in the <head> or <body> and looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Organization",
  "name": "Lead The Way",
  "url": "https://YOUR_DOMAIN_HERE.com",
  "logo": "https://YOUR_DOMAIN_HERE.com/logo.png",
  "sameAs": [
    "https://www.linkedin.com/company/YOUR_HANDLE_HERE",
    "https://x.com/YOUR_HANDLE_HERE"
  ]
}
</script>

Replace every YOUR_..._HERE placeholder with your real values. The sameAs array links your entity to your social and directory profiles, which helps Google connect the dots for a knowledge panel.

What to add, page by page

Start with the markup that maps to pages you already have. You don't need every type. You need the right ones in the right places.

Organization, once, sitewide

Put an Organization block on your homepage (or sitewide). It anchors your brand as an entity: name, logo, contact point, social profiles. This is the single most valuable block on most B2B sites because it feeds the knowledge panel and brand sitelinks.

Article on every blog post

Each post should carry Article or BlogPosting with headline, author, publish and modified dates, and a featured image. Author matters more than it used to. Tying content to a real, credentialed author supports E-E-A-T signals, especially in YMYL-adjacent B2B topics like finance or compliance.

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "Schema Markup for SEO: What to Add and How",
  "author": {
    "@type": "Person",
    "name": "YOUR_AUTHOR_NAME_HERE"
  },
  "datePublished": "2026-06-15",
  "dateModified": "2026-06-15",
  "image": "https://YOUR_DOMAIN_HERE.com/images/schema-markup.png"
}
</script>

Keep dateModified accurate. Inflating it to fake freshness is the kind of thing that gets a type abused and then killed.

Breadcrumbs on deep pages

BreadcrumbList shows your site hierarchy in the result instead of a raw URL. It's a small win that still works in 2026, and it pairs naturally with a sane site architecture. If your URLs and navigation already tell a clear story, breadcrumb markup just exposes it. We cover the structural side in our piece on internal linking for SEO.

Product and Review where they're genuine

If you sell a productized service or SaaS tier with a clear price, Product plus Offer can surface pricing in search. AggregateRating and Review can show stars, but only mark up reviews that real customers actually left, displayed on the page. Inventing ratings violates Google's guidelines and risks a manual action. The proof has to exist on the page you're marking up.

LocalBusiness if you have an office

Agencies and firms with a physical address should add LocalBusiness with address, hours, and geo coordinates. It supports the local pack and maps presence, which matters for "B2B agency near me" style intent.

How to add it without a developer

You have three realistic paths, ordered by how much control they give you.

  1. CMS or plugin. WordPress sites can use a dedicated schema plugin or an SEO plugin that emits JSON-LD. Webflow, Framer, and most modern builders let you paste a JSON-LD block into a custom code field. Fastest route, least flexible.

  2. Google Tag Manager. Inject JSON-LD with a Custom HTML tag firing on the right pages. Good when you can't edit templates directly. One caveat: Google can read GTM-injected markup, but server-rendered markup is more reliable, so prefer the template if you can reach it.

  3. Server-side in your templates. The most reliable option. Render the JSON-LD in the page source so it's there on first load, no JavaScript dependency. Pull values from your CMS fields so the markup stays in sync with the content automatically.

Whichever path you pick, generate the JSON dynamically from real page data rather than hand-copying blocks. Hand-copied markup drifts out of date the moment someone edits the page.

Validate before you ship

Markup that looks right and parses wrong is worse than no markup, because it can suppress the feature you wanted. Two free tools catch most problems:

  • Google Rich Results Test. Paste a URL or code snippet. It tells you which rich results the page is eligible for and flags errors. Note that it's being trimmed alongside the FAQ deprecation, so cross-check.
  • Schema.org Validator (validator.schema.org). A stricter, type-agnostic check of your syntax against the full vocabulary.

After launch, watch Google Search Console. Its structured data reports show valid items, warnings, and errors across your whole site, and they update as Google recrawls. A warning is a missing recommended property; an error is a broken required one. Fix errors first.

Here is the order I run on a new site, top to bottom:

1. Add Organization sitewide, validate the homepage
2. Add Article to the blog template, validate one post
3. Add BreadcrumbList to deep pages, validate
4. Add Product/Review/LocalBusiness where they apply
5. Submit to GSC, wait for recrawl, read the reports
6. Re-check after any template change

That last step gets skipped and it's the one that bites. A redesign or a plugin update can silently strip your markup. Schema is not set-and-forget. Building structured data into your routine is part of a healthy technical SEO practice, not a one-time chore.

Common mistakes that waste the effort

Marking up content that isn't visible on the page. Schema must describe what a user actually sees. Hidden or injected-only content is a guideline violation.

Faking ratings, prices, or review counts. Tempting, traceable, and the fastest way to a manual action.

Copying a competitor's block wholesale. Their values are theirs. You'll publish their author name or their address by accident, and validators won't catch a factually wrong but syntactically valid field.

Leaving placeholder text live. YOUR_DOMAIN_HERE shipped to production is more common than you'd think. Search your source before launch.

Expecting rankings to jump. They won't, directly. The lift comes from CTR and eligibility over weeks, not a switch you flip.

Frequently asked questions

Does schema markup improve my Google rankings?

Not directly. Google has repeatedly confirmed structured data is not a ranking factor. It makes you eligible for rich results and helps engines understand your content, and the better click-through rate from a richer listing can lift rankings indirectly over time.

Should I still add FAQ schema after the 2026 deprecation?

It no longer earns the expandable accordion in search for most sites. You can leave existing FAQPage markup in place, it still validates and may help AI systems parse your answers. For new pages, it's low priority, so put your effort into Organization, Article, and Breadcrumb markup instead.

JSON-LD, Microdata, or RDFa?

JSON-LD, in nearly every case. Google recommends it, it lives in one tidy script block, and you can add or update it without rewriting your HTML. The other two are still valid but harder to maintain.

How long until I see results from schema?

Once Google recrawls and indexes the pages, eligible rich results can appear within days to a few weeks. The crawl timing depends on your site's authority and how often Google visits. There's no instant switch, and CTR gains build gradually.

Can bad schema hurt my site?

Yes, in two ways. Markup that misrepresents page content (fake reviews, hidden text) can trigger a manual action. Broken syntax can make you ineligible for the very feature you wanted. Validate before you ship and monitor Search Console after.

Do I need schema on every single page?

No. Match the type to the page: Organization sitewide, Article on posts, Product on pricing or service pages, LocalBusiness if you have an office. Pages with nothing to describe in structured form don't need it.

Quick checklist before you call it done

  • Organization markup live sitewide, validated on the homepage
  • Article or BlogPosting on every post, with a real author and accurate dates
  • BreadcrumbList on deep pages
  • Product, Review, or LocalBusiness added only where the underlying facts genuinely exist on the page
  • Every block validated in the Rich Results Test and Schema.org Validator
  • No placeholder values left in production
  • Search Console structured data reports checked after the next recrawl

Schema markup is one of the few SEO tasks with a clear input and a visible output. You add the code, you validate it, and the result shows up in search. If your B2B site is leaving plain blue links on the table while competitors show ratings and breadcrumbs, that's a fixable gap, often in an afternoon.

If you'd rather have someone map the right schema types to your pages and wire it into your templates correctly, that's the kind of technical groundwork we handle for B2B clients. Get in touch for a short review of your current markup and where the quick wins are.