Has Schema Interaction Counter

Has Schema Interaction Counter reports whether the page’s body HTML contains the legacy Schema.org InteractionCounter type URI. It returns 1 when the string http://schema.org/InteractionCounter is found (case-insensitively) and 0 when it is not — a string-level detection of the old HTTP URI only, which does not validate the counts or the action they describe.

Factor IDRG-SCH-010
FamilySchema.org
MeasurementBinary presence (0 / 1)
Measured zoneBody HTML without scripts

What it measures

Has Schema Interaction Counter detects the legacy Schema.org InteractionCounter type URI in the page body. InteractionCounter is the Schema.org type used to record a count of a particular interaction — likes, shares, comments, views, and similar — alongside the action it counts. This factor reports only whether that type’s legacy identifier is present. A value of 1 means RankGear found the pattern; a value of 0 means it did not. Presence is a signal that the markup exists, not a judgment that the counts are meaningful, current, or correctly attributed.

How RankGear measures it

RankGear searches the body HTML, with scripts excluded, for the string http://schema.org/InteractionCounter case-insensitively. The match is on the legacy HTTP type URI exactly as written. The https:// form of the same URI and bare JSON-LD type names (for example an @type of InteractionCounter without the full HTTP URI) are not detected by this factor. No parsing of the surrounding markup, action type, or count value is performed — the detector reports the presence of the string alone.

What RankGear looks for

<span itemscope itemtype="http://schema.org/InteractionCounter">
  <meta itemprop="interactionType" content="http://schema.org/LikeAction">
  <meta itemprop="userInteractionCount" content="1203">
</span>
ValueMeaning
1The legacy http://schema.org/InteractionCounter URI was found in the body HTML (scripts excluded).
0The legacy URI was not found. The https:// form and bare JSON-LD @type names do not count here.

How to optimize it

Use InteractionCounter only for accurate, supportable interaction statistics tied to the proper action type — pair each counter with the interaction it truly represents (for example a LikeAction, ShareAction, or CommentAction) and a count you can stand behind. If your markup uses the modern https:// URI or a bare JSON-LD type, this legacy detector will read 0 even though your structured data is valid; that is expected. Read this factor as an observation of which URI form is present, not as a target that should push you back to the deprecated HTTP identifier.

Important considerations

  • HTTPS and bare JSON-LD types are not detected — only the legacy http://schema.org/InteractionCounter URI matches.
  • Counts and actions are not validated; the detector does not check whether the numbers or interaction types are correct.
  • Never fabricate engagement metrics — interaction counts should reflect real, supportable activity.
  • Presence alone provides no quality judgment about the page or its markup.
  • This factor relates to position within a measured result set — it is a prioritization signal, not a cause of ranking, and adding it does not by itself make a page rank.

Related factors

Part of the Factors reference · how RankGear measures · glossary.