The new Head of Organic Growth is told "our organic engine isn't pulling its weight". One cause is visible in the page code. Kraken Pro's hreflang tags tell search engines that /de/pro is German, /es/pro is Spanish and so on for 28 versions, but those URLs come back in English unless the visitor's browser asks for the language: with no language set, /de/pro has lang="en" and the H1 "Powerful. Customizable. Beautiful."; with a German browser it becomes "Leistungsstark. Individuell.". Google says its crawler sends no browser language, so it most likely sees English on every localized Pro page. Kraken's Spanish news articles already work the right way, Spanish at their own URL.
First action
Run URL Inspection on /de/pro and /es/pro and compare the rendered language.
How to measure it
Search impressions for localized /pro pages
- Now
- –
- Target
- 3x
- By
- 90 days
Steps
Confirm what crawlers see
URL Inspection and a plain request for ten localized Pro URLs.
Head of Organic Growth, Kraken Pro 1 day
List affected templates
Pro, product and feature pages that switch on the header.
Engineering Manager, Growth Foundations 3 days
Render by path
Language comes from the URL; the header only suggests a switch.
Engineering Manager, Growth Foundations 2 weeks
Fix caching
Cache key per URL language, no header-based variants.
Engineering Manager, Growth Foundations 3 days
Compliance check
Each market's Pro page wording and disclosures.
Legal and Compliance 1 week
Request indexing
Resubmit localized sitemaps; inspect key URLs.
Head of Organic Growth, Kraken Pro 1 day
Measure by market
Impressions, clicks and signups per locale in Search Console.
Growth Analytics weekly
Brief regional teams
KOL and social links point to the right language URL.
KOL Lead, Spain & Iberia 1 day
Why it works
Render the language from the URL path (/de/, /es/, /fr/) on every Pro and product page, as the news pages do; keep the browser header only for suggesting a switch. Add Accept-Language to the cache key or stop varying content by it. Check with a plain request and with Google's URL Inspection tool that /de/pro now returns German, then track localized Pro impressions and signups in Search Console per market. Have Legal and Compliance confirm each market's page wording before it is indexed.
Localized product pages can rank in each market only if crawlers see the local language. Pro is already translated, so the fix unlocks existing work for the KOL, social and copy teams being hired, with no new content.
Ready to use
ChecklistLocalized Pro pages check
[ ] curl https://www.kraken.com/de/pro (no Accept-Language) returns lang="de" [ ] Same for /es, /fr, /it, /pt, /pl, /nl and the other hreflang locales [ ] Cache key does not mix languages [ ] hreflang set unchanged and reciprocal [ ] URL Inspection shows the local language [ ] Compliance sign-off per market [ ] Search Console: impressions per locale tracked weekly
Risks and how to handle them
Wrong language for some visitors
Show a one-click language switch based on the browser header.
A market's page needs different disclosures
Hold indexing for that locale until compliance signs off.
Evidence
- HiringHead of Organic Growth, Kraken Pro (US and UK, posted October 15, 2026): "a great product only wins if the right traders find it, trust it, and actually fund an account. Right now, our organic engine isn't pulling its weight." The role owns "SEO, content, social, community, referrals, and partnerships", must "Map the funnel from first touch to first trade" and "audit and improve landing pages, sign-up flows, onboarding", and must "Partner with Legal/Comms to ensure compliant, accurate, and aligned messaging across regions".Source
- Localization testFetched on October 22, 2026 with no browser language set: kraken.com/de/pro, /es/pro, /fr/pro, /gr/pro, /ua/pro and /cn/pro all return lang="en" with the English title and H1. The same /de/pro with a German browser language returns lang="de" and the H1 "Leistungsstark. Individuell."; /es/pro/spot returns "Trade spot with precision and depth" by default and "Opera en spot con precisión y profundidad" only for a Spanish browser. Kraken's /es/news articles, by contrast, are Spanish at their URL (lang="es"). The response header is "vary: Accept-Encoding, Origin".Source
- Google Search CentralGoogle's guidance on locale-adaptive pages: Googlebot "sends HTTP requests without setting Accept-Language in the request header", and Google recommends "using separate locale URL configurations and annotating them with rel=\"alternate\" hreflang annotations".Source
- Your websiteKraken Pro page: title "Kraken Pro — Advanced Trading Platform for Crypto, Stocks & Futures"; H1 "Powerful. Customizable. Beautiful."; the body says "Open the door to 400+ assets" while the stats row says "640 Crypto assets", alongside "190+ Countries supported", "$2T+ Total platform transaction volume" and "Voted best crypto exchange 2025 by Forbes". Its hreflang tags list 28 language versions (es-es, de-de, fr-fr, it-it, pt-br, zh-cn, uk-ua, en-in and more).Source
- HiringKOL Lead, Spain & Iberia (posted September 15, 2026): "Build and scale a KOL/creator network in Spain, Iberia and other countries for Kraken Pro from the ground up", representing "perpetual futures, prop trading, margin", with "regional KOL acquisition targets and CAC efficiency" and partnership with "growth, marketing, and compliance teams"; fluent Spanish required.Source