{"id":3839,"date":"2025-12-31T19:07:05","date_gmt":"2025-12-31T16:07:05","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/marka-degisiminde-alan-adi-tasima-seo-ve-e-postayi-korumak\/"},"modified":"2025-12-31T19:07:05","modified_gmt":"2025-12-31T16:07:05","slug":"marka-degisiminde-alan-adi-tasima-seo-ve-e-postayi-korumak","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/marka-degisiminde-alan-adi-tasima-seo-ve-e-postayi-korumak\/","title":{"rendered":"Marka De\u011fi\u015fiminde Alan Ad\u0131 Ta\u015f\u0131ma: SEO ve E\u2011Postay\u0131 Korumak"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><p>Marka de\u011fi\u015ftirirken alan ad\u0131n\u0131 yenilemek, sadece tasar\u0131m ve logo g\u00fcncellemesi yapmakla k\u0131yaslanamayacak kadar kritik bir ad\u0131md\u0131r. Eski domain\u2019inizde y\u0131llarca biriken otorite, backlink\u2019ler, Google\u2019daki g\u00f6r\u00fcn\u00fcrl\u00fck ve e\u2011posta itibar\u0131n\u0131z\u0131n tamam\u0131 bu hamleden do\u011frudan etkilenir. Yanl\u0131\u015f kurgulanm\u0131\u015f bir ge\u00e7i\u015f, aylarca s\u00fcren organik trafik kayb\u0131na, m\u00fc\u015fterilerin size ula\u015famamas\u0131na ve e\u2011postalar\u0131n\u0131z\u0131n spam klas\u00f6r\u00fcne d\u00fc\u015fmesine neden olabilir. Do\u011fru planlanm\u0131\u015f bir ge\u00e7i\u015f ise, yeni markan\u0131z\u0131 \u00f6ne \u00e7\u0131kar\u0131rken eski domain\u2019de biriktirdi\u011finiz de\u011feri m\u00fcmk\u00fcn olan en y\u00fcksek oranda korur.<\/p>\n<p>Bu yaz\u0131da, eski domain\u2019den yeni domain\u2019e ge\u00e7erken SEO ve e\u2011postay\u0131 nas\u0131l koruyabilece\u011finizi; DNS, 301 y\u00f6nlendirmeleri, Search Console ayarlar\u0131, MX\/SPF\/DKIM g\u00fcncellemeleri ve pratik kesinti y\u00f6netimiyle birlikte ad\u0131m ad\u0131m anlataca\u011f\u0131m. DCHost taraf\u0131nda onlarca alan ad\u0131 ve e\u2011posta ge\u00e7i\u015fi y\u00f6nettik; sahada s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalar\u0131 ve i\u015fe yarayan kontrol listelerini bu rehbere s\u0131k\u0131\u015ft\u0131rmaya \u00e7al\u0131\u015ft\u0131m. Amac\u0131m\u0131z, hem pazarlama hem de teknik ekiplerin ayn\u0131 sayfada bulu\u015fabilece\u011fi, uygulanabilir bir yol haritas\u0131 sunmak.<\/p>\n<div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Marka_Degisimi_ve_Alan_Adi_Tasimanin_Tasidigi_Riskler\"><span class=\"toc_number toc_depth_1\">1<\/span> Marka De\u011fi\u015fimi ve Alan Ad\u0131 Ta\u015f\u0131man\u0131n Ta\u015f\u0131d\u0131\u011f\u0131 Riskler<\/a><\/li><li><a href=\"#Gecis_Oncesi_Planlama_Envanter_ve_Yol_Haritasi\"><span class=\"toc_number toc_depth_1\">2<\/span> Ge\u00e7i\u015f \u00d6ncesi Planlama: Envanter ve Yol Haritas\u0131<\/a><ul><li><a href=\"#1_Tum_URLlerin_Envanterini_Cikarin\"><span class=\"toc_number toc_depth_2\">2.1<\/span> 1. T\u00fcm URL\u2019lerin Envanterini \u00c7\u0131kar\u0131n<\/a><\/li><li><a href=\"#2_Teknik_SEO_Analitik_ve_Entegrasyon_Envanteri\"><span class=\"toc_number toc_depth_2\">2.2<\/span> 2. Teknik SEO, Analitik ve Entegrasyon Envanteri<\/a><\/li><li><a href=\"#3_DNS_ve_Hosting_Tarafindaki_Hazirlik\"><span class=\"toc_number toc_depth_2\">2.3<\/span> 3. DNS ve Hosting Taraf\u0131ndaki Haz\u0131rl\u0131k<\/a><\/li><\/ul><\/li><li><a href=\"#SEOyu_Korumak_Icin_Eski_Domainden_Yeni_Domaine_Gecis_Adimlari\"><span class=\"toc_number toc_depth_1\">3<\/span> SEO\u2019yu Korumak \u0130\u00e7in Eski Domain\u2019den Yeni Domain\u2019e Ge\u00e7i\u015f Ad\u0131mlar\u0131<\/a><ul><li><a href=\"#1_301_Yonlendirme_Stratejisi\"><span class=\"toc_number toc_depth_2\">3.1<\/span> 1. 301 Y\u00f6nlendirme Stratejisi<\/a><\/li><li><a href=\"#2_Canonical_Sitemap_ve_robotstxt_Guncellemeleri\"><span class=\"toc_number toc_depth_2\">3.2<\/span> 2. Canonical, Sitemap ve robots.txt G\u00fcncellemeleri<\/a><\/li><li><a href=\"#3_Google_Search_Console_ve_Diger_Araclar\"><span class=\"toc_number toc_depth_2\">3.3<\/span> 3. Google Search Console ve Di\u011fer Ara\u00e7lar<\/a><\/li><\/ul><\/li><li><a href=\"#DNS_SSL_ve_Barindirma_Tarafi_Sifira_Yakin_Kesinti_Mumkun_mu\"><span class=\"toc_number toc_depth_1\">4<\/span> DNS, SSL ve Bar\u0131nd\u0131rma Taraf\u0131: S\u0131f\u0131ra Yak\u0131n Kesinti M\u00fcmk\u00fcn m\u00fc?<\/a><ul><li><a href=\"#1_DNS_TTL_ve_Yayilim_Yonetimi\"><span class=\"toc_number toc_depth_2\">4.1<\/span> 1. DNS TTL ve Yay\u0131l\u0131m Y\u00f6netimi<\/a><\/li><li><a href=\"#2_SSL_HTTPS_ve_HSTS_Ayarlari\"><span class=\"toc_number toc_depth_2\">4.2<\/span> 2. SSL \/ HTTPS ve HSTS Ayarlar\u0131<\/a><\/li><li><a href=\"#3_Sunucu_Mimarisi_Staging_ve_BlueGreen_Yaklasimi\"><span class=\"toc_number toc_depth_2\">4.3<\/span> 3. Sunucu Mimarisi: Staging ve Blue\u2011Green Yakla\u015f\u0131m\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#EPostayi_Korumak_MX_SPF_DKIM_ve_Kullanici_Tarafi\"><span class=\"toc_number toc_depth_1\">5<\/span> E\u2011Postay\u0131 Korumak: MX, SPF, DKIM ve Kullan\u0131c\u0131 Taraf\u0131<\/a><ul><li><a href=\"#1_MX_Kayitlari_ve_Gecis_Stratejisi\"><span class=\"toc_number toc_depth_2\">5.1<\/span> 1. MX Kay\u0131tlar\u0131 ve Ge\u00e7i\u015f Stratejisi<\/a><\/li><li><a href=\"#2_SPF_DKIM_ve_DMARC_Guncellemeleri\"><span class=\"toc_number toc_depth_2\">5.2<\/span> 2. SPF, DKIM ve DMARC G\u00fcncellemeleri<\/a><\/li><li><a href=\"#3_Geciste_Cift_Teslim_Forwarding_Alias_Senaryolari\"><span class=\"toc_number toc_depth_2\">5.3<\/span> 3. Ge\u00e7i\u015fte \u00c7ift Teslim (Forwarding \/ Alias) Senaryolar\u0131<\/a><\/li><li><a href=\"#4_Kullanici_Iletisimi_ve_Istemci_Ayarlari\"><span class=\"toc_number toc_depth_2\">5.4<\/span> 4. Kullan\u0131c\u0131 \u0130leti\u015fimi ve \u0130stemci Ayarlar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Guvenlik_ve_Alan_Adi_Korumasi_Eski_Domaini_Asla_Hemen_Birakmayin\"><span class=\"toc_number toc_depth_1\">6<\/span> G\u00fcvenlik ve Alan Ad\u0131 Korumas\u0131: Eski Domain\u2019i Asla Hemen B\u0131rakmay\u0131n<\/a><ul><li><a href=\"#1_Eski_Domaini_En_Az_1224_Ay_Aktif_Tutun\"><span class=\"toc_number toc_depth_2\">6.1<\/span> 1. Eski Domain\u2019i En Az 12\u201124 Ay Aktif Tutun<\/a><\/li><li><a href=\"#2_Registrar_Lock_DNSSEC_ve_Erisim_Guvenligi\"><span class=\"toc_number toc_depth_2\">6.2<\/span> 2. Registrar Lock, DNSSEC ve Eri\u015fim G\u00fcvenli\u011fi<\/a><\/li><\/ul><\/li><li><a href=\"#Gecis_Sonrasi_Izleme_Hata_Tespiti_ve_Geri_Adim_Plani\"><span class=\"toc_number toc_depth_1\">7<\/span> Ge\u00e7i\u015f Sonras\u0131 \u0130zleme, Hata Tespiti ve Geri Ad\u0131m Plan\u0131<\/a><ul><li><a href=\"#1_SEO_ve_Trafik_Izleme\"><span class=\"toc_number toc_depth_2\">7.1<\/span> 1. SEO ve Trafik \u0130zleme<\/a><\/li><li><a href=\"#2_404_Hatalari_ve_Kirik_Linkler\"><span class=\"toc_number toc_depth_2\">7.2<\/span> 2. 404 Hatalar\u0131 ve K\u0131r\u0131k Linkler<\/a><\/li><li><a href=\"#3_EPosta_Teslim_Edilebilirligi_ve_Spam_Sikayetleri\"><span class=\"toc_number toc_depth_2\">7.3<\/span> 3. E\u2011Posta Teslim Edilebilirli\u011fi ve Spam \u015eikayetleri<\/a><\/li><li><a href=\"#4_Geri_Adim_Rollback_Plani\"><span class=\"toc_number toc_depth_2\">7.4<\/span> 4. Geri Ad\u0131m (Rollback) Plan\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Ozet_ve_DCHost_ile_Sonraki_Adimlar\"><span class=\"toc_number toc_depth_1\">8<\/span> \u00d6zet ve DCHost ile Sonraki Ad\u0131mlar<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Marka_Degisimi_ve_Alan_Adi_Tasimanin_Tasidigi_Riskler\">Marka De\u011fi\u015fimi ve Alan Ad\u0131 Ta\u015f\u0131man\u0131n Ta\u015f\u0131d\u0131\u011f\u0131 Riskler<\/span><\/h2>\n<p>Alan ad\u0131 de\u011fi\u015ftirmek, arama motorlar\u0131 ve e\u2011posta servisleri a\u00e7\u0131s\u0131ndan yeni bir kimlik edinmek anlam\u0131na gelir. Bu y\u00fczden teknik tarafta yap\u0131lan her hata, do\u011frudan gelir ve itibar kayb\u0131 olarak geri d\u00f6ner.<\/p>\n<p>\u00d6zellikle \u015fu iki alan kritik:<\/p>\n<ul>\n<li><strong>SEO:<\/strong> Y\u0131llar i\u00e7inde kazan\u0131lm\u0131\u015f organik s\u0131ralamalar, backlink profili ve sayfa otoritesi.<\/li>\n<li><strong>E\u2011posta:<\/strong> Kurumsal e\u2011posta adreslerinizin kesintisiz \u00e7al\u0131\u015fmas\u0131 ve spam filtrelerindeki itibar\u0131n\u0131z.<\/li>\n<\/ul>\n<p>\u015eu risklerle \u00e7ok s\u0131k kar\u015f\u0131la\u015f\u0131yoruz:<\/p>\n<ul>\n<li>Eksik veya hatal\u0131 301 y\u00f6nlendirmeleri nedeniyle trafik kayb\u0131 ve 404 patlamas\u0131<\/li>\n<li>Google Search Console\u2019da adres de\u011fi\u015fikli\u011finin bildirilmemesi<\/li>\n<li>MX ve SPF kay\u0131tlar\u0131 g\u00fcncellenmeden DNS cutover yap\u0131lmas\u0131 sonucu e\u2011posta kesintisi<\/li>\n<li>Yeni domain\u2019de SPF\/DKIM\/DMARC tan\u0131mlanmamas\u0131 nedeniyle spam oranlar\u0131n\u0131n artmas\u0131<\/li>\n<li>Eski domain\u2019in tamamen kapanmas\u0131 veya park sayfas\u0131na d\u00f6nmesi sonucu backlink de\u011ferinin bo\u015fa gitmesi<\/li>\n<\/ul>\n<p>Alan ad\u0131 de\u011fi\u015ftirirken SEO kayb\u0131n\u0131 en aza indirmek i\u00e7in daha \u00f6nce payla\u015ft\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-degistirirken-seo-kaybetmemek\/\">alan ad\u0131 de\u011fi\u015ftirirken SEO kaybetmemek \u00fczerine detayl\u0131 rehber<\/a>, bu yaz\u0131yla birlikte okunursa eksik par\u00e7alar \u00e7ok daha net tamamlanacakt\u0131r.<\/p>\n<h2><span id=\"Gecis_Oncesi_Planlama_Envanter_ve_Yol_Haritasi\">Ge\u00e7i\u015f \u00d6ncesi Planlama: Envanter ve Yol Haritas\u0131<\/span><\/h2>\n<p>Sa\u011fl\u0131kl\u0131 bir domain ge\u00e7i\u015finin %70\u2019i, canl\u0131ya almadan \u00f6nce yapt\u0131\u011f\u0131n\u0131z haz\u0131rl\u0131kt\u0131r. Biz DCHost taraf\u0131nda, herkesin ayn\u0131 dok\u00fcman \u00fczerinde konu\u015fabildi\u011fi bir <strong>ge\u00e7i\u015f \u00e7al\u0131\u015fma dosyas\u0131<\/strong> olu\u015fturmay\u0131 standart hale getiriyoruz.<\/p>\n<h3><span id=\"1_Tum_URLlerin_Envanterini_Cikarin\">1. T\u00fcm URL\u2019lerin Envanterini \u00c7\u0131kar\u0131n<\/span><\/h3>\n<p>\u00d6nce mevcut sitenizin bir foto\u011fraf\u0131n\u0131 \u00e7ekmelisiniz:<\/p>\n<ul>\n<li>Site haritas\u0131ndan (sitemap.xml) t\u00fcm URL\u2019leri \u00e7\u0131kar\u0131n.<\/li>\n<li>Log\u2019lardan ve analitik ara\u00e7lar\u0131ndan en \u00e7ok trafik alan sayfalar\u0131 listeleyin.<\/li>\n<li>\u00d6zel kampanya, landing page, PDF, dosya indirme URL\u2019lerini ayr\u0131ca i\u015faretleyin.<\/li>\n<\/ul>\n<p>Hedefiniz, <strong>eski URL \u2192 yeni URL<\/strong> e\u015fle\u015fmesini netle\u015ftirmektir. \u0130deal senaryoda URL yap\u0131n\u0131z \u00e7ok de\u011fi\u015fmez; yani <code>\/hakkimizda<\/code> sayfan\u0131z yeni domain\u2019de de <code>\/hakkimizda<\/code> olarak kal\u0131r. URL yap\u0131s\u0131 k\u00f6kten de\u011fi\u015fiyorsa, bu haritan\u0131n \u00f6nemi 2 kat artar.<\/p>\n<h3><span id=\"2_Teknik_SEO_Analitik_ve_Entegrasyon_Envanteri\">2. Teknik SEO, Analitik ve Entegrasyon Envanteri<\/span><\/h3>\n<p>Alan ad\u0131 ge\u00e7i\u015fi sadece web sayfalar\u0131ndan ibaret de\u011fildir. \u015eu \u00f6\u011feleri tek tek not al\u0131n:<\/p>\n<ul>\n<li>Google Analytics \/ Matomo \/ di\u011fer analitik kodlar\u0131<\/li>\n<li>Google Search Console, Bing Webmaster, Yandex\/Webmaster vs. hesaplar\u0131<\/li>\n<li>Tag Manager container\u2019lar\u0131<\/li>\n<li>Harici servis entegrasyonlar\u0131: \u00f6deme sa\u011flay\u0131c\u0131lar\u0131, CRM, e\u2011posta pazarlama ara\u00e7lar\u0131<\/li>\n<li>API callback URL\u2019leri, webhook adresleri<\/li>\n<\/ul>\n<p>Bir\u00e7ok projede, webhook veya \u00f6deme d\u00f6n\u00fc\u015f URL\u2019lerinin g\u00fcncellenmemesi y\u00fcz\u00fcnden kritik s\u00fcre\u00e7lerin sessizce bozuldu\u011funu g\u00f6rd\u00fck. Bu listeyi \u00e7\u0131kar\u0131p ilgili sistem sahipleriyle birlikte g\u00fcncelleme plan\u0131 haz\u0131rlay\u0131n.<\/p>\n<h3><span id=\"3_DNS_ve_Hosting_Tarafindaki_Hazirlik\">3. DNS ve Hosting Taraf\u0131ndaki Haz\u0131rl\u0131k<\/span><\/h3>\n<p>Alan ad\u0131n\u0131z\u0131n nerede kay\u0131tl\u0131 oldu\u011fu, DNS\u2019leri nereden y\u00f6netti\u011finiz ve sitenizin hangi sunucuda bar\u0131nd\u0131\u011f\u0131 net olmal\u0131. DCHost \u00fczerinde bar\u0131nan projelerde genelde \u015fu senaryolar\u0131 g\u00f6r\u00fcyoruz:<\/p>\n<ul>\n<li>Domain ba\u015fka bir registrarda, DNS DCHost\u2019ta, web ve e\u2011posta da DCHost altyap\u0131s\u0131nda<\/li>\n<li>Domain ve DNS DCHost\u2019ta, web ba\u015fka sunucuda, e\u2011posta ise harici bir serviste<\/li>\n<\/ul>\n<p>Hangi kayd\u0131n nereden y\u00f6netildi\u011fini netle\u015ftirmeden ge\u00e7i\u015f plan\u0131 yapmay\u0131n. DNS taraf\u0131nda <strong>TTL<\/strong> de\u011ferlerini planl\u0131 olarak d\u00fc\u015f\u00fcrmek, s\u0131f\u0131ra yak\u0131n kesinti i\u00e7in kritik. Bu konuyu ayr\u0131nt\u0131l\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/\">Zero\u2011downtime ta\u015f\u0131ma i\u00e7in TTL stratejileri rehberi<\/a>, DNS yay\u0131l\u0131m s\u00fcrecini pratik \u00f6rneklerle a\u00e7\u0131kl\u0131yor.<\/p>\n<h2><span id=\"SEOyu_Korumak_Icin_Eski_Domainden_Yeni_Domaine_Gecis_Adimlari\">SEO\u2019yu Korumak \u0130\u00e7in Eski Domain\u2019den Yeni Domain\u2019e Ge\u00e7i\u015f Ad\u0131mlar\u0131<\/span><\/h2>\n<p>Google taraf\u0131nda mesaj \u00e7ok nettir: Alan ad\u0131n\u0131z\u0131 de\u011fi\u015ftirirken, m\u00fcmk\u00fcn olan her yerde <strong>301 kal\u0131c\u0131 y\u00f6nlendirme<\/strong> kullan\u0131n ve yeni domain\u2019i bir devam filmi gibi konumland\u0131r\u0131n, bamba\u015fka bir site gibi de\u011fil.<\/p>\n<h3><span id=\"1_301_Yonlendirme_Stratejisi\">1. 301 Y\u00f6nlendirme Stratejisi<\/span><\/h3>\n<p>\u0130deal strateji, <strong>1:1 URL ta\u015f\u0131mas\u0131d\u0131r<\/strong>:<\/p>\n<ul>\n<li><code>https:\/\/eski\u2011domain.com\/hakkimizda<\/code> \u2192 <code>https:\/\/yeni\u2011domain.com\/hakkimizda<\/code><\/li>\n<li><code>https:\/\/eski\u2011domain.com\/urun\/kirmizi\u2011elma<\/code> \u2192 <code>https:\/\/yeni\u2011domain.com\/urun\/kirmizi\u2011elma<\/code><\/li>\n<\/ul>\n<p>Bu m\u00fcmk\u00fcn de\u011filse, en az\u0131ndan ayn\u0131 i\u00e7erik tipine y\u00f6nlendiren mant\u0131kl\u0131 gruplar olu\u015fturun (\u00fcr\u00fcn \u2192 \u00fcr\u00fcn kategorisi, blog yaz\u0131s\u0131 \u2192 ilgili blog kategori sayfas\u0131 gibi). Dikkat etmeniz gerekenler:<\/p>\n<ul>\n<li><strong>301 d\u0131\u015f\u0131nda y\u00f6nlendirme kullanmay\u0131n:<\/strong> 302, 307 veya JavaScript ile y\u00f6nlendirme SEO de\u011fer transferini zay\u0131flat\u0131r.<\/li>\n<li><strong>Y\u00f6nlendirme zincirlerinden ka\u00e7\u0131n\u0131n:<\/strong> Eski \u2192 Orta domain \u2192 Yeni gibi 2+ ad\u0131ml\u0131 zincirler yerine do\u011frudan Eski \u2192 Yeni yap\u0131n.<\/li>\n<li><strong>WWW ve non\u2011WWW, HTTP ve HTTPS varyantlar\u0131n\u0131 kapsay\u0131n:<\/strong> T\u00fcm varyantlar\u0131n tek bir kanonik URL\u2019ye 301 ile topland\u0131\u011f\u0131ndan emin olun.<\/li>\n<\/ul>\n<p>Y\u00f6nlendirmeleri sunucu katman\u0131nda (Nginx\/Apache\/LiteSpeed) yapmak her zaman daha sa\u011fl\u0131kl\u0131d\u0131r. Hosting taraf\u0131ndaki y\u00f6nlendirme kurallar\u0131n\u0131 nas\u0131l kurgulayaca\u011f\u0131n\u0131z\u0131 merak ediyorsan\u0131z, HTTP\u2192HTTPS \u00f6zelindeki <a href=\"https:\/\/www.dchost.com\/blog\/httpden-httpse-gecis-rehberi-301-yonlendirme-hsts-ve-seoyu-korumak\/\">HTTP\u2019den HTTPS\u2019e ge\u00e7i\u015f ve 301 y\u00f6nlendirme rehberi<\/a>nde anlatt\u0131\u011f\u0131m\u0131z mant\u0131k, domain ge\u00e7i\u015fi i\u00e7in de aynen ge\u00e7erlidir.<\/p>\n<h3><span id=\"2_Canonical_Sitemap_ve_robotstxt_Guncellemeleri\">2. Canonical, Sitemap ve robots.txt G\u00fcncellemeleri<\/span><\/h3>\n<p>Alan ad\u0131 ge\u00e7i\u015finde arama motorlar\u0131na net sinyaller vermek i\u00e7in \u015fu \u00fc\u00e7l\u00fc hayati \u00f6nem ta\u015f\u0131r:<\/p>\n<ul>\n<li><strong>Canonical etiketler:<\/strong> T\u00fcm sayfalarda <code>&lt;link rel=\"canonical\"&gt;<\/code> de\u011feriniz yeni domain\u2019i g\u00f6stermeli.<\/li>\n<li><strong>Sitemap.xml:<\/strong> Site haritan\u0131z sadece yeni domain URL\u2019lerini i\u00e7ermeli ve Search Console\u2019a yeniden g\u00f6nderilmeli.<\/li>\n<li><strong>robots.txt:<\/strong> robots.txt i\u00e7indeki sitemap sat\u0131r\u0131 da yeni domain\u2019e g\u00fcncellenmeli.<\/li>\n<\/ul>\n<p>Site haritalar\u0131 ve robots.txt dosyalar\u0131n\u0131n SEO taraf\u0131nda do\u011fru kullan\u0131m\u0131n\u0131 ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/robots-txt-ve-sitemap-xml-dogru-kurulumu-adim-adim-seo-ve-hosting-rehberi\/\">robots.txt ve sitemap.xml kurulum rehberi<\/a> de burada i\u015finize yarayacakt\u0131r.<\/p>\n<h3><span id=\"3_Google_Search_Console_ve_Diger_Araclar\">3. Google Search Console ve Di\u011fer Ara\u00e7lar<\/span><\/h3>\n<p>Google, alan ad\u0131 de\u011fi\u015fimlerinde Search Console \u00fczerinden <strong>Adres De\u011fi\u015fikli\u011fi Arac\u0131<\/strong> kullanman\u0131z\u0131 tavsiye ediyor. Yapman\u0131z gerekenler:<\/p>\n<ol>\n<li>Eski ve yeni domain\u2019i Search Console\u2019da do\u011frulay\u0131n (m\u00fcmk\u00fcnse domain property olarak).<\/li>\n<li>Eski domain property\u2019si i\u00e7inden \u201cAdres de\u011fi\u015fikli\u011fi\u201d ad\u0131mlar\u0131n\u0131 izleyin.<\/li>\n<li>Google\u2019a, eski domain\u2019inizin kal\u0131c\u0131 olarak yeni domain\u2019e ta\u015f\u0131nd\u0131\u011f\u0131n\u0131 bildirin.<\/li>\n<\/ol>\n<p>Ayr\u0131ca:<\/p>\n<ul>\n<li>Analytics, reklam platformlar\u0131 ve di\u011fer izleme ara\u00e7lar\u0131n\u0131zda <strong>domain ad\u0131<\/strong> ve <strong>hedef URL\u2019leri<\/strong> g\u00fcncelleyin.<\/li>\n<li>\u00d6nemli backlink kaynaklar\u0131n\u0131zla (kataloglar, partner siteler) ileti\u015fime ge\u00e7ip <strong>do\u011frudan linki<\/strong> yeni domain\u2019e \u00e7evirtmeye \u00e7al\u0131\u015f\u0131n.<\/li>\n<\/ul>\n<h2><span id=\"DNS_SSL_ve_Barindirma_Tarafi_Sifira_Yakin_Kesinti_Mumkun_mu\">DNS, SSL ve Bar\u0131nd\u0131rma Taraf\u0131: S\u0131f\u0131ra Yak\u0131n Kesinti M\u00fcmk\u00fcn m\u00fc?<\/span><\/h2>\n<p>Alan ad\u0131 ta\u015f\u0131ma operasyonlar\u0131nda \u00e7o\u011fu zaman as\u0131l stres, &#8220;Ge\u00e7i\u015f an\u0131nda site ve e\u2011postalar \u00e7al\u0131\u015facak m\u0131?&#8221; sorusundan gelir. DNS ve hosting taraf\u0131n\u0131 do\u011fru kurgularsan\u0131z, bu kayg\u0131y\u0131 b\u00fcy\u00fck \u00f6l\u00e7\u00fcde azaltabilirsiniz.<\/p>\n<h3><span id=\"1_DNS_TTL_ve_Yayilim_Yonetimi\">1. DNS TTL ve Yay\u0131l\u0131m Y\u00f6netimi<\/span><\/h3>\n<p>DNS kay\u0131tlar\u0131n\u0131z\u0131n TTL (Time to Live) de\u011feri, de\u011fi\u015fikli\u011fin internet genelinde ne kadar s\u00fcrede yay\u0131laca\u011f\u0131n\u0131 belirler. \u00d6nerdi\u011fimiz yakla\u015f\u0131m:<\/p>\n<ol>\n<li>Ge\u00e7i\u015ften 24\u201148 saat \u00f6nce, A\/AAAA, MX ve kritik kay\u0131tlar\u0131n TTL de\u011ferlerini 300 saniye (veya daha d\u00fc\u015f\u00fck) seviyesine \u00e7ekin.<\/li>\n<li>Yeni domain i\u00e7in gerekli A\/AAAA, CNAME, MX, TXT vb. kay\u0131tlar\u0131 <strong>\u00f6nceden<\/strong> haz\u0131rlay\u0131n (m\u00fcmk\u00fcnse staging ortamda test edin).<\/li>\n<li>Ge\u00e7i\u015f an\u0131nda sadece hedef IP veya host de\u011ferlerini de\u011fi\u015ftirin; kay\u0131t isimlerini de\u011fil.<\/li>\n<\/ol>\n<p>DNS yay\u0131l\u0131m\u0131n\u0131n neden bazen 24 saati buldu\u011funu ve pratikte nas\u0131l h\u0131zland\u0131rabilece\u011finizi detayl\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/dns-yayilim-suresi-nedir-neden-24-saat-surer-ve-nasil-hizlandirilir\/\">DNS yay\u0131l\u0131m s\u00fcresi rehberi<\/a>, ge\u00e7i\u015fi zamanlarken size ger\u00e7ek\u00e7i bir \u00e7er\u00e7eve sunacakt\u0131r.<\/p>\n<h3><span id=\"2_SSL_HTTPS_ve_HSTS_Ayarlari\">2. SSL \/ HTTPS ve HSTS Ayarlar\u0131<\/span><\/h3>\n<p>Yeni domain\u2019iniz i\u00e7in mutlaka <strong>ge\u00e7i\u015ften \u00f6nce<\/strong> <a href=\"https:\/\/www.dchost.com\/tr\/ssl\">SSL sertifikas\u0131<\/a> haz\u0131rlay\u0131n. Dikkat etmeniz gereken noktalar:<\/p>\n<ul>\n<li>Eski ve yeni domain ayn\u0131 sunucuda ise, sanal host yap\u0131land\u0131rman\u0131zda her iki domain i\u00e7in de HTTPS vhost tan\u0131mlay\u0131n.<\/li>\n<li>Let\u2019s Encrypt kullan\u0131yorsan\u0131z ACME istemcinizin (\u00f6rne\u011fin cPanel AutoSSL veya acme.sh) yeni domain\u2019i de kapsad\u0131\u011f\u0131ndan emin olun.<\/li>\n<li>HSTS (HTTP Strict Transport Security) kullan\u0131yorsan\u0131z, eski domain\u2019de \u00e7ok uzun max-age de\u011ferleri tan\u0131mlamadan \u00f6nce ge\u00e7i\u015f plan\u0131n\u0131z\u0131 netle\u015ftirin. Aksi halde taray\u0131c\u0131lar eski domain\u2019i zorunlu olarak HTTPS \u00fczerinden a\u00e7maya \u00e7al\u0131\u015fmaya devam eder.<\/li>\n<\/ul>\n<p>SSL taraf\u0131ndaki uyumsuzluklar, &#8220;Not Secure&#8221; uyar\u0131lar\u0131 ve kar\u0131\u015f\u0131k i\u00e7erik (mixed content) problemleri ge\u00e7i\u015f sonras\u0131nda s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalar aras\u0131nda. Bunlar\u0131 bar\u0131nd\u0131rma taraf\u0131nda nas\u0131l \u00e7\u00f6zece\u011finizi anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/ssl-sertifika-hatalari-rehberi-mixed-content-not-secure-ve-tarayici-uyarilarini-hosting-tarafinda-cozmek\/\">SSL sertifika hatalar\u0131 rehberi<\/a>ni de mutlaka g\u00f6zden ge\u00e7irin.<\/p>\n<h3><span id=\"3_Sunucu_Mimarisi_Staging_ve_BlueGreen_Yaklasimi\">3. Sunucu Mimarisi: Staging ve Blue\u2011Green Yakla\u015f\u0131m\u0131<\/span><\/h3>\n<p>\u0130mk\u00e2n\u0131n\u0131z varsa, yeni domain\u2019i \u00f6nce staging (\u00f6nizleme) ortam\u0131nda aya\u011fa kald\u0131r\u0131p t\u00fcm y\u00f6nlendirme ve SSL senaryolar\u0131n\u0131 burada test edin. DCHost \u00fczerinde s\u0131k kulland\u0131\u011f\u0131m\u0131z yakla\u015f\u0131m:<\/p>\n<ul>\n<li>Yeni domain\u2019i ge\u00e7ici bir alt alan ad\u0131yla (\u00f6rne\u011fin <code>yeni\u2011marka.staging.sirket.com<\/code>) haz\u0131rlamak<\/li>\n<li>T\u00fcm i\u00e7erik, tasar\u0131m ve SEO ayarlar\u0131n\u0131 staging \u00fczerinde tamamlamak<\/li>\n<li>Kesinti an\u0131nda sadece DNS kay\u0131tlar\u0131n\u0131 yeni domain\u2019e \u00e7evirerek canl\u0131ya almak<\/li>\n<\/ul>\n<p>Daha geli\u015fmi\u015f senaryolarda, <a href=\"https:\/\/www.dchost.com\/blog\/blue-green-deployment-ile-woocommerce-ve-laravel-uygulamalarini-sifir-kesintiyle-guncellemek\/\">blue\u2011green deployment ile s\u0131f\u0131r kesinti g\u00fcncelleme<\/a> yakla\u015f\u0131m\u0131n\u0131 da domain ge\u00e7i\u015fiyle birle\u015ftiriyoruz. B\u00f6ylece hem uygulama versiyon de\u011fi\u015fimi hem de domain de\u011fi\u015fimi kontroll\u00fc bir \u015fekilde yap\u0131labiliyor.<\/p>\n<h2><span id=\"EPostayi_Korumak_MX_SPF_DKIM_ve_Kullanici_Tarafi\">E\u2011Postay\u0131 Korumak: MX, SPF, DKIM ve Kullan\u0131c\u0131 Taraf\u0131<\/span><\/h2>\n<p>Marka de\u011fi\u015fimlerinde teknik ekip genellikle web sitesine odaklan\u0131r, e\u2011posta ise \u201cnas\u0131lsa \u00e7al\u0131\u015f\u0131r\u201d diye d\u00fc\u015f\u00fcn\u00fcl\u00fcr. Teoride MX kay\u0131tlar\u0131n\u0131 do\u011fru ta\u015f\u0131rsan\u0131z evet, \u00e7al\u0131\u015f\u0131r; pratikte ise Outlook\/Thunderbird ayarlar\u0131, mobil cihazlar, SPF\/DKIM\/DMARC gibi ba\u015fl\u0131klar y\u00fcz\u00fcnden i\u015fler kar\u0131\u015fabilir.<\/p>\n<h3><span id=\"1_MX_Kayitlari_ve_Gecis_Stratejisi\">1. MX Kay\u0131tlar\u0131 ve Ge\u00e7i\u015f Stratejisi<\/span><\/h3>\n<p>\u015eu sorulara net cevab\u0131n\u0131z olmal\u0131:<\/p>\n<ul>\n<li>E\u2011posta sunucunuz nerede? DCHost \u00fczerinde mi, ba\u015fka bir sa\u011flay\u0131c\u0131da m\u0131?<\/li>\n<li>Alan ad\u0131 de\u011fi\u015fti\u011finde e\u2011posta sunucusu da de\u011fi\u015fecek mi, yoksa sadece alan ad\u0131 m\u0131?<\/li>\n<\/ul>\n<p>Temel senaryolar:<\/p>\n<ul>\n<li><strong>Sadece alan ad\u0131 de\u011fi\u015fiyor, e\u2011posta sunucusu ayn\u0131 kal\u0131yor:<\/strong> MX kay\u0131tlar\u0131n\u0131 yeni domain i\u00e7in de ayn\u0131 mail sunucusuna (\u00f6rne\u011fin <code>mail.yeni\u2011domain.com<\/code> \u2192 ayn\u0131 IP) y\u00f6nlendirin.<\/li>\n<li><strong>Hem alan ad\u0131 hem e\u2011posta altyap\u0131s\u0131 de\u011fi\u015fiyor:<\/strong> \u00d6nce yeni e\u2011posta altyap\u0131s\u0131n\u0131 haz\u0131r edin, test edin; ard\u0131ndan MX switch i\u015flemini planlay\u0131n.<\/li>\n<\/ul>\n<p>MX de\u011fi\u015fimini yapmadan \u00f6nce yeni alan ad\u0131 i\u00e7in mail sunucusunu, SSL sertifikas\u0131n\u0131, reverse DNS\u2019ini ve test mailbox\u2019lar\u0131n\u0131 mutlaka haz\u0131rlay\u0131n. E\u2011posta altyap\u0131s\u0131n\u0131 ta\u015f\u0131rken kesinti ya\u015famamak i\u00e7in ad\u0131m ad\u0131m anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/e-posta-altyapisini-tasirken-kesinti-yasamamak\/\">e\u2011posta altyap\u0131s\u0131n\u0131 ta\u015f\u0131rken kesinti ya\u015famamak rehberi<\/a> burada \u00e7ok i\u015finize yarayacakt\u0131r.<\/p>\n<h3><span id=\"2_SPF_DKIM_ve_DMARC_Guncellemeleri\">2. SPF, DKIM ve DMARC G\u00fcncellemeleri<\/span><\/h3>\n<p>Yeni domain ile e\u2011posta g\u00f6ndermeye ba\u015flarken teslim edilebilirli\u011fi (deliverability) korumak i\u00e7in kimlik do\u011frulama kay\u0131tlar\u0131n\u0131 eksiksiz kurman\u0131z \u015fart:<\/p>\n<ul>\n<li><strong>SPF:<\/strong> Yeni domain\u2019in DNS\u2019ine, e\u2011postalar\u0131 hangi sunucular\u0131n g\u00f6nderebilece\u011fini belirten SPF kayd\u0131 ekleyin.<\/li>\n<li><strong>DKIM:<\/strong> Mail sunucusunda yeni domain i\u00e7in DKIM anahtar\u0131 \u00fcretin ve ilgili TXT kayd\u0131n\u0131 DNS\u2019e ekleyin.<\/li>\n<li><strong>DMARC:<\/strong> Raporlama ve politika y\u00f6netimi i\u00e7in temel bir DMARC kayd\u0131 tan\u0131mlay\u0131n (<code>p=none<\/code> ile ba\u015flay\u0131p raporlar\u0131 incelemek ak\u0131ll\u0131ca olur).<\/li>\n<\/ul>\n<p>Bu \u00fc\u00e7l\u00fcy\u00fc s\u0131f\u0131rdan nas\u0131l kuraca\u011f\u0131n\u0131z\u0131 ve hosting\/<a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> ortam\u0131nda hangi ayarlara dikkat etmeniz gerekti\u011fini detayl\u0131 bir \u015fekilde <a href=\"https:\/\/www.dchost.com\/blog\/spf-dkim-ve-dmarc-nedir-ozel-alan-adi-ile-e-posta-dogrulamasini-cpanel-ve-vpste-sifirdan-kurmak\/\">SPF, DKIM ve DMARC kurulum rehberi<\/a>nde anlatt\u0131k. Alan ad\u0131 ge\u00e7i\u015finde o yaz\u0131daki ad\u0131mlar\u0131 yeni domain i\u00e7in tekrar uygulaman\u0131z gerekir.<\/p>\n<h3><span id=\"3_Geciste_Cift_Teslim_Forwarding_Alias_Senaryolari\">3. Ge\u00e7i\u015fte \u00c7ift Teslim (Forwarding \/ Alias) Senaryolar\u0131<\/span><\/h3>\n<p>Marka de\u011fi\u015fimiyle birlikte e\u2011posta adresleriniz genelde \u015fu \u015fekilde evrilir:<\/p>\n<ul>\n<li><code>ad.soyad@eski\u2011domain.com<\/code> \u2192 <code>ad.soyad@yeni\u2011domain.com<\/code><\/li>\n<\/ul>\n<p>M\u00fc\u015fterilerinizin al\u0131\u015fkanl\u0131\u011f\u0131n\u0131 bir anda de\u011fi\u015ftirmek zor olaca\u011f\u0131 i\u00e7in <strong>ge\u00e7i\u015f d\u00f6neminde iki domain\u2019i paralel kullanmak<\/strong> pratik bir \u00e7\u00f6z\u00fcmd\u00fcr. \u00d6nerdi\u011fimiz yakla\u015f\u0131m:<\/p>\n<ul>\n<li>Eski domain\u2019deki t\u00fcm adresleri, yeni domain\u2019deki kar\u015f\u0131l\u0131klar\u0131na forward\/alias yap\u0131n.<\/li>\n<li>Kullan\u0131c\u0131lar\u0131n\u0131z\u0131n g\u00f6nderim adresini (From) yeni domain\u2019e ta\u015f\u0131y\u0131n; ancak eski domain adreslerine gelen maillerin de bir s\u00fcre d\u00fc\u015fmeye devam etmesini sa\u011flay\u0131n.<\/li>\n<li>E\u2011posta imzalar\u0131n\u0131zda ve otomatik yan\u0131tlar\u0131n\u0131zda \u201cYeni e\u2011posta adresimiz \u2026\u201d bilgisini belirtin.<\/li>\n<\/ul>\n<p>Bu s\u00fcreci planlarken &#8220;Alan ad\u0131 ta\u015f\u0131rken e\u2011posta kesintisini \u00f6nlemek&#8221; ba\u015fl\u0131kl\u0131 <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-tasirken-e%e2%80%91posta-kesintisini-onlemek\/\">ayr\u0131nt\u0131l\u0131 rehberimiz<\/a>i mutlaka okuyun; DNS ve MX taraf\u0131ndaki ge\u00e7i\u015f s\u0131ras\u0131n\u0131 somut \u00f6rneklerle ele ald\u0131k.<\/p>\n<h3><span id=\"4_Kullanici_Iletisimi_ve_Istemci_Ayarlari\">4. Kullan\u0131c\u0131 \u0130leti\u015fimi ve \u0130stemci Ayarlar\u0131<\/span><\/h3>\n<p>Teknik taraf kusursuz bile olsa, \u00e7al\u0131\u015fanlar\u0131n e\u2011posta istemcileri (Outlook, Apple Mail, mobil uygulamalar) do\u011fru g\u00fcncellenmezse yine &#8220;e\u2011posta \u00e7al\u0131\u015fm\u0131yor&#8221; \u015fikayetleri al\u0131rs\u0131n\u0131z. \u0130yi bir planlama i\u00e7in:<\/p>\n<ul>\n<li>T\u00fcm istemcilerde <strong>giden sunucu kimli\u011fi (SMTP TLS sertifikas\u0131)<\/strong> yeni domain\u2019le uyumlu mu, kontrol edin.<\/li>\n<li>POP3\/IMAP ba\u011flant\u0131 host adlar\u0131 (\u00f6rne\u011fin <code>mail.yeni\u2011domain.com<\/code>) ve portlar\u0131 i\u00e7in k\u0131sa bir dok\u00fcmantasyon haz\u0131rlay\u0131n.<\/li>\n<li>Kullan\u0131c\u0131lara k\u00fc\u00e7\u00fck bir kontrol listesi g\u00f6nderin: test maili atma, spam klas\u00f6r\u00fcn\u00fc kontrol etme, mobil cihazlar\u0131 g\u00fcncelleme vb.<\/li>\n<\/ul>\n<h2><span id=\"Guvenlik_ve_Alan_Adi_Korumasi_Eski_Domaini_Asla_Hemen_Birakmayin\">G\u00fcvenlik ve Alan Ad\u0131 Korumas\u0131: Eski Domain\u2019i Asla Hemen B\u0131rakmay\u0131n<\/span><\/h2>\n<p>Marka de\u011fi\u015fiminde en s\u0131k yap\u0131lan hatalardan biri, &#8220;Yeni domain aktif oldu, eskisiyle i\u015fimiz bitti&#8221; diye d\u00fc\u015f\u00fcnmektir. Bu, hem SEO hem g\u00fcvenlik a\u00e7\u0131s\u0131ndan risklidir.<\/p>\n<h3><span id=\"1_Eski_Domaini_En_Az_1224_Ay_Aktif_Tutun\">1. Eski Domain\u2019i En Az 12\u201124 Ay Aktif Tutun<\/span><\/h3>\n<p>Eski domain\u2019inizi en az 1\u20112 y\u0131l daha yenileyip 301 y\u00f6nlendirmeleri \u00e7al\u0131\u015f\u0131r halde tutman\u0131z\u0131 \u00f6neriyoruz. Neden?<\/p>\n<ul>\n<li>Y\u0131llar i\u00e7inde al\u0131nm\u0131\u015f backlink\u2019lerin bir k\u0131sm\u0131 asla g\u00fcncellenmeyecek.<\/li>\n<li>Kullan\u0131c\u0131lar yer imlerinde (bookmark) eski domain\u2019i tutmaya devam edecek.<\/li>\n<li>Eski kampanya linkleri, PDF\u2019ler, offline materyaller (katalog, kartvizit vb.) uzun s\u00fcre ya\u015fayacak.<\/li>\n<\/ul>\n<p>Eski domain\u2019in s\u00fcresi dolup d\u00fc\u015ferse ve bir ba\u015fkas\u0131 taraf\u0131ndan al\u0131n\u0131rsa, hem <strong>itibar riski<\/strong> hem de <strong>phishing<\/strong> sald\u0131r\u0131lar\u0131na a\u00e7\u0131k bir kap\u0131 b\u0131rakm\u0131\u015f olursunuz.<\/p>\n<h3><span id=\"2_Registrar_Lock_DNSSEC_ve_Erisim_Guvenligi\">2. Registrar Lock, DNSSEC ve Eri\u015fim G\u00fcvenli\u011fi<\/span><\/h3>\n<p>Hem eski hem yeni alan ad\u0131n\u0131z\u0131 ta\u015f\u0131ma s\u00fcrecinde daha da kritik hale gelen bir konu da alan ad\u0131 g\u00fcvenli\u011fidir. A\u015fa\u011f\u0131daki ad\u0131mlar\u0131 standart hale getirmenizi \u00f6neririz:<\/p>\n<ul>\n<li>Domain panelinizde <strong>transfer kilidi (Registrar Lock)<\/strong> aktif olsun.<\/li>\n<li>M\u00fcmk\u00fcnse <strong>DNSSEC<\/strong> etkinle\u015ftirerek DNS sahtecili\u011fi riskini azalt\u0131n.<\/li>\n<li>Alan ad\u0131 ve DNS panellerinizde <strong>iki fakt\u00f6rl\u00fc kimlik do\u011frulama (2FA)<\/strong> etkin olsun.<\/li>\n<\/ul>\n<p>Bu ba\u015fl\u0131klar\u0131 \u00e7ok daha detayl\u0131 ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-guvenligi-rehberi-registrar-lock-dnssec-whois-gizliligi-ve-2fa\/\">alan ad\u0131 g\u00fcvenli\u011fi rehberi<\/a>, \u00f6zellikle ge\u00e7i\u015f d\u00f6neminde domain\u2019lerinizi hukuken ve teknik olarak korumak i\u00e7in iyi bir kontrol listesi sunuyor.<\/p>\n<h2><span id=\"Gecis_Sonrasi_Izleme_Hata_Tespiti_ve_Geri_Adim_Plani\">Ge\u00e7i\u015f Sonras\u0131 \u0130zleme, Hata Tespiti ve Geri Ad\u0131m Plan\u0131<\/span><\/h2>\n<p>Domain de\u011fi\u015fikli\u011fi, DNS kay\u0131tlar\u0131n\u0131 g\u00fcncelledi\u011finiz ve 301\u2019leri tan\u0131mlad\u0131\u011f\u0131n\u0131z g\u00fcn bitmez; asl\u0131nda as\u0131l i\u015f ondan sonra ba\u015flar. \u0130lk 30 g\u00fcn, sorun yakalamak i\u00e7in en kritik d\u00f6nemdir.<\/p>\n<h3><span id=\"1_SEO_ve_Trafik_Izleme\">1. SEO ve Trafik \u0130zleme<\/span><\/h3>\n<p>Ge\u00e7i\u015ften hemen sonra \u015fu metrikleri yak\u0131ndan izleyin:<\/p>\n<ul>\n<li>Organik trafik (eski vs. yeni domain kar\u015f\u0131la\u015ft\u0131rmas\u0131)<\/li>\n<li>\u00d6nemli anahtar kelimelerdeki s\u0131ralama de\u011fi\u015fimleri<\/li>\n<li>Search Console\u2019da tarama hatalar\u0131 (404, 5xx) ve y\u00f6nlendirme sorunlar\u0131<\/li>\n<\/ul>\n<p>Alan ad\u0131 de\u011fi\u015fikli\u011finde <strong>k\u0131sa s\u00fcreli dalgalanmalar normaldir<\/strong>. \u00d6nemli olan, s\u00fcrekli a\u015fa\u011f\u0131 giden bir trend mi, yoksa birka\u00e7 hafta i\u00e7inde toparlanan bir e\u011fri mi g\u00f6rd\u00fc\u011f\u00fcn\u00fczd\u00fcr. \u00d6zellikle ilk haftalarda Search Console\u2019daki &#8220;Kapsam&#8221; ve &#8220;Sayfa deneyimi&#8221; raporlar\u0131n\u0131 s\u0131k s\u0131k kontrol edin.<\/p>\n<h3><span id=\"2_404_Hatalari_ve_Kirik_Linkler\">2. 404 Hatalar\u0131 ve K\u0131r\u0131k Linkler<\/span><\/h3>\n<p>Log analizi ve 404 takip ara\u00e7lar\u0131yla, eski domain\u2019e gelen ama yeni domain\u2019de kar\u015f\u0131l\u0131\u011f\u0131 olmayan URL\u2019leri tespit edin. Bu URL\u2019ler i\u00e7in:<\/p>\n<ul>\n<li>Yeni domain\u2019de denk gelen bir sayfa varsa, ekstra 301 kural\u0131 ekleyin.<\/li>\n<li>Hi\u00e7bir anlaml\u0131 kar\u015f\u0131l\u0131\u011f\u0131 yoksa, 410 (Gone) yan\u0131t\u0131 vermeyi d\u00fc\u015f\u00fcnebilirsiniz; ama bu karar\u0131 dikkatli verin.<\/li>\n<\/ul>\n<p>Web sunucu loglar\u0131ndan 4xx\/5xx hatalar\u0131n\u0131 okumaya al\u0131\u015fk\u0131n de\u011filseniz, <a href=\"https:\/\/www.dchost.com\/blog\/hosting-sunucu-loglarini-okumayi-ogrenin-apache-ve-nginx-ile-4xx-5xx-hatalarini-teshis-rehberi\/\">Apache ve Nginx loglar\u0131yla 4xx\/5xx hatalar\u0131n\u0131 te\u015fhis rehberi<\/a> size pratik bir ba\u015flang\u0131\u00e7 sa\u011flayacakt\u0131r.<\/p>\n<h3><span id=\"3_EPosta_Teslim_Edilebilirligi_ve_Spam_Sikayetleri\">3. E\u2011Posta Teslim Edilebilirli\u011fi ve Spam \u015eikayetleri<\/span><\/h3>\n<p>Yeni domain ile e\u2011posta g\u00f6ndermeye ba\u015flad\u0131ktan sonra:<\/p>\n<ul>\n<li>\u00d6nemli al\u0131c\u0131larda (Gmail, Outlook, kurumsal m\u00fc\u015fteriler) maillerin spam\u2019a d\u00fc\u015f\u00fcp d\u00fc\u015fmedi\u011fini d\u00fczenli test edin.<\/li>\n<li>Olas\u0131 \u015fikayetleri (\u00f6rne\u011fin &#8220;mail gelmiyor&#8221;, &#8220;ge\u00e7 geliyor&#8221;) tek tek log\u2019lardan inceleyin.<\/li>\n<li>Gerekirse <strong>IP \u0131s\u0131tma<\/strong> stratejileriyle yava\u015f yava\u015f hacmi artt\u0131r\u0131n.<\/li>\n<\/ul>\n<p>E\u2011posta itibar\u0131n\u0131z\u0131 bozmadan teslim edilebilirli\u011fi nas\u0131l y\u00f6netece\u011finizi ayr\u0131nt\u0131lar\u0131yla anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/dedicated-ip-isitma-ve-e-posta-itibari-yonetimi\/\">IP \u0131s\u0131tma ve e\u2011posta itibar\u0131 y\u00f6netimi rehberi<\/a>nde; yeni domain i\u00e7in de bire bir uygulayabilece\u011finiz pek \u00e7ok pratik ipucu bulacaks\u0131n\u0131z.<\/p>\n<h3><span id=\"4_Geri_Adim_Rollback_Plani\">4. Geri Ad\u0131m (Rollback) Plan\u0131<\/span><\/h3>\n<p>Her projede olmas\u0131n\u0131 \u00f6nerdi\u011fimiz ama \u00e7o\u011fu zaman atlanan bir ba\u015fl\u0131k da geri ad\u0131m plan\u0131d\u0131r. Kaba bir kontrol listesi:<\/p>\n<ul>\n<li>DNS\u2019te eski domain\u2019e h\u0131zl\u0131 d\u00f6n\u00fc\u015f i\u00e7in gerekli kay\u0131t \u015fablonlar\u0131n\u0131 saklay\u0131n.<\/li>\n<li>Eski domain\u2019in i\u00e7erik ve yap\u0131land\u0131rma yedeklerini elinizin alt\u0131nda tutun.<\/li>\n<li>\u00c7ok ciddi bir sorun veya dramatik bir trafik kayb\u0131 durumunda, belirli bir s\u00fcre i\u00e7in eski domain\u2019i tekrar aktif etme senaryosunu \u00f6nceden konu\u015fun.<\/li>\n<\/ul>\n<p>Ger\u00e7ek hayatta, iyi haz\u0131rlanm\u0131\u015f projelerde tam rollback ihtiyac\u0131 \u00e7ok seyrek olur. Ama b\u00f6yle bir plan\u0131n varl\u0131\u011f\u0131, ekibin daha rahat hareket etmesini sa\u011flar.<\/p>\n<h2><span id=\"Ozet_ve_DCHost_ile_Sonraki_Adimlar\">\u00d6zet ve DCHost ile Sonraki Ad\u0131mlar<\/span><\/h2>\n<p>Marka de\u011fi\u015fiminde alan ad\u0131 ta\u015f\u0131ma, sadece \u201cdomain\u2019i yeniledik\u201d deyip ge\u00e7ilecek kadar basit bir i\u015flem de\u011fil; i\u015fin i\u00e7inde SEO, DNS, SSL, e\u2011posta, g\u00fcvenlik ve kullan\u0131c\u0131 al\u0131\u015fkanl\u0131klar\u0131 i\u00e7 i\u00e7e ge\u00e7mi\u015f durumda. Sa\u011flam bir envanter \u00e7al\u0131\u015fmas\u0131, do\u011fru kurgulanm\u0131\u015f 301 y\u00f6nlendirmeleri, Search Console bildirimleri, planl\u0131 DNS\/TTL stratejisi ve eksiksiz SPF\/DKIM\/DMARC ayarlar\u0131yla bu s\u00fcreci b\u00fcy\u00fck oranda kontroll\u00fc hale getirebilirsiniz. Eski domain\u2019i aceleyle kapatmak yerine, en az 12\u201124 ay boyunca 301 y\u00f6nlendirmeleriyle canl\u0131 tutmak da hem SEO hem g\u00fcvenlik a\u00e7\u0131s\u0131ndan ciddi bir sigorta g\u00f6revi g\u00f6r\u00fcr.<\/p>\n<p>DCHost ekibi olarak; domain, DNS, hosting, VPS, <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> ve colocation altyap\u0131lar\u0131m\u0131z \u00fczerinde onlarca alan ad\u0131 ve e\u2011posta ge\u00e7i\u015fini sorunsuz \u015fekilde y\u00f6nettik. Benzer bir marka de\u011fi\u015fimi s\u00fcrecine haz\u0131rlan\u0131yorsan\u0131z, kurumsal web siteniz, e\u2011ticaret projeniz veya SaaS uygulaman\u0131z i\u00e7in ihtiyac\u0131n\u0131za uygun bir mimariyi birlikte planlayabilir; staging ortam\u0131ndan DNS cutover an\u0131na, e\u2011posta ge\u00e7i\u015finden log takibine kadar t\u00fcm ad\u0131mlar\u0131 sizinle birlikte kontrol listesi \u00fczerinden ilerletebiliriz. Mevcut sitenizin durumunu ve hedeflerinizi netle\u015ftirerek ba\u015flanm\u0131\u015f iyi bir planlama, yeni markan\u0131zla arama sonu\u00e7lar\u0131nda ve m\u00fc\u015fterilerinizin g\u00f6z\u00fcnde kesintisiz devam etmenin en g\u00fc\u00e7l\u00fc arac\u0131 olacakt\u0131r.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Marka de\u011fi\u015ftirirken alan ad\u0131n\u0131 yenilemek, sadece tasar\u0131m ve logo g\u00fcncellemesi yapmakla k\u0131yaslanamayacak kadar kritik bir ad\u0131md\u0131r. Eski domain\u2019inizde y\u0131llarca biriken otorite, backlink\u2019ler, Google\u2019daki g\u00f6r\u00fcn\u00fcrl\u00fck ve e\u2011posta itibar\u0131n\u0131z\u0131n tamam\u0131 bu hamleden do\u011frudan etkilenir. Yanl\u0131\u015f kurgulanm\u0131\u015f bir ge\u00e7i\u015f, aylarca s\u00fcren organik trafik kayb\u0131na, m\u00fc\u015fterilerin size ula\u015famamas\u0131na ve e\u2011postalar\u0131n\u0131z\u0131n spam klas\u00f6r\u00fcne d\u00fc\u015fmesine neden olabilir. Do\u011fru planlanm\u0131\u015f bir ge\u00e7i\u015f [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3840,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3839","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3839","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=3839"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3839\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/3840"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3839"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3839"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3839"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}