bt_bb_section_bottom_section_coverage_image

SEO Structure for Foreign Brands in Turkey: .com.tr, Subfolder or Subdomain?

SEO Structure for Foreign Brands in Turkey: .com.tr, Subfolder or Subdomain?

.com.tr, Subfolder or Subdomain? SEO Structure for Foreign Brands Entering Turkey

For most foreign brands entering Turkey, a subfolder on the existing global domain is the practical default. Not because it ranks better — Google does not state a ranking preference between these structures — but because it is the cheapest to maintain, it reuses infrastructure you already run, and it avoids having to establish link and brand signals for an entirely new domain. Google’s documentation lists it as a supported geotargeting option alongside country domains and subdomains.

The .com.tr question has changed, and much of the advice circulating about it is out of date. Under TRABİS, the .tr registry system operated by Turkey’s Information and Communication Technologies Authority (BTK), .com.tr moved to first-come, first-served registration rather than the document-based allocation that applied before. So the old blocker — “you need a Turkish trademark or company registration” — is no longer the constraint it was. That makes .com.tr easier to obtain, but ease of registration is not a reason to choose it.

Subdomains sit awkwardly between the two and rarely win on their own merits.

This guide works through what Google’s current documentation actually says, when each structure is the right call for Turkey specifically, how to implement hreflang without the mistake that costs foreign brands their Turkish-speaking audience outside Turkey, and which widely-repeated beliefs about geotargeting Google explicitly contradicts.

Table of Contents

What Google actually says about the three options

Google’s documentation on managing multi-regional and multilingual sites sets out four URL structure options with explicit trade-offs. Three are viable; one is not recommended.

Structure Google’s stated advantages Google’s stated drawbacks
Country-specific domain (brand.com.tr) Clear geotargeting; server location irrelevant; easy separation of sites Expensive with sometimes limited availability; more infrastructure; sometimes strict ccTLD requirements; can only target a single country
Subdomain (tr.brand.com) Easy to set up; allows different server locations; easy separation of sites Users might not recognise geotargeting from the URL alone — is “tr” the language or the country?
Subfolder (brand.com/tr/) Easy to set up; low maintenance on the same host Users might not recognise geotargeting from the URL; single server location; separation of sites harder
URL parameter (brand.com?loc=tr) Not recommended by Google

Note what is absent from that list: any claim that one structure ranks better than another. Google frames these as operational trade-offs, not ranking choices. The ccTLD’s advantage is signal clarity, and Google describes country-code top-level domains as providing a strong signal to both users and search engines that a site is explicitly intended for a certain country.

Google also lists the signals it uses to determine a page’s target locale: ccTLDs, hreflang statements in tags, headers or sitemaps, server location via IP address, and other signals including local addresses and phone numbers, local language and currency, links from local sites, and Business Profile signals where available.

The .com.tr question after TRABİS

Google’s own documentation flags that some countries restrict who may use their ccTLD, and advises checking before relying on one. For Turkey, that check now returns a different answer than it did a few years ago.

Since TRABİS became operational, .com.tr registration moved to a first-come, first-served model. Certain restricted extensions — gov.tr, edu.tr, k12.tr and similar — still require supporting documentation, but .com.tr is not generally among them. If your internal guidance or a vendor proposal still states that a Turkish trademark or company registration is required for .com.tr, that guidance predates TRABİS. Confirm current conditions with an accredited .tr registrar before planning around a specific domain.

Two consequences follow, and they point in opposite directions.

First, .com.tr is now a realistic option for foreign brands that previously ruled it out. Second — and more important — the domain you want may already be taken. First-come, first-served means someone else may hold your brand under .com.tr. If a .com.tr presence matters to your long-term plan, check availability and secure it early, independently of whether you intend to build your Turkish site on it. Defensive registration and primary-site selection are separate decisions.

Why a subfolder is the default for market entry

The case for the subfolder at market entry is operational rather than algorithmic. Google’s documentation does not express a preference between subdomains and subdirectories for indexing or ranking purposes, and treating the subfolder as an automatic ranking advantage overstates what Google actually says.

