Automatic country redirects: why they backfire
Short answer: Forcing visitors onto a country version of your site based on their IP address causes more problems than it solves. Google's crawler mostly appears to come from the USA and doesn't send a language preference, so content shown only to other countries may not be crawled or ranked, and people travelling, using VPNs or buying for someone abroad get stuck on the wrong site. Use separate URLs per country, connect them with hreflang, and suggest the local version with a banner instead of forcing it.
Irish businesses often run more than one version of their site: one in euro for Ireland, one in sterling for Northern Ireland and Great Britain, sometimes an international version. Automatically sending each visitor to "their" site sounds like good service. In practice it creates confused customers and pages that search engines can't see. Here are the common beliefs, and what really happens.
Myth 1: "Geo-redirects make sure everyone sees the right site"
Reality: they make sure everyone sees the site your IP lookup guesses is right. That guess is wrong more often than people expect:
- someone in Dublin using a work VPN routed through London;
- a customer in Belfast whose mobile provider's IP maps elsewhere;
- a parent in Cork ordering a gift for a child studying in Manchester;
- a visitor on holiday who wants to buy from the Irish site for delivery home.
When the redirect is forced, all of them have to fight the site to reach the version they want, and some can't at all.
Myth 2: "Google will crawl each country version from that country"
Reality: Google's documentation on locale-adaptive pages explains that if your site returns different content based on the perceived country or language of the visitor, Google might not crawl, index or rank all of your content for different locales. The reason it gives: Googlebot's default IP addresses appear to be based in the USA, and it sends requests without an Accept-Language header.
Google does also crawl from IP addresses outside the USA, according to the same page, and asks that you treat Googlebot like any other user from the country it appears to come from. But relying on that for your Irish and UK versions to be discovered is a gamble. If your redirect sends US-looking visitors to an international page, Googlebot may rarely see your country pages.
Google's recommendation is clear: use separate locale URLs and annotate them with rel="alternate" hreflang.
Myth 3: "A redirect is the only way to show local prices"
Reality: separate URLs do the job without forcing anyone. For example:
example.com/ie/for Ireland (euro, Irish delivery options);example.com/uk/for the UK (sterling, UK delivery).
Each version is a normal page anyone can visit and link to. Hreflang annotations tell Google which version suits which audience, so searchers in each country are more likely to see the right one in results. A visitor who lands on the "wrong" version can switch with one click.
Google's guidance on multilingual sites makes the same point for languages: avoid automatically redirecting users based on what you think their language might be, because it can prevent users and search engines from seeing all versions, and add links so users can choose.
Myth 4: "A suggestion banner is just as annoying"
Reality: a well-designed banner respects the visitor:
- "It looks like you're in the UK. Shop in pounds on our UK site?" with Go to UK site and Stay here buttons;
- shown once, remembered when dismissed;
- not covering the content or blocking the page;
- never shown to visitors who arrived through a link to a specific country page they clearly meant to open.
It gives the helpfulness of a redirect without trapping anyone.
Myth 5: "We can redirect everyone except Googlebot"
Reality: treating Googlebot differently from people with the same characteristics risks being seen as showing search engines something different from users. Google's own advice is to treat Googlebot like any other visitor from the country it appears to come from. The cleaner answer is not to force redirects for anyone.
Google also notes that robots meta tags and robots.txt should apply the same rules in every locale, so don't accidentally block a country version for crawlers.
What to do instead: a practical setup
- Give each country its own URL, as a folder (
/ie/,/uk/), subdomain or separate domain. - Add hreflang annotations connecting equivalent pages, including an
x-defaultfor a general or selector page if you have one. - Add a visible country or currency selector in the header.
- Show a suggestion banner based on location, never a forced redirect.
- Remember the visitor's choice and respect it on later visits.
- Keep product and service pages equivalent across versions where possible, so switching lands on the same item.
- Check delivery and checkout rules on each version so customers who choose a version can actually complete an order.
When a redirect is acceptable
There are narrow cases: you genuinely can't serve a country at all, or the root domain shows a country selector page. Even then, explain on the page rather than silently bouncing visitors, and let people reach content when they need to.
FAQ
Does hreflang redirect visitors automatically?
No. It helps Google show the most suitable version in search results. Visitors still land on the URL they click.
Is IP detection accurate enough for a banner?
It's good enough for a suggestion, because the visitor decides. It's not reliable enough to force anything.
What about currency switching on one URL?
Some platforms convert currency on the same page. That can work for display, but separate country URLs remain the clearer option for search and for country-specific delivery and terms.
Will removing our redirect hurt sales?
Usually the opposite: visitors who were stuck on the wrong version can now reach the right one. Monitor checkout completion by country after the change.
If your site sends visitors to a country version they didn't choose, tell us how your Irish and UK sites are set up and we'll suggest a banner-and-hreflang approach.