Article Schema Guide
Good article schema helps search engines understand what your page is, who wrote it, when it was published, and which image best represents it. This guide shows how to choose the right article type, write cleaner JSON-LD, avoid misleading markup, and test your implementation before publishing.
What this guide solves
PracticalWhat article schema actually does
Article schema is structured data that helps search engines understand the main article entity on the page. It gives clearer signals about the article headline, author, dates, and images, and it helps connect the markup to the visible content users see on the page.
This does not mean every article page will automatically earn a special search appearance. Article schema improves clarity and eligibility, but Google still decides how to present the result based on many factors.
The real value of article schema is not just search appearance. It is implementation discipline. When your title, author, publish date, modified date, and main image are all modeled cleanly, the page becomes easier for search engines and publishing teams to interpret consistently.
Valid markup, poor page alignment
The JSON-LD exists, but the author is missing, the dates are unclear, the image is a logo, or the schema describes content that is not actually visible on the page.
Clean markup tied to visible content
The schema reflects the real article headline, authors, dates, and representative image, and the page is easy to validate and maintain over time.
When to use Article, BlogPosting, or NewsArticle
Broad default choice
Best when the page is clearly an article, but not strongly tied to blog-style publishing or time-sensitive news reporting.
Best for blog-style posts
A strong fit for company blogs, educational articles, editorial posts, and knowledge content published in a blog format.
Best for real news reporting
Use this when the page reports news or provides journalism-style context around current events and time-sensitive developments.
For most business blogs and knowledge-center content, BlogPosting is usually the safest practical choice. Use NewsArticle only when the page genuinely behaves like news content, not just because it sounds more important.
The properties that matter most on real article pages
Author data is one of the easiest places to get article schema wrong
If your page shows one or more authors, your markup should include those same authors. If the page shows two authors, the schema should not collapse them into one text string or omit one of them.
Use the right type for the author. Use Person for a person and Organization for an organization. If possible, link the author to a real profile page or another valid identifying URL.
"author": {
"name": "Jane Doe, John Doe"
}
"author": [
{
"@type": "Person",
"name": "Jane Doe",
"url": "https://example.com/authors/jane-doe/"
},
{
"@type": "Person",
"name": "John Doe",
"url": "https://example.com/authors/john-doe/"
}
]
Keep author.name clean. Do not mix in publisher names, job titles, or phrases like “posted by” inside the name field.
Date handling should be accurate, not cosmetic
Article markup is stronger when publish and modified dates are accurate and meaningful. The publish date should reflect when the article first went live. The modified date should reflect the most recent meaningful update, not a trivial template change.
Use ISO 8601 datetime values and include timezone information so the signals remain precise and consistent.
"datePublished": "2026-03-23T09:30:00+08:00", "dateModified": "2026-03-24T14:10:00+08:00"
You updated the article with new examples, new screenshots, and revised recommendations, so the modified date changed.
The CMS changed a related-widget block or a footer, so the modified date changed even though the article content did not.
Image quality matters more than many teams expect
The image property should point to an image that represents the article itself. A site logo, unrelated decorative art, or a category badge is usually a weak choice for article markup.
A strong implementation uses crawlable, indexable, relevant images and, where possible, provides multiple high-resolution aspect ratios for better flexibility.
The main article cover image that appears in the article header.
The company logo, a watermark graphic, or a generic placeholder image reused sitewide.
Provide high-resolution 16:9, 4:3, and 1:1 versions when possible.
"image": [ "https://example.com/uploads/article-cover-1x1.jpg", "https://example.com/uploads/article-cover-4x3.jpg", "https://example.com/uploads/article-cover-16x9.jpg" ]
A practical JSON-LD example for a business blog article
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "BlogPosting",
"mainEntityOfPage": {
"@type": "WebPage",
"@id": "https://example.com/blog/article-schema-guide/"
},
"headline": "Article Schema Guide for Business Blogs",
"description": "Learn how to implement Article schema with better author, date, and image markup.",
"image": [
"https://example.com/uploads/article-schema-guide-1x1.jpg",
"https://example.com/uploads/article-schema-guide-4x3.jpg",
"https://example.com/uploads/article-schema-guide-16x9.jpg"
],
"datePublished": "2026-03-23T09:30:00+08:00",
"dateModified": "2026-03-24T14:10:00+08:00",
"author": [
{
"@type": "Person",
"name": "Lulu Cheng",
"url": "https://example.com/authors/lulu-cheng/"
}
],
"publisher": {
"@type": "Organization",
"name": "SEO Kit Lab",
"logo": {
"@type": "ImageObject",
"url": "https://example.com/uploads/logo.png"
}
}
}
</script>
A professional workflow for article schema rollout
Choose the right article type
Decide whether the page is best modeled as Article, BlogPosting, or NewsArticle.
Match the visible content
Make sure the headline, image, authors, and dates in markup match what users see on the page.
Use JSON-LD cleanly
Keep the block readable, complete, and easy to maintain in your CMS or template layer.
Validate before scale
Test representative pages first instead of rolling out broken markup sitewide.
Inspect live pages
Check how Google sees the live URL and confirm that images and structured data remain accessible.
Review after publishing updates
If author data, dates, or image logic changes, re-check that the structured data still matches the page.
Article schema mistakes that weaken implementation quality
Using the wrong type for the page
Not every blog post is a NewsArticle, and not every editorial page needs the most specific-looking label.
Schema does not match visible content
If the schema claims a different title, author, or image than the page shows, quality trust drops fast.
Merged author names in one field
Multiple authors should be modeled as separate entries, not one combined name string.
Using logos as the article image
The image should represent the article content, not just the site brand.
Changing modified dates without real editorial updates
This weakens trust in the date signals and makes the field less meaningful.
Assuming valid schema guarantees a rich result
Structured data improves understanding and eligibility, but display decisions remain Google’s choice.
Quick article schema QA before publishing
- The page uses the right article type.
- The headline in markup matches the visible article title.
- The image URLs are valid, crawlable, and relevant.
- Dates are in ISO 8601 format with timezone.
- Authors are modeled correctly and individually where needed.
- The marked-up content is visible on the page.
- The article image is not just a site logo or decorative badge.
- The author shown on the page matches the schema author.
- The publish and updated dates are editorially accurate.
- The page can be fetched and validated by testing tools.
Validate syntax first, then validate truthfulness. A schema block can pass a tool and still be weak if it does not represent the real page well.
Frequently asked questions
Should I use Article or BlogPosting for a company blog?
In most cases, BlogPosting is the cleaner fit for a standard company blog article. Article is still valid as a broader default.
Do I need both datePublished and dateModified?
You do not always need both for every workflow, but using both accurately usually makes the article clearer and more useful as structured data.
Can I use the company name as the author?
Yes, when the content is genuinely authored by an organization rather than an individual, but the type and visible page presentation should support that choice.
Does article schema guarantee better search results?
No. It can help Google understand the page better and support eligibility, but it does not guarantee a rich result or any particular display style.
Should the schema description match the meta description exactly?
Not necessarily word for word, but they should align closely enough that the page presents one consistent story.
What if my article has multiple authors?
List each author separately in the author array and make sure the visible page credits match the structured data.
Turn schema theory into a repeatable article publishing workflow
Pair your article schema template with a consistent author model, strong article images, and a QA pass on every major content type so the markup stays accurate as the site scales.