This factor reports whether a page’s raw HTML contains a JSON-LD @type of MoveAction — a schema.org action describing an agent moving an object from an origin to a destination. It is a simple presence signal (1 or 0), and because RankGear matches the source text rather than parsing the JSON-LD graph, a match only means the string is present, not that the markup is valid.
| Factor ID | RG-SCJ-158 |
|---|---|
| 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 MoveAction in the page’s raw source. MoveAction is the schema.org type for describing a movement action — an agent relocating an object from an origin to a destination. The result is binary: the type is either present in the source (1) or it is not (0).
How RankGear measures it
RankGear searches the raw HTML for the @type declaration MoveAction, allowing flexible whitespace around the value and optionally accepting a schema: prefix. Matching is case-insensitive, so capitalization differences do not change the result. This is a text pattern match against the source, not a validation of the JSON-LD graph.
What RankGear looks for
"@type": "MoveAction"
// also matches, e.g.:
"@type":"schema:moveaction"| Value | Meaning |
|---|---|
| 1 | The MoveAction type string was found in the raw HTML. |
| 0 | No MoveAction type string was found in the raw HTML. |
How to optimize it
Use MoveAction only for a genuine movement action, with an accurate agent, object, origin, destination, status, and timing. Every property should reflect content that users can verify on the page. Treat this factor as an observation of what your markup contains rather than a target to chase: adding the string without a real, valid action behind it earns a 1 but describes nothing meaningful and risks structured-data errors elsewhere.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 confirms the string is present, not that the markup is well-formed.
- A matching string that sits outside valid JSON-LD — in a comment, code sample, or unrelated script — can still produce a 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently before relying on this signal.
- Presence of this markup correlates with, and is prioritized within, a measured result set; it does not by itself cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.