RankGear checks whether the rendered page contains the Microdata attribute itemprop="userInteractionCount" and returns 1 when it finds it, 0 when it does not. It is a literal, case-insensitive text match — not a validation of the Microdata item graph — so a match confirms the string is present, not that the interaction count is accurate or eligible for rich results.
| Factor ID | RG-SCM-018 |
|---|---|
| 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="userInteractionCount" in the rendered body once script elements have been stripped out. This is the Microdata property Schema.org uses to state how many times users interacted with an item — watches, likes, shares, comments — typically on the InteractionCounter that accompanies content such as videos, articles, or social posts. The factor is a plain presence check: it tells you the attribute string appears somewhere in the rendered markup, nothing more.
How RankGear measures it
RankGear performs a case-insensitive search for the literal double-quoted form itemprop="userInteractionCount". It returns 1 when at least one match exists and 0 otherwise. The attribute name, equals sign, double quotes, and property value must be contiguous for the search to match; scripts are removed before the search runs, and capitalization is ignored.
What RankGear looks for
<meta itemprop="userInteractionCount" content="1200">| Value | Meaning |
|---|---|
| 1 | At least one literal itemprop="userInteractionCount" match in the rendered body. |
| 0 | No match — the attribute is absent, or written with single quotes or added spacing that breaks the contiguous pattern. |
How to optimize it
Treat this as an observation of markup presence, not a target to game. Use userInteractionCount only as part of an authentic user-interaction count that the page or its underlying data actually supports. Keep the markup aligned with visible content and with the vocabulary expected by its parent item type — the attribute belongs on an InteractionCounter nested under the item it describes. If your interaction data is already expressed in JSON-LD, adding a redundant Microdata copy purely to satisfy this string match adds no genuine value.
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 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 — a match here says nothing about whether the markup is valid or rich-result eligible.
- This is a prioritization signal that relates to position within a measured result set. It does not, on its own, cause or guarantee a ranking — correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.