bt_bb_section_bottom_section_coverage_image

Google Shopping and Product Feed Optimization for Turkey

Google Shopping and Product Feed Optimization for Turkey

Google Shopping and Product Feed Optimization for Turkey

In Turkey, the product feed is the campaign. Bidding strategy and budget matter far less than whether your feed meets the requirements for Turkey as a target country — and most foreign brands discover this after their products are disapproved rather than before.

Three things decide whether your products serve: Turkey has to be set as a target country in Merchant Center, your product data has to use a currency supported for Turkey, and your product data has to meet Turkey’s language requirements consistently with your landing pages. Get any of them wrong and the product is disapproved for that country specifically, while continuing to serve happily everywhere else — which is why the problem often goes unnoticed in a global account.

Note what those requirements do and do not say. Turkish lira and Turkish-language product data are not the only technically permitted configuration — Google supports submitting in another supported currency with automatic conversion, and supports targeting a country in another supported language. They are, however, the configuration that actually competes in this market, and the rest of this guide treats them as the recommended localisation approach rather than a compliance minimum.

There is also a structural assumption European teams bring with them that does not transfer. Google’s Comparison Shopping Service programme does not operate in Turkey. It covers 21 countries across the EEA plus the United Kingdom and Switzerland, and Turkey is not among them — so neither the CSS requirement nor the bidding economics European teams associate with CSS partners apply here. A CSS you already work with may still place your Shopping ads and free listings in Turkey, depending on your account setup, but that is a placement arrangement rather than a programme benefit.

This guide covers what actually has to be true for your products to show in Turkey, why Turkish product titles are the highest-leverage work available, how the Turkish competitive environment differs from Western Shopping auctions, and the disapprovals foreign brands hit most often.

Table of Contents

Why Shopping behaves differently in Turkey

The mechanics of Shopping are the same everywhere. What differs in Turkey is who you are bidding against and where the click goes next.

In most Western markets, a Shopping results page is dominated by retailers and brands. In Turkey, marketplaces occupy a large share of commercial search results, and price comparison platforms sit in the consideration path as well. A foreign brand’s product listing frequently appears alongside listings for the same product sold by Turkish marketplace sellers — sometimes including grey-market sellers of the brand’s own goods.

Three consequences follow, and they shape how you should plan.

Price visibility is immediate and comparative. Shopping surfaces price next to a competing price. In a market where consumers actively compare before buying, an uncompetitive price is not a nuance to be handled in the landing page — it is visible before the click.

You may be competing against your own product. If Turkish resellers already list your goods, your Shopping ad enters a results page where your brand already appears at a different price. Auditing who sells your products in Turkey before launching Shopping is a practical prerequisite, not a branding exercise. The marketplace side of that picture is covered in our guides to e-commerce in Turkey and Hepsiburada and Amazon Turkey advertising.

The click has to survive a Turkish checkout. Shopping traffic is high-intent, and losing it at a checkout that does not meet local expectations is expensive. That is a separate discipline, covered in our guide to conversion rate optimization for e-commerce in Turkey.

The three settings that decide whether you serve

Google’s documentation is unambiguous on this, and the failure mode is specific.

Target countries are the countries where the products in your product data are sold. Items uploaded to a selected target country must meet the requirements for that country, including feed specifications, policies, and language and currency requirements. If an item does not meet them, the product is disapproved for that country, with an issue shown in Merchant Center indicating the affected countries.

That per-country disapproval is what makes this easy to miss. A global feed serving fifteen markets can be healthy in fourteen and dead in Turkey, and the account-level view will look broadly fine. Filter diagnostics by country before concluding anything.

Currency. You must use a currency supported for your target country, and Google permits submitting in another supported currency with automatic conversion to the target country’s currency. So lira is not strictly required. It is, however, what practitioners recommend for a market you intend to compete in, because converted pricing is less predictable for the shopper and harder to keep consistent with your landing page. Choosing lira means maintaining lira pricing — a real operational commitment in an inflationary environment, not a feed setting.

Language. You may submit product data in any supported language and target a country in it, so Turkish is not the only permitted option. What matters is consistency: your product data, landing page and checkout have to align, and Google’s requirements apply to product data and landing pages together. An English feed pointing at English pages is a valid configuration for Turkey — it simply addresses a narrow language group rather than the market. For anything beyond a niche audience, Turkish product data pointing at Turkish landing pages and a Turkish checkout is the configuration that competes.

