Has MicroData Article Body is a boolean signal that returns 1 when RankGear finds the Microdata attribute itemprop="articleBody" in the rendered, script-free body HTML, and 0 when it does not. It is a literal text match on that exact double-quoted form — it does not parse or validate the surrounding Microdata item, so a 1 confirms only that the string is present, not that the markup is correct or eligible for rich results.
| Factor ID | RG-SCM-007 |
|---|---|
| Family | Structured data — Microdata |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Rendered body HTML with scripts removed |
What it measures
This factor reports whether the Microdata property itemprop="articleBody" appears in the page’s rendered body after script elements are stripped out. In the schema.org vocabulary, articleBody marks the main textual content of an Article item, so its presence indicates the page has annotated its article copy with Microdata. RankGear treats this as a simple presence check: the attribute is either found in the measured body, or it is not.
How RankGear measures it
RankGear performs a case-insensitive search of the rendered body for the literal, double-quoted form itemprop="articleBody". Scripts are removed before the search runs. It returns 1 when at least one match exists and 0 otherwise. Because the match is literal, the attribute name, equals sign, double quotes, and property value must appear contiguously — single quotes or extra spacing around the equals sign will not match.
What RankGear looks for
<div itemscope itemtype="https://schema.org/Article">
<div itemprop="articleBody">
… the visible main body of the article …
</div>
</div>| Value | Meaning |
|---|---|
| 1 | The literal string itemprop="articleBody" was found at least once in the rendered, script-free body (matched case-insensitively). |
| 0 | The string was not found — including cases where articleBody is present but written with single quotes, extra spacing, or only inside a removed script. |
How to optimize it
Use articleBody only as part of the visible main body of a genuine article, and keep the markup aligned with the content readers actually see. Ensure the property belongs to a parent item whose type expects it — typically a schema.org Article or one of its subtypes — and use the standard double-quoted attribute form so the detector recognizes it. Treat this factor as an observation about how the page is annotated rather than a target to chase: adding the attribute where no real article body exists misrepresents the page and does nothing useful.
Important considerations
- The detector pattern-matches HTML text rather than parsing or validating a Microdata item graph, so a 1 does not confirm the markup is well-formed or complete.
- The match requires the attribute name, equals sign, double quotes, and property value to be contiguous; single quotes or added spacing will not match and will read as 0.
- Scripts are removed before matching, and capitalization does not affect detection.
- Validate the parent item type, property value, nesting, and structured-data eligibility independently — this factor does not check any of those.
- This is a correlation-based prioritization signal within a measured result set, not a cause of ranking — the presence of
articleBodyMicrodata does not make a page rank or guarantee position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.