Seat

Seat is an Intangible for a reserved seat. It adds 4 direct properties:

seatNumber (Text): the seat position ("27", "14A").
seatRow (Text): row ("B").
seatSection (Text): section ("Orchestra", "Main cabin").
seatingType (QualitativeValue or Text): class ("Business", "Economy", "Premium").

Attach to a Ticket via ticketedSeat.

Full example of schema.org/Seat json-ld markup

The markup is verified as valid with Rich Results Test from Google.

Highlight legend:Required by GoogleRecommendedOptional

schema.org/Seat

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "FlightReservation",
  "reservationNumber": "XOO-7A9K2",
  "reservedTicket": {
    "@type": "Ticket",
    "ticketNumber": "XOO-TKT-4472881",
    "ticketedSeat": {
      "@type": "Seat",
      "seatNumber": "14A",
      "seatRow": "14",
      "seatSection": "Main cabin",
      "seatingType": "Economy (window)"
    }
  }
}
</script>

Minimal valid version

The smallest markup that still produces a valid Seat entity. Use it as the floor. Reach for the advanced example above when you want search engines and AI agents to understand more about your content.

schema.org/Seat (minimal)

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "Seat",
  "seatNumber": "14A",
  "seatSection": "Main cabin"
}
</script>

Google rich results this unlocks

Markup matching this example makes your page eligible for the following Google Search rich results. The primary target drives the required / recommended property classification in the advanced code block above.

Gmail reservation surfaces (via containing Ticket / Reservation)
Google docs

Common Seat mistakes

Mistakes that pass validation but silently fail to earn rich results or mislead consumers walking the graph. Avoid these and your markup will be ahead of most sites in the wild.

01
Seat details concatenated in a string
Wrong
```
ticketedSeat: "14A, main cabin, window"
```
Right
```
Typed Seat with seatNumber + seatSection + seatingType
```
Consumers parse structured seat fields for seat maps; concatenated strings are parsed loosely.

Schema properties in this example

Seat Intangible seatNumber seatRow seatSection seatingType Ticket ticketedSeat FlightReservation reservationNumber reservedTicket ticketNumber

About the example data

Jane Xoo's seat 14A on her XooAir flight to JFK.

Comments

Loading comments...