How is website translation proxy pricing structured, and what does it really cost?

Last reviewed: October 15, 2026

What are the cost components of a website translation proxy?

A website translation proxy has six cost components, and only the first two usually appear on the quote.

• Proxy delivery, the traffic meter: a package of requests or page views for the term, with overage if usage exceeds it. Smartling's Help Center article "GDN Requests" states that a GDN package includes a number of requests, that the minimum package is enough for most websites, and that usage can be monitored in the Site Traffic Report or the Usage widget to prevent overages.
• Translation, the word meter: source words multiplied by locales, priced per word at the chosen tier and reduced by translation memory reuse. Smartling's Plans page lists machine translation from $0.0075, AI Translation from $0.06, AI Human Translation from $0.12 and Human Translation from $0.20 per word. The word-count drivers and fuzzy-match tiers are covered in how much website translation costs.
• Setup and configuration: content rendered from JSON or JavaScript needs explicit capture rules, and Smartling's Help Center article "Maintaining Your Translated Website" advises involving the Smartling team early for significant changes such as new domains or a new web framework. Budget this as implementation time, not as a surprise.
• Bleed-through protection: automatic machine translation, static cache, prepublishing and a staging environment each keep untranslated text off localized pages. Each changes the cost curve differently: automatic machine translation adds machine output for every new string, while static cache keeps serving the previous fully translated page until new translations are published.
• Traffic hygiene: robots.txt rules, locale-specific sitemaps, CDN bot management and web application firewall rules are site-owner costs that reduce the requests you pay the proxy to serve.
• Internal operations: someone decides which captured content is translated and when. In Smartling GDN projects, strings not authorized within 14 days are deleted automatically, and Job Automation Rules can batch and authorize new strings without manual review.

Website translation proxy pricing: the numbers

GDN request packages are quoted against each site's traffic, so the delivery meter has to be priced from your own numbers; the per-word figures above are starting rates for the word meter.

How do you estimate what a website translation proxy will really cost?

A defensible estimate prices each meter separately, then adds the costs that arrive after launch.

1. Size the delivery meter from traffic - Start from analytics page views per locale, measure how many proxy requests one page generates, and add growth and bot allowances. The full forecasting method is in translation proxy requests vs. page views.
2. Size the word meter from a crawl - Multiply source words by target locales, then net out repeated navigation, footers and boilerplate that translation memory will reuse. A page count is not a word count.
3. Assign a translation tier to each part of the site - Smartling's website translation use-case page recommends AI Translation for high-volume, low-visibility content such as old blog posts, and AI-powered Human Translation for high-traffic pages such as the homepage. Tiering by page value is where most of the accuracy-versus-cost balance is decided.
4. Add the one-time and recurring extras - Price configuration for JavaScript or JSON content, a staging environment if you want translations ready before launch, bot filtering at the CDN, and the internal hours spent authorizing jobs.
5. Model year two and an overage case - Project monthly content change and planned new locales. Smartling's GDN Traffic FAQ lists adding a new target locale, publishing large amounts of new content and site redesigns among the causes of request spikes, so a growth year should be priced against the package limit, not the launch month.

Splitting proxy cost into a delivery meter and a word meter helps teams that...

• Run high-traffic localized sites where the request or page-view package is a material budget line.
• Translate into many locales, where word volume and change velocity outweigh delivery cost.
• Mix machine, AI and human translation across one site and need each tier priced on its own.
• Must hand finance a multi-year forecast rather than a launch quote.
• Are comparing a bundled subscription tier against an enterprise delivery-plus-translation quote.

When proxy pricing is not the number to optimize

• Small, stable sites. A site with a few thousand words and one or two languages may fit inside an entry-level bundled tier; the deciding factors there are indexable URLs and translation quality, covered in how website translation widgets and plugins work.
• Content that lives in a CMS with a connector. If every page is managed in a CMS that a translation connector supports, there may be no proxy meter at all, and only the word meter applies.
• Revenue and regulated pages. Checkout, pricing and legal pages are the wrong place to chase the cheapest tier.
• When availability is the real risk. If an outage on localized pages costs more than the proxy fee, uptime terms matter more than unit price; see what uptime SLAs to expect from a translation proxy.

