This factor reports whether RankGear finds a MonetaryAmount @type value in a page’s raw JSON-LD. It returns 1 when the string is present and 0 when it is not — but it matches source text, so a match does not confirm the surrounding structured data is valid.
| Factor ID | RG-SCJ-153 |
|---|---|
| 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 for MonetaryAmount in a page’s raw source. MonetaryAmount is the schema.org type used to describe a specific sum of money — a currency paired with an amount or a value range — typically nested inside an offer, a price specification, or a financial entity. The result is simply whether that type appears, not how well it is formed.
How RankGear measures it
RankGear searches the raw HTML for the string "@type": "MonetaryAmount", allowing flexible whitespace around the colon and an optional schema: prefix on the type name. Matching is case-insensitive, so capitalization differences do not change the result. Any match sets the value to 1; no match sets it to 0.
What RankGear looks for
<script type="application/ld+json">
{
"@type": "MonetaryAmount",
"currency": "USD",
"value": 49.00
}
</script>| Value | Meaning |
|---|---|
| 1 | A "@type": "MonetaryAmount" string (optionally schema:MonetaryAmount) was found in the raw HTML. |
| 0 | No such string was present in the raw HTML. |
How to optimize it
Use MonetaryAmount only for a genuine monetary value, with an accurate currency and a real amount or range, and a clear relationship to the offer or financial entity that encloses it. Every property should reflect content a user can verify on the page. Treat this factor as an observation of whether the markup exists, not a target to hit for its own sake — adding the type where no real monetary value applies helps nothing and can mislead validators.
Important considerations
- The detector pattern-matches source text rather than validating a full JSON-LD graph.
- A matching string that sits outside valid JSON-LD can still produce a 1.
- Capitalization differences do not affect detection.
- Validate the complete structured data independently — this factor confirms presence, not correctness.
- Presence correlates with pages in a measured result set; it is a prioritization signal, not a cause of ranking, and does not guarantee any position.
Related factors
Part of the Factors reference · how RankGear measures · glossary.