
Key takeaways
- After NFON moved nfon.at to nfon.com/at/ in early 2015, Austrian organic traffic grew 90% in the first five months versus the previous year.
- Leads generated through organic search in Austria grew 100% year over year in the same five-month window after the migration.
- The Germany migration lost most of its SEO visibility right after the switch, which the author ties to redirect chains rather than to the domain strategy.
- The author names several factors behind the growth, including content and technical work, so the domain move is a likely driver and not the only one.
- Once country versions share one domain their performance is closely connected, which cuts both ways when one market has a problem.
This is a write-up of a case documented by Eoghan Henn at searchviu, who says NFON was his client at the time and that he had access to their numbers. We have not seen NFON’s analytics ourselves, so every figure below is the author’s, and both are percentages: the source gives no absolute traffic counts.
Why would a company merge its country domains?
Henn’s core argument is that pages on the same domain share ranking signals more easily than pages on different domains, so links earned by one market help the others. He adds practical reasons: one website is simpler and cheaper to manage than several, and a weak country site can borrow strength from a stronger one. Google’s own guide to multi-regional sites frames the trade-off from the other side: a ccTLD gives a strong, clear geotargeting signal, while subdirectories on a gTLD are easy to set up and low maintenance but less obvious to users.
What NFON changed
NFON is a cloud telephone system provider operating in 12 countries. Its Austrian domain, nfon.at, had been online since 2010 before it was merged into the international gTLD in early 2015, becoming nfon.com/at/. The German site moved from nfon.net to nfon.com/de/ at the end of 2013 or early 2014, and the UK site moved from nconnect.com to nfon.com/gb/.
What the source reports
For Austria, the article states that organic traffic grew 90% in the first five months after the migration compared with the previous year, and that leads generated through organic search grew 100% in the same time frame, year over year. Henn notes the migration came with a redesign, so the domain switch cannot take all the credit.
Germany started differently. The old German domain had a manual penalty for unnatural link building and a recovery of more than half a year in 2013 and 2014. After the switch, NFON lost most of its German visibility directly, which the author attributes to redirect chains. For the three years after the migration, he reports stable organic traffic growth in Germany for the first time.
The UK section gives no percentage figures, but it is the closest thing to a reversal test. A redesign weeks before the move had no noticeable effect; the boost came after the switch to nfon.com/gb/. In May 2017 the UK team moved to nfon.co.uk, which, in Henn’s words, did not have the power to maintain the rankings and was even outranked by the English version on nfon.com. After moving back to nfon.com/gb/, he says NFON was stronger than ever in the UK.
What does the author say can go wrong?
Henn is explicit that there is no one-size-fits-all answer. His warnings:
- Merging one strong domain with several weak ones often fails; NFON’s country domains already had history and decent link profiles.
- A brand new gTLD ranks less easily than an established one, and short-term losses are almost always part of a migration.
- Merged versions share negative signals too, such as harmful links or thin content, and their performance becomes closely connected.
- Different brands per country, local user preference for a ccTLD, or market-specific rules can rule the move out. He calls a mixed setup a viable option.
What should you check before a merge?
The Germany dip is the practical lesson. Henn’s advice is to redirect every old URL directly to its new target, keep the old domains and their SSL certificates, update the links you control, and connect the country versions with correct hreflang. Google’s site move guide says the same about chains, advising a redirect to the final destination directly, and to keep redirects generally for at least a year. Before launch, run your redirect map through the redirect chain analyzer and generate the annotations with the hreflang tag generator. Henn also recommended setting a country per directory in Search Console; Google’s current multi-regional guide no longer mentions that setting.
How to read it
The author says several factors were at play, including content focus and a solid technical foundation, and that he believes the international domain strategy was one of the most important drivers. That is his judgment, not a controlled test. A single client, one migration and year-over-year comparisons cannot separate the domain move from everything else changing at the time. Treat it as a documented outcome, and note the Germany dip as the cost of a poorly executed redirect plan.
The evidence
- Subject
- NFON's merge of country domains into nfon.com subfolders
- Timeframe
- Austria, first five months after 2015
- Verified
- Yes, against first-party data
| Metric | Before | After |
|---|---|---|
| Austria organic traffic, first five months after migration vs. prior year | 0% | 90% |
| Austria organic search leads, same period year over year | 0% | 100% |
Sources
- 1.Migrating from ccTLDs to a gTLD: The WHY, the HOW, and the WTF - searchviu, May 7, 2018Primary
- 2.Managing multi-regional and multilingual sites - Google Search CentralPrimary
- 3.Site moves with URL changes - Google Search CentralPrimary
About the author

Founder, UpgradIQ FZC LLC
Adam Hafez works on technical SEO and search measurement: how pages get crawled, indexed, ranked and now quoted by answer engines. He founded UpgradIQ, which reads Google Search Console and GA4 to tie ranking movement back to the changes that caused it. He publishes what the data supports and states the limits of it.
- Technical SEO
- Search Console and GA4 measurement
- Answer engine optimization
- Structured data
The briefing
Only what actually changed in search, delivered in full by RSS, Atom or JSON feed.
FollowRelated reading
Nuvemshop lifted good LCP from 57% to 96% by fixing image loading
Nuvemshop's web.dev case study: removing lazy loading on top images and adding fetchpriority took good LCP from 57% to 96% across its stores.
CoinStats fixed a Core Web Vitals bug, tripled search impressions
DebugBear's case study: CoinStats found Base64 images were bloating 15,000 pages, fixed it, and saw Good URLs and search impressions both increase 3x.
IFTTT's internal linking fix and its 33% YoY traffic gain
Uproer's case study on IFTTT: searchbots reached only 59 pages via internal links until a fix, after which the site saw 33% YoY organic traffic growth.
Simms Fishing's Magento to Shopify migration: the real numbers
Inflow's case study: Simms Fishing saw organic traffic up 126% YoY and non-brand category traffic up 5,642% after a Magento to Shopify move.



