Launching a Turkish Site Without Losing Search Equity
In Turkey you have to run the migration twice, and most foreign brands only run it once. Google and Yandex handle a site move through entirely different mechanisms. Google asks for permanent redirects, a one-to-one URL map and, for domain or subdomain moves, the Change of Address tool. Yandex works on the concept of a site’s main address and secondary mirror, and the move only completes when its robot reassigns the main address — which requires both the old and new sites to be added and verified in Yandex Webmaster and a request submitted through its Relocate site tool.
Skip the Yandex side and the old address can keep appearing in Yandex results while the new one does not. Yandex states plainly that when the main mirror changes it does not guarantee that the number of pages in search results, ranking or traffic will stay the same, and that the process takes from a few weeks to months — usually about a month for changes to appear. This article covers the mapping work that determines the outcome, the redirect rules, both webmaster processes, the Turkish-specific cases that complicate a launch, and what to watch afterwards.
Table of Contents
- What actually loses traffic in a market-entry launch
- Build the URL map before anything else
- Redirects: type, chains and how long to keep them
- Telling Google
- Telling Yandex
- Turkish cases that complicate the move
- The pre-launch sequence
- What to monitor, and for how long
- When it goes wrong
- Common mistakes
- Frequently asked questions
What actually loses traffic in a market-entry launch
A Turkish launch is rarely a clean greenfield build. There is almost always something already ranking, and what happens to it decides the first six months.
Four situations account for most of the damage:
A distributor or partner site is replaced. The pages that ranked for your products in Turkish belonged to someone else, and switching the market to a brand-owned site without redirects discards every signal those pages accumulated — assuming you can get redirects implemented on a site you do not control, which is a commercial conversation to have before the launch date is set.
An old Turkish site is replaced by a new structure. The most common version: a legacy .com.tr built years ago is folded into a subfolder of the global domain, or the reverse. Every URL changes.
The global site adds Turkish and existing URLs shift. Introducing a language path often rewrites URLs that were previously serving Turkish visitors in English, and those were ranking.
A replatform coincides with the localisation. New CMS, new URL patterns, new Turkish content, all at once — which makes diagnosis impossible when traffic moves, because nobody can tell which change caused it.
The last one is worth a planning decision of its own: separating the platform change from the localisation change by a few weeks costs schedule and buys the ability to tell what happened.
Build the URL map before anything else
Google’s guidance is explicit that mapping is the foundation of the move: “It’s important to map your old site’s URLs to the URLs for the new site.” Everything downstream — redirect rules, QA, monitoring — depends on a complete list that exists before development starts.
Where to assemble the list from, per Google’s documentation: sitemaps, server logs, analytics and the CMS. Include images, videos, JavaScript and CSS, not only pages.
Four additions that matter in practice:
- Pull the list from reality, not from the CMS alone. Server logs and analytics reveal URLs the CMS no longer knows about — campaign landing pages, old PDFs, pages built by a previous agency.
- Add the URLs that earn links and traffic even if they are obscure. A forgotten technical specification page can be the most-linked asset on a legacy site.
- Map one-to-one wherever a genuine equivalent exists. Google warns directly against the alternative: “Don’t redirect many old URLs to one irrelevant single URL destination.”
- Decide explicitly what has no equivalent. Discontinued products and expired campaigns need a deliberate decision — the closest relevant category, or a proper status code — not a default to the homepage.
Keep the map as a living document owned by one person. On a mid-sized site it is the single artefact that determines whether the migration succeeds, and it is the one most often treated as a developer’s spreadsheet rather than a commercial asset.
Redirects: type, chains and how long to keep them
Three rules from Google’s own documentation cover most of what matters.
Use permanent server-side redirects. Google recommends “HTTP permanent redirects if possible, such as 301 and 308”, and confirms that “301 and other permanent redirects don’t cause a loss in PageRank.” The widespread belief that redirects leak value is not what the documentation says.
Point each redirect at its final destination. Chains add latency and should be kept short — a practical concern in a migration where a redirect from an old distributor URL might otherwise pass through two intermediate rules.
Keep the redirects in place for at least a year. Google’s guidance is to keep them “generally at least 1 year”, so it can transfer signals and recrawl links from other sites. Redirects can stay indefinitely for users, though they slow page loads, which is why Google also advises updating your own and high-traffic external links.
Two operational notes. Internal links should be updated to the new URLs immediately after the move starts rather than left to resolve through redirects. And the redirect rules need to survive the next deployment — a migration undone by a routine release three months later is a common and avoidable failure.
Telling Google
The Change of Address tool is narrower than most teams assume, and using it for the wrong kind of move wastes time. Google states: “You only need this tool when moving from one domain or subdomain to another.” It is not needed for HTTP-to-HTTPS moves, for switching between www and non-www on the same domain, or for moving paths within a domain.
Where the move does cross domains, Google advises submitting requests for all verified variants of the old domain, including subdomains and www and non-www versions, even if they are no longer in use.
The rest of the Google-side work:
- Submit the new sitemap in Search Console so the new URLs are discovered; the old sitemap can then be removed, and warnings about redirects in it are expected and can be ignored.
- Self-referencing canonicals on each new page, with hreflang annotations updated to the new URLs.
- Update internal links immediately after the move starts.
- Ask external sites to update their links, prioritised by the traffic they send.
- Update profile links and ad campaigns — social profiles, directory listings, and the landing pages behind live campaigns.
Where the Turkish site’s structure itself is still an open question — country domain, subfolder or subdomain, and the hreflang work that follows — that decision belongs before the migration rather than inside it, and is covered in our guide to SEO structure for foreign brands in Turkey.
Telling Yandex
Yandex does not have an equivalent of the Change of Address tool; it has a different model entirely, built around which address is treated as the site’s main one. Ignoring it is the single most common omission in Turkish migrations run by international teams.
Yandex groups addresses with the same content and designates one as the main site address — the one included in search results — with the other as a secondary mirror, which is not. Some accumulated metrics are assigned to the main address during that grouping. The robot will choose automatically if you give it no instruction, which is exactly what happens when nobody tells it.
The process Yandex documents:
- Add both sites to Yandex Webmaster and verify management rights over each.
- Set redirects from the old URLs to the corresponding new ones, with Yandex recognising 301 as permanent and 302, 303 and 307 as temporary. Yandex specifically requires a redirect from the old home page to the new home page for a proper move.
- Avoid redirecting every old page to the new home page. Yandex states such redirects are inconvenient for users and consequently slow the new site’s indexing.
- Use the Relocate site tool, found under Indexing in Yandex Webmaster, to submit the move. If the site is currently grouped as another’s secondary mirror, the addresses have to be separated first.
- Expect it to take time. Yandex says the main mirror is changed within a few weeks, that a relocation request can take from a few weeks to months depending on the relocation type and crawl speed, and that changes usually appear in search results in about a month.
Yandex also states the expectation clearly: when the main mirror changes, it does not guarantee that the number of pages in search results, page ranking or traffic will remain the same. Plan the launch calendar accordingly rather than promising a stable transition.
Why this matters commercially in Turkey rather than as a technical footnote is covered in our guide to SEO in Turkey: Yandex is a material second channel here in a way it is not in most of Western Europe.
Turkish cases that complicate the move
Four local specifics turn a routine migration into a difficult one.
Turkish characters in URLs. Slugs containing ı, ş, ğ, ç, ö or ü have to be handled consistently — either percent-encoded or transliterated to ASCII — and the choice has to be the same everywhere. Mixed handling produces two URLs for the same page, which creates duplicates on the old site and broken mappings on the new one. Decide the transliteration rule, apply it to the whole map, and check that the dotless ı and dotted İ are not being collapsed incorrectly by a case-normalisation step.
Redirects on a site you do not control. Where the legacy Turkish presence belongs to a distributor, the redirects are a commercial negotiation. Raise it early and write it into the transition agreement, because asking after the relationship has ended rarely works.
A parked or legacy .com.tr. Many brands hold a .com.tr from the old registration regime that serves a thin site or a holding page. Decide whether it becomes the primary address or redirects into the global structure, and implement that decision deliberately in both Search Console and Yandex Webmaster rather than leaving two addresses competing.
Marketplace and partner pages that rank. On many Turkish launches, the pages ranking for your products sit on marketplaces rather than on any site you can redirect. Those cannot be migrated, only competed with — which changes what success looks like in the first months and is part of the wider picture in our guide to e-commerce in Turkey.
The pre-launch sequence
Order matters more than completeness here, because several steps are only testable before the switch.
1. Freeze the URL structure. Nothing else can be built until the new patterns are final.
2. Complete the map, from sitemaps, logs, analytics and the CMS, including assets.
3. Build and test redirects on staging, checking status codes rather than visual outcomes — a 302 that looks identical to a 301 in a browser is a different instruction to a crawler.
4. Prepare both webmaster accounts. Verify the new property in Search Console and add and verify both sites in Yandex Webmaster before launch day, not after.
5. Check indexability. The staging site’s noindex directives and robots.txt disallow rules are the most common thing carried into production by accident.
6. Confirm canonicals and hreflang reference new URLs, with self-referencing canonicals in place.
7. Launch, then immediately submit the new sitemap, run the Change of Address request where the move crosses domains, submit the Yandex Relocate site request, and update internal links.
8. Update the things outside the site — ad campaign destinations, social profiles, directory listings, email templates and printed QR destinations.
The build side of this sits with Medyae’s web design and software service, and the search side with its SEO service; in practice the migration succeeds or fails on whether those two are working from the same map.
What to monitor, and for how long
Google is explicit that fluctuation is expected and that medium-sized sites may take “a few weeks or more” to show new URLs. The question is which movement is normal and which is a defect.
The crossover pattern. Google’s stated ideal is that “the traffic on the old site will go down, while on the new site the traffic goes up.” Watch both properties together; a fall on the old site without a corresponding rise on the new one is the signal that something is wrong.
Indexing counts on both properties. Pages indexed should fall on the old site and rise on the new one.
Server logs. Googlebot crawling the new URLs, unexpected error codes, and whether the server has capacity for the increased crawl rate — Google names insufficient server capacity as a common problem during migrations.
Leftover noindex tags and wrong redirect targets, which Google also lists among the common problems.
The Yandex side separately. Whether the main address has actually changed, which Yandex Webmaster reports and notifies on, remembering its stated timeline of weeks to months.
Two local additions worth building into the monitoring: track rankings and traffic for Google and Yandex separately rather than as a blended figure, and watch how your brand and product information is being surfaced in AI answers during the transition, since that layer draws on the same signals and is covered in our guide to AI search in Turkey.
Keep monitoring for at least the year the redirects stay in place, not the fortnight the project plan allocates.
When it goes wrong
Most migration problems are configuration failures rather than ranking failures, and they are diagnosable in a fixed order.
First, check indexability. A noindex or a robots.txt disallow carried from staging explains a total disappearance better than any ranking theory.
Second, sample the redirects. Not the homepage — a spread of deep pages, checking the actual status code and the final destination.
Third, check for chains and loops, which commonly appear where old rules from a previous migration are still live.
Fourth, check the canonicals. New pages canonicalising to old URLs is a frequent cause of a new site that refuses to index.
Fifth, check both webmaster tools for whether the move was actually registered on each side.
On rolling back: it is usually the wrong instinct. Reverting a move midway leaves both sites with partial signals and restarts the clock in both engines. Unless the new site is fundamentally broken, fixing forward is normally faster than reversing — but the decision should be made on evidence from the checks above rather than on the shape of a traffic graph in week two.
Common mistakes
- Running the migration only for Google. Yandex needs its own process through Relocate site, and will otherwise pick a main address on its own.
- Redirecting everything to the homepage. Google advises against it and Yandex says it slows indexing of the new site.
- Using the Change of Address tool for a path move. It applies to domain and subdomain moves only.
- Removing redirects after a few months. Google’s guidance is to keep them generally at least a year.
- Building the map from the CMS alone. Logs and analytics hold the URLs the CMS forgot.
- Inconsistent handling of Turkish characters in slugs. It creates duplicate URLs and broken mappings.
- Leaving staging noindex in production. The most common total-disappearance cause.
- Replatforming and localising in the same release. It makes diagnosis impossible.
- Negotiating distributor redirects after the switch. The leverage is gone.
- Reporting Google and Yandex as one number. It hides which engine the problem is in.
Frequently asked questions
Do we need to do anything in Yandex when we launch a new Turkish site?
Yes, and it is separate from the Google process. Yandex groups addresses with the same content and designates one as the main site address, which is the one included in search results; if you give no instruction, its robot decides. Add both the old and new sites to Yandex Webmaster, verify them, set redirects from old URLs to the corresponding new ones including home page to home page, and submit the move through the Relocate site tool under Indexing. Yandex says the change takes from a few weeks to months, usually about a month to appear.
How long should we keep the redirects?
Google’s guidance is to keep permanent redirects in place “generally at least 1 year”, which allows it to transfer signals and recrawl links from other sites. They can remain indefinitely for users, though they add latency, so Google also advises updating your own internal links and asking high-traffic external sites to point at the new URLs.
Do 301 redirects lose ranking value?
Google’s documentation states that “301 and other permanent redirects don’t cause a loss in PageRank.” The practical risks in a migration are elsewhere: incomplete mapping, redirects to irrelevant destinations, long chains, and leftover noindex directives.
When do we use Google’s Change of Address tool?
Only when moving between domains or subdomains. Google states it is not needed for HTTP-to-HTTPS moves, for switching between www and non-www on the same domain, or for moving paths within a domain. Where it does apply, submit requests for all verified variants of the old domain, including subdomains and the www and non-www versions.
How long before traffic recovers?
Nobody can give you a date, and a supplier who does is guessing. Google says fluctuations are expected while it recrawls and that medium-sized sites may take a few weeks or more for new URLs to appear; Yandex says a main address change usually takes about a month to show in results and may take longer. The pattern to watch is the crossover — old-site traffic falling as new-site traffic rises — rather than the absolute number in any single week.
Conclusion
A Turkish launch that replaces something already ranking is a migration, whether or not anyone calls it one, and the outcome is decided by work done before the switch.
Four things carry most of the risk. Build the URL map from sitemaps, logs, analytics and the CMS before development starts, and map one-to-one rather than defaulting to the homepage. Use permanent redirects pointed at final destinations and keep them in place for at least a year, since Google states permanent redirects do not cost PageRank. Run both engines’ processes — Search Console with the Change of Address tool where the move crosses domains, and Yandex Webmaster’s Relocate site tool to reassign the main address, which Yandex says takes weeks to months. And settle the Turkish-character handling in your slugs before the map is built, because inconsistent transliteration produces duplicates that no redirect rule can repair afterwards.
For the structural decision that should precede the migration, our guide to SEO structure for foreign brands in Turkey is the companion piece; for what the new site then has to do for Turkish users, our guide to website localization for Turkey; and our pillar guide to marketing in Turkey for foreign brands is the place to start.
This article is general information about site migration for the Turkish market, and the guidance cited comes from the published documentation of Google Search Central and Yandex Webmaster as referenced. Search engine tools and documentation change; confirm current procedures before executing a migration.