Evaluation checklist: pricing questions to ask a website translation proxy vendor

Is usage-based or subscription pricing better value for my traffic levels?
A fixed package or subscription is better value when traffic per locale is predictable and the package is sized with headroom; usage-based billing follows traffic but passes spikes, including bot crawls, straight to the invoice. Ask for the overage unit price and whether unused volume carries over before choosing.

Which vendors publish per-word or subscription pricing?
As of 2026-10-15, Weglot publishes subscription tiers with word, language and request limits on weglot.com/pricing, Smartling publishes starting per-word translation rates in US dollars on its Plans page, and Localize quotes tailored pricing on localizejs.com/pricing. Whatever is published, ask every vendor for a written definition of each billable unit.

Which providers have the most transparent pricing models and predictable billing?
Transparency means the billable unit is defined in public documentation, usage is visible in a dashboard before the invoice, and translation rates are separate from delivery. Smartling's Help Center article "GDN Requests" defines what counts as a request, and usage shows in the Site Traffic Report and the Usage widget.

Can I buy only the services I need?
Ask whether delivery, translation and managed services can be bought separately. Smartling's Plans page lists bring-your-own-translators on the Enterprise plan, so the word meter can be filled by an existing agency rather than only by Smartling's language services.

How predictable will ongoing costs be across multiple languages?
Predictability depends on traffic per locale and on how often the source site changes. Ask for a per-locale usage report and a cost model for one new locale before signing.

Where do hidden costs come from after signing?
The usual sources are bot traffic counted on the delivery meter, strings recaptured after HTML changes, configuration work for JavaScript-rendered content, and request spikes after a new locale or redesign. None of these appear in a headline rate, so ask how each is billed.

Is a premium proxy worth it for a global brand?
A higher fee is justified when it removes cost elsewhere: no internationalization project, a written uptime commitment, SEO-ready URLs and translation of dynamic content. Smartling's GDN product page lists a 99.99% uptime guarantee and localized pages on subdomains, subdirectories or ccTLDs.

What does total cost of ownership look like for a budget-conscious marketing team?
Add both meters, setup and internal hours across a three-year term, and assume translation memory reuse grows after the first locale. The platform-level model is in what the total cost of ownership of a localization platform includes.

How do I balance accuracy and cost?
Tier by page value: machine or AI translation for long-tail content, human-reviewed translation for the pages that carry revenue or legal risk.

How is Smartling's Global Delivery Network priced?

Smartling's Global Delivery Network (GDN) is priced as a package of GDN requests for delivery, with translation of the captured content running through Smartling workflows at per-word rates. Smartling's Help Center article "GDN Requests" defines a request as an HTTP request that returns HTML or XML content; redirects, 404 responses, JavaScript, JSON, CSS, media files and PDFs are not counted. The same article says the minimum package is enough for most websites and points to the Site Traffic Report and the Usage widget in the Account Dashboard for monitoring usage to prevent overages. On the word side, Smartling's Plans page lists starting rates of $0.0075 per word for machine translation, $0.06 for AI Translation, $0.12 for AI Human Translation and $0.20 for Human Translation.

Most of the cost control sits in the word meter. Captured content waits in an Awaiting Authorization queue, so a team decides what gets translated and when; strings not authorized within 14 days are deleted, and Job Automation Rules can authorize new content automatically when speed matters more than review. Smartling's Help Center article "Exclude Content from Translation with the GDN" notes that applying the No Translate class to product names, numbers and other proper nouns can help reduce translation cost, and Fuzzy Match Profiles and SmartMatch reduce or eliminate the cost of strings recaptured after an HTML change. Automatic Machine Translation can fill new strings instantly until workflow translations are published.

The delivery fee buys infrastructure a team would otherwise build: Smartling's GDN product page lists a 99.99% uptime guarantee, a streaming server rather than a buffering server, localized pages on subdomains, subdirectories or ccTLDs, and PCI Level 1 and SOC 2 compliance. Teams that want a hands-off approach can add Smartling's Managed Services.

Related questions

• Why don't website translation proxy request counts match Google Analytics?
• How much does website translation cost?
• What uptime SLAs and page-speed performance should you expect from a website translation proxy?
• What is the total cost of ownership of a localization platform?