Two companies may each have a 30-page website but receive very different translation quotes. One site contains short corporate pages. The other includes technical product descriptions, SEO landing pages, downloadable brochures, and forms. The difference is not simply the number of pages; it is the content and work required to deliver usable translations.
For marketing, localization, and procurement teams, the most reliable way to estimate website translation cost is to build a content inventory, define target languages, and price each agreed deliverable. This guide explains how to do that without relying on misleading averages.
Quick Answer: How Much Does Website Translation Cost?
Website translation cost depends on source-content volume, target languages, subject complexity, translation workflow, repetition, and review requirements. A complete quote may also include SEO metadata, CMS extraction and import, graphics, downloadable files, linguistic quality assurance (QA), project management, and subsequent updates.
A practical starting formula is:
Initial website translation budget = linguistic translation work across all target languages + separately scoped supporting services.
For first-year planning, add the expected cost of new and revised content and any recurring platform fees. A per-word rate is therefore only one input. Two suppliers quoting the same word rate may be proposing different services.
Start with a Content Inventory, Not a Page Count
A 300-word contact page and a 3,000-word technical guide should not receive identical translation estimates merely because each counts as one URL. Some content is also invisible in the main page editor: navigation labels, reusable blocks, form responses, and SEO fields.
Before requesting a quote, export or audit your website content and record what must be translated.
| Content group | What to count | Common oversight |
|---|---|---|
| Core pages | Home, about, service, industry, product pages | Accordion and tab content |
| Resource content | Articles, FAQs, case studies, help pages | Archived or duplicate posts |
| Shared elements | Menus, buttons, footer, reusable blocks | Strings stored outside page content |
| Search content | SEO titles, meta descriptions, relevant alt text | Keyword adaptation excluded from translation |
| Supporting assets | Forms, emails, diagrams, PDFs, downloads | Text embedded in images or scanned files |
Define whether the project covers the entire site or a prioritized subset. Exclude obsolete pages, unused templates, duplicated exports, and content intended to remain in the source language. Preserve source files and URL-to-content mappings so translators can understand context.
Gross source words are not necessarily billable words. A supplier may analyze repeated segments and existing translations before applying an agreed pricing policy. Ask for the counting method, especially where content is stored as structured data or the language is billed by characters rather than words.

