Visual identity consistency, brand-voice continuity across the audit set, font reference verification, and the multi-language SEO opportunity Kokomo is leaving on the table for Latin American and European wellness travelers. The property sits in the Turks and Caicos Islands, a British Overseas Territory; language and locale decisions are framed around that.
Homepage source scan · cross-platform brand audit · ES, FR market opportunity sizingBrand identity on Kokomo's owned website is largely consistent: one canonical name on the site, two logos, a defined typography stack, and a visual system that reads "wellness boutique." The fragmentation surfaces off the website (five different brand-name variants across Facebook, TripAdvisor, Pinterest, Apple Maps, and Booking.com, fully covered in the Reviews and Social, Press & Earned Media audits).
Two minor surface findings plus one structural one. The homepage references font-family: 'GT America Trial' in CSS, which could indicate either an unlicensed trial-version font shipped to production or simply a CSS reference left behind after a proper licence was purchased. Worth a five-minute check with whoever installed the theme; not an alarm. Second, the document declares lang="en-CA". Kokomo is in the Turks and Caicos Islands (British Overseas Territory) where English follows British conventions; primary tourist source markets are roughly US 75%, Canada 15%, UK and Europe 10%. en-CA is therefore defensible (Canadian travelers are a meaningful slice and Canadian English overlaps with British conventions used in TCI). The structural finding is the one that matters: zero hreflang tags and no alternate-language version exists for Spanish or French. For Caribbean wellness traffic from Latin America and from European travelers planning a Caribbean trip in their own language, the property is effectively invisible.
The on-site brand voice is fine. The off-site brand name is a mess (root-caused in three earlier audits). The GT America font reference is worth verifying but is not an alarm. The single real growth lever in this audit is multi-language: Spanish first, French second. Each language version pulls a new traveler segment and adds AI-citation depth.
<html lang>), hreflang link tags, and any localisation switcher in the navigation.This audit reconfirms the five-platform brand-name fragmentation already surfaced in three prior audits. The fix list belongs in the platform-rename sprint already scoped under those audits.
| Surface | Brand name displayed | Per audit |
|---|---|---|
| Website (canonical) | Kokomo Botanical Resort | Design Review |
| Kokomo Botanical Resort | Social audit | |
| YouTube | Kokomo Botanical Resort | Social audit |
| Google Business Profile | Kokomo Botanical Resort | GBP Analysis |
| Kokomo Botanical Resort & Spa | Social audit | |
| TripAdvisor | Kokomo Botanical Resort Caribbean Family Cottages | Reviews audit |
| Kokomo Botanical Resort - Caribbean Family Cottages | Social audit | |
| Apple Maps duplicate | Address typo ("Street" instead of "Drive") | AI Visibility |
| Booking.com URL slug | venetian-ridge-vacation-villas-spa | AI Visibility |
The homepage HTML declares font-family: 'GT America Trial'. GT America is a commercial typeface licensed by Grilli Type (gt-america.com). The "Trial" suffix in the CSS family name could mean one of three things, in decreasing order of likelihood:
Five-minute check with whoever installed the theme: open the live site in DevTools, look at the Network tab, find the font file being loaded. If the file is named with "Trial" in it and is being served from the property's own hosting, scenario 3 applies and the fix is either to purchase the licence (~$200-$500 per family) or substitute (Manrope, Plus Jakarta Sans, Inter on Google Fonts).
fonts.googleapis.com. The page-builder appears to be serving fonts from a custom source or from the GT America trial file.var(--e-global-typography-text-font-family), Sans-serif (page-builder's global token, fallback chain intact).font-display: swap verifiable from this source scan; flagged in open items for a live performance test.| Setting | Value | Status |
|---|---|---|
HTML lang attribute | en-CA | Defensible. Kokomo is in the Turks and Caicos Islands (British Overseas Territory). TCI English follows British conventions, which Canadian English shares more than American English does. Canadian travelers are a meaningful audience segment. |
Schema.org inLanguage | en-CA | Matches HTML. Consistent. |
| hreflang link tags | None | FAIL. No alternate-language versions declared. |
| Language switcher in nav | None visible | FAIL. No user-facing way to switch languages. |
| Spanish version of the site | None | FAIL. Latin American wellness traveler intent is uncatered. |
| French version of the site | None | FAIL. European wellness traveler intent in French is uncatered. |
Kokomo's physical location is the Turks and Caicos Islands, a British Overseas Territory. TCI does not have a dedicated en-TC locale code, so the property has to pick from the standard English-locale options. The realistic choices and their trade-offs:
en-CA (current): Canadian English. Defensible for an audience that is ~15% Canadian, and Canadian English uses British conventions ("colour," "centre," "organise") that align with TCI's own English heritage.en-GB: British English. The most accurate match for TCI's local English usage. Would signal correctly to Google that the property is in a British-conventions market.en-US: American English. The largest single-market choice (US is ~75% of TCI tourism). Would slightly favor US-targeted SERP positioning at the cost of regional accuracy.en (no region): Region-neutral. Lets Google decide. Reasonable for a property serving multiple English-speaking countries with no strong preference.The current en-CA declaration is not a problem. If a change is wanted for strict accuracy, en-GB reflects TCI's actual English conventions best. If the priority is the dominant traveler market, en-US wins. This is a low-priority decision, not a P0 fix.
If Kokomo's English-only direct organic traffic is generating $X per year in direct bookings, a properly localised Spanish version that captures 10% of equivalent intent adds roughly $0.10X. For a property at this ADR with the wellness keyword set already audited, a credible mid-case is $15K to $80K in additional annual direct revenue per added language, depending on the executable conversion rate and the maturity of the OTA Spanish-language flow.
The cost side is meaningful: translation of 100+ pages, hreflang implementation, multi-language CMS configuration, localized booking flow (the WebRezPro engine must support locale switching, confirmed in the Booking Engine Audit), and ongoing content maintenance. Expect a 6 to 12-month commitment for Spanish, longer for adding French.
Multi-language is the right Q3 to Q4 investment, not the immediate next move. The base-rate ROI on multi-language for a hospitality property without an existing Latin-American sales channel is real but slow. The right sequence: ship the spam removal, the booking engine fix, the reviews program, the funnel pages, the press play. Then commit to Spanish in the second half of the next year, French the year after.
en-GB aligns most accurately with TCI's local English conventions. Optional, not urgent.Two easy P0s this month: resolve the GT America Trial font (purchase the license or substitute) and update the HTML lang attribute to match the primary buyer geography. One P1 inside 30 days: document the palette and logo rules so the next vendor doesn't drift further. Cross-reference the platform-rename sprint already scoped in three earlier audits.
The strategic decision is multi-language. Spanish first, in the second half of the next year, after the more urgent fixes ship. The financial case is real but slow, and the property has higher-yield work to do first.