Schema markup that maritime websites should be using (Service, Organization, Vessel)

Schema markup on most maritime corporate sites is either missing or copied from a template that doesn’t reflect the actual business. A ship management company with LocalBusiness schema. A shipping line with no Service markup at all. A port authority whose homepage schema describes a hotel because the developer reused a Squarespace block.

Three schema types do the heavy lifting on a maritime site. Get them right and you’ve covered 90% of what matters.

Organization schema (sitewide)

Every page on your site should reference your Organization. The minimum useful properties:

• name, legalName, url, logo
• address for each registered office, with PostalAddress nested properly
• sameAs linking to LinkedIn, Companies House, your wikipedia entry if you have one, your X/Twitter account and any registry IDs (IMO company number for shipowners, for example)
• contactPoint for each function (commercial, technical, agency desk)
• parentOrganization if you’re part of a group, so Google understands the corporate structure

That sameAs block is doing more work than people realise. It’s how Google’s knowledge graph reconciles the same entity across data sources, and it’s how an LLM working from web data knows that “Acme Marine Services Ltd” on your site is the same entity as “Acme Marine” in TradeWinds and “Acme Marine Group” in Lloyd’s List.

Service schema (on every service page)

A service page without Service schema is a service page that LLMs and AI search struggle to categorise. Each service page should declare:

• name of the service (be specific: “Technical management of LNG carriers”, not “ship management”)
• provider referencing your Organization
• serviceType mapped to a recognisable industry term
• areaServed listing the geographies where you actually operate
• audience describing who the service is for (fleet operators, charterers, equipment manufacturers)

For maritime services the areaServed field is genuinely valuable. If you do drydock supervision in Singapore, Rotterdam and Houston but not in Mumbai, list those three places. AI search will use it; static “global” claims it won’t.

BreadcrumbList (sitewide)

BreadcrumbList schema is the cheapest schema win on most maritime sites. It clarifies hierarchy for crawlers and produces clean breadcrumb display in Google results. If your CMS doesn’t generate it automatically, hand-roll it on the templates that matter most: services, case studies, regional pages.

Where the Vessel question gets interesting

If you publish per-vessel pages, fleet pages or technical specs, structured data starts to matter more. There’s no fully formalised Vessel type in schema.org, but you can extend Vehicle with cargo-specific properties or use Product for vessels treated commercially (sale, charter listing). Marine Insight and Splash both publish vessel pages that Google clearly understands as distinct entities; both rely on consistent structured data and clean URL patterns.

For most operators, named entities in your text (vessel names, IMO numbers, classification society references) plus solid Organization and Service schema is enough. Don’t over-engineer schema before the basics are right.

How to validate

Use Google’s Rich Results Test for individual URLs. Use Schema.org’s validator for syntax. For a sitewide check, crawl with Screaming Frog’s structured data extraction enabled and look for missing or malformed schema across the templates that matter.

Schema isn’t glamorous and it doesn’t make pages rank by itself. What it does is make the machines that decide what to show your buyers actually understand who you are. That’s worth a couple of hours of developer time on every maritime site.