Structured Data for Content in 2026: What Schema Markup Still Does (and What It Doesn’t)

Published January 25, 2026 · Updated October 4, 2026 · By the FreelanceWriter.net editorial team

Structured data is one of the most over-promised topics in SEO. It is useful — it makes pages eligible for rich results and gives search engines an unambiguous description of what a page is — but it is not a ranking boost, and there is no special markup that gets content into AI answers. This guide separates what schema markup reliably does from what it is often claimed to do.

What structured data is

Structured data is machine-readable information about a page, written in the schema.org vocabulary. Instead of a crawler inferring that a block of text is a recipe, a product or an article by a particular author, the page states it explicitly. Search engines accept three syntaxes — JSON-LD, Microdata and RDFa — and Google recommends JSON-LD because it sits in a single script block, separate from the visible HTML, which makes it easier to maintain.

What it does — and doesn't — do

It does:

Make a page eligible for specific rich results (review snippets, product details, breadcrumbs, recipes, events, videos and others), provided the page meets that feature's guidelines.
Remove ambiguity about entities: who published a page, who wrote it, which organisation a logo belongs to, what a product's price is.
Feed merchant, video and other specialised surfaces that depend on precise data.

It doesn't:

Act as a general ranking factor. Google has said repeatedly that markup helps it understand a page and enables rich results, not that it ranks pages higher.
Guarantee a rich result. Eligibility is not entitlement; Google decides whether to show one.
Make thin content useful. Markup describes the page; it cannot improve it.

Be wary of precise-sounding claims such as "rich snippets raise click-through by X%". Click-through effects depend heavily on the query, the feature and the competition on the page, and most published figures come from vendor case studies that are hard to generalise.

Structured data and AI answers

Content teams now ask whether schema markup helps them appear in Google's AI Overviews and AI Mode, Bing's Copilot answers, or tools like ChatGPT and Perplexity. The honest answer:

Google states that there are no additional technical requirements, and no special schema, for appearing in its AI features. The same fundamentals apply: the page must be indexable and eligible for a snippet, and structured data should match the visible content.
Microsoft has said publicly that schema markup helps its systems, including the models behind Bing's AI answers, understand content. That is a reason to keep markup accurate, not evidence of a direct citation boost.
Third-party assistants mostly read the visible page text (or a search index built from it). Clear headings, direct answers and well-sourced facts in the body matter more there than anything in a script tag.

In other words, structured data supports machine understanding; it is not a lever for "AI visibility" on its own. The content still has to be the best answer.

Schema types worth using on content sites

Type	Use it for	Notes
`Article` / `BlogPosting`	Blog posts, guides, news	Google lists no required properties; `headline`, `author`, `datePublished`, `dateModified` and `image` are recommended.
`Organization`	Home or About page	Name, logo, URL, `sameAs` links to official profiles. Helps logo and knowledge panel understanding.
`Person`	Author pages	Pair with real author bios. Markup for an author who has no visible bio is pointless.
`BreadcrumbList`	Any page with a hierarchy	Can replace the URL path with a readable trail in results.
`Product`, `Review`	Product and review pages	Reviews must be genuine and visible on the page; self-serving reviews of your own business are not eligible for review snippets.
`VideoObject`	Pages where a video is the main content	Enables video features and key moments.
`Event`, `Recipe`, `JobPosting`	Their specific page types	Each has strict guidelines; read them before marking up.

Rich results that have been restricted or retired

Much schema advice online is out of date. Several features writers were once told to target no longer work the way they did:

FAQ rich results — since August 2023 Google shows them only for well-known, authoritative government and health sites. FAQPage markup elsewhere is harmless but will not produce the expandable snippet.
HowTo rich results — removed from Google Search in 2023.
Several niche features — in 2025 Google announced it was phasing out a group of lesser-used rich results, including ClaimReview, Course Info, Estimated Salary, Learning Video, Special Announcement, Book Actions and Vehicle Listing.
speakable — has only ever been a beta for news publishers and has never been a general "voice search" lever.

Check Google's Search Gallery for the current list of supported features before investing in a markup project.

Implementation: JSON-LD examples

A minimal, valid BlogPosting block. Every value must match what a reader sees on the page:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "BlogPosting",
  "headline": "How to Write a Content Brief That Gets Used",
  "datePublished": "2026-05-12",
  "dateModified": "2026-10-04",
  "author": {
    "@type": "Person",
    "name": "Jane Example",
    "url": "https://example.com/authors/jane-example"
  },
  "publisher": {
    "@type": "Organization",
    "name": "Example Co",
    "logo": { "@type": "ImageObject", "url": "https://example.com/logo.png" }
  },
  "image": "https://example.com/images/content-brief.jpg"
}
</script>

Use @id references so that the same organisation or author is described once and referenced everywhere:

{
  "@context": "https://schema.org",
  "@graph": [
    { "@type": "Organization", "@id": "https://example.com/#org",
      "name": "Example Co", "url": "https://example.com/" },
    { "@type": "BlogPosting", "headline": "…",
      "publisher": { "@id": "https://example.com/#org" } }
  ]
}

For templated sites, generate the block from the same data that renders the page — title, dates, author — so the two can never drift apart.

Testing and monitoring

Rich Results Test (Google) — checks eligibility for Google's supported features on a live URL or code snippet.
Schema Markup Validator (validator.schema.org) — checks general schema.org validity, including types Google does not use for rich results.
Search Console enhancement reports — show errors and valid items at scale after deployment.
Bing Webmaster Tools — its URL inspection and markup validation show how Bing reads the page.

Re-test after template changes; a broken theme update is the most common reason markup silently disappears.

Common mistakes

Marking up content that isn't visible. Reviews, FAQs or prices that appear only in the JSON-LD violate the guidelines and can lead to a manual action.
Fabricated ratings. An aggregateRating with no real reviews behind it is the classic example of spammy markup.
Stale dates. Bumping dateModified without changing the content is misleading; leaving it unchanged after a real update wastes a freshness signal.
Wrong type. Marking a category page as a Product or a service page as a Recipe because a plugin defaulted to it.
Duplicate, conflicting blocks from a theme and a plugin describing the same page differently.
Broken URLs in logo, image or url properties.

Bottom line. Add accurate Article, Organization and BreadcrumbList markup across a content site, add specialised types only where the page genuinely is that thing, and spend the rest of the effort on the content itself.

Structured Data for Content in 2026: What Schema Markup Still Does (and What It Doesn’t)

What structured data is

What it does — and doesn't — do

Structured data and AI answers

Schema types worth using on content sites

Rich results that have been restricted or retired

Implementation: JSON-LD examples

Testing and monitoring

Common mistakes

Related