The Hidden Tax of an English-Only Site: What You're Paying to Not Speak Spanish

Founders sometimes ask me "what does translation cost?" and I can tell from the question they're bracing for sticker shock. The real answer — and the one that usually ends the conversation — is to flip the question around.

What does not translating cost you?

Because that number is always bigger. Almost always significantly bigger. And unlike the translation bill, the not translating bill shows up in your financials whether you pay attention to it or not.

The tax, line-item by line-item

Line 1: Bounced paid traffic

Pull your Google Ads report. Filter by country. Look at any non-English-primary country where you're spending at least a few hundred dollars a month. Now look at the conversion rate vs your domestic rate.

It'll be 30–70% lower. Sometimes 90% lower.

That gap is money you're spending on ad impressions and clicks that convert less than half as well as they could, because the landing page is in the wrong language. You can't fix it by "optimizing the funnel." The funnel's fine. The page is in the wrong language for the audience.

Line 2: Organic traffic you never show up for

Every Spanish-language SERP for your product category. Every German how-to search. Every French comparison query. You aren't buried in those results — you aren't in them at all. A competitor that translated their site is collecting that traffic for free.

Estimating this line is harder than line 1 but the magnitude is usually larger. Pull a keyword tool, look up the top 20 terms you already rank for in English, and check the search volume for their Spanish or French or German equivalents in the relevant market. Multiply by a realistic CTR-at-rank and your average page-to-customer conversion rate.

You'll often find you're leaking more through this channel than through line 1.

Line 3: Wasted email and retargeting spend

You have a list. You send campaigns. A subset of that list is international — and the emails go out in English because that's what your ESP has templated. Those subscribers open at half the rate of domestic. They unsubscribe at double the rate. Retargeting ads follow them across the web, still in English, still not landing.

This is a tax you're paying per-send, per-touch.

Line 4: Customer support friction

International customers who do convert create more support tickets per dollar than domestic ones, because the product documentation is in English and they have to translate it themselves, often getting it wrong. They escalate more. They churn more. They leave one-star reviews in their native language that you'll never see because you can't read the review platform in Spanish.

This is the quiet line. The one nobody blames on language. But it compounds.

Line 5: The brand that isn't built

Every market has a leader for your category. When English-only, you can't become the leader in Mexico's category, or Germany's, or Brazil's, because you aren't present in that market's conversation. Five years from now, someone else is the leader there, with the brand moat, the backlinks, and the customer loyalty. You're still sending English ads into their country trying to win a battle that's already been decided.

Line 5 is the one that shows up in retrospect, when a growth stalls and nobody can figure out why. It's because the international flank got closed off quietly while domestic got all the attention.

A simple model

Let's do the math on a stripped-down case. Take these numbers as inputs — replace with your own:

• Monthly organic visitors: 50,000
• % from non-English-primary countries: 18%
• Your average session-to-lead conversion rate (domestic): 3.5%
• Your current session-to-lead conversion rate (international, English-only): 0.6%
• Your average lead value: $180

Math: 50,000 × 18% = 9,000 international sessions. At 0.6% you're generating 54 leads = $9,720/mo.

If you close the gap to even half of domestic (conservative — properly-translated sites often close it entirely) at 1.75%, you'd generate 158 leads = $28,440/mo. A $18,720/mo delta. $224,640/year.

A $225k/year tax you're paying to remain English-only, in this modest example. Scale up to more traffic or higher-value transactions and the tax scales linearly.

The line item on the other side of the ledger

Now what does fixing it cost?

• Hiring professional translators for 50 pages × 5 languages: $15k–$30k upfront, plus ongoing for every content update
• Building a proper i18n system into your CMS: 3–6 developer weeks, $40k–$80k loaded cost
• Running a translation SaaS that handles both on-the-fly: typically $0.10–$1.00 per visitor for the first million, scaling down

For most sites in the first-hundred-thousand-sessions range, the SaaS option is two orders of magnitude cheaper than the in-house build, and gets you live in minutes instead of months.

That's the deal SiteDialect makes. One script tag. 20+ languages. Every page on your site serves to international visitors in the language their browser asked for. hreflang emitted correctly. Translations cached at our edge. Priced as a small percentage of the tax you stop paying.

The frame shift

Stop thinking about translation as a cost center. It's a cost recovery. The cost is already there. Translating your site is how you stop paying it.