Has MicroData Interaction Type reports whether the Microdata attribute itemprop="interactionType" appears anywhere in a page’s rendered body once script elements are stripped. It returns 1 when at least one match is found and 0 otherwise — a presence flag, not a validation of your structured data.
| Factor ID | RG-SCM-021 |
|---|---|
| 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="interactionType" in the rendered body after script elements are removed. Microdata expresses schema.org properties as HTML attributes on visible markup, and interactionType is the property that names the kind of user interaction an interaction-counter describes — for example a view, a like, or a share. A value of 1 means the attribute is present somewhere in the measured zone; it says nothing about whether the surrounding item type or property value is correct.
How RankGear measures it
RankGear performs a case-insensitive search for the literal double-quoted form itemprop="interactionType". It returns 1 when at least one match exists and 0 otherwise. The check is a text pattern match against the rendered body — it does not parse or validate a Microdata item graph.
What RankGear looks for
<span itemprop="interactionType">https://schema.org/WatchAction</span>The attribute name, equals sign, double quotes, and the value interactionType must be contiguous. Single quotes (itemprop='interactionType') or added spacing around the equals sign do not match, and capitalization does not affect detection.
| Value | Meaning |
|---|---|
| 1 | At least one contiguous, double-quoted itemprop="interactionType" was found in the rendered body after scripts were removed. |
| 0 | No matching attribute was found — the markup is absent, uses single quotes or extra spacing, or lives only inside a stripped script block. |
How to optimize it
Use interactionType only as part of a genuine interaction counter, where it names the correct kind of user interaction represented by an authentic count. Keep the value aligned with visible content and the vocabulary expected by its parent item type. Treat this factor as an observation of whether the attribute is detectable, not as a target to chase: adding the attribute where it does not belong, or inflating interaction counts to justify it, works against the structured data it is meant to describe.
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 confirms presence, not correctness.
- 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.