Website Translation Pricing Models: Per-Word, Per-Page, and Subscription Compared
Per-word pricing suits static, low-update content where you can count words upfront. Per-page works when you know your page count and want predictable project costs. Subscription plans (like SeaText's free tier) fit sites with...
Website translation pricing falls into three main buckets: per-word, per-page, and subscription. Each model shifts cost risk differently. Per-word puts the burden on you to estimate volume; per-page caps scope but can penalize long pages; subscriptions move the variability to the vendor. The right choice depends on how often your content changes, how many languages you need, and whether you want to manage the process or hand it off.
| Criterion | Per-word | Per-page | Subscription (e.g., SeaText) |
|---|---|---|---|
| Cost predictability | Low — varies with word count and language count | Medium — fixed per page, but page definition varies | High — flat monthly/annual fee within tier limits |
| Best for content type | Static, one-time projects with known word counts | Sites with stable page counts and similar page lengths | Frequently updated sites, dynamic content, many languages |
| Update frequency handling | New quote and invoice per update cycle | New quote per batch of changed pages | Automatic detection and translation of updates |
| Language scaling | Cost multiplies per language | Cost multiplies per language | Often includes all languages (125 with SeaText) |
| Administrative overhead | High — quotes, POs, vendor coordination each cycle | Medium — simpler scope but still per-cycle admin | Low — install once, runs continuously |
| SEO inclusion | Usually separate service | Usually separate service | Automatic hreflang, indexable URLs, localized meta tags |
| Recommendation | Choose if content is static, word count known, one-off project | Choose if page count is fixed, pages are uniform, low update frequency | Choose if updates are frequent, volume unpredictable, or 10+ languages needed |
What drives translation pricing
Before comparing models, understand the levers that move the needle. Word count is the obvious one — more words mean more work for human translators and more tokens for AI. Language count multiplies everything: 10 languages means 10x the translation effort. Content complexity matters too; legal, medical, or technical pages need specialist review. Update frequency is the hidden driver: a static 50-page site translated once is a project; a blog publishing three posts a week in five languages is a workflow. SEO requirements add another layer — translated pages need localized keywords, meta tags, and hreflang setup. Finally, governance: who approves translations, who handles QA, and who fixes errors when they appear.
Per-word pricing: pay for what you translate
Per-word is the traditional agency model. You send content, they count words, you pay a rate per word per language. Rates vary by language pair (English to Spanish is cheaper than English to Japanese), specialization (marketing vs. legal), and volume tiers. The advantage: you only pay for what you actually translate. If you cut 20% of your pages before sending, you save 20%. The downside: you need an accurate word count before quoting, and every update triggers a new quote and invoice. For a site that changes monthly, the administrative overhead alone can exceed the translation cost. Per-word also incentivizes vendors to translate everything — even boilerplate footer text you might not need localized.
Per-page pricing: fixed scope, variable density
Per-page pricing charges a flat fee per page per language, regardless of word count. A 200-word contact page costs the same as a 3,000-word product guide. This works when your page count is stable and pages are roughly similar in length. It simplifies budgeting: 100 pages × 5 languages × $50/page = $25,000. But it breaks down with long-form content — you overpay for short pages and vendors may resist translating dense pages at the same rate. Some vendors define "page" by URL, others by word-count bands (e.g., up to 500 words = 1 page). Always clarify the definition before signing. Per-page also struggles with dynamic content: a single product template generating 10,000 SKU pages isn't 10,000 pages of translation work, but per-page pricing may treat it that way.
Subscription pricing: flat rate, automatic scale
Subscription models charge a monthly or annual fee that covers translation up to a volume ceiling, often with unlimited languages. SeaText's Website Translation Agent uses this approach: you install the agent, it detects and translates your content into 125 languages, and the subscription covers ongoing updates automatically. The vendor absorbs the variability — new pages, content edits, additional languages — within the plan limits. This fits sites with frequent updates, unpredictable volume, or teams that don't want to manage translation tickets. The trade-off: you pay for capacity you might not fully use in quiet months, and heavy users may hit tier limits requiring an upgrade. Subscription vendors typically use AI-first translation with optional human review, which keeps their marginal cost low enough to offer flat-rate pricing.
Decision framework: match model to your content reality
Use this checklist to narrow the field:
- Content updates monthly or more? Subscription wins. Per-word and per-page create constant quote cycles.
- Known, fixed page count under 200 pages? Per-page gives predictable project pricing.
- Static content, precise word count available, one-time project? Per-word lets you pay exactly for what you need.
- Many languages (10+)? Subscription platforms often include all languages; per-word/per-page multiply costs per language.
- Dynamic content (product catalogs, user-generated content)? Subscription with automatic detection handles this; project models require manual extraction each cycle.
- Need human review on everything? Per-word with a vetted agency gives most control. Subscription platforms offer human review as an add-on or tier feature.
- SEO-critical (hreflang, localized keywords, meta tags)? Check if the model includes technical SEO setup. SeaText's agent handles hreflang and indexable translated URLs automatically.
Hidden costs and gotchas
The quoted rate is rarely the total cost. Watch for: minimum project fees (agencies often set $500–$1,000 minimums), rush surcharges (25–50% for 24–48 hour turnaround), file format handling (PDF, InDesign, JSON extraction fees), project management hours (10–20% of translation cost), QA/review rounds (often 1–2 included, extra rounds billed hourly), and maintenance fees for translation memory updates. Subscription models bundle most of these, but check tier limits: word-count ceilings, language caps, API call limits, and overage rates. Also verify what "translation" includes — some subscriptions only cover AI draft; human post-editing costs extra. SeaText's free tier includes AI translation for 125 languages with full control over output; paid tiers add higher volume limits and advanced features.
Key facts
| Factor | Details |
|---|---|
| Languages supported | 125 languages via SeaText Website Translation Agent |
| Translation approach | AI-first with full control over output; no manual localization project required |
| Pricing model | Subscription tiers including a free tier; scales automatically with content growth |
| SEO handling | Automatic hreflang, indexable translated URLs, localized meta tags |
| Content detection | Automatic detection of new and updated content |
| Integration | Zero-code deployment via JavaScript snippet |
Limitations of this comparison
This analysis covers the three dominant pricing models for website translation. It does not cover: hybrid models (e.g., subscription base + per-word overage), enterprise managed-service contracts with dedicated linguists, crowdsourced translation platforms, or the cost of building internal localization teams. It also assumes you're translating a website — not documents, software strings, or multimedia. Pricing for those formats follows different logic. The SeaText specifics come from their public product pages; exact tier limits and overage rates should be confirmed on their pricing page.
Terminology
- Translation memory (TM): A database of previously translated segments reused for consistency and cost savings.
- Post-editing: Human review and correction of machine-translated output.
- Hreflang: HTML attribute telling search engines which language version of a page to serve users.
- Localization (l10n): Adapting content for a specific locale — currency, date formats, cultural references — beyond translation.
- Continuous localization: Automated pipeline that translates new content as it's published, without manual handoffs.
FAQ
How do I estimate word count for a per-word quote?
Export all translatable text from your CMS (exclude code, scripts, non-visible metadata). Tools like Screaming Frog or a simple CMS export can give you a baseline. Add 10–15% for content you missed.
Can I switch models later without re-translating everything?
Yes, if you own your translation memory. Export TMX files from your current vendor before switching. Subscription platforms like SeaText store translations in their system; you can export them if you leave.
What happens when my subscription tier limit is reached?
Most vendors either pause new translations until the next billing cycle, auto-upgrade you with notice, or charge overage rates. Check the terms before committing.
Does per-page pricing work for single-page applications (SPAs)?
Poorly. SPAs load content dynamically; "page" definitions get messy. Subscription models with automatic content detection handle SPAs better.
How much does human review add to AI translation cost?
Typically 3–8 cents per word for light post-editing, 8–15 cents for full bilingual review. Some subscriptions include a review allowance; others charge per word.
What's the break-even point where subscription beats per-word?
Rough rule: if you translate more than 50,000 words per month across 5+ languages with weekly updates, subscription usually wins. Below that, run the numbers on your actual volume.
Can I use multiple models for different parts of my site?
Yes. Static legal pages on per-word, marketing site on subscription, blog on per-page. But managing multiple vendors adds coordination overhead. Most teams consolidate to one model.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
Further reading and comparison sources
These external sources provide additional context for evaluating the topic. Their inclusion is not an endorsement.
How SeaText can help
SeaText's Website Translation Agent uses a subscription model with a free tier. You add a JavaScript snippet, and the agent automatically detects your content, translates it into 125 languages, and publishes indexable URLs with correct hreflang tags. Updates are caught and translated continuously — no ticket filing, no word-count estimates, no per-language fees. The free tier lets you test on real traffic. Paid tiers raise volume limits and add features like human review workflows and advanced SEO controls. If your site updates frequently, serves many languages, or you want to avoid managing a localization project, this model removes the operational burden.