By Milod · 19 August 2026 · 1 min read · Technical

The schema every blog post should ship

The handful of structured-data fields worth adding, what each one does, and where people get them wrong.

Structured data doesn't make a page rank. It makes a page legible: it tells search engines and extractors what the page is, who published it and when it last changed. That legibility is what earns rich results and makes a page easier to quote.

The minimum worth shipping

• Article (or BlogPosting): headline, description, datePublished, dateModified, author, publisher.
• Organization on the site level, with the logo and a stable @id the articles reference.
• BreadcrumbList, so the path shows in results instead of a raw URL.
• FAQPage only when the page really does answer those questions on-page.

dateModified is the one people fake

Bumping dateModified without changing the content is a habit that gets sites ignored. Set it from the real edit, and make the edit visible in the text: a changed number, a new section, a removed claim.

Keep JSON-LD and the page in agreement

If the schema says the author is someone the page never mentions, or the headline differs from the H1, you have given a machine two stories. Generate the JSON-LD from the same data that renders the page, so they can't drift apart.

Validate with Google's Rich Results Test after any template change. Most schema bugs arrive with a redesign, not with the original build.