This factor reports whether a page carries the Microdata attribute itemprop="interactionService" in its rendered body after scripts are stripped. It returns 1 when at least one contiguous, double-quoted match is present and 0 when none is found — a presence signal, not a validity check or a ranking guarantee.
| Factor ID | RG-SCM-019 |
|---|---|
| Family | Structured Data — Microdata |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Rendered body HTML with scripts removed |
What it measures
RankGear checks whether the Microdata property itemprop="interactionService" appears anywhere in the rendered body once <script> elements have been removed. The attribute is part of the schema.org Microdata vocabulary for describing the service or platform on which an interaction — a comment, share, like, or similar action — took place. This factor records presence only: it says the attribute string is there, not that the surrounding item graph is well formed.
How RankGear measures it
RankGear runs a case-insensitive search for the literal double-quoted form itemprop="interactionService". It returns 1 when at least one match exists and 0 otherwise. The match is a text search, not a Microdata parse: the attribute name, equals sign, double quotes, and property value must be contiguous.
What RankGear looks for
<span itemprop="interactionService" itemscope
itemtype="https://schema.org/WebSite">
<meta itemprop="name" content="Example">
</span>| Value | Meaning |
|---|---|
| 1 | The contiguous, double-quoted string itemprop="interactionService" was found at least once in the script-stripped body. |
| 0 | No matching string was found. The attribute may be absent, or it may use single quotes or added spacing that the pattern does not match. |
How to optimize it
Use interactionService only as part of the real service or platform on which the interaction occurred. Keep the value aligned with visible content and with the vocabulary expected by its parent item type. Treat this factor as an observation of what your markup already contains rather than a target to hit — adding the attribute where it does not describe a genuine interaction service adds no real structured-data value.
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 — a 1 here does not confirm valid or eligible markup.
- This is a prioritization signal that relates to patterns within a measured result set; it does not on its own make a page rank or guarantee any position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.