A technical SEO audit framework for maritime websites

A maritime website audit that just runs Screaming Frog, exports a report and recommends “fix broken links” is not an audit. It’s a checklist someone could have generated on autopilot. The actual job is working out which technical issues are quietly costing the shipping line, port authority or marine equipment manufacturer real visibility on the queries their buyers run.

A useful framework has five layers. Start at the bottom, work up.

1. Crawl and indexability

Pull a full crawl of the public site. The numbers worth watching:

• Indexable URL count vs. URLs in the sitemap. A 30% delta usually means the sitemap is stale, the CMS is generating tag pages nobody asked for or both.
• Soft 404s in Search Console. Common on maritime sites with thin “service area” or “vessel type” landing pages built years ago and never filled out.
• Orphan pages. A capability page on chemical tanker management with no internal links pointing at it isn’t going to rank no matter how good the copy is.

2. Rendering

Most modern maritime sites now run on a JavaScript framework somewhere in the stack. Fleet portals, dashboard-style service explorers and interactive port maps are particularly common offenders. Check what Googlebot actually sees by using the URL Inspection tool’s rendered HTML view, not the raw source.

If your service descriptions, contact details or schema only appear after a client-side render, you have a problem. Server-side rendering or static generation should be the default for any page you actually want to rank.

3. Site architecture

Maritime sites tend to mix corporate content, service pages, regional offices, news and case studies in a tangle. Map the URL structure and look for:

• Service taxonomies that bury technical management three clicks below “About”.
• Regional pages that aren’t linked from any service page, so a buyer searching “ship management Singapore” lands on a generic global page.
• News categories that have ballooned to 400 posts with no internal linking back to relevant services.

The fix is usually less radical than people assume: add a navigation tier, link from each news post back to the related service and prune the dead categories.

4. Performance

Run Core Web Vitals on the templates buyers actually land on, not just the homepage. The biggest offenders we see on maritime sites:

• 4MB hero photography of vessels at sunset, uncompressed.
• Embedded video players that load the entire YouTube SDK on every page.
• Web fonts loaded synchronously, blocking text rendering for two seconds on a 4G connection.

LCP under 2.5 seconds and INP under 200ms is the bar. Most maritime corporate sites are nowhere near it.

5. Schema and entities

Schema is where AI search and Google’s knowledge graph either understand your business or guess. Organization schema on the homepage, Service schema on every service page, BreadcrumbList sitewide. For shipping lines and operators, Vessel and FleetOwner schema (using extended types or properly nested data) helps clarify what your business actually does.

What to do with the audit

A useful audit ends with a prioritised remediation list, not a 90-page PDF. Three buckets: ship today (broken canonicals, indexation issues), ship this quarter (rendering, schema, internal linking) and roadmap (architecture, performance overhauls).

If the audit doesn’t tell the marketing director what to do on Monday morning, the auditor wasn’t doing their job.