Adding Turkey is not a checkbox. Google notes that when you configure additional countries, you may need to customise your product data, and that if you do not complete those steps your products may not show in the additional countries. Adding “Turkey” to an existing European feed without localising currency, language and shipping is the single most common way this goes wrong.

The CSS assumption that does not transfer

This deserves its own section because it wastes more planning time than any other misconception.

In countries within the European Economic Area, plus the United Kingdom and Switzerland, merchants must work with a Comparison Shopping Service to place Shopping ads on Google’s general search results page. Google lists the programme as operating in 21 countries: Austria, Belgium, Czechia, Denmark, Finland, France, Germany, Greece, Hungary, Ireland, Italy, the Netherlands, Norway, Poland, Portugal, Romania, Slovakia, Spain, Sweden, Switzerland and the United Kingdom.

Turkey is not on that list. The CSS programme is not available there, and the bidding economics European teams associate with third-party CSS partners do not apply.

Two practical implications. First, if your Merchant Center account is switched to a third-party CSS, be aware that Google’s own guidance addresses exactly this scenario: where a switched account contains product data for countries where the CSS programme is not available, those ads and listings can stop being served unless the new CSS has chosen to place listings in those countries. Turkey is one of those countries. Check that your Turkish products are actually being placed rather than assuming the switch was neutral.

Second, treat any proposal offering CSS bidding savings on Turkish Shopping spend with scepticism. Those savings are a feature of the European programme, and the programme does not operate in Turkey. A CSS can still place your listings here — but that is placement, not a discount, and conflating the two is a useful signal about whether the vendor understands the market. It is worth weighing alongside the criteria in our guide to choosing a digital marketing agency in Turkey.

Turkish product titles are the highest-leverage field

If you do one thing with a Turkish feed, do this.

Shopping matches products to queries largely through product data, and the title carries most of that weight. A translated title is not the same as a title built from how Turkish shoppers search. The gap shows up in three specific ways.

Category vocabulary is not a direct translation. Turkish product categories often use different terms than a dictionary translation produces, and in many categories Turkish consumers use a mix of Turkish and borrowed English terms, with the dominant term varying by category. This has to be checked against how Turkish retailers and marketplaces actually name the category, not decided by a translator.

Turkish word order and suffixes differ from English title conventions. A title assembled by concatenating brand, product type and attributes in English order can read awkwardly in Turkish and miss the phrasing shoppers use.

Attribute order matters for truncation. Titles are truncated in display. Front-load the terms most likely to match the query — typically brand and the product term Turkish shoppers actually use — rather than a global taxonomy label.

The underlying language mechanics are the same ones that govern Turkish search generally, covered in our guide to SEO in Turkey, and the broader principle that translation is not localisation is set out in website localization for Turkey.

A practical method: before writing titles, search your three most important products on Google in Turkish and on the major Turkish marketplaces, and record how the listings that appear are named. That naming reflects commercial testing you do not otherwise have access to.

Identifiers, categories and attribute language

A detail that catches teams building Turkish feeds for the first time: while your product content is in Turkish, attribute names and the values for attributes that use supported values must be submitted in English. Google’s product data specification is explicit — the condition attribute, for example, uses the supported values new, refurbished and used, which must be submitted in English for the system to read them.

So a Turkish feed is bilingual by design: Turkish titles and descriptions, English attribute keys and enumerated values. Feeds built by a Turkish developer without that context are a recurring source of disapprovals.

On identifiers, the standard requirements apply — brand and GTIN where the product has them, with the identifier exists attribute used where they genuinely do not. Products assembled for Turkey from a regional catalogue sometimes lose identifier data in the transformation; check rather than assume.

Google product category and your own product type attribute both help Google understand what you sell. Where your global taxonomy does not map cleanly onto Turkish category conventions, the product type field is where you can express the local naming without disturbing your global structure.

Shipping and returns configuration

Shipping configuration is a common cause of Turkish products not serving, because it is easy to add a country without adding its shipping service.

Google notes that setting up multi-country shipping settings allows you to use a single set of shipping information across multiple countries, but does not automatically change which countries you target or where products show. Those are separate settings. Configure Turkish shipping explicitly.

Beyond compliance, shipping detail is commercially significant in Turkey. Delivery speed expectations are set by domestic marketplaces, and a listing showing a long international delivery window competes poorly against one offering local dispatch. If you fulfil from outside Turkey, that disadvantage is structural and worth modelling honestly before committing budget — it may point toward local stock or a marketplace-first approach instead.

