Published March 19, 2026
Blog posts are the most common content type on the web — and the content type most likely to already have some schema thanks to CMS platforms. But auto-generated blog schema is typically the bare minimum: title, date, maybe an author name. AI needs more than that to properly attribute, cite, and match blog content to user queries.
The difference between AI using your blog content and AI citing it comes down to whether AI can identify who wrote it, what it covers, and whether the source is credible.
A blog post with Article schema that includes the author, publication, topic, and date gives AI everything it needs for attribution. A post with only a title and date forces AI to infer the rest — and inference often means the content gets used without citation or passed over for a source with clearer data.
Blog posts also serve a secondary function for business sites: they give AI evidence of expertise. A service business publishing about commercial roofing best practices reinforces the signals from its homepage and service page schema.
For content sites, blog post schema is the core product. Every article is a potential citation, and the schema on each determines whether AI can cite it properly.
BlogPosting, NewsArticle, or Article — the content type helps AI match the right kind of content to the right kind of query. A user asking for expert analysis should get an article, not a news brief.
The headline and a structured description of what the article covers. This is how AI matches the content to topic-specific queries.
Who wrote it — name, credentials, and connection to the publishing organization. Particularly important for topics where authority matters.
The organization behind the article. This connects the blog post to the homepage Organization schema and helps AI assess the source's credibility.
When the article was published. AI uses this for recency matching — a user asking about current best practices should get recent content, not a five-year-old post.
What subject the article covers. Structured topic data helps AI match articles to specific queries rather than relying on keyword extraction from the body text.
Relying entirely on auto-generated schema. CMS platforms add basic Article schema — title, date, sometimes an author name. Author credentials, publisher identity, and topic classification are usually missing.
No author schema or generic attribution. A post attributed to "Admin" gives AI nothing to assess expertise with. Every post should have a real author with Person schema linked to the organization.
Missing publisher connection. Posts that do not reference the publishing organization are orphaned content AI cannot reliably attribute.
No topic or category classification. Structured classification makes matching more precise than inferring from body text.
Same schema on every post. Each post should have schema reflecting its specific content, author, and topic.
Mark up: Article type, title, description, author with credentials, publisher, publication date, topic or category.
Skip: Comment counts, social share counts, word counts, reading time estimates. These add complexity without adding citation value. Leaner schema means less noise for AI to parse and a clearer signal of what matters.
The AIFDS content blueprints include blog post and article page blueprints with the exact JSON-LD fields AI needs. Each blueprint connects the article back to the publishing organization via @graph, ensuring proper attribution.
For business blogs that support a service, healthcare, or other industry site, blog post schema is available within those industry blueprint families as well.
David Valencia writes about how AI systems find, parse, and cite websites.