Web · SEO · GEO · Active

Marine services digital platform

A bilingual corporate website built on route-aware technical SEO and a real entity model rather than a keyword list.

Role: Architecture and delivery
Category: Web · SEO · GEO
Status: Active

The problem

Most corporate websites treat SEO as a content exercise — write the keywords, fill the meta description field, move on. The result is a site that is technically indistinct: duplicate titles, no canonical strategy, no structured data, and no coherent statement of what the organisation actually is.

Approach

Build the metadata layer as architecture. Every route generates its own title, description and canonical URL; structured data describes the pages and the organisation as connected entities rather than isolated blobs; and Arabic is part of the information architecture rather than a second site bolted on.

What it does

Route-aware metadata: Titles, descriptions and canonicals are generated per route from a single source, so no two pages can silently share metadata.
Canonical URL strategy: One canonical form per page, applied deliberately rather than left to whatever the framework emits by default.
Structured data with real relationships: WebPage, BreadcrumbList and an Organization entity connected by ID, rather than disconnected fragments that describe nothing collectively.
Open Graph and Twitter metadata: Complete social metadata so shared links present correctly instead of falling back to whatever text happens to be first on the page.
English and Arabic: Both languages treated as primary, with RTL handled in layout and navigation rather than as a stylesheet flip.

The hard parts

Entity clarity is not a keyword problem: Getting a search engine to understand what an organisation is requires consistent, connected structured data — a different discipline from writing page copy.
Bilingual SEO doubles every decision: Canonicals, hreflang considerations and content hierarchy all have to hold in two directions at once.

Detail

Client confidentiality

I'm not naming the company. I describe it here as a marine services company.

Why the emphasis is on architecture

Claims about ranking are not verifiable, so I do not make them. What is verifiable is what I implemented: unique metadata per route, a canonical strategy, connected structured data and a bilingual information architecture. Those are engineering facts. Whether they produce a particular ranking is not something I can honestly promise.

Stack

Metadata: Route-aware titles and descriptionsCanonical URLsOpen GraphTwitter cards
Structured data: JSON-LDWebPageBreadcrumbListOrganization entity
Localisation: EnglishArabicRTL

Case studies

The decisions behind the build

CS-01Building route-aware technical SEO for a multi-page corporate website CS-02Building an Arabic/English corporate website without treating Arabic as an afterthought

ARTICLEWhy Arabic-first software is more than translating an English UI ARTICLEHow I think about SEO for AI search engines ARTICLESEO is not just titles and keywords anymore

All work