The Polish trade community in Greater Manchester alone runs into the tens of thousands. Across the UK, there are hundreds of thousands of Polish-speaking tradespeople, agencies, and customers. So when a Polish electrician sits down to commission a website, the language question is genuinely strategic, not vanity. It changes who finds you, who trusts you, and who picks up the phone.

Here's the short version: most Polish tradespeople in the UK are best served by an English-first website with a small, well-built Polish version alongside it. Below is why, and the cases where the answer flips.

Who actually finds you in Google

The first thing to understand: Google decides which version of your site to show based on the searcher's language settings, not their nationality. A Polish customer in Oldham who has set their phone to English will mostly see English search results. The same person, with their phone set to Polish, will see a different mix — including more Polish-language sites, even when they search for things in the UK.

For most working-age Polish people in the UK, the phone is in English. They use English in shops, on the bus, at school pickup. When they need an electrician in a hurry, they'll type "electrician Oldham" into Google before "elektryk Oldham" — even if Polish is their first language at home. This is a generational pattern: it's much weaker for older Polish residents, and it disappears entirely for Polish-speaking customers visiting from Poland.

If your website is Polish-only, you're invisible to that working-age, mostly English-searching majority. If it's English-only, you're missing a smaller but real seam of Polish-searching customers — typically the older diaspora, the more recently arrived, and the cross-border traffic.

The case for an English-first website

For a Polish electrician, plumber, or builder working anywhere in the UK, English is the dominant language of finding you. That covers:

  • British customers, who are the majority of your potential market in any UK town.
  • Polish customers using English search habits, which is most working-age people.
  • Letting agents, builders, contractors, who almost always operate in English.
  • Insurance companies, councils, landlords — same.

For all of these, an English-language website with proper local SEO (town names, postcodes, NICEIC/Gas Safe credentials, a clear phone number) is the higher-leverage build. If you only build one site, build the English one.

The case for a Polish version alongside it

Here's where most agencies get it wrong. They treat the Polish version as either (a) unnecessary, or (b) a full duplicate of the English site. Neither is right. The Polish version of your site doesn't need to compete with the English one — it needs to do different jobs:

  • Win the trust of older Polish customers who may switch to a Polish-language site instinctively, even if they understand English fine.
  • Reassure recently-arrived Polish workers and families who haven't yet built confidence searching in English.
  • Capture cross-border traffic — Polish people visiting family in the UK, or Polish-owned businesses operating between countries.
  • Signal community membership. A trade business that has clearly invested in a Polish version reads as part of the community, not just an outsider taking work.

The trick is that the Polish version doesn't need to be a 1-for-1 translation. It needs to be a small, well-built version of the same site, with the same phone number and credentials, but with the framing tilted toward the Polish-speaking audience. Sometimes that means leading with a different town (Konin instead of Manchester, in the example we built for our own site). Sometimes it means slightly different testimonials, different photography, or different services foregrounded.

The Polish version isn't a translation. It's a sister site that does different jobs — speaks to a different audience, while pointing at the same business and the same phone number.

The technical bit (it's simpler than agencies make it sound)

If you've ever been quoted four figures for "multilingual setup" you've been overcharged. The actual technical requirements are short:

  1. Use a separate URL path for each language. The English site lives at yoursite.co.uk/, the Polish version at yoursite.co.uk/pl/. Don't put a flag dropdown that swaps text in place — Google can't index it properly, and customers can't share a link to "the Polish version."
  2. Add hreflang tags. Three lines in the HTML head of every page tell Google "here's the English version, here's the Polish version, this is the default." Free, takes minutes, hugely improves how Google routes the right version to the right searcher.
  3. Add an EN | PL switcher in the nav. Top-right of every page. Visible, but not shouting. Customers find it; Google sees that you have a real bilingual setup.
  4. Translate properly. No machine translation for the homepage. Google penalises obvious auto-translated content, and Polish customers spot it in a second. A native speaker, half a day's work, done right.

That's it. There is no "Polish CMS plugin" you need. There is no separate hosting required. A well-built static site can serve both languages from the same server, the same domain, the same maintenance schedule.

When Polish-only actually makes sense

There are situations where flipping the priority — Polish-first, with English secondary or absent — is the correct call:

  • You serve a specific Polish-speaking community exclusively, e.g. a builder who works mainly with Polish landlords renting to Polish tenants. Your customer base searches in Polish, your subcontractors are Polish-speaking, your suppliers are Polish.
  • Your work is in Poland, with UK clients as occasional visitors. A Polish carpenter who lives in the UK but does fitted-furniture jobs across both countries probably wants the Polish site as the dominant one, with a small English landing page for UK enquiries.
  • You've niched into translation-heavy services — a Polish-speaking lettings agent, a Polish-language tutor, a financial adviser specialising in cross-border situations. The whole pitch is "in your language," and English is a secondary aid.

For most general-trade businesses serving the UK market, none of those apply. English-first plus a Polish version is the right call.

What we built for ourselves

We use the same setup. Craftpine is a small studio based in Manchester, but we work with Polish-speaking clients across the UK and a smaller number in Poland (Konin and the surrounding area). The English version of our site (the one you're reading) targets the UK audience and Polish tradespeople in the UK. The Polish version at /pl/ leads with Konin, mentions Manchester as secondary, and is aimed at the Polish-speaking audience whether they're in the UK or in Poland.

Same phone number on both. Same studio. Same work. Two doors into the same room — picked by the visitor, not forced on them.

The decision in one sentence

If you're a Polish tradesperson working in the UK and you can only afford to build one site, build the English one. If you can build both, build the English one first, then add a small, well-translated Polish version with the same phone number and a clear EN | PL switcher in the nav. The cost difference is small. The reach difference is significant.

If you'd like a 15-minute Zoom about whether your situation falls in the English-only, English-first, or Polish-first camp, drop us a line. We do this assessment for free; the build, if you want one, is priced separately.