Traffic Dropped in One Country Only: Hreflang, Competitors and When to Ignore It

Short answer

A drop confined to one market usually means hreflang problems, a local competitor gaining, a country-specific SERP change, or a regional Google update rolling out unevenly. Segment by country in Search Console before assuming a global cause, because a global fix applied to a regional problem wastes a full reassessment cycle.

Country segmentation is the check I run second, right after device, and it changes the diagnosis often enough to be worth the thirty seconds. Performance, then the Countries tab, then compare your drop period against the one before it.

What you are looking for is disproportion. If every market fell by roughly the same share, the cause is global and the country data is noise. If one market fell hard while others held, something specific happened there, and the list of things that can do that is short.

Do you actually have an international site?

Worth separating two situations that look identical in the Countries tab.

The first is a genuine multi-market site with regional versions, hreflang, local currencies and localised content. There, a single-market drop usually has a structural cause you can find and fix.

The second is a single-language site that happens to pick up traffic from several countries because English is spoken in them. That traffic is incidental, it converts poorly, and losing it often means nothing at all. I have watched teams spend weeks investigating the loss of Indian or Filipino traffic on a site that only sells in Australia, where the honest answer was that the traffic was never worth anything.

Before diagnosing, check what the affected market was contributing commercially. If it was impressions without conversions, the correct response may be none.

Hreflang is the usual culprit

On real multi-market sites, this is where most single-country drops come from, and it breaks silently. Nothing errors, nothing 404s, the site looks perfect. Google simply starts showing the wrong regional version, or stops treating your versions as alternates at all.

  • Return tags must be reciprocal. If your UK page points at the US page, the US page has to point back. One-way declarations are ignored.
  • Every version must include itself. A self-referencing hreflang is required and is the most commonly omitted line.
  • Codes have to be valid. en-UK is wrong; the country code is GB. en-EU is not a thing. Invalid codes are dropped silently.
  • Hreflang and canonical must agree. If a regional page canonicalises to another region, you have told Google it is not a separate page and the hreflang is discarded.
  • Migrations break it. A domain or URL change without updating every hreflang URL leaves the whole set pointing at addresses that no longer exist.

That last point is why this often surfaces weeks after a site migration rather than immediately. The redirects work, the pages rank, and then the regional targeting quietly falls apart as Google recrawls and finds the declarations inconsistent.

The other causes worth checking

CauseMeasurement (how to confirm)Fixable?
Hreflang broken or inconsistentCompare declarations across versions; check canonical agreementYes, 2 to 6 weeks
A local competitor gainedSearch your terms with that country’s Google and see who is thereCompetitive, not technical
SERP layout differs in that marketCheck the query on that country’s domain; count what sits above organicNot a demotion
Regional regulation changed the SERPCheck whether the change coincides with a known local rule changeUsually not
An update rolled out unevenlyCompare your drop date against confirmed rolloutsWaits for reassessment
Local hosting, CDN or blocking issueTest page load from that country; check server logs for blocked rangesYes, fast

The last row is rarer but genuinely catches people. An aggressive firewall rule or bot-blocking service can start refusing requests from particular regions, including Googlebot traffic routed through them. The site works perfectly from your desk and is unreachable from somewhere else.

Checking a foreign SERP properly

You cannot diagnose a market you cannot see, and most quick methods for viewing foreign results are unreliable. Changing the Google domain alone does not do it, because results still reflect where you are.

The options that actually work are a VPN with an exit in that country, a rank tracker configured for that location, or asking somebody who lives there to send you a screenshot. The third is free, takes five minutes, and I use it more often than the other two.

What you are checking is straightforward. Are you still there at all? If yes, what sits above you, and is it a competitor or a SERP feature? If no, is anything of yours present, or has the whole domain gone from that market?

This is not a regional problem if

  • Every market fell proportionally. One market having the biggest absolute loss is not the same as being singled out. Compare percentages, not totals.
  • The affected market never converted. Incidental English-language traffic from countries you do not serve is not a loss worth fixing.
  • You have no regional versions. Without separate pages per market there is no hreflang to break, so the cause is competitive or algorithmic instead.
  • Positions held and only clicks fell. That is displacement, and it is covered in traffic dropped but rankings the same.

Order of work

  1. Segment by country and confirm the loss is disproportionate rather than just largest.
  2. Check what that market contributed commercially before spending anything on it.
  3. If you run regional versions, audit hreflang for reciprocity, self-reference, valid codes and canonical agreement.
  4. View the actual SERP from that country and identify what replaced you.
  5. Test page load and crawlability from that region.
  6. Only then check the date against confirmed updates.

Step two is the one most likely to save you money, and it is the one most often skipped because a falling line on a chart feels like something that must be fixed.

Frequently asked questions

Why did my traffic drop in one country only?

Usually broken or inconsistent hreflang, a local competitor gaining, a SERP layout that differs in that market, or a regional crawling or blocking issue. Segment by country in Search Console before assuming a global cause.

Can a Google update affect one country more than others?

Yes. The October 2023 spam update, for example, targeted detection in specific languages including Turkish, Vietnamese, Indonesian and Hindi, which made it far more consequential outside English-speaking markets.

How do I check search results in another country?

Use a VPN with an exit in that country, a rank tracker set to that location, or ask someone who lives there. Changing the Google domain alone does not work, because results still reflect where you actually are.

What breaks hreflang most often?

Missing return tags, a missing self-reference, invalid country codes such as en-UK instead of en-GB, and canonical tags that contradict the hreflang. Migrations break all of these at once by changing the URLs.

Should I fix a drop in a market I do not sell to?

Usually not. Incidental traffic from countries you do not serve rarely converts, and the effort is better spent on markets that produce revenue. Check the commercial contribution before treating it as a problem.

One market gone, the rest fine?

Regional losses are usually structural and fixable, but sometimes the honest answer is that the traffic was never worth recovering. Send your Search Console access and within 48 hours I will tell you which, segmented by market. Free, no obligation.

Get free recovery audit