PropertyValue is a Schema.org structured data type used to explicitly define a property-value pair, linking a characteristic name to its quantitative or qualitative value. It is commonly nested within additionalProperty to describe product specifications, technical features, or custom attributes, allowing search engines to parse specific details like a laptop's RAM capacity or a material's tensile strength.
Glossary
PropertyValue

What is PropertyValue?
Defining the PropertyValue type, a mechanism for pairing a property name with its specific value to describe product features, technical specifications, or custom attributes in a machine-readable format.
This type relies on the name property to define the characteristic and the value property to state its data; optional qualifiers like unitCode and unitText provide measurement context using UN/CEFACT codes. By disambiguating raw text into structured pairs, PropertyValue enables AI-driven search interfaces to confidently extract and compare entity attributes across different sources.
Key Properties of the PropertyValue Type
The PropertyValue type is a flexible Schema.org construct for defining custom property-value pairs. It enables precise specification of product features, technical attributes, and quantitative measurements that AI engines can parse as discrete, comparable data points.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Frequently Asked Questions
Clear, technically precise answers to the most common implementation questions about the PropertyValue structured data type, designed for engineers and CTOs building entity-rich product and specification markup.
The PropertyValue type is a Schema.org utility class designed to describe a discrete, structured property-value pair—a specific characteristic and its corresponding datum. It functions as a reusable, extensible container for expressing attributes that fall outside a defined schema's standard properties. The mechanism relies on three core fields: name (the property label, e.g., 'Fuel Efficiency'), value (the quantitative or qualitative datum, e.g., '25'), and unitText or unitCode (the unit of measure, e.g., 'MPG'). When a Product or Vehicle schema lacks a native field for a specification, a PropertyValue node is attached via the additionalProperty property, allowing search engines to parse highly granular, domain-specific technical specifications without requiring schema vocabulary extensions.
Related Terms
Understanding PropertyValue requires familiarity with the broader Schema.org ecosystem for entity description and structured data markup.
Product
The Product type is the most common parent context for PropertyValue. It represents any tangible item or intangible service offered for sale. PropertyValue pairs are typically nested within a Product's additionalProperty array to define technical specifications like weight, color, or material that don't have a dedicated Schema.org property.
StructuredValue
PropertyValue is a subtype of StructuredValue, a class used to represent values that are not simple strings or numbers but have a defined structure. Other StructuredValue subtypes include:
- QuantitativeValue: For values with a unit (e.g., 5 kg)
- MonetaryAmount: For values with a currency
- GeoCoordinates: For latitude/longitude pairs This inheritance means PropertyValue can be used wherever StructuredValue is expected.
DefinedTerm
When a PropertyValue describes a specification that has a formal definition in a controlled vocabulary or glossary, link it to a DefinedTerm. For example, if propertyID references an industry standard like an ISO code, a DefinedTerm can provide the canonical definition and context. This strengthens entity linking and disambiguation for AI parsers.
MeasurementUnitEnumeration
For quantitative specifications, PropertyValue should reference a unitCode using a standard enumeration like UN/CEFACT Common Codes. Schema.org provides MeasurementUnitEnumeration subtypes such as:
unitCode: "KGM"for kilogramsunitCode: "MMT"for millimetersunitCode: "H87"for pieces This ensures AI models correctly interpret and convert units across different contexts.
QualitativeValue
When a property doesn't have a numeric value but a descriptive one, use QualitativeValue instead of PropertyValue. For example, a product's 'durability' might be 'High' or 'Military-Grade'. QualitativeValue allows you to define:
- valueReference: A canonical entry in an enumeration
- additionalProperty: Further metadata about the qualitative assessment This distinction is critical for accurate entity salience optimization.
MerchantReturnPolicy
In e-commerce contexts, PropertyValue is often used within MerchantReturnPolicy to specify conditional properties like restocking fees or return windows. For instance, a propertyID of 'RestockingFee' with a value of '15%' can be structured as a PropertyValue pair within the policy's additionalProperty array, making return conditions machine-readable for AI shopping agents.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us