Multi-Lingual Websites: Why UK Businesses Need More Than English
A multi-lingual website is not a plugin you turn on. For UK businesses serving Welsh, Polish, Urdu, or any second language, it is a structure decision. Here is when you need it, how to build it, and what we do.
November 18, 2026 · 20 min read · DRVN Media

A business in Cardiff that only has an English site is invisible to a customer who searches in Welsh. A clinic in London that serves a Polish-speaking neighborhood and has no Polish page is hoping those patients will translate the site themselves. Most will not. They will call the practice that already speaks their language on the page.
Multi-lingual websites are one of the things we build. Not as a toggle. As a set of real pages, in the languages your customers actually use, linked so a person and a search engine can find the right one. This post is when you need that, how it should be structured, and what it costs you to do it badly.
We build for towns across the UK. The same rules apply in London, Manchester, Birmingham, Cardiff, Edinburgh, Glasgow, and Belfast. The languages change. The structure does not. If you want the general design standards, those are in website design best practices.
English is not the only search
The UK is not a single-language market. Welsh is an official language in Wales. Scots Gaelic has official status in Scotland. Polish, Urdu, Punjabi, Bengali, Arabic, Romanian, and others are everyday languages in specific cities and specific industries.
People search in the language they think in. A parent looking for a dentist, a contractor looking for a supplier, a new arrival looking for a solicitor. If your page is only in English, you are absent from that search. A translate button in the corner is not the same as a page. Browser translation is rough, it does not create a URL you can rank with, and it does not help the person who already searched in their own language.
This is a local problem, not a global one. You do not need ten languages because a chart said the UK is diverse. You need the language your customers in your town actually use. A practice in Cardiff has a different answer than a practice in Belfast. A contractor in a Polish-speaking part of London has a different answer than one in a town where English is the only language that comes up.
When you need a second language
You need a second language when three things are true.
Your customers use it. Not “some people in the country speak it.” The people who call you, or the people you want to call you, use it at home and search in it.
You can serve them in it. A page in Polish that leads to a phone answered only in English is a broken promise. The page and the front desk have to match. If you have a bilingual staff member, the page should get the caller to that person.
The search exists. People look for the service in that language, in your area. If they do, a page can rank for it. If they do not, a translated page is a courtesy, not an acquisition channel. Courtesy is fine. Do not expect it to pay for itself the same way.
If only one of those is true, start smaller. A single service page in the second language, for the one service they search for. Not a full mirror of the site.
Need the site in more than one language? Tell us the town, the languages, and who answers the phone. We'll scope the pages.
Get a Project Quote →What a multi-lingual site actually is
A multi-lingual site is a set of pages, one per language, for the content you chose to translate. Each page has its own URL. The English page and the Welsh page are different URLs. A person can share either one. A search engine can index either one.
The pages are linked to each other. A language switcher that goes to the matching page, not to the homepage of the other language. If someone is on the roof-repair page in English, the Welsh switch goes to the roof-repair page in Welsh. Sending them to the homepage makes them start over, and it wastes the link.
The site tells search engines which page is which. Hreflang annotations say “this English URL is the English version of that Welsh URL, for users in the UK.” Without that, you can end up with the wrong language ranking, or with the two pages competing. With it, each page can rank for its own language.
That is the whole mechanism. Separate URLs. A switcher that preserves the page. Hreflang so the relationship is explicit. Everything else is content and care.
What it is not
It is not a plugin that translates the page in the browser. That does not create a URL. It does not rank. It often reads like a machine, because it is one.
It is not a single page with both languages stacked. That page cannot rank cleanly for either, and it is a poor read in both.
It is not machine translation pasted in and left. Machine translation is a draft. For anything a customer will trust, a person who knows the language has to read it. Legal, medical, and financial pages need a person. A slogan that was translated word for word and means something else is a real failure mode. We have seen it.
It is not every page on the site, by default. Translate the pages that earn it. The homepage, the core services, the contact page, the locations you serve in that language. A blog archive from 2019 does not need a Welsh version unless Welsh-speaking customers are reading the blog.
Wales, Scotland, Northern Ireland, England
The legal and practical picture is not the same in each nation.
In Wales, Welsh has official status. Public bodies have Welsh-language duties. A private business does not have the same legal duty, and a business that serves Welsh-speaking customers still has a commercial one. A site for a Cardiff practice, or for a business along the coast and in the Valleys, should at least ask the question. Many customers will use English. Some will choose the business that also has Welsh. For public-facing services, Welsh is often expected even when it is not legally required of you.
In Scotland, Gaelic is not the majority language, and it is the right second language in specific places and for specific organizations. Do not add Gaelic to an Edinburgh or Glasgow site because it seemed thorough. Add it if your customers use it.
In Northern Ireland, the language question is Irish and Ulster-Scots, and it is sensitive. A business in Belfast should follow its customers and its own judgment, not a template. If you serve customers in Irish, build the pages. If you do not, do not add a language to look complete.
In England, the second language is usually a community language, not an official one. Polish in parts of the East Midlands and in London. Urdu and Punjabi in Birmingham, Bradford, and parts of Greater Manchester. Bengali in Tower Hamlets. Arabic in several cities. The test is the same. Do your customers search in it, and can you serve them in it?
We build the pages either way. The UK web design pages are the place to see the towns. A Manchester contractor and a Leeds clinic do not need the same languages. They need the same structure if they need more than one.
URLs and the switcher
Pick a URL pattern and keep it.
A subfolder is the usual choice. /cy/ for Welsh, /pl/ for Polish, with the same path after it. example.com/roof-repair/ and example.com/cy/roof-repair/. Clear, shareable, and easy to put hreflang on.
A subdomain works too. cy.example.com. Slightly more setup. Fine if you have a reason.
A separate domain is rarely worth it for a small business. Two sites to maintain, and the authority splits.
The switcher uses the pattern. It does not guess. If the translated page does not exist, the switcher should not pretend. Link to the pages you have. Do not offer Welsh and then land the visitor on an English page with a banner.
Put the switcher where it can be found. Header, and on the page. A footer-only switcher is how people never see it.
Hreflang, without the jargon
Hreflang is a note in the page, or in the sitemap, that says which URL is which language. Each page lists itself and the other versions.
Get the codes right. cy for Welsh. gd for Scots Gaelic. pl for Polish. ur for Urdu. pa for Punjabi. en-gb for British English if you want to be specific. A wrong code is worse than no code, because you have told Google something false.
Every page in the set points to every other page in the set, including itself. If the Welsh page points to the English page but the English page does not point back, the pair is incomplete.
This is part of the build, not a plugin you hope is configured. We add it when we build the language versions. It is the same care we put into titles and internal links in website design best practices.
Want the language versions built properly? Separate URLs, a real switcher, hreflang. Tell us the languages and the pages.
Get a Project Quote →Translation is a person
Machine translation has gotten better. It is still a first draft.
For a headline, a service name, and a call to action, a person should read it. Those are the words that decide the call. A wrong nuance in a medical or legal page is not a small thing. A law firm page and a medical practice page need a reviewer who knows the language and the subject. A contractor page needs someone who knows what the trade is called in that language, not a literal rendering of the English.
We do not pretend to be the translator for every language. We structure the pages, we place the content you provide or that a translator provides, and we tell you where a machine draft is not good enough. If you have a bilingual staff member, they are often the right reviewer. They know how your customers talk.
Do not translate the keyword list and call it a page. Translate the page a customer needs: what you do, where, what it costs or how pricing works, and how to start. The same job as the English page. What a lead-generation site actually needs applies in every language.
SEO in the second language
A translated page can rank. It ranks for searches in that language, in the places you serve.
The title and the H1 should be in the language of the page. The meta description too. The internal links on that page should point to the other pages in that language, with anchor text in that language. An English link in the middle of a Welsh page is a small break. A page that only links back to English is a dead end for the Welsh-speaking visitor and a weaker signal.
Do not duplicate the English page, translate four words, and expect a ranking. Thin in Welsh is still thin. This is the same standard we use on town pages. A Liverpool page that could be any city is a weak page. A Welsh page that could be any business is a weak page.
Local signals still matter. The town name, in the language customers use for it. The phone number, the same one. The Google Business Profile in the primary language, and additional profiles or descriptions only where Google’s rules and your real languages support it. Do not create a second profile to chase a language. Fix the site first.
What we build
On a website design project, multi-lingual is a scope line, not a surprise.
We agree the languages and the pages. Usually the homepage, the core services, contact, and the locations that matter. Not the whole site on day one.
We set the URL pattern and the switcher. We add hreflang. We build the templates so a translated page looks like the site, not like a pasted document.
We take the translated copy from you or from a translator you trust, and we place it. We flag machine output that should not ship. We check the forms, the phone, and the links in each language.
If you already have a site and you need a language added, that can be a redesign or an addition to the current site, depending on how it was built. A WordPress site can hold a second language. So can a static build. The maintenance differs. A WordPress language plugin is another thing to update, which belongs in the same conversation as WordPress and whether to stay.
Ongoing changes in two languages are two changes. A care plan can cover that. DRVN Web Care is the updates, the monitoring, and the hours for the edits you ask for. A second language means the edits happen twice, or you decide which language is canonical and which follows.
Common mistakes
A flag icon and no pages. The flag promises a language you did not build.
Browser translate as the strategy. No URL, no ranking, rough copy.
Translating everything. Cost and delay, for pages no one reads in that language.
Translating nothing that matters. The homepage in Welsh and every service page only in English. The visitor hits a wall on the second click.
A switcher that goes to the homepage. They lose their place.
No hreflang. The wrong page ranks, or the two pages compete.
Machine translation on a trust page. A clinic or a firm shipping unchecked output.
Different phone numbers by accident. The Welsh page has an old number. The English page has the new one.
No one to answer in that language. The page worked. The call did not.
A sensible first version
If you are starting, do this.
Pick the one language your customers use besides English. Confirm you can serve them in it.
Translate the homepage, the two or three services they search for, and the contact page. Not the blog. Not the legal archive.
Give each a URL. Add the switcher. Add hreflang. Have a person read the copy.
Link the pages to each other in that language. Put the town on the page if local search is the goal. Bristol, Sheffield, Nottingham, wherever you actually work.
Then watch. If those pages get calls, expand. If they do not, fix the pages or the promise before you translate more.
Want a first version scoped? One extra language, the pages that matter, built so it can grow. Tell us the town and the language.
Get a Project Quote →How this fits the rest of the site
Multi-lingual does not replace the basics. The first screen still has to say what you do and what to do next. The phone still has to match the profile. The service pages still have to exist. Internal links still have to use real words. All of that, in each language you publish.
A second language on a site that is unclear in English gives you two unclear sites. Fix the English structure first if it is broken. Then add the language. The order matters.
For a UK business, the town pages we build are the local layer. The language pages are the language layer. A Welsh service page for a Cardiff contractor is both. We can build that. The UK index is where the town coverage lives.
What we will not do
We will not add ten languages to look international. We will not ship machine translation on a page where the wording matters and call it done. We will not create a second Google profile to fake a language presence. We will not promise that a translated page will rank in a month.
We will build the URLs, the switcher, and the hreflang, place copy that a person has approved, and link the pages so the second language is a real part of the site.
The short version
Build a second language when your customers use it, you can serve them in it, and they search in it. Give each language its own URLs. Switch between matching pages. Mark the relationship with hreflang. Have a person read the words that ask for the call. Start with the pages that matter, in the towns you actually serve.
That is a normal part of a website design project for a UK business that needs it. It is not a plugin. It is pages.
Get a project quote if you want it scoped for a specific town and language. Start with a free audit if you want to know whether the current site is even ready for a second language. If you are choosing a platform at the same time, the WordPress post covers when a CMS is the right call for a team that has to edit the site.
Forms, phone numbers, and the call that follows
A translated page that sends the form to a queue no one reads in that language is a dead end. Decide where the enquiry goes before you translate the button.
If a bilingual person handles those calls, the page should say so, in that language. “Ask for Anna” is a useful line when it is true. If everyone on the phone speaks English, say that too, honestly, and make the page set the expectation. A customer who starts in Polish and is met with English will not always mind. A customer who was promised Polish and gets confusion will.
The form fields can stay in the language of the page. Name, phone, the question. Do not ask for more in the second language than you ask for in English. The thank-you page should be in the same language. A Welsh form that confirms in English feels unfinished, because it is.
The phone number is the same number, unless you genuinely have a language line. Do not invent a second number. Match the Google Business Profile and the English page. Consistency is the same rule in every language.
Images and alt text
Photos do not need translating. Alt text does, if the image is meaningful. A photo of the office can have Welsh alt text on the Welsh page and English alt text on the English page. Decorative images can have empty alt. Do not stuff the alt with keywords in either language.
File names can stay in English. The visible caption, if you have one, should match the page.
Right-to-left languages
Arabic and Urdu are right-to-left. A page in those languages needs a layout that flips, not a left-to-right template with the text forced in. The switcher, the menu, and the form have to work in that direction. This is a real build task, not a font change. If you need Urdu for a Birmingham audience or Arabic in London, say so at the start. Retrofitting direction is more work than building it.
Maintenance in two languages
Every change is a decision. A new price, a new service, a closed location. You either update both languages or you accept that one is behind.
The practical rule: English is canonical, and the second language is updated for the pages that rank and the pages that get calls. A blog post does not need a twin unless you are publishing for that audience. A changed phone number needs a twin the same day.
This is why a second language belongs in the care conversation. Web Care hours cover the edits. Two languages means you spend those hours in two places, or you keep the second language to a smaller set of pages so the updates stay affordable. A smaller set is usually the right call.
Plugins and PHP still need updating if you are on WordPress. A language plugin is one more thing on that list. The WordPress post covers why that stack needs an owner. A second language does not change that. It adds to it.
Internal links across languages
On the English page, link to other English pages. On the Welsh page, link to other Welsh pages. Cross-link between languages with the switcher and with hreflang, not by dropping English links in the Welsh body.
A footer can list the languages you support. It should not list fifty towns in two languages. The same restraint as any footer. Link to the pages that matter.
If you have town pages and language pages, a Cardiff Welsh page can link to the Welsh versions of the services you offer there. It should not link to every English town page. Keep the reader in the language they chose until they switch.
How to know it is working
Look at three things after launch.
Calls and forms that arrive in the second language, or from the second-language pages. If the page is live and nothing comes, the search may not exist, the page may be thin, or the promise may not match the phone. Find out which.
The queries in Search Console for those URLs. Impressions in the language are the leading indicator. Clicks follow.
The switcher. If people land on English and never switch, the English page is doing the job, or they do not see the switcher. If they land on the second language from search, the URL and hreflang are doing the job.
Do not judge it in a week. A new language is a new set of URLs. Give it time, and do not add three more languages while you wait.
A note on automated translation widgets
Widgets that translate on the fly are tempting because they are fast. They are the wrong tool for a page you want to rank or a page a customer will trust.
Use a widget, if at all, as a convenience on pages you have not translated, and do not expect it to create a searchable URL. For the pages that matter, build the page. The widget can sit beside that. It cannot replace it.
Towns, not the whole country
You do not need a language strategy for the UK. You need one for the towns you serve.
A business in Cardiff decides about Welsh. A business in Belfast decides about Irish. A business in Birmingham or Manchester looks at the languages on the high street and in the inbox. A business in a smaller town may need nothing but English. That is a valid answer.
We work across the UK, and the town pages exist so a business can see we build for their place. The language decision is local. Bring the town and the language. We will tell you whether it is a full set of pages or a first version, and what it takes to keep it.
Get a project quote with the town and the language. If you are not sure the current site can hold it, start with the audit.
What to send us
If you want this scoped, send four things. The site, if you have one. The town or towns you serve. The language or languages you are considering, and why. Who on your team can review the copy or answer the phone in that language.
With that, we can say whether it is a build, an addition, or a no. A no is a useful answer. Not every UK business needs a second language. The ones that do should have real pages, not a widget.
That is the work. It sits next to the rest of what we do: the design, the local pages, the care that keeps both languages current, and the quote if you are ready to start.
Ready for a fixed quote?
Tell us about the business and what the site needs to do. We'll come back with a scope and a number. No hard sell.
Get a Project Quote →Or start with a free auditWordPress Is Losing Market Share. That Does Not Mean You Should Leave It.
WordPress is a smaller share of the web than it was. For a business whose marketing team needs to edit the site, leaving it can cost more than staying. Here is the real trade, including the plugins, PHP, and updates WordPress still requires.
Website Design Best Practices: What a Site Needs to Rank and Convert
Website design best practices that hold up in search. Structure, the first screen, speed, service pages, and how internal links tie a site together so it ranks and gets the call.
How Much Does a Small Business Website Cost in 2026?
Honest price ranges for a small business website in 2026, from DIY builders to agency builds, what actually drives the cost, the ongoing fees people forget, and how to compare quotes.