Has JSON-LD QuantitativeValue

This factor reports whether RankGear finds a JSON-LD QuantitativeValue type in a page’s raw HTML. It returns 1 when the source text contains an "@type": "QuantitativeValue" declaration and 0 when it does not. The important caveat: it pattern-matches source text rather than validating a structured-data graph, so it is an observation of what markup is present, not proof the schema is correct or that it lifts rankings.

What it measures

The factor reports whether RankGear finds an @type value of QuantitativeValue in the raw source. QuantitativeValue is the schema.org type for a measured or bounded quantity — a number paired with a unit and, often, a minimum and maximum — used to describe things like product dimensions, capacities, ratings ranges, or specification values in a machine-readable form.

How RankGear measures it

RankGear searches the raw HTML for the string "@type": "QuantitativeValue", allowing flexible whitespace around the colon and value and optionally allowing a schema: prefix on the type. Matching is case-insensitive, so capitalization differences do not affect detection. A match sets the value to 1; no match sets it to 0.

What RankGear looks for

"@type"\s*:\s*"(schema:)?QuantitativeValue"   (case-insensitive)

// e.g. a matching declaration in raw source:
{
  "@type": "QuantitativeValue",
  "value": 32,
  "unitCode": "INH",
  "minValue": 24,
  "maxValue": 40
}

How to optimize it

Use QuantitativeValue only for a genuine measured or bounded value, with an accurate number, unit, minimum, maximum, and reference context. Every property should reflect content users can actually verify on the page. Treat this factor as an observation of whether such markup exists, not a target to chase — adding the type where there is no real quantity to describe adds noise rather than value.

Important considerations

• The detector pattern-matches source text instead of validating a JSON-LD graph, so it confirms the string is present, not that the surrounding structured data is well-formed.
• A matching string that sits outside valid JSON-LD — in a comment, an example block, or malformed markup — can still produce 1.
• Capitalization differences do not affect detection; matching is case-insensitive.
• Validate the complete structured data independently with a schema validator before relying on it.
• Correlation is not causation: presence of this markup relates to position within a measured result set and is a prioritization signal — it does not by itself make a page rank.

Related factors

• Has JSON-LD PublicHealth
• Has JSON-LD Question

Part of the Factors reference · how RankGear measures · glossary.