What it does avoid is work. A new .com.tr domain has no link profile and no history, so you take on the job of building recognition and links for a second property — in a market where you may have no local awareness, no Turkish press coverage and no Turkish backlinks to build from. A subfolder sits on a property that already has those signals, so the effort goes into the Turkish pages rather than into establishing a new domain alongside them. Whether that translates into better Turkish rankings depends on your content and links, not on the structure itself.

The subfolder is also the cheapest to run — one host, one certificate, one CMS, one technical SEO baseline. Google lists low maintenance on the same host as its explicit advantage. For a market-entry phase where the Turkish site may be a few dozen pages, running a separate domain infrastructure is disproportionate.

The drawback Google names is real but manageable: users may not recognise geotargeting from the URL alone. You address that with visible local signals on the page — Turkish language, Turkish currency, a Turkish address and phone number where you have them, and a clear language selector. The wider on-page and content side of ranking in Turkey is covered in our guide to SEO in Turkey.

When .com.tr is the right call

There are genuine cases where the country domain is the better structure:

  • Turkey is a major standalone market with its own P&L, team and roadmap. Separation of sites becomes an operational advantage rather than an overhead, and Google lists it as one.
  • Your Turkish offering diverges substantially from the global one — different catalogue, different pricing model, different service scope. At that point you are not localising a global site, you are running a different site.
  • Local trust is decisive in your category. In financial services, healthcare and some regulated sectors, a local domain carries perceived legitimacy with Turkish users that a subfolder does not.
  • Turkish competitors all run .com.tr and your buyers expect it. Category convention is a real user-trust signal even where it carries no ranking weight. This weighs more heavily in consumer retail, where trust cues affect conversion directly — see e-commerce in Turkey.
  • You are already established in Turkey with local awareness, local coverage and the ability to build a Turkish link profile. The main practical objection to a separate domain — that you would be starting its signals from scratch — largely falls away once you have local signals to build with.

Google notes the ccTLD’s constraint plainly: it can only target a single country. If your Turkish-language site is also intended to serve Turkish speakers elsewhere, a .com.tr domain works against that goal.

Why subdomains rarely win

The subdomain offers one advantage the subfolder does not — different server locations, and cleaner separation where your Turkish site runs on separate infrastructure or a different platform.

Outside that scenario, it tends to combine the subfolder’s ambiguity with the country domain’s separation, without the country domain’s signal strength. Google’s documentation contains a specific and often-missed warning on this point: in its worked example using language-specific subdomains, it states that those subdomains are not used by Google to determine the target audience for the page, and that you must explicitly map the target audience.

In other words, naming a subdomain “tr” does not communicate Turkey or Turkish to Google. The hreflang annotation does the work regardless. If you choose a subdomain, choose it for infrastructure reasons, not because the URL looks localised.

Language or region: the distinction that decides your structure

Google draws a distinction that foreign brands routinely collapse, and getting it wrong produces the wrong structure.

A multilingual site offers content in more than one language. A multi-regional site explicitly targets users in different countries. Many sites are both.

For Turkey the question is concrete: are you building a Turkish-language site, or a Turkey site? They are not the same. If your Turkish content is intended only for customers in Turkey — because you ship only there, price only in lira, or serve only Turkish locations — you are building a regional site. If your Turkish content could equally serve a Turkish speaker in Germany, the Netherlands or Austria, you are building a language site that happens to be most relevant in Turkey.

This distinction determines your hreflang codes, and it is where the most consequential Turkey-specific mistake happens. It also determines how much of your content genuinely needs adapting rather than translating — see website localization for Turkey.

hreflang for Turkey: tr or tr-TR?

Under Google’s specification, the first code in an hreflang value is the language, in ISO 639-1 format, optionally followed by a region code in ISO 3166-1 Alpha 2 format. So:

  • hreflang="tr" — Turkish language content, independent of region
  • hreflang="tr-TR" — Turkish language content for users in Turkey

Google is explicit that you cannot specify a country code by itself, and that it does not derive the language from a country code. A value intended to mean “Turkey” on its own is not valid.

Neither is universally correct, and the choice should follow who the content is actually for.

Choose tr-TR if the content is genuinely aimed at the Turkish market — lira pricing, Turkish delivery, Turkish legal terms, local stock. That is true even if you have only one Turkish version. The annotation is describing your intended audience, and narrowing it deliberately is legitimate when the page really is Turkey-specific.

