Translations & Internationalization Policy

We deliberately do not ship machine-translated marketing pages. Bad translations hurt brand credibility, and Google penalizes thin/translated content. What we do ship: hand-curated short landings in six target locales, multilingual structured data on every page, and a complete hreflang map so crawlers can resolve locale variants without ambiguity.

Hand-curated locale landings

What we ship in every language

hreflang declarations site-wide for 14 variants (including x-default and English).
JSON-LD inLanguage on every WebPage / Article / DefinedTerm.
Multilingual labels on Organization (availableLanguage) and ContactPoint.
Per-locale og:locale on landing pages.

What we do NOT ship

Auto-translated full product pages, blog posts, or research findings. The methodology paper is published in English on SSRN; partial translations would create canonical ambiguity.
Country subdomains or ccTLDs. Locale routing is at the path level (/zh, /ja, etc.) so link equity stays consolidated.
Currency localization on pricing. Prices are quoted in EUR; Stripe handles charging in the customer's local currency at checkout.

Five breakout startups, every Sunday, before the round gets crowded

The free Acceleration Watch: five venture-backed teams accelerating on the engineering signal, translated into plain English, 21 to 47 days before the deck circulates. No code-reading, no card.

Get the free Sunday issue →

Signed The Data Nerd · pseudonymous narrator · methodology over personality

See also: Standards · Citation guide · Press kit