This factor reports whether RankGear finds an @type value of UpdateAction in a page’s raw HTML. It is a binary presence check (1 or 0) run against source text, not a validation of the JSON-LD graph — so a matching string can register even when it sits outside valid structured data.
| Factor ID | RG-SCJ-261 |
|---|---|
| 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 UpdateAction in the raw source. UpdateAction is a schema.org action type describing the act of updating an object — the agent doing the update, the object being updated, and details such as collection, result, status, and timing. The check answers a single yes/no question: is that action type declared anywhere in the page’s HTML?
How RankGear measures it
RankGear searches the raw HTML for "@type": "UpdateAction", allowing flexible whitespace around the colon and optionally permitting a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not affect the result. It is a text pattern match against source, not a parse of the JSON-LD graph.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "UpdateAction",
"agent": { "@type": "Person", "name": "..." },
"object": { "@type": "Article", "name": "..." }
}
</script>
"@type" : "schema:updateaction"| Value | Meaning |
|---|---|
| 1 | The UpdateAction type string was found in the raw HTML. |
| 0 | No matching UpdateAction type string was found. |
How to optimize it
Use UpdateAction only for a genuine update action, with an accurate agent, object, collection, result, status, and timing. Ensure every property reflects content users can actually verify on the page. Treat this factor as an observation of what your markup contains, not a target to chase — adding the type string without a real, verifiable update behind it does not help, and mismatched or fabricated structured data can undermine trust in your markup.
Important considerations
- The detector pattern-matches source text instead of validating a JSON-LD graph.
- A matching string that sits outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection — matching is case-insensitive.
- Validate the complete structured data independently with a schema validator; this factor does not confirm your JSON-LD is well-formed or eligible for rich results.
- Presence of this action type correlates with, and is a prioritization signal within, a measured result set — it does not on its own cause or guarantee a ranking.
Related factors
Part of the Factors reference · how RankGear measures · glossary.