2026 Structured Data Blueprint

The Ultimate Order
Schema Generator

An order is a confirmation of a transaction (a receipt), which can contain multiple line items, each represented by an Offer that has been accepted by the customer.

Includes:acceptedOfferadditionalTypealternateNamebillingAddressbrokerconfirmationNumbercustomerdescription+27 more

Instant JSON-LD Generation

Start Generating Sign up for Bulk Tools

Magic Build

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

Configuration

Live Generator

Why use Order?

Structured data like Order 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 Order Schema?

An order is a confirmation of a transaction (a receipt), which can contain multiple line items, each represented by an Offer that has been accepted by the customer.

Why It Matters for SEO

Google uses Order 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 Order 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 Order JSON-LD

Generate

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

Copy

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

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

Order 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.

Property	Description	Expected Type	Status
acceptedOffer	The offer(s) -- e.g., product, quantity and price combinations -- included in the order.	Offer	Optional
additionalType	An 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, URL	Optional
alternateName	An alias for the item.	Text	Optional
billingAddress	The billing address for the order.	PostalAddress	Optional
broker	An entity that arranges for an exchange between a buyer and a seller. In most cases a broker never acquires or releases ownership of a product or service involved in an exchange. If it is not clear whether an entity is a broker, seller, or buyer, the latter two terms are preferred.	Organization, Person	Optional
confirmationNumber	A number that confirms the given order or payment has been received.	Text	Optional
customer	Party placing the order or paying the invoice.	Organization, Person	Optional
description	A description of the item.	Text, TextObject	Optional
disambiguatingDescription	A 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.	Text	Optional
discount	Any discount applied (to an Order).	Number, Text	Optional
discountCode	Code used to redeem a discount.	Text	Optional
discountCurrency	The currency of the discount.\n\nUse standard formats: [ISO 4217 currency format](http://en.wikipedia.org/wiki/ISO_4217), e.g. "USD"; [Ticker symbol](https://en.wikipedia.org/wiki/List_of_cryptocurrencies) for cryptocurrencies, e.g. "BTC"; well known names for [Local Exchange Trading Systems](https://en.wikipedia.org/wiki/Local_exchange_trading_system) (LETS) and other currency types, e.g. "Ithaca HOUR".	Text	Optional
identifier	The 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, URL	Optional
image	An image of the item. This can be a URL or a fully described ImageObject.	ImageObject, URL	Recommended
isGift	Indicates whether the offer was accepted as a gift for someone other than the buyer.	Boolean	Optional
mainEntityOfPage	Indicates 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, URL	Optional
merchant	'merchant' is an out-dated term for 'seller'.	Organization, Person	Optional
name	The name of the item.	Text	Required
orderDate	Date order was placed.	Date, DateTime	Optional
orderDelivery	The delivery of the parcel related to this order or order item.	ParcelDelivery	Optional

Example Order JSON-LD

Here's what valid Order 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": "Order",
  "name": "Example Order",
  "image": "https://example.com/images/example.jpg",
  "url": "https://example.com/page",
  "acceptedOffer": {
    "@type": "Offer",
    "name": "Example Offer",
    "image": "https://example.com/images/example.jpg",
    "url": "https://example.com/page"
  },
  "additionalType": "Example additionalType",
  "alternateName": "Example alternateName",
  "billingAddress": {
    "@type": "PostalAddress",
    "name": "Example PostalAddress",
    "image": "https://example.com/images/example.jpg",
    "url": "https://example.com/page"
  },
  "broker": {
    "@type": "Organization",
    "name": "Example Organization",
    "image": "https://example.com/images/example.jpg",
    "url": "https://example.com/page"
  }
}

Validate Your Order 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 Order schema for errors and Rich Result eligibility

SchemaGen

The Ultimate Order Schema Generator