Is Schema Markup for Travel Itineraries a thing?

Looking for answers to structure individual voyages.

[TechNoob]

Hey Guys - I'm looking for additional optimization opportunities for my cruise client's website, and I have been circling back to world of Schema and the magic therein.

I understand different markups exist for Events, Products, Services, etc., but I'm trying to understand which I can utilize for individual voyages/itineraries, if it is even possible. Since guests can book different rooms on different decks, there are also around 6 different possibilities of pricing, along with the WAITLIST option for sold out room types. Or course, itineraries include multiple ports of call, date ranges, excursions, etc etc - it's exactly what you would expect.

For the record, I've been using [searchengineland.com...] as a reference point, aside from the official [schema.org...] site, but I feel overwhelmed as I have not done enough markups in my career to know, so I'd like to ask for you guys for guidance.

Can Schema Markup work for an individual Voyage?

[keyplyr]

The first thing I would do is study the mark-ups at other successful cruise & airline sites. Are they using the schema vocabulary? If so... how and for which utilities.

[not2easy]

There are some Schema tools in links at the bottom of the page. You can take a look at the fields for the different types of schema markup and see if your data might fit in one of those? It largely depends on what is on the page. If there are different pages for each of the options then they might fit in product schema? I don't use them myself, so not much help, sorry.

[TechNoob]

It seems if I am able to use Schema for voyages, the most logical/relevant Schema is Event (although Product is a close second).

I used the Schema Tool on the bottom of the page of WW and came up with the following:

<div itemscope itemtype="http://schema.org/Event">
<meta itemprop="description" content="[Destination] to [Destination] | [Date] to [Date] | 7 Days | [Vessel Name] | [Voyage ID]">
<meta itemprop="startDate" content="YYYY-MM-DDTXX:XX">
<meta itemprop="endDate" content="YYYY-MM-DDTXX:XX">
<link itemprop="url" href="http://www.mydomain.com/voyage-url" rel="author"/>
<a itemprop="url" href="http://www.mydomain.com/voyage-url"><span itemprop="name" style="display:block;"><strong>[Voyage Title]</strong></span></a>
</div>

It's worth noting I have a developer who can implement dynamic values to pick the information up from the page itself (date, time, voyage name, etc)

@keyplyr - I'm not noticing any travel sites marking up individual events, although [schemaapp.com...] tells me Schema isn't exactly as widely practiced as it should be. I don't believe I should be looking at the way flights are set up either.

Do you think I should proceed?

[not2easy]

It looks like it might be fairly easy to find out. You can complete the schema markup manually and run a few tests, both with Google's Rich Schema Markup Testing Tool [search.google.com] and then see it in action using Fetch as Google in your GSC. If it doesn't kick up a fuss, you can submit that page as a trial to see whether it sees improvement. Testing anything is much more accurate if the sample size is more than one page, but I would limit it until some indicators tell you whether it is helping or not.

[keyplyr]

@TechNoob - I suggested looking at other sites in your niche, or close to it, because there's a reason for the term "industry standard."

Flights of course would be much busier than cruises I assume, but the on-page mark-up may show techniques you can use. Just an idea.

[TechNoob]

@Keyplyr - I have checked about 5 competitors and other indirect competitors but there doesn't seem to be an industry standard as I see it. I see organization and other basic schemas, but nothing for individual itineraries.

When I search "cruise" on Schema.org, it refers me to Offer or Ticket. Wordstream's blog gives me the impression I may have to add to Schema's vocabulary.

It's dissuading, but I feel oddly determined to make this happen somehow