Case studies / Financial services
Web design & developmentOne firm, two languages, and no translated afterthought.
Hilo Capital Group needed a website that worked as well in Spanish as in English not an English site with a language switcher bolted on. We built both from the ground up, structured so neither version competes with the other in search.
See it working.
A corporate financial layout built for credibility, structured so the offering is legible within the first screen.
The site is live. Open it and judge the work directly.
Visit the live siteMost "bilingual" sites are one site wearing a costume.
A translation plugin produces Spanish text. It doesn't produce a Spanish website. The difference shows up in three places: what the copy sounds like to a native speaker, whether Google indexes both versions, and whether the two versions end up competing with each other.
Translate and hope
English site built first, machine translation applied, one URL serving both. Native speakers recognise translated copy almost immediately. Search engines often see duplicate content or fail to index the second language at all and the two versions cannibalise each other's rankings.
Two real versions, properly declared
Separate URLs per language, copy written rather than translated, and reciprocal hreflang so Google serves the right version to the right searcher without the two competing.
What we were handed.
Hilo Capital Group had the credentials and the client base. What it didn't have was a site that said so and in financial services, where the buying decision runs almost entirely on perceived credibility, that gap costs real money.
-
The site undersold the firm
Visitors couldn't tell within one screen what the firm actually offered or who it served. In a category where prospects compare four or five providers in a sitting, that ambiguity loses the comparison.
-
Half the audience was being served an English site
A meaningful share of the firm's prospective clients prefer to research financial decisions in Spanish. They were being asked to do it in their second language, on a page that hadn't been written for them.
-
No path from interest to inquiry
Content described services but never asked for anything. Visitors who wanted to talk had to go looking for a way to do it.
What shipped.
Custom corporate design
A financial-sector visual language built for investor credibility rather than trend.
Full Spanish build
Every page in both languages, written for the market rather than translated into it.
hreflang architecture
Reciprocal tags and self-referencing canonicals so both versions index cleanly.
Mobile-first responsive
Built for the phone first, where most first visits to the site actually happen.
Conversion paths
Inquiry routes placed at each decision point, in both languages.
Performance & schema
Core Web Vitals optimisation and structured data on every page.
Need the same in two languages?
Send us your current site. We'll tell you what a bilingual build would take, what it would cost, and whether it's the right call for your market on the first call.
Findings are yours to keep · You own everything we build