Global SEO Priorities

I begin by forcing myself to stop listing every country my client wants. Global SEO priorities start with a single decision: which market gets the first six months of work. I run three numbers: monthly search volume for the core product term in each language, the approximate cost-per-click from Google Ads data (a proxy for competition), and the business's existing organic visibility in that market. The market that scores highest on volume divided by competition gets the budget. Everything else waits.

Once I have the target market, I do [international SEO keyword research](/international-seo-keyword-research/) properly. I hire a native speaker or use a local SEO agency to find the exact terms people use, not the direct translations. For example, when I worked on a UK-based electronics brand entering Germany, I assumed "Staubsauger" would be the head term. It was, but the long-tail queries were different: "beste Saugroboter für Tierhaare" (best robot vacuum for pet hair) had higher purchase intent than the literal translation of "best vacuum cleaner for pet hair" in German. That insight changed the page structure.

Next, I choose the URL structure. I have used subdirectories (example.com/de/) for every project in the last four years. Subdomains (de.example.com) split authority and make hreflang harder to maintain. I implement [localization SEO](/localization-seo/) by creating a separate page for each language-region pair, even if the language is the same. For instance, Spanish for Spain and Spanish for Mexico get different pages, because the search behaviour and spelling differ. I then add hreflang tags in the HTML head, including self-referencing tags and a return tag for each alternative. I test the tags using Google Search Console's URL inspection tool before launch.

Finally, I build a [global SEO strategy](/global-seo-strategy/) that includes a local backlink plan. I do not rely on the .com domain's authority to lift every country. I commission outreach to local bloggers, directories, and media in the target market. For the German project, I secured links from German tech review sites and a local university's electronics blog. Within three months, the page moved from page five to page two for the head term. The local links were the only variable that changed.

The first watch-out is URL structure indecision. I have seen teams flip from subdomains to subdirectories six months in, and the redirects undermine the authority they built. If you are unsure, pick subdirectories and do not look back. The second is hreflang implementation traps. The biggest is forgetting to include self-referencing hreflang tags — every page must point to itself. Another trap is using x-default without a valid fallback page. I once set x-default to the English home page, but visitors from non-targeted countries landed on content they could not read. I now set x-default to a language selector page or the most globally relevant version.

Third, do not assume Google is the only search engine. In markets like Russia, China, and South Korea, [Yandex Search Engine](/yandex-search-engine/), [Baidu SEO](/baidu-seo/), and Naver dominate. I have seen a UK-based travel site ignore Baidu and lose 80% of its potential Chinese traffic. For those markets, you need to adapt your technical setup: Baidu requires a Chinese ICP license, your site must be hosted in China, and it prefers simplified Chinese characters. Yandex favours sites with a .ru domain and backlinks from Russian sites. If you are targeting those countries, factor in the extra lead time and cost from the start.

Fourth, do not mix languages on one page. I have reviewed sites where the navigation was in English but the body in French. Google's hreflang algorithm scans the page to determine language, and a mixed-language page confuses the classifier. It may combine the signals and rank the page for neither language well. Keep one language per page, even if you think your users are bilingual. The same applies to internal links: keep them within the same language version. [International link building](/international-link-building/) should target local domains, not your global .com. A Spanish link to your Spanish subdirectory passes more relevance than a general link to the English homepage.

Finally, beware of translation quality. Machine translation might work for low-stakes content, but for key pages like product descriptions or category pages, invest in [SEO translations](/seo-translations/) from a native-speaking copywriter who understands SEO. I once saw a French page that was technically correct but used a keyword phrase that French users never search for — the translator had translated the English keyword literally instead of localising it. The page never ranked.

I used to think that a single .com domain with hreflang tags was enough to rank globally. I was wrong. For my first international project, a UK-based fashion brand, we kept the .com domain and added subdirectories. We ranked fine in the UK and US, but in France and Germany we barely appeared. The reason was not hreflang misconfiguration; it was that Google's algorithm did not recognise the French and German subdirectories as authoritative for those countries because they lacked local backlinks and local content signals. The hreflang told Google which page to show, but Google still chose to show the English version because it had more global authority. I had to go back and build local links and rewrite the content to include local references (e.g., shipping carriers, local sizing, and currency). That fixed the ranking, but it cost three months of lost traffic.

Another mistake was ignoring local search engines. I assumed Google was the only game everywhere. When I later worked on a project targeting South Korea, I did not even consider Naver. The client missed out on a huge audience because Naver handles over 70% of Korean search traffic. I now include a section in every global SEO plan that asks: "What is the primary search engine in this market?" If it is not Google, I adjust the strategy accordingly.

I also misjudged the importance of local hosting and server location. I once launched a site for a client in India with the server in the US. The site loaded fast for me in London, but users in India experienced high latency. Google's Core Web Vitals penalised the site. I now test load times from the target country using a tool like WebPageTest with a location node in that country. If the load time is over 2.5 seconds, I consider moving the hosting to a local data centre or using a CDN with a strong presence in the region.

Finally, I underestimated the cost of ongoing content adaptation. I thought we could translate the English blog posts and be done. But local audiences expect culturally relevant examples, holidays, and references. A post about "summer sales" in the UK targets July, but in Australia that is January. I now budget for a local content creator who spends 10% of their time adapting the editorial calendar to the local season and events, not just translating the text.