This factor reports whether RankGear finds a JSON-LD OrganizeAction type in a page’s raw HTML. It returns a simple present-or-absent signal (1 or 0) — and because it pattern-matches source text rather than parsing a structured-data graph, a match only confirms the string is on the page, not that your JSON-LD is valid.
| Factor ID | RG-SCJ-191 |
|---|---|
| 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 OrganizeAction in the raw source. OrganizeAction is a schema.org action type describing the act of organizing an object — its presence tells the analyzer that the page declares this specific action in its markup. The result is a binary observation: the type is either found (1) or not found (0).
How RankGear measures it
RankGear searches the raw HTML for the @type declaration of OrganizeAction, tolerating flexible whitespace around the key and value and optionally allowing a schema: prefix. Matching is case-insensitive, so capitalization differences do not affect the result.
What RankGear looks for
"@type": "OrganizeAction"
// also matches, e.g.:
"@type":"organizeaction" // case-insensitive
"schema:@type": "OrganizeAction" // optional schema: prefix| Value | Meaning |
|---|---|
| 1 | An OrganizeAction @type string was found in the raw HTML. |
| 0 | No OrganizeAction @type string was found. |
How to optimize it
Use OrganizeAction only for a genuine organizing action, with an accurate agent, object, result, status, and timing. Make sure every property reflects content users can verify on the page. Treat this factor as an observation of what your markup declares, not a target to chase — adding the string without a real organizing action serves no reader and risks misrepresenting the page.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a match confirms presence of the string, not correctness of the structured data.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or plain text — can still produce a 1.
- Capitalization differences do not affect detection, since matching is case-insensitive.
- Validate the complete structured data independently with a schema.org or Google validator; this factor does not do that for you.
- Presence of this markup correlates with pages in a measured result set — it is a prioritization signal, not a guarantee of ranking, and does not on its own cause a page to rank.
Related factors
Part of the Factors reference · how RankGear measures · glossary.