Schema Markup for Blog Posts - Which Types Matter and How to Add Them (2026)

Schema markup tells search engines and AI systems what a page is about in a structured way. A few well-chosen types cover most blog posts.

The Short Version

For most blog posts, Article (or BlogPosting) and BreadcrumbList schema are the essentials, plus Organization and WebSite at site level. Add FAQPage where you have a genuine FAQ section and Product details only when facts are visible and verified. Use JSON-LD, keep markup consistent with the visible page, and validate it before publishing. Never mark up ratings or claims that aren't real.

What Schema Markup Is

Schema markup is structured data, usually added as a small block of JSON-LD code, that describes a page using a shared vocabulary from Schema.org. It tells search engines things like "this is an article, written by this organisation, published on this date, sitting in this section of the site".

It doesn't directly boost rankings, but it helps search engines understand your content and can make pages eligible for enhanced search features. It also gives AI systems a cleaner summary of what each page contains.

The Essential Types for Blog Posts

Illustration for the section The Essential Types for Blog Posts on the Schema Markup for Blog Posts page
Common Schema Types for Blogs
TypeUse onWhat it describes
Article / BlogPostingEvery blog postHeadline, description, author or publisher, dates, image
BreadcrumbListEvery page with breadcrumbsThe page's position in your site hierarchy
OrganizationSite-wideYour publication's name, logo and URL
WebSiteSite-wideSite name and URL
FAQPagePosts with a visible FAQ sectionQuestion and answer pairs
Product / OfferReviews and pricing pages with verified detailsProduct name, offers and prices shown on the page
ItemListRoundups and ranked listsThe ordered items on the page

A Simple Article Example

Here's what basic Article markup looks like in JSON-LD. It sits in a script tag in the page's HTML:

{
  "@context": "https://schema.org",
  "@type": "Article",
  "headline": "How to Descale a Coffee Machine",
  "description": "Step-by-step descaling for home coffee machines.",
  "datePublished": "2026-03-10",
  "dateModified": "2026-11-01",
  "author": { "@type": "Organization", "name": "Example Coffee Guide" },
  "publisher": { "@type": "Organization", "name": "Example Coffee Guide" },
  "mainEntityOfPage": "https://example.com/descale-coffee-machine/"
}

Use real values that match the visible page: the same headline, the same dates, the same publisher.

FAQ Schema: Useful but Limited

FAQPage markup describes question-and-answer content. Google has limited FAQ rich results to a small set of well-known, authoritative sites, so most blogs won't see FAQ snippets in search results. The markup can still help machines understand your Q&A content, as long as the questions and answers are visible on the page.

Only mark up genuine FAQs. Don't add questions to schema that aren't shown to readers.

Product and Review Schema: Be Careful

Illustration for the section Product and Review Schema: Be Careful on the Schema Markup for Blog Posts page

Product markup can describe products and offers on review and pricing pages. Include only details that are visible and accurate, such as the product name and current prices shown on the page.

Avoid AggregateRating or review ratings unless they come from a genuine, verifiable source. Invented ratings break structured data guidelines and damage trust. If you don't have real ratings, leave them out entirely.

Koala's SEO Agent on Professional can help manage schema across your site. Try Koala free to see the workflow.

Try Koala Free

How to Add Schema to Your Site

  1. Use an SEO plugin if you're on WordPress. Most add Article, Breadcrumb and Organization schema automatically.
  2. Add custom JSON-LD for page-specific types like FAQPage or ItemList, either through your plugin or a script block.
  3. Keep values consistent with the visible headline, dates and content.
  4. Validate with Google's Rich Results Test and the Schema.org validator.
  5. Monitor Search Console for structured data errors and warnings.

Schema Rules to Follow

Match Visible Content

Markup should describe what readers can see on the page.

Be Specific and Truthful

Pick the most accurate type for each page.

No Fake Data

Never invent ratings, prices, authors or reviews.

Stay Consistent

Use the same organisation name and URLs everywhere.

Illustration for the section Schema and AI Search on the Schema Markup for Blog Posts page

Structured data helps machines interpret your pages consistently, which can support how AI systems understand and summarise your content. Google has also said pages don't need special markup to appear in its AI features beyond being indexed and eligible for snippets. So treat schema as a helpful clarity layer, not a shortcut. Clear, accurate content remains the main factor. See generative engine optimisation.

Common Schema Mistakes

  • Marking up content that isn't visible on the page.
  • Adding fake or unverifiable ratings.
  • Using the wrong type, such as Product on a general guide.
  • Mismatched dates or headlines between schema and page.
  • Duplicate or conflicting markup from several plugins.
  • Never validating after changes.

Schema as Part of Your Publishing Checklist

Treat schema as a standard step rather than a one-off project. Every new post should get the right markup automatically from your template or plugin, with page-specific types added where relevant. Our on-page SEO checklist includes schema alongside the other pre-publish checks.

Schema for Different Page Types

Illustration for the section Schema for Different Page Types on the Schema Markup for Blog Posts page
Suggested Schema by Page Type
Page typeSuggested types
Standard blog postArticle or BlogPosting, BreadcrumbList
Post with FAQsArticle, BreadcrumbList, FAQPage
Best-of roundupArticle, BreadcrumbList, ItemList
Review or pricing pageArticle, BreadcrumbList, Product with verified offers
HomepageWebSite, Organization

Start with the basics and add specific types only where the page genuinely contains that kind of content.

If you use a CMS with an SEO plugin, check what it already outputs before adding your own markup, so you do not end up with duplicate or conflicting schema on the same page. One clean, accurate set of structured data is better than several overlapping ones.

Re-validate after theme or plugin updates, since these can change the markup without warning.

A quick check after every major site change keeps your structured data clean and trustworthy over time.

Keep Content and Structure in Sync

Use Koala to produce well-structured articles with FAQs and clear headings that map neatly onto schema. Start on the free plan.

Try Koala Free

Frequently Asked Questions

What schema should a blog post have?
Article or BlogPosting plus BreadcrumbList, with Organization and WebSite at site level. Add FAQPage for genuine FAQs.
Does schema improve rankings?
Not directly. It helps search engines understand pages and can make them eligible for enhanced features.
Should you use FAQ schema?
You can for genuine, visible FAQs, but most sites won't see FAQ rich results in Google.
Can you add review stars to your own reviews?
Only with genuine, verifiable ratings. Invented ratings break guidelines and damage trust.
How do you test schema markup?
Use Google's Rich Results Test and the Schema.org validator, then check Search Console for errors.