How Languages, Repetition, and Translation Memory Affect Cost
Every target language creates its own workstream. A site being translated from English into German and Japanese should normally be assessed separately for each target language, because rates, terminology needs, review arrangements, and formatting requirements can differ.
Specify regional requirements, too. French for France and French for Canada may share considerable language content but can require different terminology or review. Technical identifiers such as fr-FR and fr-CA are based on language-tag conventions described in IETF BCP 47; the actual commercial scope must still be agreed.
Translation memory (TM) stores previously translated segments for potential reuse. A translation analysis may identify new segments, exact matches, fuzzy matches, and repetitions within the current batch. These categories can change the amount of work required, but they do not carry universal discount percentages.
A fuzzy match may still require substantial editing. An exact match may need contextual verification. And a source phrase translated into German does not automatically provide an approved Japanese translation. Ask each supplier how matches are analyzed, charged, reviewed, and retained—and who owns the resulting TM.
Which Website Translation Pricing Model Makes Sense?
Website translation pricing is commonly structured by source word, target word, character, hour, fixed project, or recurring usage. The most useful comparison is the total scope of deliverables, not the lowest displayed unit price.
| Model | Suitable application | What buyers should verify |
|---|---|---|
| Per source word | Defined text volume | Match policy, minimum fees, included revision |
| Per target word or character | Agreed language-specific work | Counting method and final-bill uncertainty |
| Hourly | Content preparation, specialist review, QA | Rate, estimated hours, approval threshold |
| Fixed project | Stable scope and delivery package | Included pages, revisions, change requests |
| Subscription or usage | Continuous platform-based translation | Limits, overages, review, publishing responsibilities |
The translation workflow also influences costs. Human-led translation may suit high-stakes technical, legal, or brand content. Machine translation with human post-editing can be evaluated for suitable content with a defined quality target. AI-assisted workflows may support drafting, terminology tasks, or review, but their suitability depends on language, content, system controls, and human oversight.
Do not treat an automated subscription as equivalent to professionally reviewed, publication-ready copy. Evaluate confidentiality terms, data handling, review effort, and the cost of corrections. For a broader comparison of pricing mechanisms, see Translation Services Cost: How Professional Pricing Works.
What Website Content Creates Costs Beyond Main Page Copy?
SEO Metadata and Keyword Adaptation
Website translation can include page titles, meta descriptions, headings, image alt text, and internal-link labels. However, translating a keyword is not the same as researching what buyers search for in a target market. A technical product term may have a locally preferred synonym or different search intent.
If international organic search is important, request a separate line item for target-language keyword research and metadata adaptation. Google’s snippet guidance also explains that search snippets are generated primarily from page content and may use—but do not always reproduce—meta descriptions.
Forms, System Strings, and Shared Components
Quote form labels, field placeholders, validation messages, success confirmations, consent wording, navigation, and automated customer emails can all require translation. Shared strings should be inventoried once where genuinely reusable, rather than counted repeatedly in every page export.
Translating a form’s text does not necessarily include changing its phone-number validation, address fields, or submission logic. Those are separate functional localization tasks.
Text in Images and Downloadable Files
Banner slogans, charts, product diagrams, PDFs, brochures, and datasheets are easy to miss. Editable graphics may require translation plus layout work; flattened artwork or scanned PDFs can require additional text extraction and design preparation. Confirm whether new export files are part of the quote or will be prepared by your design team.
What Do CMS Handling, QA, and Project Management Add?
Content must move safely between the website and the translation workflow. Depending on the platform, teams may use structured CMS exports, CSV or JSON files, translation connectors, or XLIFF packages. OASIS XLIFF 2.1 is a standardized interchange format, but support depends on the actual CMS and tools.
Clarify whether the supplier will merely return translated files or also import them, check field mapping, and verify text in page context. Formatting, broken variables, missing strings, and inconsistent terminology can require correction even when the sentences are linguistically sound.
A quote should identify translation, revision, linguistic QA, in-context checking, stakeholder review rounds, and project management separately—or state clearly what the bundled fee includes. Formal process standards such as ISO 17100 concern defined translation-service requirements, while ISO 18587 addresses full human post-editing of machine translation output. Neither establishes a universal website translation price.
Website Translation Cost vs Website Localization Cost
Website translation primarily budgets the language conversion and associated content workflow. Website localization may add engineering, market adaptation, user experience, functional testing, and technical international SEO. The W3C’s explanation of localization makes clear that localization can involve much more than language.
| Cost area | Translation-focused budget | Broader localization budget |
|---|---|---|
| Page copy and UI text | Core work | Core work |
| Metadata | Translation; optional keyword adaptation | Market SEO strategy may be added |
| CMS | Text extraction/import as agreed | Multilingual configuration or engineering |
| Forms | Labels and messages | Local validation and user journeys |
| QA | Linguistic and contextual checks | Linguistic, visual, and functional tests |
| Market experience | Usually limited | UX, formats, offers, and regional adaptation |
These are scope distinctions, not fixed service bundles. For a detailed decision framework, read Website Translation vs Localization: Which Does Your Business Need?.
How to Calculate Website Translation Costs: Three Budget Examples
The following hypothetical content volumes are calculation examples, not industry averages or Textsprime prices. The figures represent gross source-word-language units before any TM adjustments or exclusions.
| Example site | Source words | Target languages | Gross word-language units |
|---|---|---|---|
| Small corporate site | 5,000 | 2 | 10,000 |
| Medium B2B site | 22,000 | 3 | 66,000 |
| Large content site | 90,000 | 5 | 450,000 |
For each language, use the supplier’s actual analysis to establish an adjusted billable volume or itemized match categories. Then apply that language’s agreed rates. Do not multiply a global word total by an assumed universal rate.
Example 1: Small Corporate Website
Consider 5,000 source words across corporate, service, contact, and policy pages, translated into two languages. Begin with 5,000 words per language, then apply each language’s approved TM and repetition analysis. Add any separately priced metadata, form strings, CMS import, and linguistic review.
Budget logic: language A’s analyzed linguistic fee + language B’s analyzed linguistic fee + separately quoted supporting services.
Ask whether minimum project charges apply and whether the supplier or internal team will publish the translated pages.
Example 2: Medium B2B Website
A 22,000-word manufacturer or software-marketing site may contain product specifications, application pages, industry terminology, and technical downloads. Across three target languages, the gross scope is 66,000 word-language units—not necessarily 66,000 fully billable new words.
Calculate each language separately. Group marketing copy and technical content where review needs differ. Add approved terminology development, priority keyword adaptation, PDF work, and stakeholder review only when they are not already included in the service rate.
Budget logic: sum of the three language-specific translation analyses + agreed technical/SEO/asset services + CMS and coordination costs.
Example 3: Large Content Website
A site with 90,000 source words and five target languages begins with 450,000 gross word-language units. Some articles may be low priority, while product pages or essential support content need earlier release. Approved translations and repeated components may be reusable within a target language.
Split the project into launch and later phases. Cost each phase using its own word analysis and review requirements; then forecast ongoing publication, updated pages, terminology maintenance, and any platform charges.
First-year budget logic: initial phased translation and supporting services + planned updates + recurring software or management fees.
The strongest budget is an itemized worksheet showing assumptions, language rates, match categories, included services, and exclusions. It allows procurement to compare equivalent proposals instead of treating the lowest headline number as the lowest total cost.

