This factor reports whether RankGear finds an AssessAction @type in a page’s raw rendered HTML. 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 matching string anywhere in the source can register a 1.
| Factor ID | RG-SCJ-017 |
|---|---|
| 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 AssessAction in the raw source of the page. AssessAction is the schema.org action type for evaluating or judging an object — a review, rating, or assessment of something. The factor is a simple observation of whether that type appears in the markup, not a measure of how complete or correct the surrounding structured data is.
How RankGear measures it
RankGear searches the raw HTML for the @type key paired with the AssessAction value, tolerating flexible whitespace around the tokens and optionally allowing a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not affect the result. When a match is found the factor returns 1; otherwise it returns 0.
What RankGear looks for
"@type": "AssessAction"
"@type" : "schema:AssessAction" (schema: prefix allowed, case-insensitive)| Value | Meaning |
|---|---|
| 1 | An AssessAction @type string was found in the raw HTML. |
| 0 | No AssessAction @type string was found. |
How to optimize it
Use AssessAction only when the page genuinely represents an assessment action — with a real action, the object being assessed, the agent performing it, and the result it produces. Because RankGear pattern-matches source text rather than parsing the graph, this factor is best read as an observation of whether the markup is present, not a target to chase. Adding the type to a page that does not describe a real assessment adds no value and risks a mismatch with the visible content.
Important considerations
- RankGear pattern-matches source text rather than parsing or validating a JSON-LD graph.
- A matching string that sits outside a valid JSON-LD script — in a comment, a code sample, or inline copy — can still produce a 1.
- Capitalization differences do not affect detection; matching is case-insensitive.
- All structured data must match visible, truthful content on the page.
- Presence of this type relates to how pages are described within a measured result set; it is a prioritization signal, not a guarantee of ranking. Correlation is not causation.
Related factors
Part of the Factors reference · how RankGear measures · glossary.