This factor reports whether RankGear finds a JSON-LD CreateAction type in a page’s raw HTML source. It is a binary presence signal — 1 when the string is matched, 0 when it is absent — and because it pattern-matches source text rather than validating a structured-data graph, a 1 confirms the markup is present, not that it is valid.
| Factor ID | RG-SCJ-064 |
|---|---|
| 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 CreateAction in the page’s raw source. CreateAction is a Schema.org action type describing the act of creating something — an agent producing an object, optionally with an instrument and a result. The check answers a single yes/no question: does this markup appear in the delivered HTML?
How RankGear measures it
RankGear searches the raw HTML for a flexible-whitespace match around "@type": "CreateAction", optionally allowing a schema: prefix on the type value. Matching is case-insensitive, so capitalization differences do not affect the result. It reads the raw source rather than a parsed JSON-LD graph, so the signal reflects the presence of the string pattern, not the validity of the surrounding structured data.
What RankGear looks for
"@type": "CreateAction"
"@type" : "schema:CreateAction" ← schema: prefix allowed
"@TYPE":"createaction" ← case-insensitive, flexible whitespace| Value | Meaning |
|---|---|
| 1 | A CreateAction type string was matched in the raw HTML. |
| 0 | No matching string was found in the raw HTML. |
How to optimize it
Use CreateAction only for a genuine creation action, with an accurately represented agent, object, instrument, and result, and with properties that match the page’s visible content. Treat the detection as an observation of what your markup contains, not a target to chase — adding the string without a real, correct action behind it invites the mismatch problems below rather than any benefit.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph, so a 1 means the string appears, not that the structured data is well-formed.
- A matching string that sits outside valid JSON-LD — in a comment, a code sample, or a script block — can still produce a 1.
- Capitalization differences do not affect detection; the match is case-insensitive.
- Validate the complete structured data independently with a dedicated tool before relying on it.
- This is a prioritization signal that relates to positions within a measured result set. It does not cause ranking and does not guarantee a position — correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.