A small brochure-style multilingual website in the UK typically starts in the low thousands, while a full ecommerce rollout across several languages can run into tens of thousands. The final figure depends on three things: how big your site is, how many languages you need, and whether you choose human, machine, or hybrid translation. Layer in design, technical setup, and ongoing maintenance, and you have your real budget picture, not just a headline number.
TL;DR:
- The total cost of a multilingual UK website depends heavily on site size, language count, and translation method, with larger and more complex sites costing tens of thousands.
- Designing, developing, and maintaining hreflang tags and technical infrastructure requires clear budgeting, as these ongoing costs can outweigh initial setup expenses.
- Prioritizing human translation for key revenue pages and using machine or hybrid workflows for the rest helps control long-term costs, especially when targeted at top-performing content.
- Hreflang implementation should be automated via sitemaps rather than manual updates, and CMS integration costs vary based on platform, impacting ongoing maintenance.
- SEO, cultural adaptation, and accessibility work typically add 15% to 25% to base translation costs, ensuring content is findable, culturally appropriate, and functional across markets.
Table of Contents
- What actually makes up a multilingual website quote
- Human, machine or hybrid translation: what UK rates actually look like
- What hreflang, URLs and CMS choices really cost you
- Budgeting for SEO, cultural fit and accessibility
- Timelines and annual costs you should plan for
- Three UK budget scenarios worth comparing
- What to ask suppliers before you sign anything
- Why our UK pricing bands are a useful reference point
- What most cost guides get wrong
- Ready to scope your multilingual project properly?
- Where to check the detail yourself
- Sources
- FAQ
What actually makes up a multilingual website quote
When you ask for a quote and get a single number back, you are not seeing the whole picture. A multilingual website budget is built from three separate buckets, and each one can swing the total considerably depending on the choices you make.
Design and development is the foundation. If your site uses a subfolder structure (yoursite.co.uk/fr/, yoursite.co.uk/de/), development is usually more efficient because you are working from one template that flexes per language. A multisite setup, where each language effectively runs as its own instance, gives you more control over region-specific content but multiplies your build and testing time. Bespoke templates per language, perhaps because Arabic needs right-to-left layout or German text runs 30% longer than English, add real hours to a project.
Translation and localisation is where most business owners underestimate cost. Agencies price by the word or by the page, and either way you are paying for more than just swapping words. A proper translate-edit-proofread (TEP) workflow means three separate people touch your content before it goes live. Add desktop publishing (DTP) work if your site has embedded graphics with text, or extra formatting time for non-Latin scripts like Japanese or Arabic, and the per-word rate stops telling the whole story.
Technical operations cover everything that keeps the multilingual experience working behind the scenes. That includes hosting configured for multiple locales, a content delivery network if you are targeting international visitors, hreflang tags so search engines serve the right language to the right audience, Google Search Console setup per language version, and API or connector work if your CMS needs to talk to a translation management system. Quality assurance testing across every language version rounds out this bucket, and it is often the line item agencies quote too thinly.
Here is how those three buckets typically break down in scope:
- Design and development: template creation, layout adjustments for text expansion, subfolder or multisite architecture decisions.
- Translation and localisation: per-word or per-page translation, TEP review cycles, DTP for graphics, non-Latin script formatting.
- Technical operations: hosting and CDN configuration, hreflang implementation, Search Console setup, CMS connectors, cross-language QA testing.
The businesses that budget well treat these as three separate conversations with their supplier, not one blended number. If your quote does not break these out, ask for it to be split. You will see immediately where the money is going, and where you might trim scope without damaging the result.
Human, machine or hybrid translation: what UK rates actually look like
Your translation method choice affects cost more than almost any other decision in the project, so it is worth getting specific about UK pricing bands before you commit.
Human translation for general business content in the UK typically runs at £0.10 to £0.18 per word, with specialist subjects such as legal or medical content pushing rates higher and rush jobs carrying surcharges. Machine translation with human post-editing sits well below that, at roughly £0.04 to £0.08 per word, because the human editor is refining rather than translating from scratch.
Human translation gives you the highest quality and the safest choice for anything customer-facing where tone and accuracy matter, product pages, legal terms, checkout flows. It costs more and takes longer, but for content that drives revenue, that cost is usually justified.
Machine translation with post-editing works well for high-volume, lower-stakes content: blog archives, help centre articles, product descriptions that follow a repeatable pattern. Quality has improved considerably, but nuance, humour and persuasive copy still suffer without a skilled editor checking the output.
Hybrid workflows are what most sensible UK businesses land on. You put human translation budget into the pages that earn you money, checkout, pricing, core service pages, and let machine translation plus light editing handle the long tail. Translation agencies typically build TEP cycles and project management into their agency rates, and translation memory can reduce effective per-word costs on large or recurring projects, since repeated phrases are not billed twice.
One figure worth remembering: agencies commonly recommend directing human translation budget to the top 10% to 20% of revenue-driving pages and using hybrid or machine-assisted workflows for everything else, which keeps lifetime translation costs under control as your site grows.
A practical way to think about this: if you are translating a 12,500-word ecommerce catalogue into German, base translation at the general business rate could land around £1,250, before you add SEO localisation on top. That figure is a useful anchor, not a universal price, since your own word count and language pair will move it.
- Human translation suits customer-facing, revenue-critical pages where accuracy and tone matter most.
- Machine translation with post-editing suits high-volume, lower-stakes content like archives or FAQs.
- Hybrid workflows let you concentrate spend where it earns the most return.
What hreflang, URLs and CMS choices really cost you
Technical decisions made in week one of a multilingual project tend to echo through every year that follows, so it is worth slowing down here rather than letting a developer default to whatever is quickest to set up.
Your URL structure choice affects both upfront and ongoing cost. A ccTLD (a separate domain per country, like yoursite.de) gives you the strongest local signal to search engines and users but costs more to run, since you are managing multiple domains, and it splits your overall domain authority. A subdomain (de.yoursite.co.uk) sits in the middle. For most UK businesses, a subfolder (yoursite.co.uk/de/) is the recommended default, because it keeps your domain authority consolidated and is the cheapest structure to build and maintain.
Hreflang tags tell search engines which language version to show which audience, and they are essential for any multilingual site that wants to rank properly. The catch is maintenance. Hreflang requires reciprocal annotations between every language version, so adding a fifth language to a four-language site means updating tags across all five, not just the new one. Done manually, this becomes a growing developer task with every language you add. Done through a template or sitemap-based approach, the system updates itself when new pages are published, which keeps ongoing costs far lower than manual tagging.
CMS integration costs vary depending on your platform. Some CMS platforms have multilingual plugins that handle much of this natively, others need custom connector or API work to sync content with a translation management system. Either way, budget time for QA testing every language version separately, since a layout that works in English can break when German text runs longer or Arabic needs right-to-left alignment.
- Subfolders are usually the cheapest and easiest structure for UK businesses to build and maintain.
- Hreflang needs reciprocal tagging across every language version, so plan for template or sitemap-based automation rather than manual updates.
- CMS connector and API costs depend on your platform, and QA testing should be budgeted per language, not once for the whole site.
Pro Tip: Ask your developer to build hreflang through your sitemap rather than hard-coding it into templates. It is a small extra cost upfront that saves hours every time you add a language.
Budgeting for SEO, cultural fit and accessibility
Getting a page translated is only half the job. If nobody in your target market can find it, or if it reads as obviously foreign, the translation has not done its work.
Multilingual SEO means researching keywords in each target language rather than translating your English keyword list directly, since search behaviour and phrasing differ by market. It also means localising metadata, page titles and structured data for each version. Agencies commonly see this work add an estimated 15% to 25% uplift on top of base translation costs, depending on how many pages need keyword-specific optimisation rather than direct translation.
Cultural adaptation, sometimes called transcreation, goes further still. Marketing copy, taglines and calls to action often need rewriting rather than translating, because a phrase that works in English can fall flat or mean something unintended elsewhere. This applies most to your homepage, hero messaging and any campaign-specific landing pages, less to functional content like shipping policies.
Accessibility and layout work rounds this out. Non-Latin scripts need font support and spacing checks. Dates, currencies and number formats need localising properly, £10.50 does not automatically become €10,50 just because the page is in French, and getting this wrong undermines trust fast.
- SEO localisation includes keyword research, metadata rewrites and structured data per language, not just translated text.
- Cultural adaptation and transcreation matter most on homepages, taglines and campaign copy.
- Accessibility work covers script support, and correct date, currency and number formatting per market.
A figure worth budgeting against: SEO localisation work typically adds 15% to 25% on top of base translation costs, which means a project that looks affordable on translation alone can grow once search visibility is factored in properly.
Timelines and annual costs you should plan for
A realistic timeline protects your budget as much as a good quote does, because rushed multilingual projects tend to generate rework, and rework costs money twice.
A small brochure site with one additional language typically takes four to six weeks from content freeze to launch. An SME ecommerce site with two to three languages usually needs eight to twelve weeks, accounting for TEP cycles, technical QA and SEO localisation. Larger rollouts across five or more languages, particularly with non-Latin scripts, commonly stretch to four to six months when you include proper testing and staged launches.
Once your site is live, the cost does not stop. Here is what a sensible annual maintenance budget accounts for:
- Translation refreshes for updated product information, seasonal campaigns and policy changes, priced against the same per-word bands you used at launch.
- Hosting and CDN costs, which scale slightly with additional language traffic but rarely by much.
- Hreflang monitoring, checking that reciprocal tags stay correct as pages are added, removed or restructured.
- Minor content updates, translating new blog posts, FAQs or product launches as they happen rather than in one annual batch.
To forecast your first year properly, estimate how much new content you expect to publish monthly and multiply by your chosen translation rate. A business publishing 2,000 words of new content monthly across three languages, for example, is looking at a recurring translation line that deserves its own budget code rather than being lumped into “website costs” generally. Our guide to UK website maintenance costs breaks down what ongoing site upkeep looks like beyond translation specifically.
Three UK budget scenarios worth comparing
Numbers land better with context, so here is how the layers stack up across three common UK project types.
- Small brochure site, one extra language: design and development from a few thousand pounds for a template-based build, translation at general business rates for perhaps 2,000 to 3,000 words. Hreflang and technical setup as a modest fixed addition, and first-year maintenance covering occasional content refreshes. Our one-page website cost guide is a useful reference point for the base build cost before translation is added.
- SME ecommerce site, two to three languages: design and development scales with product catalogue size, translation covers product descriptions, checkout flows and policy pages using a hybrid workflow, technical work includes subfolder structure and full hreflang implementation, and SEO localisation adds its typical uplift on top of base translation. VAT applies to the UK business’s own invoiced services under GOV.UK’s place-of-supply rules where the supply is to UK consumers, so this should be confirmed with your accountant against your specific customer base.
- Enterprise rollout, five or more languages: this is where multisite architecture, dedicated project management, and QA testing across every locale become significant line items, and where translation memory and framework agreements with an agency start meaningfully reducing per-word costs over time.
Across all three, cookie and consent design for language preferences deserves a line of its own. ICO guidance notes that a language-preference cookie may fall within the appearance exception if it only lasts the session, but persistent or multi-purpose storage typically requires proper consent under UK GDPR. Specifying this during scoping is far cheaper than retrofitting it after launch.
What to ask suppliers before you sign anything
A good quote answers questions before you have to ask them. A weak one leaves gaps that turn into disputes later.
- Ask what translation workflow they use. A proper TEP process with a named editor and proofreader is a sign of quality control; “we translate it” with no further detail is not.
- Ask how hreflang will be implemented and maintained. Template or sitemap-based approaches age far better than manually hardcoded tags.
- Ask about translation memory and whether it reduces cost on future updates. If they cannot explain how repeated content is priced, assume you will pay full rate every time.
- Ask what the consent and cookie plan is for language preferences. If this is not mentioned, it has probably not been scoped.
- Ask what ongoing support looks like after launch, and whether it is a retainer, a plan, or ad hoc invoicing.
Red flags worth walking away from: no mention of a TEP cycle, a vague answer on hreflang, and no discussion of cookie consent at all.
Pro Tip: If a quote does not separate design, translation and technical costs into distinct lines, ask for it to be rebroken down before you compare it against anyone else’s.
Why our UK pricing bands are a useful reference point
Some agencies have spent over a decade partnering with UK business owners on branding and website projects, which gives them a grounded view of what multilingual work actually costs to deliver properly, not just to quote cheaply.
Our own services, including Web Design & Development and ongoing site support through our Fix, Steady, Secure and Scale plans, map closely to the scenarios above: a template-based build for smaller sites, fuller technical and SEO work for ecommerce, and a maintenance plan that covers the ongoing content and monitoring work a multilingual site needs. Our website design cost guide sets out agency-validated bands for the UK market that sit alongside the examples in this article.
What most cost guides get wrong
Most advice on this topic treats translation as the main cost and everything else as an afterthought. That gets the priorities backwards. The translation line is visible and easy to quote, which is exactly why it gets scrutinised while hreflang maintenance, cookie consent design and ongoing content updates quietly become the real long-term spend.
The judgement worth taking from all this: budget your first twelve months as one connected project, not a launch cost plus a vague promise of “maintenance later.” Legal and technical groundwork, VAT treatment, consent design, sitemap-based hreflang, is cheap to build in at the start and expensive to retrofit.
If you take one thing from this article, prioritise where human translation goes rather than how much of your site gets it. A smaller, well-targeted human translation budget on your highest-value pages beats a larger budget spread thin across content nobody reads.
— Kukoo
Ready to scope your multilingual project properly?
If you are weighing up a multilingual website for your UK business, the biggest cost risk is not the translation line, it is a build that was not planned as a whole system from the start. We provide bespoke Web Design & Development built around your business, along with UX/UI design and ongoing support plans so your site keeps working properly as you add languages and content over time.
Our four-step collaborative process and unlimited revisions mean you are not stuck with a first draft that does not fit your market, and our ongoing support plans, Fix, Steady, Secure and Scale, cover the maintenance work a multilingual site needs after launch. If budgeting your content workload alongside the build, this UK content hire rate guide is a useful companion reference. Get in touch through our services page to request a quote tailored to your languages, site size and timeline.
Where to check the detail yourself
The figures and rules referenced throughout this article come from primary UK sources worth bookmarking if you want to verify anything before you brief a supplier.
- Gov, for confirming VAT treatment on digital services.
- ICO guidance on consent and storage technologies, for cookie and preference consent rules.
- SEO Handbook’s hreflang best practices, for technical implementation guidance.
Sources
- VAT: how to work out your place of supply of services
- How do we manage consent in practice? | ICO
- Hreflang best practices — SEO Handbook
- How much do translation services usually cost? UK pricing, rates and buyer’s guide – Translation Services UK
FAQ
How much should I charge for a website in the UK?
Pricing depends heavily on scope, but our UK website design cost guide sets out agency-validated bands that reflect typical UK market rates. A single-page site sits at the lower end, while multilingual or ecommerce builds cost considerably more once translation and technical setup are included.
How much does a website domain cost in the UK?
Domain pricing varies by registrar and extension, with .co.uk and .com domains typically among the cheaper options available in the UK market. This cost is separate from and much smaller than your design, development and translation budget.
How much should I charge for translation per page?
UK translation is usually priced per word rather than per page, with general business content typically running at £0.10 to £0.18 per word. Typical page length varies, with specialist content or rush turnaround pushing costs higher.
What is the cheapest website builder in the UK?
Cheapest is not always the most practical measure for a multilingual project, since builder cost is only one layer of the total budget. Design, translation, hreflang setup and ongoing maintenance usually outweigh the builder cost itself, which is why our one-page website cost guide looks at total project cost rather than platform fees alone.