International SEO for global maritime brands: hreflang done properly

Global maritime websites tend to fall into one of three traps with international SEO: hreflang isn’t implemented at all, it’s implemented incorrectly or the regional content is so similar that there’s nothing to differentiate.

The third problem is the hardest to fix and the most common.

Why hreflang matters for shipping lines and ship managers

A fleet director in Athens searching for “tanker technical management” should see the page that speaks to Greek owners, references local class society relationships and lists your Piraeus office. A charter manager in Singapore searching the same query in English should see the Singapore office content with regional vessel data and Asian terminal experience.

Without hreflang, Google guesses. Sometimes it gets it right; often it serves the US page to a UK buyer or vice versa. Worse, it sometimes splits ranking signals across pages it sees as duplicates and ranks none of them well.

The two attributes that matter

Hreflang takes a language code (en, el, zh-Hans) and optionally a region code (en-GB, en-SG, zh-Hans-CN). Use both when targeting different English-speaking markets. Use just language when content is genuinely the same across regions.

Every page should reference every variant of itself, including itself. So an English-Greek site with one page in two languages needs both pages to declare:

<link rel="alternate" hreflang="en" href="https://example.com/services/technical-management/" />
<link rel="alternate" hreflang="el" href="https://example.com/el/services/technical-management/" />
<link rel="alternate" hreflang="x-default" href="https://example.com/services/technical-management/" />

The x-default value tells Google what to show when no specific match exists. For most maritime brands that should be the English global page or whichever version is most generic.

Where it goes wrong

The mistakes I see most often on maritime sites:

• Self-referencing missing. A page declares its alternates but doesn’t declare itself, so Google ignores the cluster.
• Mismatched URLs. The English page lists the Greek alternate as /el/services/technical-management/ but the Greek page actually lives at /gr/services/technical-management/.
• Region without language. hreflang="GB" is invalid; it has to be en-GB.
• Trailing slash inconsistency. One side has it, the other doesn’t and the cluster breaks.
• 404’d alternates. A page lists alternates that no longer exist after a content prune.

A clean hreflang setup should validate cleanly in the Search Console International Targeting report and round-trip without errors when you crawl with Screaming Frog set to extract hreflang.

The harder problem: regional differentiation

Hreflang only helps if the regional pages are meaningfully different. A shipping line that publishes the same “Our values” page on en-GB, en-SG and en-US with no localised content is wasting hreflang and risking thin-content flags.

What actually differentiates a regional page on a maritime site:

• Office contacts, regional commercial leads, agency relationships
• Local case studies (a Greek client referenced on the en-GR page, an Indonesian client on en-ID)
• Region-specific compliance content (EU ETS for the European pages, IMO 2020 for global, regional class society relationships)
• Currency and unit references where relevant

Regional differentiation is where most maritime international SEO stalls. Hreflang is easy. Producing fifteen genuinely localised service pages is the work.

Where to start

Pick your three highest-priority regions. Build properly localised pages for each. Implement hreflang sitemap-style across those three plus your global default. Verify in Search Console. Then, only then, expand to the next three.

Trying to launch fifteen regional variants in a single sprint is how shipping lines end up with hreflang implementations that confuse Google more than they help.