Returns policy data matters for the same reason. Turkish consumer protection rules give consumers withdrawal rights in distance sales, and a returns proposition that looks worse than domestic alternatives is visible in the comparison.

Pricing, VAT and the installment question

Three pricing issues specific to running Shopping in Turkey.

Price consistency. The price in your feed must match the price on the landing page. This sounds trivial until you run dynamic pricing or currency-converted pricing, at which point mismatches become a persistent disapproval source. In an inflationary environment where lira prices change more often than in other markets, feed refresh frequency is a real operational requirement rather than a setting you configure once.

VAT presentation. Turkish consumers see VAT-inclusive prices in retail. Feeding a net price that differs from the displayed price creates both a mismatch problem and a trust problem.

Installments — and why the feed attribute probably will not help you. Installment payment is central to Turkish e-commerce, so teams reasonably look for a way to express it in the feed. Merchant Center does have an installment attribute, but in Turkey it is not available across general product categories: its availability there is limited to certain wireless product and service categories. On top of that, products using the installment attribute can target only a single country and are not eligible for cross-border trade.

For most catalogues, then, the practical answer is that installment availability is communicated on your product page and at checkout rather than through the feed. Plan the taksit proposition as a merchandising and checkout question, not a feed field — and confirm the current attribute availability in Google’s product data specification before assuming otherwise.

A dedicated Turkey feed is still usually the right structure, for reasons that have nothing to do with the installment attribute: Turkish-language product data, lira pricing with its own refresh cadence, Turkey-specific shipping and returns configuration, and the general benefit of keeping a market with different localisation and operational rhythms separate from your global catalogue.

Free listings alongside paid

Merchant Center product data powers cost-free product listings as well as Shopping ads, and the same language, currency and policy requirements apply to both.

For a foreign brand entering Turkey this is worth deliberate attention, because it means the feed work has a return even before you commit media budget. A well-formed Turkish feed produces organic product visibility, which for a brand with no Turkish awareness is a cheap first signal of whether demand exists at all. It is also a reason to complete feed work properly rather than treating it as campaign setup.

Campaign structure and the Turkish auction

Two structural decisions matter more in Turkey than the bidding detail.

Separate Turkey from your regional campaigns. A campaign spanning several markets will allocate toward whichever market converts most efficiently, which for a new entrant is never Turkey. Separate budgets are how Turkey gets a fair test rather than being starved by an algorithm optimising across markets.

Give the system enough data to learn. Automated bidding needs conversion volume. A deliberately small Turkish test that never accumulates conversions produces noise rather than a verdict on the channel. Either fund a test large enough to clear the learning phase or use a manual approach until volume exists.

On cost, there is no reliable published Turkey-specific Shopping benchmark, and figures circulating online are largely global averages that do not transfer to the Turkish auction. Build your own benchmark through a deliberate test. The broader channel cost picture is in our budget guide to digital marketing costs in Turkey, and the search and social layer around Shopping is covered in our guide to Google Ads and Meta Ads in Turkey.

Shopping traffic also feeds your remarketing audiences, which in a market where first-visit conversion is harder is a meaningful secondary benefit — see our guide to retargeting and remarketing in Turkey.

The disapprovals foreign brands hit most

In rough order of how often they appear on a first Turkish feed:

  • Currency not matching the target country. Prices left in euros or dollars while targeting Turkey.
  • Landing page language mismatch. Turkish product data pointing at an English page, or the reverse.
  • Price mismatch between feed and landing page. Frequently caused by currency conversion or delayed feed refresh.
  • Missing shipping configuration for Turkey. Country added, shipping service not.
  • Attribute values submitted in Turkish where English supported values are required.
  • Missing identifiers lost when a regional catalogue was transformed into a Turkish feed.
  • Restricted or regulated products. Category-specific rules apply and vary; cosmetics, supplements and health-adjacent products carry additional requirements under Turkish law that sit outside Merchant Center policy.

Newly uploaded products go through data quality checks and can take time to process, so allow for that before concluding that a fix has not worked.

Measurement

Two measurement points specific to this channel in Turkey.

Segment Turkey properly. Shopping performance blended across a region tells you nothing about Turkey. Currency handling, market segmentation and conversion configuration all need to be right, and they are a common failure point — covered in our GA4 and marketing analytics setup guide for Turkey.

Read product-level data, not just campaign data. Shopping performance is driven by which products match which queries. The useful analysis is which items get impressions and which do not, which usually points back to titles and categorisation rather than bids.

