2026 Structured Data Blueprint

The Ultimate Ticket
Schema Generator

Used to describe a ticket to an event, a flight, a bus ride, etc.

Includes:additionalTypealternateNamedateIssueddescriptiondisambiguatingDescriptionidentifierimageissuedBy+13 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 Ticket fields for you.

Configuration

Live Generator

Why use Ticket?

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

Used to describe a ticket to an event, a flight, a bus ride, etc.

Why It Matters for SEO

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

Generate

Use the form above to fill in your details and generate valid Ticket 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

Ticket 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
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
dateIssued	The date the ticket was issued.	Date, DateTime	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
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
issuedBy	The organization issuing the item, for example a Permit, Ticket, or Certification.	Organization	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
name	The name of the item.	Text	Required
owner	A person or organization who owns this Thing.	Organization, Person	Optional
potentialAction	Indicates a potential Action, which describes an idealized action in which this thing would play an 'object' role.	Action	Optional
priceCurrency	The currency of the price, or a price component when attached to PriceSpecification and its subtypes.\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
sameAs	URL 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.	URL	Optional
subjectOf	A CreativeWork or Event about this Thing.	CreativeWork, Event	Optional
ticketedSeat	The seat associated with the ticket.	Seat	Optional
ticketNumber	The unique identifier for the ticket.	Text	Optional
ticketToken	Reference to an asset (e.g., Barcode, QR code image or PDF) usable for entrance.	Text, URL	Optional
totalPrice	The total price for the reservation or ticket, including applicable taxes, shipping, etc.\n\nUsage guidelines:\n\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.	Number, PriceSpecification, Text	Optional
underName	The person or organization the reservation or ticket is for.	Organization, Person	Optional

Example Ticket JSON-LD

Here's what valid Ticket 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": "Ticket",
  "name": "Example Ticket",
  "image": "https://example.com/images/example.jpg",
  "url": "https://example.com/page",
  "additionalType": "Example additionalType",
  "alternateName": "Example alternateName",
  "dateIssued": "2026-08-01",
  "description": "A sample description for this Ticket.",
  "disambiguatingDescription": "Example disambiguatingDescription"
}

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

SchemaGen

The Ultimate Ticket Schema Generator