Choose tr if Turkish speakers outside Turkey are also part of the audience. Turkey has a large diaspora, particularly in Germany, and for some brands those users matter commercially. Region-independent tr is the broader signal and does not restrict the page to one country.

The mistake to avoid is not the code itself but the mismatch: labelling a page tr-TR while expecting it to serve Turkish speakers everywhere. If you later add a second Turkish variant for a different locale, Google’s guidance is to also provide a catchall URL for geographically unspecified users of that language, which can be one of the specific pages.

hreflang rules that actually break implementations

Google supports three equivalent methods — HTML link elements, HTTP headers, and XML sitemap entries. The documentation is clear that there is no Search benefit to using more than one, and that maintaining three implementations is harder than picking one. Choose a single method.

Beyond that, four rules cause most failures:

Every version must list itself and all others. The set of annotations is identical across all versions of the page, including a self-reference.

Return links are mandatory. If page X points to page Y, page Y must point back. Google states that if two pages don’t both point to each other, the tags will be ignored — a deliberate safeguard so that an unrelated site cannot declare itself an alternate version of your page.

URLs must be fully qualified. Including the protocol. Protocol-relative or root-relative paths do not work.

Invalid region codes are silently dropped. Google ignores codes reserved for other purposes, naming EU, UN and UK as examples that have no effect. Note that the United Kingdom’s valid code is GB.

Also consider x-default as a fallback for users whose language settings match none of your versions. It was designed for language-selector pages and works best there — which matters if your global site has a country selector that Turkish visitors land on first.

What Google explicitly ignores

Several widely-repeated tactics are stated in Google’s documentation to have no effect, and international SEO briefs still routinely include them.

The HTML lang attribute does not determine language. Google states that it uses the visible content of the page to determine its language, and does not use code-level language information such as lang attributes, or the URL. The documentation on localized versions repeats this: Google doesn’t use hreflang or the HTML lang attribute to detect a page’s language; it uses algorithms. Keep lang for accessibility, but do not treat it as an SEO signal.

Geo meta tags do nothing. Google explicitly ignores locational meta tags such as geo.position or distribution, and geotargeting HTML attributes.

IP-based content adaptation is discouraged. Google’s guidance is not to use IP analysis to adapt content, describing IP location analysis as difficult and generally unreliable, and noting that Google may not crawl variations of your site properly because most Google crawls originate from the US and it does not vary crawl location to detect site variations.

Automatic language redirects are advised against. Google says to avoid automatically redirecting users from one language version to another based on assumed language, because those redirects can prevent users and search engines from seeing all versions. Use hyperlinks to other language versions instead.

That last point has a direct implementation consequence for Turkey: if your site auto-redirects Turkish IP addresses to /tr/, Googlebot — crawling from the US without an Accept-Language header — may never see the Turkish pages properly. A visible language switcher is the supported pattern.

On geotargeting methods, Google’s current documentation lists locale-specific URLs at page or site level, and hreflang or sitemaps at page level. Older guides that instruct you to set a country target inside Search Console reflect an earlier version of that tool; verify current Search Console functionality rather than building a plan around a setting that may no longer exist.

Handling same-language duplicates

If you end up with similar content in the same language on different URLs — for example both a .com.tr site and a /tr/ subfolder serving near-identical Turkish content — Google’s instruction is to pick a preferred version and use rel=”canonical” together with hreflang so the correct regional URL is served.

This situation arises more often than it should, usually during a half-completed migration or when a local partner launches a .com.tr site while the global subfolder is still live. It is worth auditing for at launch rather than discovering later.

One clarification from the documentation that prevents unnecessary worry: localized versions of a page are only considered duplicates if the main content remains untranslated. Properly translated Turkish pages are not a duplicate content problem.

The migration cost of changing your mind

This decision is reversible, but not cheaply. Moving from a subfolder to a .com.tr domain later means registering and configuring the domain, migrating content, rebuilding the hreflang set against new URLs, implementing redirects from every old URL, updating whatever backlinks you can influence, and resubmitting sitemaps. Expect a transitional period of unstable rankings.

That asymmetry argues for the structure that is easiest to start and hardest to regret. For most brands entering Turkey that is the subfolder — it costs least to begin, and if Turkey grows into a market that justifies its own domain, you will make that move with local signals and a business case behind it rather than as an opening bet.

