Schema.org for Maritime Websites: A Practical Guide

You can have the most authoritative maritime services website in your sector, and Google still might not understand what you do. Your potential clients might search for exactly what you offer, in exactly the geography you serve, and your site will not appear. Not because you lack credibility. Not because you lack content. But because your website has not told search engines and AI systems what it is in the language they are designed to read.

Schema.org markup is that language. It is a standard vocabulary for describing things on the web in a structured, machine-readable format. Implemented correctly, it transforms your website from a document that search engines have to interpret into one that explicitly declares what it is, what it does, who it serves, and where it operates. For maritime companies operating in a B2B environment where buyers are increasingly using AI-assisted search to find and evaluate service providers, schema markup is not optional. It is infrastructure.

This guide covers the specific schema types that matter for maritime businesses, the exact properties you need to include in each, how to implement them using JSON-LD (the format Google recommends), how to test your implementation, and how to keep it maintained over time.

What Schema.org Actually Is

Schema.org is a collaborative project founded in 2011 by Google, Microsoft, Yahoo, and Yandex. The four largest search engines at the time agreed on a shared vocabulary for structured data: a standardised set of types (Organisation, Person, Place, Service, Event, Product, and hundreds more) and properties (name, description, location, telephone, knowsAbout, and so on) that webmasters could use to describe their content in a format that all search engines could process consistently.

The vocabulary is implemented as structured data embedded in your HTML, typically using a format called JSON-LD (JavaScript Object Notation for Linked Data). JSON-LD allows you to include a block of machine-readable structured data in a script tag anywhere in your HTML without interfering with the visible content of the page. Google has stated a preference for JSON-LD over the older inline microdata format, and it is the format this guide uses throughout.

Schema markup originally existed to enable rich snippets in search results: star ratings, opening hours, event details, recipe information. These remain valid use cases. But for maritime B2B companies, the more important function of schema markup in 2026 is AI visibility: making your site legible to the AI systems that synthesise search results, power Copilot in enterprise tools, and provide the answers that buyers receive when they query AI assistants about service providers in your category.

The Four Schema Types Every Maritime Business Needs

Organization Schema

The Organization schema is the most important piece of structured data your site can have. It declares what your company is, what it is called, where it operates, how to contact it, and what it knows about. For AI systems, the Organization schema is the primary source of ground truth about who you are.

A minimal Organisation schema for a maritime services company looks like this:

<script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ProfessionalService",
  "name": "Your Company Name",
  "alternateName": ["Any trading names or abbreviations"],
  "url": "https://yourcompany.com",
  "logo": "https://yourcompany.com/logo.png",
  "description": "A two to three sentence description of what you do, who you serve, and where you operate. Be specific about vessel types, trade routes, or regulatory frameworks you work within.",
  "foundingDate": "2005",
  "areaServed": "Mediterranean Sea, Black Sea, Adriatic Sea",
  "knowsAbout": ["Ship management", "ISM Code compliance", "Crew management", "SOLAS", "Flag state requirements"],
  "contactPoint": {
    "@type": "ContactPoint",
    "telephone": "+1-234-567-8900",
    "contactType": "customer service",
    "email": "contact@yourcompany.com"
  },
  "sameAs": [
    "https://www.linkedin.com/company/yourcompany",
    "https://www.facebook.com/yourcompany"
  ]
}
</script>

Two properties deserve particular attention for maritime businesses. The knowsAbout property is your opportunity to declare topical authority. List the specific regulations, vessel types, services, and industry concepts your company works with. These terms are what AI systems match against user queries. The more precisely you declare your expertise here, the more accurately AI systems will include you in relevant responses.

The areaServed property should be specific. “Worldwide” sounds ambitious but is effectively useless as a geographic signal. “Mediterranean ports from Gibraltar to the Suez Canal” or “North Sea, Baltic Sea, and Norwegian waters” gives AI systems a geographic context they can match against location-specific queries.

Service Schema

For each service you offer, create a Service schema on the relevant service page. The Service schema allows you to describe the service in structured terms, specify who it is for, what it costs (if applicable and appropriate to disclose), and what the expected outcome is.

A Service schema for a crew management service would include:

{
  "@context": "https://schema.org",
  "@type": "Service",
  "name": "Crew Management Services",
  "description": "Full-cycle crew management for bulk carrier and tanker operators, covering recruitment, STCW certification verification, flag state documentation, travel coordination, and repatriation logistics.",
  "provider": {
    "@type": "Organization",
    "name": "Your Company Name"
  },
  "areaServed": "Asia-Pacific region, Mediterranean ports",
  "serviceType": "Crew Management",
  "audience": {
    "@type": "Audience",
    "audienceType": "Bulk carrier operators, tanker operators, ship managers"
  }
}

