Reviewed: 5 October 2026.
Quick answer
Website translation costs depend on the content that needs processing, the language pair, specialist terminology, review requirements and the agreed delivery method. A quote for translated text is different from a quote that also includes uploading content, checking forms and reviewing the website in context. To compare proposals fairly, give each provider the same page inventory and ask them to describe the same deliverables.
The number of visible pages is a useful starting point, but it is not a complete measure of work. A short company page, a product specification table and a transactional form create different tasks. Before asking for a total, identify the target audience, the source version and the content your visitors need to complete their journey. You can discuss the project through website localization services or send an initial quotation request.
What to confirm first
- Does the proposal cover translation only, or also CMS entry?
- Are menus, forms, automated messages and metadata included?
- How will repeated content and later changes be handled?
- Who will approve terminology and review the translated interface?
- What files or published pages will you receive?
- Who is responsible for final approval and publication?
Why websites with the same page count can cost differently
Consider two hypothetical websites with twenty pages each. The first contains short company introductions. The second contains product tables, specialist descriptions, warning text and diagrams with embedded labels. Their page counts match, but their translation and checking requirements do not. This illustration is a planning example, not a client case or a LocalizeZone price estimate.
Content may also appear outside the main page body. Navigation labels, error messages, confirmation screens and downloadable documents can be essential to the visitor experience. Some are visible publicly, while others only appear after an action. A provider reviewing the homepage alone cannot reliably identify all of them.
Send a page list and representative samples, including a complex page rather than only the most straightforward introduction. If the website is not public, an export with screenshots can help show where each item appears. A stable inventory makes it easier to explain the workload and avoid surprises after the quote has been accepted.
Translation and localization have different boundaries
W3C describes localization as adaptation to the language, cultural and other requirements of a target market. [1] In a website project, this can involve more than transferring sentences into another language. However, the word localization should not be treated as an unlimited promise to redesign every interaction.
The brief should distinguish translation, editorial adaptation and technical implementation. For example, adapting a call to action may be a language task, while changing the structure of a purchase flow is a product or development task. Each needs its own owner and acceptance criteria.
If your development team will implement the content, you may need translated files and an in-context language review. If you also want content entry, specify the platform, the working environment and the person authorized to publish. A phrase such as full service is helpful only when it is followed by an actual list of included work.
Build a content inventory before comparing prices
Organize the inventory by function and location. This makes it easier to notice content that a page count misses and to assign internal reviewers. The following framework is a suggested project tool; it should be adjusted to the website rather than treated as a mandatory checklist for every business.
| Content group | Typical items | Useful input | Scope confirmation |
|---|---|---|---|
| Core pages | Home, company and services | URLs and current source copy | Approved page list |
| Products | Descriptions, attributes and tables | Export with field identifiers | Translate or preserve each field |
| Interface | Menus, buttons and notifications | String list with screenshots | Check the actual display context |
| Forms | Labels, errors and confirmations | Examples of each state | Include success and failure states |
| Search fields | Titles and descriptions | Current metadata and target market | Separate translation from research |
| Messages | Enquiry or transaction emails | Templates with variables | Preserve system placeholders |
| Visuals | Banners and diagram labels | Editable assets where available | Agree translation and layout work |
| Downloads | Catalogues and manuals | Source files and reference exports | Identify separate document tasks |
An inventory also supports approval. A product owner can confirm specifications, marketing can approve positioning, and a technical contact can check form behavior. Collecting decisions through one coordinator is usually clearer than allowing several reviewers to make conflicting changes in separate copies.
Understand the pricing basis
Quotes may use a word count, hours, a project total or an agreed update arrangement. None of these is automatically the best choice for every website. The useful question is whether the charging method reflects the work and the boundaries that have been agreed.
| Pricing basis | Can suit | Ask the provider | Common misunderstanding |
|---|---|---|---|
| Per word | Exported, stable source text | Which source and fields are counted? | Interface content is omitted |
| Per hour | Review, CMS work and investigation | How is time recorded and capped? | The final budget is unclear |
| Project total | A defined delivery inventory | Which pages and review rounds? | The scope behind the total is vague |
| Update arrangement | Regular new or changed content | What volume and schedule apply? | New material is confused with corrections |
Compare total costs for the same outcome. A lower translation rate may exclude the upload or interface checks included elsewhere. Equally, a higher total does not prove better quality without an explanation of review and delivery. Ask about unclear items before deciding rather than assuming they are included.
This article does not publish invented prices as a LocalizeZone tariff. A real commitment needs the source content, language pair and deliverables to be assessed. Dates and costs should be confirmed against that actual project.
Define the SEO work separately
Translating a title, adapting a page to a search intent and implementing technical SEO are related but distinct jobs. A quote should say which are included and who approves changes. Search research for a new market should not be silently treated as part of translating existing sentences.
Google recommends descriptive, concise titles and discourages keyword stuffing. [2] Each translated page therefore needs a title that reflects its own subject rather than a repeated generic phrase. Google also explains that snippets may come from page content and sometimes from a meta description. [3] A translated description is useful, but it does not guarantee that the search engine will display it unchanged.
When keyword research is requested, agree on the market, data source and pages to be adapted. Do not treat an unverified search-volume figure or a promised ranking as evidence of a sound translation plan. The deliverable should be a defined set of decisions that your team can review and implement.
Decide between file delivery and CMS entry
File delivery can work well when your own team manages the website. It should include page identifiers, field names and a clear connection between the source and translated text. An unlabeled document of translated paragraphs may create unnecessary work and increase the chance of placing content on the wrong page.
For CMS entry, agree on access, a test environment and publication authority. Someone may be allowed to enter text without being authorized to change URLs or publish the site. Permissions should follow the actual task. A quotation review does not usually require sharing a full administrator password.
Google recommends separate URLs for language versions. [4] If the project includes a new language structure, identify who creates those URLs and handles language links. Translation cannot substitute for that technical implementation. The proposal should make the handoff between the language team and the website team explicit.
Compare proposals using the same acceptance criteria
Create one list of expected outputs and place each proposal against it. Mark an absent or unclear item as a question rather than an inclusion. This exercise often reveals whether two totals describe the same service.
A practical sequence is to freeze the source version, list pages and fields, identify the audience, agree terminology and separate new translation from review of existing text. Then confirm revision rounds, file formats, CMS responsibilities and publication approval. Finally compare the price and schedule against those same requirements.
Acceptance should be observable. Instead of asking for perfect translation, specify that approved terminology is used, agreed fields are present and essential form states have been reviewed in context. If your staff must approve technical content, identify them in the plan and allow time for their feedback.
Changes need a clear route too. Ten pages added after the inventory is agreed are different from a missing field that was already included. Define how new content is assessed, how approved wording is updated and how comments are consolidated. This avoids turning every later change into a dispute over what the original quote meant.
Reduce unnecessary work without removing essential checks
Prioritize content that supports the target visitor. A first phase may cover the homepage, key services or products, contact details and the enquiry flow. Older news can be assessed later. Check links between these pages so that the visitor does not encounter an untranslated essential step in the middle of the journey.
Prepare consistent names and resolve contradictory source content before translation. If one product has several different descriptions internally, nominate a person to choose the approved version. This reduces avoidable discussion, although no fixed saving percentage can be promised from that preparation.
Avoid removing important checks merely to shorten the quote. A form error or confirmation message can explain what the customer should do next. Reviewing a complete enquiry journey may be more useful than translating every archived article in the first phase. Prioritization is a business decision supported by a clear inventory, not an excuse to leave critical information unexamined.
FAQ
Can I request a quote by sending only a URL?
A URL is enough to start reviewing public content. Hidden pages, messages, downloads and form states may need an export or additional examples. The final quote should reflect the complete agreed scope rather than only what can be seen from the homepage.
Is website translation charged by page or by word?
The method depends on the content and deliverables. Ask how the count is calculated and which fields are included. Comparing rates is meaningful only when the proposals use the same scope and offer the same type of output.
Can I translate selected pages first?
Yes, a phased plan can be considered. Identify the priority pages and check the visitor journey between them. Essential instructions or contact steps should not be missing simply because they sit on a page outside the first list.
How is an AI-translated website assessed?
Send the source and the existing translation together. A representative sample helps determine whether post-editing, more extensive revision or translation of some sections is appropriate. The tool used to produce the draft does not by itself establish the work needed.
Are later updates included?
Only when they are part of the agreed scope. Separate corrections to the delivered work from new pages or changed product information. An update arrangement should specify the submission process, expected volume and approval responsibilities.
Do I need to share administrator access for a quote?
An initial review can usually begin with URLs, exports or screenshots. Access should be considered when an implementation task has been agreed, using a suitable account and permissions. Confirm who will enter, review and publish the content.
Sources and method
The numbered references support the points about localization and official search guidance. The inventory tables, comparison method and hypothetical example are editorial project-planning proposals. They are not evidence of a particular client result, a fixed price, a certification or a guaranteed search ranking.
References
[1] W3C Internationalization — Localization vs. Internationalization.
[2] Google Search Central — Influencing your title links in search results.
[3] Google Search Central — Control your snippets in search results.
[4] Google Search Central — Managing multi-regional and multilingual sites.
Request a quote for your website
Send the website URL, required languages and expected timing through the quotation form. You can attach an export to help define the scope. If you need to discuss delivery or implementation, visit website localization or contact LocalizeZone so the proposed work can be reviewed against your actual website.