This factor is a yes/no check: RankGear returns 1 when it finds the string "@type": "AchieveAction" in a page’s raw rendered HTML, and 0 when it does not. It is a raw-source pattern match, not a validator — a match anywhere in the source counts, even outside a valid JSON-LD script.
| Factor ID | RG-SCJ-004 |
|---|---|
| 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 AchieveAction in the page’s raw source. AchieveAction is a schema.org action type describing an agent achieving an objective — completing a goal, earning an award, or reaching a result. The factor answers one question only: is that type declared on the page? It does not judge whether the markup is correct, complete, or well-formed.
How RankGear measures it
RankGear searches the raw HTML for "@type": "AchieveAction", allowing flexible whitespace around the colon and optionally permitting a schema: prefix. The detector is case-insensitive and returns 1 on the first match, 0 otherwise. Because it reads raw source rather than a parsed graph, it looks for the literal string pattern — not a validated JSON-LD object.
What RankGear looks for
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "AchieveAction",
"agent": { "@type": "Person", "name": "..." },
"object": "...",
"result": "..."
}
</script>Matching is case-insensitive and tolerant of extra whitespace; a schema:AchieveAction form is also accepted.
| Value | Meaning |
|---|---|
| 1 | An AchieveAction type string was found in the raw HTML. |
| 0 | No matching string was found. |
How to optimize it
Use AchieveAction only when the page genuinely describes an action whose object, agent, and result can be represented accurately — for example a documented achievement, milestone, or completed goal. Treat the 1/0 value as an observation of what your markup declares, not a target to chase. Adding the type to a page that does not describe such an action inflates the signal without reflecting the content, which the detector cannot catch but which structured-data validators and search engines can.
Important considerations
- RankGear pattern-matches raw source; it does not parse or validate the JSON-LD graph, so a 1 confirms the string is present, not that the markup is valid.
- A matching string that sits outside a valid JSON-LD script — in a comment, a code sample, or inline text — can still produce 1.
- Capitalization differences do not affect this detector; it is case-insensitive.
- The type and all of its properties should accurately reflect the page’s visible content.
- This is a prioritization signal that relates to position within a measured result set. Its presence correlates with, and does not cause or guarantee, any ranking outcome.
Related factors
Part of the Factors reference · how RankGear measures · glossary.