Schema Markup for Blogs: What Still Earns Rich Results in 2026 (and What Quietly Died)

Schema markup — structured data describing your content in machine-readable JSON-LD — occupies a strange place in blog SEO. It is genuinely useful, it is cheap to implement, and half the advice written about it describes rich results Google stopped showing years ago. This guide covers what each schema type actually does for a blog in 2026, what got deprecated, and why markup quietly matters more in the AI-answer era even as some of its visible rewards shrank.

First, the ground rule Google has repeated for years: schema is not a ranking factor. It changes how your results can be displayed and helps machines understand your pages — both valuable, neither a rankings lever. Anyone selling schema as a way to rank higher is selling something else.

The types worth having on every post

Article

The baseline for any blog post: headline, author, publisher, published and modified dates. Article markup makes you eligible for enhanced presentation in Google's article surfaces, and — increasingly the bigger payoff — gives AI systems clean, unambiguous answers to "who wrote this, who published it, when, and when was it updated." Those are exactly the provenance and freshness signals that AI engines weigh when choosing citations. Keep the dates honest: marking stale content as fresh is the fastest way to teach machines to distrust your markup.

BreadcrumbList

Simple, unglamorous, still fully supported: breadcrumb markup replaces the raw URL in your search snippet with a readable path and helps Google understand your site's structure. If your blog is organized in topic clusters, breadcrumbs express that hierarchy explicitly.

Organization (and Person for authors)

Site-level markup declaring who you are — name, logo, URL, and sameAs links to your profiles elsewhere. This is entity plumbing: it helps Google and AI engines connect your domain to a coherent identity they can trust and cite. Author-level Person markup does the same for the humans behind posts, which feeds directly into E-E-A-T signals.

The types that changed — know before you copy old advice

FAQPage: still worth writing, no longer a SERP badge

In 2023 Google restricted FAQ rich results — the expandable Q&A dropdowns in listings — to a small set of authoritative government and health sites. For a normal blog, FAQ markup no longer decorates your snippet. So why do our posts still carry it, visible FAQ section and matching markup together? Because the Q&A format itself is what wins now: question-shaped, self-contained answers are the most extractable passages on a page — prime material for AI Overviews, chat citations, and People Also Ask. The markup labels them unambiguously for machines at near-zero cost. Write the FAQ for extraction; treat the schema as free labeling, not a display feature. (Google's policy either way: the Q&A must be visible on the page, never markup-only.)

HowTo: deprecated

Google removed HowTo rich results entirely in late 2023. Existing markup does no harm, but adding it to new posts buys nothing — structure your tutorials with clear numbered steps in the visible content instead, which is what both readers and AI extraction actually consume.

Implementation in ten minutes

• Use JSON-LD in a script tag — Google's recommended format. Never mark up content that is not visible on the page.
• Check your platform first. Good platforms emit Article, breadcrumb, and Organization markup automatically — Ghost does, WordPress does via SEO plugins, and it is a line-item in our CMS SEO requirements. Verify before hand-writing anything.
• Validate with Google's Rich Results Test, and watch Search Console's enhancement reports for errors after deploying.
• Do not stack irrelevant types. Marking a blog post as Product or Review to chase stars is a manual-action risk, not a growth hack.

DraftRank handles this layer automatically — every generated post ships with Article markup and a visible FAQ section backed by FAQPage JSON-LD — because schema is exactly the kind of correct-but-tedious work automation should own.