If you run an ecommerce brand looking to expand into new countries and markets, there is a set of mistakes that can quietly undo all of your effort. I recently audited the accounts of several brands, one of which generates around $250,000 a month, and the work focused on Google Search Console. The same issues came up again and again, and they are worth knowing before you commit budget to going international, not after.
Start With Sitemaps and Hreflang
The two most common problems I found were both foundational. First, the sitemaps for pages targeting different countries had not been submitted to Google at all, and the sitemaps that were submitted had errors that stopped Google reading them correctly. If Google cannot read your sitemaps, it cannot reliably discover your localized pages, and everything downstream suffers. This is the same class of issue I keep returning to in why fixing Google Search Console issues is the fastest way to boost a store.
Second, the hreflang tags were set up incorrectly, which causes targeting errors that send the wrong version of your site to the wrong audience. The details matter here more than almost anywhere else in SEO. Avoid invalid codes like fr-EU, and use proper ones such as fr-FR. For multi-language countries, use the correct combinations, for example de-CH for German speakers in Switzerland. And do not mix versions carelessly: hreflang set to fr-GB targets French speakers in the UK, which is almost never what a brand actually intends.
Get the Domain Strategy Right
Where your localized content lives is a strategic decision, not a technical afterthought. Avoid awkward setups like placing a German section at sitename.co.uk/de/, because a country-specific domain carrying another country’s content sends a confused signal. For simplicity, subfolders such as example.com/de/ work well and are easy to manage. For serious scaling, local domains like example.de can perform better, at the cost of more overhead to maintain.
Whichever you choose, the localized versions must genuinely be localized. The pages need to be fully translated into their respective languages, not half-translated with English bleeding through. And the localized versions must cross-link, each pointing back to the main site and the main site pointing out to them, so the whole structure reads as one coherent international presence rather than a set of disconnected islands.
Monitor Each Market Separately
Once the structure is right, you have to watch it properly. Create separate Google Search Console accounts for each language version of your site, so you can actually see whether each localized version is earning impressions and clicks rather than guessing from a single blended view. Then check that data regularly, because international setups drift and break in ways a domestic site does not.
The final check is the simplest and the most ignored: have a dedicated expert review the whole setup before you rely on it. International configuration is unforgiving, and a single wrong hreflang pattern repeated across a catalogue can suppress an entire market. A second set of expert eyes is cheap compared to the cost of a launch that never ranks.
A Special Note for Shopify
Shopify is the platform most affected by incorrect international settings, so if you are on Shopify, your Markets configuration deserves particular attention. The same care applies to your sitemaps and collections, which is why I have written about fixing Shopify collections and sitemaps in GSC and a Shopify sitemap change that broke Search Console. If you are operating on the platform at all, it is worth reading this carefully before you act, and being just as careful if you are migrating, where a headless Shopify migration can cost you organic traffic if the international structure is mishandled.
Get these right and the upside is real. After fixing this kind of setup for one brand, they saw their traffic increase by around 300% within three weeks. If you are in the UK and already receiving a fifth of your orders from the EU, the demand is clearly there, and a properly configured international setup is one of the most overlooked growth levers you have.
MageCloud SEO Note
Where International Expansion Quietly Fails
THE MISTAKE
Broken hreflang and unsubmitted sitemaps
The localized pages Google never properly reads.
THE FIX
Correct codes, clean sitemaps, separate monitoring
A coherent structure Google can actually rank.
Paul Ryazanov · MageCloud · international is unforgiving of small errors
If you are expanding into new markets, or you suspect your current international setup is holding you back, get in touch. I will audit what you have, tell you exactly what is broken, and lay out the fastest route to having it done properly.