O
Otter Trade Google Ads Landing Page Prototypes
Static HTML prototype only

Built from the Track A / Track B media plan

Two routes, one Otter Trade brand system.

These prototypes translate the existing Google Ads strategy into two distinct landing page directions: Track A is mobile-first, playful, and de-financialized for broad acquisition; Track B is rational, competition-led, and higher-intent for disciplined players and builders.

/play Track A Route
/competitions Track B Route
3 files Hub + 2 pages

Directional Split

Same brand. Different cognitive load.

Both pages keep the Otter Trade identity centered around arena competition, humans plus agents, and a premium dark-surface visual system. The difference is what each page chooses to explain first.

Track A prioritizes instant comprehension.

The first screen behaves like a poster for a live event. Copy is short, benefits are obvious, and the page explains the loop in under a minute. This is for colder traffic where friction is the enemy.

Track B prioritizes confidence and fit.

The page spends its first screen on competition structure, scoring, and who this is for. It assumes the visitor wants a reasoned brief, not a teaser. This is for narrower, higher-intent audiences.

Track A keeps language de-financialized.

It avoids direct trading, crypto, wallet, and deposit framing. The prototype talks about arenas, play points, leaderboards, skill, and rewards to match the compliance-safe direction in the media plan.

Track B allows more system detail.

It introduces strategy, execution, market simulation, and API readiness in a restrained way. The tone is still brand-led, but the information architecture is more like a competition brief than an ad creative.

Prototype Notes
The files are intentionally static and self-contained so they can live inside the current portal without wiring any signup flow. If you want the next step, these can be converted into real routes on go.otter.trade and then connected to the shared signup form, GA4 events, and Google Ads conversion tracking defined in the original plan.