.svg)
articleBody
articleBody · Not mentioned by Google
Appears in
What is it?
articleBody contains the full text content of an article. It is a plain text field that stores the article's body copy inside the structured data block. In practice, most implementations omit this field because search engines already read the visible page content.
Why this matters for AEO
AI answer engines extract information from visible page content, not from articleBody in structured data. Including the full article text in JSON-LD does not give AI engines additional information they cannot already access from the HTML. For this reason, articleBody provides minimal AEO benefit for most implementations.
What the specs say
Schema.org: Text. The actual body of the article. schema.org/articleBody
Google: Not mentioned. articleBody does not appear in Google's Article structured data documentation. Google Article docs
Google Search Central community threads confirm that Googlebot reads page content regardless of whether articleBody is present in structured data.
How to find your value
- Article page — The main body text between the headline and footer
- CMS — The rich text or long text field containing the article
- Webflow — The Rich Text field in your blog post collection
Format and code
Type: Text (string)
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "How to Implement Schema Markup",
"articleBody": "Schema markup helps search engines understand your content. This guide covers the basics of JSON-LD implementation..."
}
Most SEO practitioners recommend omitting articleBody from JSON-LD. Including the full article text bloats the script tag without providing search engine benefit, since Googlebot parses the visible HTML content directly.
If used, keep it to a summary sentence rather than the full article. The schema.org example on the NewsArticle page (BBC News) includes articleBody as a short excerpt, not the complete text.
Webflow implementation
Static pages
Not recommended. If needed, add a brief summary:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"headline": "Your Article Title",
"articleBody": "Brief summary of the article content."
}
</script>
CMS template pages
If including articleBody, reference the CMS rich text field. Note that Webflow CMS field references in custom code output plain text, stripping HTML:
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Article",
"articleBody": "{{wf {"path":"post-body","type":"PlainText"} }}"
}
</script>
In Schema HQ
By default, the articleBody field is not included by default, following the industry best practice of letting search engines parse visible page content directly.
Real examples
BBC News (bbc.com):
{
"@type": "NewsArticle",
"headline": "Trump Russia claims: FBI's Comey confirms investigation of election 'interference'",
"articleBody": "Director Comey said..."
}
BBC uses a truncated summary in articleBody, not the full article text.
AirOps (airops.com) :
{
"@type": "Article",
"headline": "A Comprehensive Guide to Blog Schema Markup",
"articleBody": "This comprehensive guide explores the intricacies of implementing schema markup in your blog, enhancing visibility and engagement."
}
Related fields
FAQ
Should I include articleBody in my Article schema?
For most sites, no. Google does not require or recommend it, and Googlebot reads the visible page content directly. Including the full article text in JSON-LD adds unnecessary page weight. If you choose to include it, use a brief summary rather than the complete text.
Does articleBody affect search rankings?
No. Google does not use articleBody structured data for ranking. Content quality and relevance are determined from the visible page HTML, not from JSON-LD fields.