A decision framework

  1. Is Turkey a test market or a committed operation? Test means subfolder.
  2. Does your Turkish content serve only customers in Turkey, or Turkish speakers generally? This sets your hreflang codes and may rule out a country domain.
  3. Do you have local signals to build on? Turkish links, coverage and brand awareness make standing up a separate domain far less costly.
  4. Does your category require visible local legitimacy? Regulated and trust-sensitive sectors lean toward .com.tr.
  5. Will the Turkish site run on separate infrastructure? The main legitimate case for a subdomain.
  6. Is your brand’s .com.tr available? Check now under first-come, first-served, and treat defensive registration separately from your primary-site decision.

Common mistakes

Using tr-TR while expecting to reach Turkish speakers everywhere. The region code narrows the page to users in Turkey; use tr if the diaspora is part of the audience.

Using a country code alone in hreflang. Not valid; the first code must be the language.

Relying on the lang attribute or the URL to signal Turkish. Google states it uses neither to determine language.

Auto-redirecting by IP. Discouraged by Google and liable to hide your Turkish pages from a US-based crawler.

Missing return links in hreflang. The annotations get ignored entirely.

Choosing a subdomain because “tr” looks localised. Google’s documentation states such subdomains are not used to determine target audience.

Assuming .com.tr still requires a Turkish company or trademark. Outdated under TRABİS — and the resulting delay may cost you the domain.

Implementing hreflang in all three methods at once. No Search benefit, three times the maintenance.

Frequently asked questions

Does a .com.tr domain rank better in Turkey than a subfolder?

Google describes ccTLDs as a strong signal of a site’s intended country, but frames the choice between country domains, subdomains and subfolders as a set of operational trade-offs rather than a ranking hierarchy, and does not state a preference between subdomains and subdirectories. The subfolder’s advantage at market entry is practical: lower maintenance, existing infrastructure, and no need to build link and brand signals for a second domain.

Do foreign companies need a Turkish entity to register .com.tr?

Under TRABİS, .com.tr registration operates on a first-come, first-served basis rather than the document-based allocation that applied previously. Certain restricted extensions such as gov.tr and edu.tr still require documentation. Confirm current conditions with an accredited .tr registrar.

Should I use hreflang tr or tr-TR for my Turkish pages?

It depends on the audience, not on how many versions you have. tr denotes Turkish content independent of region; tr-TR denotes Turkish content for users in Turkey. If your content is specifically for the Turkish market — lira pricing, Turkish delivery and terms — tr-TR is appropriate even with a single version. If Turkish speakers abroad are also part of your audience, tr is the broader choice. Google does not allow a country code on its own.

Should my Turkish site automatically redirect Turkish visitors?

Google advises against automatically redirecting users between language versions and against using IP analysis to adapt content, partly because its crawlers generally originate from the US and do not vary location. Offer a visible language switcher instead.

Is translated Turkish content a duplicate content problem?

No. Google states that localized versions of a page are only considered duplicates if the main content remains untranslated. Where you have similar same-language content on different URLs, use rel=”canonical” plus hreflang to designate the preferred version.

Can I change my site structure later?

Yes, but it requires a full migration — new URLs, rebuilt hreflang, comprehensive redirects and resubmitted sitemaps — with a period of ranking instability. Choose the structure that fits the next two years rather than the eventual end state.

Conclusion

Most foreign brands entering Turkey should start with a subfolder, choose between tr and tr-TR based on whether Turkish speakers outside Turkey are part of the audience, implement hreflang in one method with correct return links, and separately check whether their .com.tr is still available. That combination keeps the setup cheap to run, matches the annotation to the audience you actually want, and leaves the country-domain option open for the point where Turkey justifies it.

If you are still deciding how committed the Turkish operation will be, that question sits upstream of this one — our guide to marketing in Turkey for foreign brands covers it. The structural decision matters less than the implementation quality around it. A well-implemented subfolder with correct annotations, genuine Turkish content and visible local signals will outperform a .com.tr domain with broken hreflang, an IP redirect and translated copy. Get the architecture decision made deliberately, then spend the effort on the signals Google actually says it reads.