Start with conditions that can block discovery or make a high-intent inquiry path unreliable. Each check should be supported by a reproducible test, not by a visual review alone.
Check: Mobile rendering and primary content delivery. Evidence required: a tested mobile URL, field or lab performance output, and a screen recording or trace showing when the main fleet, vessel, route, or inquiry content becomes usable.
Pass condition: the primary content renders without hidden navigation, unusable controls, or blocking shifts, and the tested Largest Contentful Paint is at or below 2.5 seconds for the chosen audit profile.
Fail condition: the tested page is materially slower, unstable, or requires interaction before essential content becomes usable. Severity: high. Owner: developer with SEO reviewer. Corrective action: reduce unnecessary blocking resources, compress media, reserve layout space, and simplify the critical rendering path. Validation step: rerun the same mobile profile and confirm the failing condition no longer reproduces.
Check: Crawlable fleet and vessel detail. Evidence required: rendered HTML, URL inspection output, and a comparison between what a user sees and what the rendered document exposes. Pass condition: core aircraft or yacht facts, availability context, and internal navigation are present in crawlable page content even when a booking component is involved.
Fail condition: essential information exists only inside an inaccessible frame, client-side state, or interaction that is absent from the rendered document. Severity: critical. Owner: developer. Corrective action: expose essential descriptive content in server-rendered or otherwise crawlable HTML while keeping transactional widgets separate from indexable copy.
Validation step: inspect the rendered page and confirm the same essential facts are available without relying on the widget.
Check: Dynamic empty-leg lifecycle. Evidence required: a sample of active offers, expired offers, sitemap entries, internal links, and indexability directives. Pass condition: active offers have a clear current state, expired offers follow the site's chosen retirement policy, and users are not sent to stale availability.
Fail condition: expired routes remain indexable as current inventory, internal links continue to promote them, or retirement produces an unintended 404 where a more useful destination is available. Severity: high.
Owner: SEO lead with developer. Corrective action: define the lifecycle for active, expired, consolidated, and retired offer URLs, then align internal links, sitemap entries, and indexability with that lifecycle.
Validation step: test representative active and expired URLs after deployment and confirm their status, directives, and destination behavior match the policy.
Check: Canonical and indexation consistency. Evidence required: canonical tags, indexability directives, sitemap membership, and search-console inspection for representative fleet, vessel, route, and location URLs.
Pass condition: each important page declares a consistent preferred URL and is neither blocked nor duplicated by conflicting technical signals. Fail condition: canonical targets, sitemap entries, redirects, or indexability directives disagree.
Severity: critical. Owner: SEO lead with developer. Corrective action: resolve conflicting signals and remove avoidable duplicate URL variants. Validation step: inspect the corrected URLs and confirm the preferred version is internally linked, indexable when intended, and consistently declared.