Hidden Website Translation Costs to Check Before Approval
Unexpected invoices usually come from poorly defined scope rather than the act of translation itself. Watch for late-discovered CMS fields, scanned files, incomplete source exports, graphic text, and rewritten source pages after translation has begun.
Other frequent questions concern additional reviewer rounds, supplier minimum fees, urgent changes, software overages, and whether translated content will arrive as files or actually appear on the website. Specify which party is responsible for corrections after import and which changes trigger a new quote.
A useful contract separates included revisions from new requests: fixing a mistranslation is different from translating a marketing paragraph rewritten after approval.
How Much Should You Budget for Ongoing Website Updates?
A multilingual website is a continuing content operation. Product specifications change, articles are published, landing pages are revised, and old claims need updating. The relevant cost is the new or changed content requiring translation—not automatically the entire previously translated page.
A simple first-year formula is:
First-year budget = initial project cost + translation and review of updates + recurring platform or service fees.
Ask your content team to estimate monthly or quarterly new words, likely updates, target languages, and review requirements. Compare pay-as-you-go requests with batched releases or a retainer using the same annual scope. Reuse may help, but only when the TM remains accessible, current, and contractually reusable.
How to Reduce Long-Term Translation Costs Without Sacrificing Quality
The most dependable savings strategy is to translate the right content through a repeatable workflow, not simply select the cheapest rate.
Prioritize commercially important pages and market-required information first. Remove stale material before exporting. Maintain approved terminology, reuse consistent product descriptions, and centralize translation memory where appropriate. Freeze or version source content before each release to limit avoidable rework.
Match review depth to the risks of each page. High-value product claims and technical instructions may need specialist approval; lower-risk reference content may follow another agreed workflow. A documented update schedule and clear ownership of approvals can prevent recurring coordination costs. For the wider operating model, see What Is a Global Content Strategy?.
What to Include When Requesting a Website Translation Quote
A useful supplier briefing should make two proposals comparable. Before sending it, complete the following checklist:
- Source website, CMS, available exports, and page/content inventory.
- Source language, exact target languages or locales, and target audiences.
- Included and excluded URLs, assets, PDFs, and system strings.
- Source-word or character counts, repetition analysis, and counting rules.
- Translation workflow, subject expertise, terminology, and review level.
- SEO metadata translation and any separate keyword adaptation.
- Ownership of CMS extraction, import, in-context checks, and publication.
- QA, stakeholder approvals, correction rounds, and acceptance criteria.
- Rates by language, TM-match rules, minimums, software fees, and exclusions.
- Deadlines, change-request process, TM ownership, and planned updates.
If the site is technically complex or updated frequently, a professional language team can help determine which tasks require translation, which need content engineering, and which should be quoted separately. Explore Textsprime’s language translation solutions when preparing that scope.
FAQ
Is Website Translation Usually Charged Per Word?
Often, but not always. Suppliers may use source words, target words, characters, hours, fixed project fees, subscriptions, or combinations. Confirm the billing unit and what review is included.
Does Translating More Languages Multiply the Cost?
Each language adds work, but the total is not necessarily a simple multiple. Rates, selected pages, existing translation memory, and review requirements may vary by language.
Can Translation Memory Reduce Update Costs?
It can support reuse of approved segments and reduce repeat work. The financial effect depends on match quality, context checks, contractual pricing rules, and access to the TM.
Is AI Website Translation Cheaper Than Human Translation?
Automated generation may carry a lower initial processing charge, but total costs depend on human review, corrections, tool subscriptions, privacy requirements, and quality expectations. Compare equivalent finished deliverables, not only generation fees.
Are Website Translation and Localization Costs the Same?
No. Translation-centered costs cover language and associated content work. Localization can add market research, UX adaptation, technical configuration, and functional testing. The correct scope depends on what visitors need to do on the site.
Final Takeaway
To estimate the cost to translate a website, start with a reliable inventory, price the actual content for each target language, and specify exactly what happens before and after translation. Include supporting assets, quality checks, CMS responsibilities, and future updates. A transparent scope-based estimate gives business teams a budget they can defend—and a fair basis for comparing translation providers.

