Content Schema: Article, BlogPosting, HowTo
Session 8.5 · ~5 min read
Entity Schema vs. Content Schema
Module 5 covered entity schema: Organization, Person, LocalBusiness. These describe who you are. Content schema is different. It describes what you have published. Article, BlogPosting, HowTo, FAQPage, and other content types tell Google exactly what kind of content each page contains and connect it to the entity that created it.
Entity schema and content schema work together. Your Organization schema says "We are PT Arsindo Perkasa." Your Article schema on a blog post says "This article was written by John Smith, who works for PT Arsindo Perkasa, and it was published on this date about this topic." The combination creates a chain from entity to content.
Entity schema establishes identity. Content schema establishes what that identity has produced. Both are needed for Google to associate content authority with your entity.
Choosing the Right Content Type
Each content page should use the most specific schema type that applies.
| Schema Type | Use For | Rich Result Potential |
|---|---|---|
| Article | News articles, feature articles, investigative pieces | Top stories carousel, article snippet |
| BlogPosting | Blog posts, opinion pieces, updates | Article snippet with date and author |
| HowTo | Step-by-step tutorials, installation guides, processes | Step-by-step rich result in search |
| FAQPage | FAQ pages with question-answer pairs | Expandable FAQ dropdown in search results |
| TechArticle | Technical documentation, specifications, API docs | Article snippet (same as Article) |
| Review | Product or service reviews | Star ratings in search results |
BlogPosting is a subtype of Article. If your content is a blog post, use BlogPosting. If it is a formal article (industry analysis, research piece), use Article. Both inherit the same properties, but BlogPosting is more specific.
Article / BlogPosting Schema Structure
A complete Article or BlogPosting schema includes both content metadata and entity connections:
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"headline": "How to Size a Centrifugal Pump for Industrial Use",
"description": "A practical guide to centrifugal pump sizing...",
"image": "https://yourcompany.com/images/pump-sizing.jpg",
"datePublished": "2026-03-15",
"dateModified": "2026-03-20",
"author": {
"@type": "Person",
"@id": "https://yourcompany.com/about/john-smith/#person"
},
"publisher": {
"@type": "Organization",
"@id": "https://yourcompany.com/#organization"
},
"mainEntityOfPage": "https://yourcompany.com/blog/pump-sizing-guide/"
}The author and publisher properties create the entity-to-content links. The @id references connect to your existing Person and Organization schema without duplicating data.
The Entity-Content Connection Map
@id: /#organization"] -->|publisher| A1["Article: Pump Sizing Guide"] O -->|publisher| A2["Article: Maintenance Best Practices"] O -->|publisher| A3["HowTo: Install a Centrifugal Pump"] P["Person Schema
@id: /about/john/#person"] -->|author| A1 P -->|author| A2 P2["Person Schema
@id: /about/sarah/#person"] -->|author| A3 P -->|worksFor| O P2 -->|worksFor| O style O fill:#222221,stroke:#c8a882,color:#ede9e3 style P fill:#222221,stroke:#6b8f71,color:#ede9e3 style P2 fill:#222221,stroke:#6b8f71,color:#ede9e3
HowTo Schema
HowTo schema is particularly valuable because it can trigger a step-by-step rich result that occupies significant visual space in search results. Each step is a distinct element with a name and description.
HowTo works best for content that is genuinely procedural: installation guides, setup tutorials, maintenance procedures. Do not force HowTo schema onto content that is not actually step-by-step. Google will ignore or penalize misused schema.
FAQPage Schema
FAQPage schema triggers expandable question-and-answer rich results. Each FAQ item gets its own row in search results, dramatically increasing your SERP real estate. However, Google has reduced FAQ rich results in recent updates, showing them primarily for authoritative government and health websites. They still provide structured data value even when the visual rich result does not appear.
| Schema Type | When to Use | When NOT to Use |
|---|---|---|
| Article / BlogPosting | Any written content with an author and publication date | Product pages, category pages, homepages |
| HowTo | Step-by-step procedural content | Opinion pieces, general articles, non-procedural guides |
| FAQPage | Pages with genuine Q&A pairs users actually ask | Pages where you invented questions to stuff keywords |
Validation and Common Errors
After implementing content schema, validate every page using Google's Rich Results Test. Common errors include:
- Missing required properties (headline, author, datePublished for Article)
- Invalid date format (must be ISO 8601: YYYY-MM-DD)
- Author or publisher referencing a non-existent @id
- Using Article schema on pages that are not articles (product pages, navigation pages)
Content schema is the bridge between your entity and your published work. Without it, Google sees your content but cannot confirm who created it or what type of content it is.
Further Reading
- Article structured data documentation - Google's official Article schema guide
- HowTo structured data documentation - Google's HowTo schema implementation guide
- FAQPage structured data documentation - Google's FAQ schema guide with eligibility updates
- Organization Schema Markup: Complete Guide - Stackmatix on connecting content schema to entity schema
Assignment
Audit your content pages. For each, determine the correct schema type (Article, BlogPosting, HowTo, FAQPage). Check whether that schema is implemented. For your 5 highest-traffic content pages, write or update the schema with all required properties: headline, description, image, datePublished, dateModified, author (referencing your Person @id), and publisher (referencing your Organization @id). Validate each using the Rich Results Test.