Article schema is used on pages with under 300 words, making them ineligible for article rich results.
By Seoxpert Editorial · Published
Google expects substantial content for Article or BlogPosting schema to qualify for rich results. Using Article schema on thin content can lead to wasted crawl resources and may undermine Google's trust in your structured data, potentially affecting eligibility for enhancements across your site.
Pages may not be eligible for article rich results and could reduce the perceived quality of your structured data.
An automated crawler checks for Article or BlogPosting schema on pages and flags those with fewer than 300 words of visible content.
Incorrect: Article schema on thin content
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Short Update",
"articleBody": "Just a quick note."
}Correct: Remove Article schema, use WebPage
{
"@context": "https://schema.org",
"@type": "WebPage",
"name": "Short Update"
}Correct: Article schema with sufficient content
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "In-Depth Analysis of Market Trends",
"articleBody": "This article provides a comprehensive overview of current market trends... (400+ words)"
}Google uses Article schema to enhance search results for substantial articles. Thin content does not meet their guidelines for rich results.
If the update is under 300 words, it's best to use WebPage schema instead, as it likely won't qualify for article rich results.
No, removing inaccurate Article schema improves your structured data quality and avoids misleading search engines.
Aim for at least 400-600 words to meet typical expectations for article rich results.
Run a scan to see if Article Schema on Thin Content Pages affects your pages.
Scan my website →