SEO for English-language websites most often fails because of seven recurring mistakes: literally translated keywords, mixed varieties of English, missing hreflang, IP-based redirects, machine-generated text, Polish backlinks and Polish contact details. You can run the diagnosis in an hour. You can roll out most of the fixes in a few days.
SEO for English-language websites means optimising the English version of a site so that it wins Google traffic in the USA, the UK and other English-speaking countries. The simplest test? The Polish phrase “pozycjonowanie stron” is simply “SEO” in English. Nobody types “website positioning”.
Key takeaways
- An hreflang annotation only works in pairs: every language version must point to all the others and to itself, otherwise Google may ignore it.
- The hreflang code for the United Kingdom is en-GB. en-UK is wrong and Google won't recognise it.
- Googlebot crawls mostly from US IP addresses, so a forced location-based redirect can hide your UK version from it.
- One URL serves one variety of English: British or American, never both at once.
How can you tell SEO for an English-language site isn't working?
The main symptom is near-zero traffic from the UK and the US even though your /en/ pages are indexed. You can check this in Google Search Console in about 60 minutes. Since 2022 Search Console no longer has an International Targeting report, so you have to catch hreflang errors yourself: in the reports and with a crawler.
- Open the Performance report and add a page filter containing
/en/. Then a country filter: United Kingdom, followed by United States. Note the impressions for the last 3 months. - Review the queries for those pages. If you mostly see your brand name or odd word-for-word renderings of Polish, the problem lies in your keywords.
- Go to Page indexing and look for the status “Duplicate, Google chose different canonical than user”. On /en/ versions this is a common sign of misconfigured canonical or hreflang tags.
- Check 3 key URLs with the URL Inspection tool. Compare the canonical chosen by Google with the one you declared.
- Crawl the site and export the list of hreflang tags without return links.
| Symptom in the data | Most likely mistake |
|---|---|
| Impressions exist, but for phrases nobody searches | Mistake 1: translated keywords |
| Traffic from the US, almost none from the UK (or vice versa) | Mistake 2 or 4 |
| Google shows the Polish page to British users | Mistake 3: hreflang |
| The /en-gb/ page isn't indexed | Mistake 4: IP-based redirect |
| High bounce rate from the UK/US | Mistake 5 or 7 |
| Good content, but low rankings for competitive phrases | Mistake 6: no local backlinks |
Mistake 1: You translate Polish keywords instead of researching English ones
A translated keyword usually has zero search volume, because British and American users describe the same problem in different words. “Realizacje” isn't “realizations”, it's “case studies” or “portfolio”. “Szkolenia BHP” is “health and safety training”. You research the market from scratch rather than rewriting your Polish list.
Symptom: the page gets impressions for phrases nobody types, or none at all.
Cause: someone took the Polish keyword spreadsheet and ran it through a translator.
Fix:
- Set your keyword research tool to a specific country: the UK separately, the US separately.
- Search Google with an English-speaking region setting the way your customer would describe the problem. Read the “People also ask” section.
- Check the intent. American and British queries about the same product can carry different purchase intent.
- Rewrite titles, H1 headings and URLs for the new phrases. Not just the body copy.
Mistake 2: You mix British and American English on one page
Google and readers notice the difference between “optimise” and “optimize”, “flat” and “apartment”, “trousers” and “pants”. A page that says “colour” in one paragraph and “color” in the next looks like a sloppy translation. It also loses its match with local queries, because a Brit searches for “flat to rent” and an American for “apartment for rent”.
Symptom: traffic comes from one country while the other ignores the site.
Fix: pick one variety per URL. If you're targeting both markets, build two versions: /en-gb/ and /en-us/. The differences go beyond spelling:
| Element | UK | USA |
|---|---|---|
| Spelling | optimise, colour | optimize, color |
| Date | 25/10/2026 | 10/25/2026 |
| Currency | £ | $ |
| Units | mostly metric | inches, feet, pounds, °F |
| Vocabulary | flat, trousers, postcode | apartment, pants, ZIP code |
Only have the budget for one version? Choose the market with more potential for your product. One consistent site beats two half-finished ones.
Mistake 3: No hreflang, or hreflang without return links
Hreflang is an attribute that tells Google which version of a page is meant for which language and region. Without it, Google may show a British user your Polish page or treat /en-gb/ and /en-us/ as duplicates. According to Google's documentation on localized versions of pages, every version must point to all the others and to itself.
Symptom: the Polish version of the page shows up in results on google.co.uk.
Fix: add the full set of tags in the <head> section of every version:
<link rel="alternate" hreflang="pl" href="https://domena.com/" />
<link rel="alternate" hreflang="en-GB" href="https://domena.com/en-gb/" />
<link rel="alternate" hreflang="en-US" href="https://domena.com/en-us/" />
<link rel="alternate" hreflang="x-default" href="https://domena.com/en/" />Four rules most implementations break:
- Return links. The Polish page points to the English one, the English page points to the Polish one. Without the pair, there's no signal.
- Correct codes. Language per ISO 639-1, region per ISO 3166-1. Hence en-GB, not en-UK.
- Self-referencing canonical. The
/en-gb/version has its canonical set to/en-gb/. A canonical pointing to the Polish page wipes the English one from the index. - x-default for the language selector page or the global version.
On WordPress, a multilingual plugin usually adds the tags. Still, check the source code by hand, because language version settings often break after a theme update.
Mistake 4: Automatic IP-based redirects block Googlebot
Googlebot crawls mainly from US IP addresses and usually doesn't send a language header. If your server redirects every US visitor to /en-us/, the bot may never see /en-gb/ or the Polish version. Google describes this in its guide to locale-adaptive pages and recommends separate URLs for each version.
Symptom: the British version has the status “Discovered – currently not indexed” or doesn't appear in Search Console at all.
Cause: a geolocation rule in the CMS, in the CDN (e.g. Cloudflare) or in a shop plugin.
Fix:
- Remove the forced IP-based 301 or 302 redirect.
- Show a banner instead: “Looks like you're in the UK. Switch to the UK site?”. The user chooses, the bot sees everything.
- Remember the choice in a cookie, not in a redirect.
Mistake 5: Machine-translated content without a native speaker's edit
Google classes text from an automatic translator without human editing as automatically generated content, which may violate its spam policies. But something else matters more: a reader in London will spot a word-for-word translation within three seconds. Polish sentence structure, “we are a dynamic company”, no local examples. They leave and don't come back.
Symptom: people land and leave without clicking through to your offer. Short time on page despite good rankings.
Fix: write natively, don't translate. Start from the English phrase and the English intent, then build the text. A native speaker or an editor from the target market reviews at least the service pages and the homepage. Native content has a second payoff too: AI answer engines such as ChatGPT and Perplexity are more likely to cite clear, specific paragraphs in natural language than choppy literal translations.
Native writing beats clumsy translation. Every time.
Mistakes 6 and 7: Polish backlinks and Polish contact details on a UK or US site
An English page linked to only by Polish directories and .pl portals signals to Google that its audience is in Poland. A page with a phone number missing the +48 code, prices in złoty and a Polish form in the footer loses the trust of a customer in Manchester before they've read the offer.
Mistake 6: a backlink profile from Poland only
Fix: earn links from industry sites in the UK or the US: guest posts, digital PR, expert commentary for local media, trade association directories. It costs more than a Polish link network, so build it into the budget from the start. Check internal links as well: the menu and footer of the /en/ version mustn't lead to a Polish privacy policy or a Polish blog. When planning your spend, factor in how much SEO costs in a market where a link is far more expensive than in Poland.
Mistake 7: Polish contact details
Fix:
- Phone number in international format: +48, with business hours in GMT or ET.
- Prices in GBP or USD, or a clear note about the currency.
- An EU VAT number rather than just the Polish tax ID (NIP).
- Legal pages (privacy policy, terms) in English.
Don't invent a fake London address. A Google Business Profile without a real office breaks the guidelines and risks suspension. Once you actually open an office, local SEO will come into play.
What does the fix look like in practice?
Take a typical scenario: a Polish garden furniture manufacturer has had an /en/ version for two years. Search Console shows impressions mostly for the brand name. The diagnosis from the table points to three mistakes at once: keywords translated from Polish, no hreflang and an IP-based redirect set up in the CDN.
- Day 1: you switch off the IP redirect and add a country selection banner.
- Day 2: you implement hreflang with return links and self-referencing canonicals. You check with a crawler.
- Week 1: you research keywords for the UK. It turns out Brits search for “garden furniture sets”, not the translated “garden furniture complets”. You rewrite the titles and H1s of the 10 most important pages.
- Weeks 2–4: an editor from the market revises the service pages. You switch the currency to GBP and add a returns policy in line with UK consumer law.
- Month 2+: you start earning links from British gardening blogs.
The order matters. First you unblock indexing, then you improve the content. Do it the other way round and you're writing for a bot that can't see the page.
Frequently asked questions
Is an /en/ subfolder or a separate .co.uk domain better?
On a limited budget, choose a subfolder on your current domain, e.g. /en-gb/, because it inherits the authority the domain has already built. A .co.uk domain sends a stronger local signal, but it starts from zero and needs its own link building. Only go for it once the UK market brings in revenue that justifies a second SEO project.
Do I need to care about Bing in English-speaking markets?
Yes. In the US and the UK, Bing has a noticeably larger share of desktop searches than in Poland, especially in workplaces. The first step is to add your site to Bing Webmaster Tools and submit a sitemap. Bing also powers some of Copilot's answers, so you benefit twice.
How long does it take from the fixes to a rise in traffic?
Google usually picks up technical fixes such as hreflang or removing a redirect after re-indexing, so within weeks. New rankings for competitive phrases take months to build, because they depend on links from the target market. If nothing moves after a full recrawl, go back to the diagnosis: there's usually one mistake left unfixed.
Can I keep a single English version for all countries?
You can, if you don't sell in local currencies and your offer doesn't differ. In that case, mark it as hreflang="en" without a region and stick to one spelling variety. Split the versions only when prices, delivery or regulations differ between countries.
Where to start with SEO for your English-language site this week
Run the diagnosis from the first section today. One hour in Search Console and a crawler. List which of the seven mistakes you have. Fix the ones that block indexing first (hreflang, redirects), then the keywords and content. Without SEO blockers, even average copy starts picking up impressions. With them, even excellent copy gets nothing.
At UPGeoSEO we do this on autopilot. An SEO + GEO audit catches SEO blockers and hreflang errors. Then we research keywords for each market separately, learn your tone of voice and write native English content, not translations. We publish it on your site and track your AI visibility: citations in ChatGPT, Gemini and Perplexity, with no inflated metrics. You approve, we publish.
Run a small agency with a few clients who have /en/ versions? Take a look at the UPGeoSEO agency dashboard: you can check whether your clients' sites appear in Google's AI Mode and AI Overviews, run GEO and SEO audits for each client, connect Bing Webmaster Tools and publish articles for up to 10 websites.
