Designing fleet pages that don't read like brochure inserts

Take a sample of shipping line, ship manager and owner websites and audit the fleet pages. The dominant pattern is a static grid of vessel cards: a rendered photo, the vessel name, DWT, year built and a sentence of marketing copy. They look like inserts ripped out of a 2009 fleet brochure. They are not commercial assets; they are decoration.

The fleet page is one of the highest-intent pages on a maritime operator’s website. A buyer who lands on it has narrowed their consideration set. They are checking what you actually have, whether it matches what they need and whether you appear to know your own fleet. Designing this page as a brochure throws that intent away.

What a working fleet page does

It treats the fleet as structured data, not a gallery. Each vessel is a record with attributes a buyer might filter on: vessel type, DWT or TEU, year built, flag, classification society, ice class, propulsion, scrubber-fitted, current charter status, IMO number. That data drives the display, and the display has to work three ways at once.

As a filterable list. A buyer with a specific need (an aframax tanker built after 2015 with a scrubber, available open) should get to the vessels matching that filter in under 30 seconds. Multi-select filters across three or four attributes is the minimum.

As individual vessel pages. Each vessel has its own URL, its own metadata, its own document downloads (Q88 for tankers, vessel particulars for bulkers, GA drawings for offshore). The vessel pages need to be indexed and shareable; a chartering broker emailing a colleague a link to “the 2018 LR1 with the Korean GA” should land them on the right vessel page directly.

As a structured feed. If you have brokers, charterers or partners who want vessel data, expose a JSON or XML feed. A surprisingly large number of maritime data products would happily consume this and link back to your site.

What makes the difference

Real photography, not renders. Renders signal “we don’t have a photo of this vessel”. A photo of the actual vessel underway, on delivery or at port, signals that you operate it. Commission photography on dry-dock or port calls; it pays back across web, brochure and pitch decks for years.

Live status, where commercially appropriate. Some operators are comfortable showing employed/open status on the public site; others restrict it to authenticated broker portals. Either way, the data should be current. A chartering manager who sees “Status: open” on a vessel that’s actually fixed for nine months has just lost trust in everything else on the site.

Relevant technical specifications, not all of them. A buyer needs DWT, year built, class, flag, propulsion type, key cargo capacity figures. They do not need a 60-row spec table from the original delivery booklet. Put the headline data on the page, link to the full Q88 or particulars as a downloadable PDF.

Document downloads with dates. “Q88 (last updated 14 March 2026)” beats “Q88 download”. Buyers and brokers care whether the document is current.

Sister-vessel cross-linking. A buyer looking at one vessel often wants to see similar vessels in the fleet. Cross-link by sister-class, vessel type or build year.

What to cut

The marketing copy on each vessel card. A two-sentence narrative about how the vessel “exemplifies our commitment to operational excellence” is noise. The buyer wants the data. If you must have copy, save it for the fleet overview page.

The “Total fleet DWT” headline. Aggregate figures without context are useless. Replace with structured aggregates that match how buyers think: “12 aframax tankers, 8 LR1s, 6 chemical tankers, 4 LPG carriers, all dual-fuel where new-built post 2022”.

Build it once, maintain it forever

The hard part of fleet pages isn’t the design; it’s the data discipline. A fleet page that updates manually in WordPress will be six months out of date by Christmas. Build it from a CMS-managed structured collection that one person owns. Better: pipe it from your fleet management system (Veson, Q88, ShipNet, custom) on a schedule. Nobody outside the operations team will catch a wrong DWT figure on the website, but the buyer comparing your aframax to a competitor’s will notice the wrong year built.

The fleet page is the most operational content on your marketing site. Treat it like operational content, not brochure copy.