This factor reports whether the page carries the Microdata attribute itemprop="upvoteCount". RankGear returns 1 when it finds that exact double-quoted string anywhere in the rendered body after scripts are stripped, and 0 when it does not. It is a text match on markup, not a validation that the up-vote count is correct or that the surrounding item graph is well formed.
| Factor ID | RG-SCM-047 |
|---|---|
| Family | Structured Data — Microdata |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Rendered body HTML with scripts removed |
What it measures
This factor reports whether RankGear finds the Microdata attribute itemprop="upvoteCount" in the rendered body after script elements are removed. The upvoteCount property is the Schema.org vocabulary used to mark up the number of up-votes on a contribution — for example a comment, an answer, or a forum reply. Its presence signals that the page annotates community endorsement in a machine-readable way.
How RankGear measures it
RankGear performs a case-insensitive search for the literal double-quoted form itemprop="upvoteCount". It returns 1 when at least one match exists and 0 otherwise. The check runs against the rendered body with script elements removed; capitalization does not affect the result.
What RankGear looks for
<div itemprop="interactionStatistic" itemscope itemtype="https://schema.org/InteractionCounter">
<meta itemprop="interactionType" content="https://schema.org/LikeAction" />
<meta itemprop="userInteractionCount" content="128" />
</div>
<span itemprop="upvoteCount">128</span>| Value | Meaning |
|---|---|
| 1 | The string itemprop="upvoteCount" appears at least once in the script-stripped body. |
| 0 | The string is absent — or present only in a form the detector does not match (see considerations). |
How to optimize it
Use upvoteCount only as part of the authentic number of up-votes associated with the marked-up contribution. Keep the value aligned with visible content and with the vocabulary expected by its parent item type. Treat this factor as an observation of whether that markup is detectable, not as a target to chase: adding the attribute where no genuine up-vote count exists inflates the signal without reflecting real engagement, and can conflict with structured-data guidelines.
Important considerations
- The detector pattern-matches HTML text instead of parsing or validating a Microdata item graph.
- It requires the attribute name, equals sign, double quotes, and property value to be contiguous; single quotes or added spacing do not match.
- 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 is a prioritization signal that relates to position within a measured result set. It does not by itself cause a page to rank, and its presence guarantees nothing about position — correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.