This factor reports whether RankGear finds a TransferAction @type value in a page’s raw HTML source. It returns 1 when the string is present and 0 when it is not — it is a text match, not a validated JSON-LD graph, so a stray match outside real structured data can still register a 1.
| Factor ID | RG-SCJ-256 |
|---|---|
| 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 TransferAction in the raw source. TransferAction is the schema.org action type used to describe the movement of an object — money, goods, or ownership — from one party to another. The check is a straightforward yes/no: the markup is either present in the source or it is not.
How RankGear measures it
RankGear searches the raw HTML for a "@type": "TransferAction" declaration, allowing flexible whitespace around the colon and an optional schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect detection. The result is 1 when a match is found anywhere in the source and 0 otherwise.
What RankGear looks for
"@type": "TransferAction"
"@type" : "schema:TransferAction" (optional prefix, flexible spacing, case-insensitive)| Value | Meaning |
|---|---|
| 1 | A TransferAction @type string was found in the raw HTML source. |
| 0 | No matching TransferAction string was present. |
How to optimize it
Use TransferAction only for a genuine transfer action, and describe it accurately: agent, recipient, object, origin, destination, status, and timing. Every property should reflect content a user can verify on the page. Because RankGear matches the source string rather than validating the graph, adding the markup is only worthwhile when it truly describes the page — treat the presence of this markup as a description of what the page contains, not as a target to chase.
Important considerations
- The detector pattern-matches source text; it does not validate a JSON-LD graph.
- A matching string that sits outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently — this check confirms presence, not correctness.
- This is a correlation-based prioritization signal within a measured result set. Presence of the markup relates to position; it does not by itself make a page rank or guarantee a result.
Related factors
Part of the Factors reference · how RankGear measures · glossary.