This factor reports whether RankGear finds an InteractionCounter @type value in a page’s raw HTML source. It returns 1 when the string is present and 0 when it is not — a presence signal only, not a validation that the surrounding JSON-LD is well-formed.
| Factor ID | RG-SCJ-126 |
|---|---|
| Family | Structured Data – JSON-LD |
| Measurement | Binary presence (0 / 1) |
| Measured zone | Raw rendered HTML |
What it measures
This factor reports whether RankGear finds an @type value of InteractionCounter in the raw source. InteractionCounter is the schema.org type used to express a count of a specific interaction — likes, shares, views, comments — usually nested inside an interactionStatistic property. The check answers a single question: does that type appear in the markup or not.
How RankGear measures it
RankGear searches the raw HTML for the token "@type": "InteractionCounter", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not change the result. A match anywhere in the source returns 1; no match returns 0.
What RankGear looks for
"@type": "InteractionCounter"
"@type" : "schema:InteractionCounter" (prefix allowed, spacing flexible, case-insensitive)| Value | Meaning |
|---|---|
| 1 | An InteractionCounter @type token was found in the raw HTML. |
| 0 | No such token was found. |
How to optimize it
Use InteractionCounter only for an authentic interaction count that is tied to the correct interaction type and the correct item, and keep that count current and consistent with what visitors actually see on the page. Every property should reflect content users can verify. Treat this factor as an observation of whether the type is present, not a target to hit for its own sake — adding the markup without a real, matching interaction count is misrepresentation, not optimization.
Important considerations
- The detector pattern-matches source text; it does not parse or validate a JSON-LD graph.
- A matching string that sits outside valid JSON-LD — in a comment, an example, or malformed markup — can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently before relying on it; presence of the string is not proof of a valid graph.
- This is a prioritization signal that relates to position within a measured result set. Its presence correlates with, and does not cause or guarantee, any ranking outcome.
Related factors
Part of the Factors reference · how RankGear measures · glossary.