The description field is the most commercially important property. It should read like a precise, factual account of what the service does, using the specific terminology that your target clients would use when searching. Avoid marketing language. A client searching for “STCW certification management for tanker crew” will be matched to your Service schema if those terms appear in it. They will not be matched if your description says “world-class crew solutions for maritime excellence.”

FAQPage Schema

FAQPage schema marks up a page of frequently asked questions in a format that allows search engines and AI systems to extract individual questions and answers and present them directly in search results or AI-generated responses. For maritime B2B companies, FAQ schema is one of the highest-value structured data implementations because maritime buyers frequently search in question format.

Queries like “what documents does a vessel need for port state control in Rotterdam,” “how long does flag state approval take for a new manning agency,” and “what is the difference between technical management and commercial management in ship management” are exactly the queries that maritime buyers ask. If your site has a well-structured FAQ page covering these questions, with FAQPage schema implemented, your answers can appear directly in AI-generated responses to those queries, with your company cited as the source.

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "What is included in a full ship management service?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Full ship management typically covers technical management (planned maintenance, class surveys, dry docking), crew management (recruitment, documentation, rotation), commercial management (voyage instructions, freight collection, port agency coordination), and compliance management (ISM, ISPS, MLC 2006, flag state requirements). The exact scope varies by manager and is defined in the ship management agreement."
      }
    }
  ]
}

BreadcrumbList Schema

BreadcrumbList schema marks up the navigational hierarchy of your site in a format that search engines use to display breadcrumb paths in search results. For maritime companies with service pages nested within categories, breadcrumb schema helps search engines understand the relationship between pages and improves the appearance of your listings in search results.

It is a lower-priority implementation than Organization, Service, and FAQPage schema, but it contributes to overall site architecture legibility and takes under an hour to implement across a typical site.

How to Implement JSON-LD Schema on Your Site

JSON-LD schema blocks are placed within script tags in the HTML of the relevant page. The Organization schema belongs on your homepage and on every page where it adds context. Service schemas belong on individual service pages. FAQPage schema belongs on your FAQ page or on service pages that include FAQ content.

On WordPress, the simplest implementation method without a plugin is to add the JSON-LD block directly to the page template in your theme. For sites running page builders, most builders allow custom HTML or script injection at the page level. If you are using an SEO plugin like Yoast or Rank Math, check whether it supports custom schema injection before building your own — both plugins have schema functionality, though it may not cover all the maritime-specific properties you need.

Do not use the same JSON-LD block across all pages without modification. The Organization schema can appear sitewide with minor modifications, but Service schemas should be specific to each page and should describe only the service on that page. Generic schema applied identically across all pages provides less value than specific schema that accurately describes each page’s content.

How to Test Your Schema Implementation

Google provides two tools for testing structured data implementation. The Rich Results Test (search.google.com/test/rich-results) checks whether your schema is eligible for rich results in Google Search. The Schema Markup Validator (validator.schema.org) checks whether your JSON-LD is valid according to the Schema.org specification. Use both. The Rich Results Test tells you whether Google can read it; the Schema Markup Validator tells you whether it is correctly structured.

Common errors to watch for: missing required properties (Organization schema requires at minimum a name and url), incorrectly nested objects (ContactPoint must be nested inside Organization, not at the root level), and type mismatches (using LocalBusiness when your company is not a location-based consumer business, for example).

After implementation, monitor Google Search Console for schema-related errors and warnings under the Enhancements section. Google will flag structured data issues that are preventing rich result eligibility.

Maintaining Your Schema Over Time

Schema markup is not a set-and-forget implementation. It needs to be updated whenever your services change, your geographic coverage changes, your contact information changes, or you add new service pages. Outdated schema that describes services you no longer offer or geographic coverage you no longer provide can actively harm your credibility with AI systems that detect discrepancies between your schema and your actual content.

Build schema review into your regular website maintenance cycle. Every time you update your services page, update the Service schema on that page at the same time. Every time you add a new service, create a new Service schema block. Treat schema as part of your content, not as a technical setting that was configured once.

Get Your Current Schema Score

The free Marine Brand Audit at Signe Agency checks your current schema implementation as part of a five-category assessment. You receive a score out of 100 across Technical, SEO, AI/GEO visibility, Content, and Conversion categories, with specific feedback on what is missing or incorrectly implemented in your structured data. The audit takes three minutes and the results give you a precise implementation priority list. Run it at signeagency.com/audit.