2026 Structured Data Blueprint

The Ultimate QuantitativeValue
Schema Generator

A point value or interval for product characteristics and other purposes.

Includes:additionalPropertyadditionalTypealternateNamedescriptiondisambiguatingDescriptionidentifierimagemainEntityOfPage+12 more
Instant JSON-LD Generation

Magic Build

Paste your URL below and our AI will automatically fill the QuantitativeValue fields for you.

Configuration

Live Generator

QuantitativeValue Schema

Fill in the fields below to generate your JSON-LD. Required fields are marked with *.

Required Fields

The name of the item. (Expects: Text)

Recommended

An image of the item. This can be a [[URL]] or a fully described [[ImageObject]]. (Expects: ImageObject, URL)

URL of the item. (Expects: URL)

Why use QuantitativeValue?

Structured data like QuantitativeValue markup helps search engines identify the most important details about your content instantly, improving your chances of earning rich results.

Output Panel

Awaiting input...

Want to automate this?

Connect your site to SchemaGen and our AI will automatically extract and deploy schemas for you. No manual coding required.

Launch AI Generator

What is QuantitativeValue Schema?

A point value or interval for product characteristics and other purposes.

Why It Matters for SEO

Google uses QuantitativeValue structured data to understand the content and context of your pages. When correctly implemented, this schema can unlock rich results in Google Search — enhancing your listing with additional information that dramatically improves visibility and click-through rates.

Why Add QuantitativeValue Structured Data?

🔍

Appear in Rich Results

Structured data helps Google show enhanced results for your pages in search — including stars, prices, FAQs, and more.

📈

Boost Click-Through Rate

Rich snippets can increase CTR by up to 30% compared to plain search results — more clicks with the same ranking.

🤖

Feed AI Search Engines

AI answer engines like Perplexity and Google SGE use structured data to verify and cite facts from your content.

How to Implement QuantitativeValue JSON-LD

1

Generate

Use the form above to fill in your details and generate valid QuantitativeValue JSON-LD markup in seconds.

2

Copy

Copy the generated JSON-LD output code with one click — it's already formatted and ready to deploy.

3

Deploy

Paste the code into your <head> tag, or use SchemaGen's SDK to deploy without touching code.

Want to skip steps 2 & 3? Connect SchemaGen's SDK to deploy directly from the dashboard.

Properties You Can Include

QuantitativeValue schema supports the following schema.org properties. Required fields are the minimum Google needs to consider your markup valid; recommended fields unlock richer search result appearances.

PropertyDescriptionExpected TypeStatus
additionalPropertyA property-value pair representing an additional characteristic of the entity, e.g. a product feature or another characteristic for which there is no matching property in schema.org.\n\nNote: Publishers should be aware that applications designed to use specific schema.org properties (e.g. https://schema.org/width, https://schema.org/color, https://schema.org/gtin13, ...) will typically expect such data to be provided using those properties, rather than using the generic property/value mechanism.PropertyValueOptional
additionalTypeAn additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. Typically the value is a URI-identified RDF class, and in this case corresponds to the use of rdf:type in RDF. Text values can be used sparingly, for cases where useful information can be added without their being an appropriate schema to reference. In the case of text values, the class label should follow the schema.org style guide.Text, URLOptional
alternateNameAn alias for the item.TextOptional
descriptionA description of the item.Text, TextObjectOptional
disambiguatingDescriptionA sub property of description. A short description of the item used to disambiguate from other, similar items. Information from other properties (in particular, name) may be necessary for the description to be useful for disambiguation.TextOptional
identifierThe identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See [background notes](/docs/datamodel.html#identifierBg) for more details.PropertyValue, Text, URLOptional
imageAn image of the item. This can be a URL or a fully described ImageObject.ImageObject, URLRecommended
mainEntityOfPageIndicates a page (or other CreativeWork) for which this thing is the main entity being described. See [background notes](/docs/datamodel.html#mainEntityBackground) for details.CreativeWork, URLOptional
maxValueThe upper value of some characteristic or property.NumberOptional
minValueThe lower value of some characteristic or property.NumberOptional
nameThe name of the item.TextRequired
ownerA person or organization who owns this Thing.Organization, PersonOptional
potentialActionIndicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.ActionOptional
sameAsURL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website.URLOptional
subjectOfA CreativeWork or Event about this Thing.CreativeWork, EventOptional
unitCodeThe unit of measurement given using the UN/CEFACT Common Code (3 characters) or a URL. Other codes than the UN/CEFACT Common Code may be used with a prefix followed by a colon.Text, URLOptional
unitTextA string or text indicating the unit of measurement. Useful if you cannot provide a standard unit code for unitCode.TextOptional
urlURL of the item.URLRecommended
valueThe value of a QuantitativeValue (including Observation) or property value node.\n\n* For QuantitativeValue and MonetaryAmount, the recommended type for values is 'Number'.\n* For PropertyValue, it can be 'Text', 'Number', 'Boolean', or 'StructuredValue'.\n* Use values from 0123456789 (Unicode 'DIGIT ZERO' (U+0030) to 'DIGIT NINE' (U+0039)) rather than superficially similar Unicode symbols.\n* Use '.' (Unicode 'FULL STOP' (U+002E)) rather than ',' to indicate a decimal point. Avoid using these symbols as a readability separator.Boolean, Number, StructuredValue, TextOptional
valueReferenceA secondary value that provides additional information on the original value, e.g. a reference temperature or a type of measurement.DefinedTerm, Enumeration, MeasurementTypeEnumeration, PropertyValue, QualitativeValue, QuantitativeValue, StructuredValue, TextOptional

Example QuantitativeValue JSON-LD

Here's what valid QuantitativeValue structured data looks like with sample values filled in. Use the generator above to replace these with your own data.

Example Output
{
  "@context": "https://schema.org",
  "@type": "QuantitativeValue",
  "name": "Example QuantitativeValue",
  "image": "https://example.com/images/example.jpg",
  "url": "https://example.com/page",
  "additionalProperty": {
    "@type": "PropertyValue",
    "name": "Example PropertyValue",
    "image": "https://example.com/images/example.jpg",
    "url": "https://example.com/page"
  },
  "additionalType": "Example additionalType",
  "alternateName": "Example alternateName",
  "description": "A sample description for this QuantitativeValue.",
  "disambiguatingDescription": "Example disambiguatingDescription"
}

Validate Your QuantitativeValue Schema

Once deployed, validate your schema is working correctly with our free audit tool. Paste your URL and we'll check for errors, missing properties, and Google Rich Result eligibility.

Free Schema Audit Tool →

Check your QuantitativeValue schema for errors and Rich Result eligibility