PrimeXBT publishes the same 110 core pages in English and 12 other languages, and it is hiring a Content Lead to coordinate localisation plus partner and country managers for Vietnamese, Thai, Indonesian, Arabic-speaking and other markets. But none of the 1,433 sitemap URLs carries hreflang tags: each language page only points to itself. Search engines are left to guess which version to show, so a trader searching in Vietnamese or Bengali can land on the English page, with the English risk warning and legal text, and the localisation work the new hires produce is harder to find.
First action
Generate the hreflang map for the 110 core pages and test it on the homepage.
How to measure it
Visits landing on the right language version
- Now
- –
- Target
- 90%
- By
- 90 days
Steps
Map languages
Folder to language code for all 13 versions, plus x-default.
SEO specialist 1 day
Add tags
Reciprocal hreflang in the page head or sitemap for the 110 core pages.
Frontend engineering lead 1 week
Fix lastmod
Real change dates in the sitemap instead of the generation time.
Frontend engineering lead 2 days
Check risk text
Translated risk warning, entity and restricted-country text on every language page.
Compliance team 1 week
Validate
Search Console international targeting and a crawl for return-tag errors.
SEO specialist 1 week
Extend
Glossary, research and price-chart pages that have translations.
Content Lead 1 month
Measure
Organic entrances by language and country.
SEO specialist monthly
Why it works
Add reciprocal hreflang tags (for example vi, th, id, bn, ar, es, pt-BR, ru, ja, ko, zh-Hans, zh-Hant and x-default) to every language version, either in the page head or in the sitemap. Map the folder codes to the right language codes (the Indonesian folder is /in, the language code is id). Fix the sitemap lastmod so it shows each page's real change date. Then check each language in Search Console and make sure the translated risk warning, entity and restricted-country text are present and approved on every page.
Hreflang is the standard way to tell search engines which page serves which language. It sends local searchers to the page written for them, raises click-through from local results, and makes sure each reader sees the risk disclosure in their own language, which supports trust and compliance at the same time.
Ready to use
ChecklistHreflang rollout list
[ ] One map: folder -> language code (in -> id, cn/zh -> zh-Hans/zh-Hant, kr -> ko, jp -> ja) [ ] Every page lists all its language versions, including itself [ ] x-default points to English [ ] Return tags match on every version [ ] Sitemap lastmod = real change date [ ] Translated risk warning and restricted-country text approved [ ] Search Console checked per language
Risks and how to handle them
Pages without a translation
Only tag pages that exist in that language; fall back to x-default.
Traffic from countries PrimeXBT does not serve
Hreflang targets languages, not countries; keep the restricted-country notice and registration checks in place.
Evidence
- Your websiteLanguage versions: the sitemap (sitemap-site.xml, 1,433 URLs, checked October 23, 2026) lists the same 110 core pages in English and 12 other language folders (es, pt, in, vi, cn, zh, jp, kr, bn, th, ar, ru). Each page has a self-referencing canonical, but no page head and no sitemap entry carries hreflang tags (checked on the English and Spanish homepages, fees, VIP, negative balance protection and zero stop-out pages). Every URL also shows the same lastmod time, the moment the sitemap was generated.Source
- HiringContent Lead, posted October 5, 2026: to "bring consistency to our brand communications", "develop and apply a consistent tone of voice", "coordinate localisation to preserve meaning and tone", write "landing pages, campaigns, CRM communications, articles", "work with Compliance and subject-matter experts to ensure accuracy and meet regulatory requirements", and build "AI-assisted workflows" while reviewing AI output "for facts".Source
- HiringPartner and market hiring on the Greenhouse board (20 open roles, all remote, 17 in the Revenue Department): Business Development Managers (Crypto/CFD; Nigeria; Thai, Turkish and Vietnamese speakers), Partner Acquisition Managers (English, MENA, Urdu, Vietnamese), Country Managers (Bahasa Indonesian, Filipino, Nigeria). Partner managers source "influencers, educators, communities, agencies" via "LinkedIn, Telegram, YouTube, Instagram" and drive partners to "Active status (5+ first-time deposits)".Source
- Your websiteFooter and regulations page: services come from different entities by jurisdiction (an FSCA-authorised provider in South Africa, licence 45697; a DASP and BSP licensed entity in El Salvador; a Saint Lucia company). "The entities above do not offer services to residents of certain jurisdictions including the USA, Canada, Iran, North Korea, Russia"; content "not intended for residents of the European Economic Area or the United Kingdom". Risk warning: Crypto Futures and CFDs "are high-risk, leveraged products that may not be suitable for all investors, as they can lead to significant losses."Source