Has MicroData Text records whether RankGear finds the Microdata attribute itemprop="text" in a page’s rendered body HTML after script elements are removed. It returns 1 when the attribute is present at least once and 0 when it is not. This is a presence check on literal markup, not a validation of the underlying item graph, and it does not on its own move a page’s position.
| Factor ID | RG-SCM-045 |
|---|---|
| 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 attribute itemprop="text" appears in the rendered body of the page once script elements have been stripped out. The text property is the Microdata convention for marking the visible textual content of an item — for example the body of an answer, a comment, or a creative work — so its presence signals that a page is using inline Microdata to expose that content to parsers.
How RankGear measures it
RankGear performs a case-insensitive search of the rendered body HTML for the literal double-quoted form itemprop="text". It returns 1 when at least one match exists and 0 otherwise. The match is a raw string comparison: the attribute name, the equals sign, the double quotes, and the property value must be contiguous.
What RankGear looks for
<div itemscope itemtype="https://schema.org/Answer">
<div itemprop="text">The visible answer copy lives here.</div>
</div>
Matched literal (case-insensitive): itemprop="text"| Value | Meaning |
|---|---|
| 1 | The literal itemprop="text" was found at least once in the scripts-removed body HTML. |
| 0 | No contiguous double-quoted itemprop="text" match was found. |
How to optimize it
Use the text property only as part of the genuinely visible text of a marked-up creative work, answer, comment, or other eligible entity — not as an empty or decorative attribute. Keep its value aligned with the visible content on the page and with the vocabulary expected by its parent item type. Treat this factor as an observation about how a page is marked up rather than a target to chase: add itemprop="text" because the entity genuinely warrants it, not to satisfy the detector.
Important considerations
- The detector pattern-matches HTML text; it does not parse or validate a Microdata item graph.
- It requires the attribute name, equals sign, double quotes, and property value to be contiguous — single quotes or added spacing (for example
itemprop = "text"oritemprop='text') do not match. - Script elements are removed before matching, and capitalization does not affect detection.
- Validate the parent item type, property value, nesting, and structured-data eligibility independently — a match here says nothing about whether the Microdata is correct or eligible for rich results.
- This is a correlation-level signal within a measured result set. It relates to how pages in that set are marked up; it does not make a page rank or guarantee any position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.