Feed quality, site performance and pricing operations sit across marketing and web development, which is one reason this work tends to land with a partner able to cover both — the combination of paid media and web and software capability that agencies like Medyae are structured around. The point is practical rather than promotional: a feed problem is rarely solvable by the media team alone.

Common mistakes

Adding Turkey to an existing European feed. Shipping has to be configured for Turkey, and currency and language need to be coherent with your landing pages; adding the country alone does not serve products.

Budgeting for CSS savings in Turkey. The programme’s 21 countries do not include Turkey, so its bidding economics do not apply — even though a CSS may still place your listings there.

Translating product titles. Translation produces grammatically correct titles that miss how Turkish shoppers search.

Trying to express taksit through the feed. The installment attribute is limited to certain wireless categories in Turkey and rules out cross-border targeting; for most catalogues it belongs on the product page and at checkout.

Submitting attribute values in Turkish. Supported values must be in English.

Reading account-level diagnostics. Disapprovals are per country; filter for Turkey.

Setting lira prices once. Price mismatch accumulates when feed refresh does not keep pace with pricing changes.

Launching Shopping before auditing existing sellers. You may be bidding into a results page where your own product already appears cheaper.

Ignoring free listings. The same feed work produces organic visibility with no media spend.

A 30-day plan

Week 1 — audit. Check whether Turkey is configured as a target country and whether your account is switched to a CSS that may not be placing Turkish listings. Filter diagnostics by Turkey. Audit who already sells your products in Turkish search results.

Week 2 — build a dedicated Turkey feed. Lira pricing, Turkish titles and descriptions written from Turkish search behaviour rather than translated, English attribute values, Turkish landing pages, Turkish shipping and returns configured.

Week 3 — validate. Clear disapprovals, confirm feed-to-landing-page price consistency, verify free listings are serving, and set a feed refresh cadence that matches how often your lira prices change.

Week 4 — launch small and read product-level data. Separate Turkey campaigns and budget, enough volume to be interpretable, and analysis focused on which products receive impressions rather than on bid adjustments.

Frequently asked questions

Is Google Shopping available in Turkey?

Yes. Turkey can be set as a target country in Merchant Center, and products meeting Turkey’s feed specification, policy, language and currency requirements are eligible for Shopping ads and cost-free product listings. Products that do not meet those requirements are disapproved for Turkey specifically while continuing to serve in other countries.

Do I need a CSS partner for Google Shopping in Turkey?

No. The Comparison Shopping Service programme operates in 21 countries across the EEA plus the United Kingdom and Switzerland, and Turkey is not among them. If your account is switched to a third-party CSS, check that your Turkish products are still being placed, since Google notes that listings for countries outside the programme can stop serving unless the new CSS places them.

Do product prices need to be in Turkish lira?

You must use a currency supported for your target country, and Google can convert automatically if you submit in another currency. Submitting in Turkish lira for Turkey is the recommended approach, which means maintaining lira pricing and refreshing the feed often enough to stay consistent with your landing pages.

Can I use my English product feed for Turkey?

Yes — you may submit product data in any supported language and target Turkey with it. The requirement is consistency: product data, landing page and checkout have to align, so an English feed needs English landing pages and an English checkout. That is a valid setup, but it addresses a narrow language group rather than the Turkish market, so it is rarely the right commercial choice.

Should Turkish product titles be translated from English?

No. Translation produces correct titles that frequently miss the terms Turkish shoppers use, since category vocabulary mixes Turkish and borrowed terms differently by category. Build titles from how Turkish retailers and marketplaces actually name the category, then front-load the terms most likely to match the query.

Should I create a separate feed for Turkey?

In most cases yes — on localisation and operational grounds rather than technical ones. Turkish-language product data, lira pricing with its own refresh cadence, and Turkey-specific shipping and returns configuration are easier to manage in a dedicated feed than as exceptions inside a global one.

Conclusion

Google Shopping in Turkey rewards preparation rather than optimisation. The work that decides performance happens before any campaign goes live: a dedicated Turkish feed with lira pricing, titles built from Turkish search behaviour, correctly configured shipping, and landing pages that match the feed in both language and price.

The two assumptions worth discarding at the outset are that Turkey can be added to a European feed as a checkbox, and that the CSS arrangement saving you money in Europe does anything here. Neither is true, and both cost weeks.

Do the feed properly and you get two channels from one piece of work — paid Shopping and cost-free listings — in a market where product-level search visibility is one of the few ways a foreign brand competes with marketplace sellers on their own results page.