{"id":2146,"date":"2025-11-19T16:14:10","date_gmt":"2025-11-19T13:14:10","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/alan-adi-degistirirken-seo-kaybetmemek\/"},"modified":"2025-11-19T16:14:10","modified_gmt":"2025-11-19T13:14:10","slug":"alan-adi-degistirirken-seo-kaybetmemek","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/alan-adi-degistirirken-seo-kaybetmemek\/","title":{"rendered":"Alan Ad\u0131 De\u011fi\u015ftirirken SEO Kaybetmemek"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Alan_Adi_Degistirirken_Neden_SEO_Kaybi_Yasaniyor\"><span class=\"toc_number toc_depth_1\">1<\/span> Alan Ad\u0131 De\u011fi\u015ftirirken Neden SEO Kayb\u0131 Ya\u015fan\u0131yor?<\/a><\/li><li><a href=\"#Gecis_Oncesi_Planlama_Envanter_Zamanlama_ve_Test_Ortami\"><span class=\"toc_number toc_depth_1\">2<\/span> Ge\u00e7i\u015f \u00d6ncesi Planlama: Envanter, Zamanlama ve Test Ortam\u0131<\/a><ul><li><a href=\"#1_URL_envanteri_cikarma\"><span class=\"toc_number toc_depth_2\">2.1<\/span> 1. URL envanteri \u00e7\u0131karma<\/a><\/li><li><a href=\"#2_Yeni_URL_yapisini_netlestirmek\"><span class=\"toc_number toc_depth_2\">2.2<\/span> 2. Yeni URL yap\u0131s\u0131n\u0131 netle\u015ftirmek<\/a><\/li><li><a href=\"#3_Zamanlama_ve_dusuk_trafik_penceresi\"><span class=\"toc_number toc_depth_2\">2.3<\/span> 3. Zamanlama ve d\u00fc\u015f\u00fck trafik penceresi<\/a><\/li><li><a href=\"#4_Test_ortami_staging_kurmak\"><span class=\"toc_number toc_depth_2\">2.4<\/span> 4. Test ortam\u0131 (staging) kurmak<\/a><\/li><\/ul><\/li><li><a href=\"#301_Yonlendirme_Stratejisi_Eski_URLden_Yenisini_Kaybetmeden_Tasimak\"><span class=\"toc_number toc_depth_1\">3<\/span> 301 Y\u00f6nlendirme Stratejisi: Eski URL\u2019den Yenisini Kaybetmeden Ta\u015f\u0131mak<\/a><ul><li><a href=\"#1_301_vs_302_vs_410_Hangisi_ne_zaman\"><span class=\"toc_number toc_depth_2\">3.1<\/span> 1. 301 vs 302 vs 410: Hangisi ne zaman?<\/a><\/li><li><a href=\"#2_Birebir_URL_eslestirme_mapping_tablosu\"><span class=\"toc_number toc_depth_2\">3.2<\/span> 2. Birebir URL e\u015fle\u015ftirme (mapping) tablosu<\/a><\/li><li><a href=\"#3_www_non-www_ve_http_https_tutarliligi\"><span class=\"toc_number toc_depth_2\">3.3<\/span> 3. www \/ non-www ve http \/ https tutarl\u0131l\u0131\u011f\u0131<\/a><\/li><li><a href=\"#4_Sunucu_tarafinda_301_kurulumu_Apache_Nginx_uygulama\"><span class=\"toc_number toc_depth_2\">3.4<\/span> 4. Sunucu taraf\u0131nda 301 kurulumu: Apache \/ Nginx \/ uygulama<\/a><\/li><li><a href=\"#5_Canonical_ve_hreflang_etkilesimi\"><span class=\"toc_number toc_depth_2\">3.5<\/span> 5. Canonical ve hreflang etkile\u015fimi<\/a><\/li><\/ul><\/li><li><a href=\"#DNS_ve_TTL_Plani_Yayilimi_Yonetmek_ve_Kesintiyi_Sifira_Yaklastirmak\"><span class=\"toc_number toc_depth_1\">4<\/span> DNS ve TTL Plan\u0131: Yay\u0131l\u0131m\u0131 Y\u00f6netmek ve Kesintiyi S\u0131f\u0131ra Yakla\u015ft\u0131rmak<\/a><ul><li><a href=\"#1_Mevcut_DNS_kayitlarini_analiz_etmek\"><span class=\"toc_number toc_depth_2\">4.1<\/span> 1. Mevcut DNS kay\u0131tlar\u0131n\u0131 analiz etmek<\/a><\/li><li><a href=\"#2_TTL_stratejisi_Zero-downtimea_mumkun_oldugunca_yaklasmak\"><span class=\"toc_number toc_depth_2\">4.2<\/span> 2. TTL stratejisi: Zero-downtime\u2019a m\u00fcmk\u00fcn oldu\u011funca yakla\u015fmak<\/a><\/li><li><a href=\"#3_Eski_ve_yeni_alan_adinin_DNS_yapilarini_senkron_tutmak\"><span class=\"toc_number toc_depth_2\">4.3<\/span> 3. Eski ve yeni alan ad\u0131n\u0131n DNS yap\u0131lar\u0131n\u0131 senkron tutmak<\/a><\/li><\/ul><\/li><li><a href=\"#E-posta_Tasima_Plani_MX_SPF_DKIM_DMARC_ve_Testler\"><span class=\"toc_number toc_depth_1\">5<\/span> E-posta Ta\u015f\u0131ma Plan\u0131: MX, SPF, DKIM, DMARC ve Testler<\/a><ul><li><a href=\"#1_MX_kayitlarini_planlamak\"><span class=\"toc_number toc_depth_2\">5.1<\/span> 1. MX kay\u0131tlar\u0131n\u0131 planlamak<\/a><\/li><li><a href=\"#2_SPF_DKIM_DMARC_kayitlarini_guncellemek\"><span class=\"toc_number toc_depth_2\">5.2<\/span> 2. SPF, DKIM, DMARC kay\u0131tlar\u0131n\u0131 g\u00fcncellemek<\/a><\/li><li><a href=\"#3_Gonderici_adi_From_ve_imzalari_guncellemek\"><span class=\"toc_number toc_depth_2\">5.3<\/span> 3. G\u00f6nderici ad\u0131 (From:) ve imzalar\u0131 g\u00fcncellemek<\/a><\/li><li><a href=\"#4_E-posta_gecis_testleri\"><span class=\"toc_number toc_depth_2\">5.4<\/span> 4. E-posta ge\u00e7i\u015f testleri<\/a><\/li><\/ul><\/li><li><a href=\"#SEO_Sinyallerini_Koruma_Analytics_Search_Console_ve_Ic_Baglantilar\"><span class=\"toc_number toc_depth_1\">6<\/span> SEO Sinyallerini Koruma: Analytics, Search Console ve \u0130\u00e7 Ba\u011flant\u0131lar<\/a><ul><li><a href=\"#1_Google_Search_Consoleda_adres_degisikligi\"><span class=\"toc_number toc_depth_2\">6.1<\/span> 1. Google Search Console\u2019da adres de\u011fi\u015fikli\u011fi<\/a><\/li><li><a href=\"#2_Analytics_ve_hedefler\"><span class=\"toc_number toc_depth_2\">6.2<\/span> 2. Analytics ve hedefler<\/a><\/li><li><a href=\"#3_Ic_baglantilari_guncellemek\"><span class=\"toc_number toc_depth_2\">6.3<\/span> 3. \u0130\u00e7 ba\u011flant\u0131lar\u0131 g\u00fcncellemek<\/a><\/li><li><a href=\"#4_Dis_baglantilari_backlink_guncellemek\"><span class=\"toc_number toc_depth_2\">6.4<\/span> 4. D\u0131\u015f ba\u011flant\u0131lar\u0131 (backlink) g\u00fcncellemek<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_ile_Ornek_Tasima_Senaryosu_Adim_Adim_Zaman_Cizelgesi\"><span class=\"toc_number toc_depth_1\">7<\/span> DCHost ile \u00d6rnek Ta\u015f\u0131ma Senaryosu: Ad\u0131m Ad\u0131m Zaman \u00c7izelgesi<\/a><ul><li><a href=\"#T-7_gun_Hazirlik\"><span class=\"toc_number toc_depth_2\">7.1<\/span> T-7 g\u00fcn: Haz\u0131rl\u0131k<\/a><\/li><li><a href=\"#T-48_saat_TTL_dusurme_ve_DNS_hazirligi\"><span class=\"toc_number toc_depth_2\">7.2<\/span> T-48 saat: TTL d\u00fc\u015f\u00fcrme ve DNS haz\u0131rl\u0131\u011f\u0131<\/a><\/li><li><a href=\"#T-0_Gecis_ani\"><span class=\"toc_number toc_depth_2\">7.3<\/span> T-0: Ge\u00e7i\u015f an\u0131<\/a><\/li><li><a href=\"#T24_saat_Izleme\"><span class=\"toc_number toc_depth_2\">7.4<\/span> T+24 saat: \u0130zleme<\/a><\/li><li><a href=\"#T7_gun_Stabilizasyon\"><span class=\"toc_number toc_depth_2\">7.5<\/span> T+7 g\u00fcn: Stabilizasyon<\/a><\/li><\/ul><\/li><li><a href=\"#Alan_Adi_Transferi_ve_Barindirma_Tarafini_Unutmamak\"><span class=\"toc_number toc_depth_1\">8<\/span> Alan Ad\u0131 Transferi ve Bar\u0131nd\u0131rma Taraf\u0131n\u0131 Unutmamak<\/a><\/li><li><a href=\"#Hizli_Kontrol_Listesi_Alan_Adi_Degistirirken_SEO_Kaybetmemek_Icin\"><span class=\"toc_number toc_depth_1\">9<\/span> H\u0131zl\u0131 Kontrol Listesi: Alan Ad\u0131 De\u011fi\u015ftirirken SEO Kaybetmemek \u0130\u00e7in<\/a><\/li><li><a href=\"#Sonuc_Dogru_Planla_Alan_Adi_Degisimi_Korkulacak_Bir_Is_Degil\"><span class=\"toc_number toc_depth_1\">10<\/span> Sonu\u00e7: Do\u011fru Planla Alan Ad\u0131 De\u011fi\u015fimi Korkulacak Bir \u0130\u015f De\u011fil<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Alan_Adi_Degistirirken_Neden_SEO_Kaybi_Yasaniyor\">Alan Ad\u0131 De\u011fi\u015ftirirken Neden SEO Kayb\u0131 Ya\u015fan\u0131yor?<\/span><\/h2>\n<p>Alan ad\u0131n\u0131 de\u011fi\u015ftirmek, marka taraf\u0131nda taze bir ba\u015flang\u0131\u00e7 gibi g\u00f6r\u00fcnse de arama motoru g\u00f6z\u00fcnde bu, adres de\u011fi\u015fikli\u011fi anlam\u0131na gelir. Y\u0131llar i\u00e7inde biriktirdi\u011finiz <strong>backlink otoritesi<\/strong>, kullan\u0131c\u0131 davran\u0131\u015f\u0131 sinyalleri, t\u0131klanma oranlar\u0131 ve sayfa otoritesi eski alan ad\u0131n\u0131za yaz\u0131l\u0131d\u0131r. Ge\u00e7i\u015fi do\u011fru planlamazsan\u0131z, arama motoru bu sinyalleri yeni alan ad\u0131n\u0131za tam olarak aktaramaz ve s\u0131ralama kayb\u0131 ya\u015fars\u0131n\u0131z.<\/p>\n<p>DCHost taraf\u0131nda g\u00f6rd\u00fc\u011f\u00fcm\u00fcz en tipik hata, \u201cZaten ayn\u0131 i\u00e7erik, Google anlar.\u201d yakla\u015f\u0131m\u0131. \u0130\u00e7erik ayn\u0131 olsa bile, URL adresi de\u011fi\u015fti\u011fi anda Google bunu yeni bir sayfa gibi ele al\u0131r. E\u011fer <strong>do\u011fru 301 y\u00f6nlendirmeler<\/strong> kurulmam\u0131\u015fsa, <strong>DNS ge\u00e7i\u015fi<\/strong> bilin\u00e7li yap\u0131lmam\u0131\u015fsa ve <strong>e-posta kay\u0131tlar\u0131<\/strong> (MX, SPF, DKIM, DMARC) g\u00fcncellenmemi\u015fse; hem SEO taraf\u0131nda d\u00fc\u015f\u00fc\u015f, hem de kullan\u0131c\u0131 taraf\u0131nda kesinti ya\u015fan\u0131r.<\/p>\n<p>Bu yaz\u0131da, DCHost\u2019ta s\u0131k\u00e7a uygulad\u0131\u011f\u0131m\u0131z \u201ckontroll\u00fc alan ad\u0131 ge\u00e7i\u015fi\u201d yakla\u015f\u0131m\u0131n\u0131, ad\u0131m ad\u0131m bir <strong>301 y\u00f6nlendirme, DNS ve e-posta ta\u015f\u0131ma plan\u0131<\/strong> olarak anlataca\u011f\u0131m. Amac\u0131m\u0131z \u015fu: Alan ad\u0131n\u0131 de\u011fi\u015ftirirken <strong>m\u00fcmk\u00fcn olan en az SEO kayb\u0131<\/strong> ile, tercihen hi\u00e7 kay\u0131p ya\u015famadan, trafi\u011fi yeni domain\u2019e temiz \u015fekilde ta\u015f\u0131mak.<\/p>\n<h2><span id=\"Gecis_Oncesi_Planlama_Envanter_Zamanlama_ve_Test_Ortami\">Ge\u00e7i\u015f \u00d6ncesi Planlama: Envanter, Zamanlama ve Test Ortam\u0131<\/span><\/h2>\n<p>Ba\u015far\u0131l\u0131 bir alan ad\u0131 ge\u00e7i\u015finin %70\u2019i haz\u0131rl\u0131ktan gelir. Teknik detaylara girmeden \u00f6nce, \u201cNeyi ta\u015f\u0131yoruz?\u201d sorusuna net cevap vermek gerekiyor.<\/p>\n<h3><span id=\"1_URL_envanteri_cikarma\">1. URL envanteri \u00e7\u0131karma<\/span><\/h3>\n<p>\u0130lk ad\u0131m, mevcut alan ad\u0131n\u0131zdaki t\u00fcm \u00f6nemli URL\u2019leri listelemek:<\/p>\n<ul>\n<li>SEO trafi\u011fi alan t\u00fcm sayfalar (kategori, \u00fcr\u00fcn, blog yaz\u0131lar\u0131, landing sayfalar)<\/li>\n<li>\u00d6nemli kampanya \/ reklam URL\u2019leri<\/li>\n<li>Eski ama h\u00e2l\u00e2 backlink alan sayfalar (redirect\u2019li olanlar dahil)<\/li>\n<\/ul>\n<p>Bunu yapmak i\u00e7in:<\/p>\n<ul>\n<li>Google Analytics veya di\u011fer analitik arac\u0131n\u0131zdan en \u00e7ok trafik alan landing sayfalar\u0131n\u0131 d\u0131\u015fa aktar\u0131n.<\/li>\n<li>Google Search Console\u2019dan performans raporunda yer alan URL\u2019leri indirin.<\/li>\n<li>Sunucu loglar\u0131n\u0131 veya eri\u015fim loglar\u0131n\u0131 kullanarak s\u0131k ziyaret edilen URL\u2019leri \u00e7\u0131kar\u0131n.<\/li>\n<\/ul>\n<p>Bu liste, 301 y\u00f6nlendirme haritan\u0131z\u0131n temelini olu\u015fturacak.<\/p>\n<h3><span id=\"2_Yeni_URL_yapisini_netlestirmek\">2. Yeni URL yap\u0131s\u0131n\u0131 netle\u015ftirmek<\/span><\/h3>\n<p>Alan ad\u0131 de\u011fi\u015ftirirken genellikle iki senaryo g\u00f6r\u00fcr\u00fcz:<\/p>\n<ul>\n<li><strong>Sadece alan ad\u0131 de\u011fi\u015fiyor:<\/strong> example.com \u2192 yeniad.com, URL yollar\u0131 ayn\u0131 kal\u0131yor.<\/li>\n<li><strong>Alan ad\u0131 + URL yap\u0131s\u0131 de\u011fi\u015fiyor:<\/strong> \/blog\/ yerine \/yazi\/, \/urun\/ yerine \/shop\/ vb.<\/li>\n<\/ul>\n<p>SEO a\u00e7\u0131s\u0131ndan en g\u00fcvenli yakla\u015f\u0131m, <strong>m\u00fcmk\u00fcn oldu\u011fu kadar ayn\u0131 URL yap\u0131s\u0131n\u0131 korumak<\/strong>t\u0131r. Ayn\u0131 yap\u0131y\u0131 korursan\u0131z, 301 haritan\u0131z basitle\u015fir. E\u011fer yap\u0131y\u0131 da de\u011fi\u015ftirecekseniz, her eski URL i\u00e7in birebir yeni URL e\u015fle\u015fmesini netle\u015ftirmeniz \u015fart.<\/p>\n<p>URL mimarisi hakk\u0131nda daha derin bir karar s\u00fcrecindeyseniz, \u00f6zellikle blog, ma\u011faza ve dil yap\u0131lar\u0131 i\u00e7in <a href='https:\/\/www.dchost.com\/blog\/subdomain-mi-alt-dizin-mi-blog-magaza-ve-dil-surumleri-icin-seo-ve-hosting-karsilastirmasi\/'>subdomain mi alt dizin mi tercih etmeniz gerekti\u011fini anlatt\u0131\u011f\u0131m\u0131z rehbere<\/a> g\u00f6z atman\u0131z faydal\u0131 olacakt\u0131r.<\/p>\n<h3><span id=\"3_Zamanlama_ve_dusuk_trafik_penceresi\">3. Zamanlama ve d\u00fc\u015f\u00fck trafik penceresi<\/span><\/h3>\n<p>Alan ad\u0131 ge\u00e7i\u015fini, sitenizin <strong>trafik olarak en sakin oldu\u011fu zaman aral\u0131\u011f\u0131na<\/strong> denk getirmeniz riskinizi azalt\u0131r. \u00d6rne\u011fin B2B bir SaaS iseniz hafta i\u00e7i g\u00fcnd\u00fcz yo\u011fun, hafta sonu sakin olabilirsiniz; B2C e-ticaret iseniz tam tersi.<\/p>\n<p>Genelde \u015fu yakla\u015f\u0131m\u0131 \u00f6neriyoruz:<\/p>\n<ul>\n<li>Haz\u0131rl\u0131klar\u0131 hafta i\u00e7i g\u00fcnd\u00fcz yap\u0131n (ekip ula\u015f\u0131labilir olsun).<\/li>\n<li>As\u0131l DNS ve 301 ge\u00e7i\u015fini gece ge\u00e7 saatlerde veya trafi\u011fin en d\u00fc\u015f\u00fck oldu\u011fu zaman diliminde uygulay\u0131n.<\/li>\n<li>Ge\u00e7i\u015f sonras\u0131 ilk 24 saati, ekibin \u201cn\u00f6bet\u201dte oldu\u011fu bir zaman dilimine denk getirin.<\/li>\n<\/ul>\n<h3><span id=\"4_Test_ortami_staging_kurmak\">4. Test ortam\u0131 (staging) kurmak<\/span><\/h3>\n<p>E\u011fer m\u00fcmk\u00fcnse, yeni alan ad\u0131n\u0131z\u0131 \u00f6nce bir <strong>staging ortam\u0131nda<\/strong> aya\u011fa kald\u0131r\u0131p t\u00fcm URL\u2019lerin \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan, tema \/ eklentilerin sorun \u00e7\u0131karmad\u0131\u011f\u0131ndan emin olun. DCHost \u00fczerindeki <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a> veya <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a> hizmetleriyle, canl\u0131 ortam\u0131 kopyalay\u0131p staging i\u00e7in ayr\u0131 bir alt alan ad\u0131 veya ayr\u0131 bir domain \u00fczerinde test ortam\u0131 olu\u015fturmak olduk\u00e7a pratik.<\/p>\n<h2><span id=\"301_Yonlendirme_Stratejisi_Eski_URLden_Yenisini_Kaybetmeden_Tasimak\">301 Y\u00f6nlendirme Stratejisi: Eski URL\u2019den Yenisini Kaybetmeden Ta\u015f\u0131mak<\/span><\/h2>\n<p>SEO kayb\u0131n\u0131 asgariye indirmenin kalbi <strong>301 y\u00f6nlendirmeler<\/strong>dir. 301, \u201cBu sayfa kal\u0131c\u0131 olarak ta\u015f\u0131nd\u0131.\u201d sinyalini verir ve arama motoruna, eski URL\u2019nin otoritesinin yeni URL\u2019ye aktar\u0131lmas\u0131 gerekti\u011fini s\u00f6yler.<\/p>\n<h3><span id=\"1_301_vs_302_vs_410_Hangisi_ne_zaman\">1. 301 vs 302 vs 410: Hangisi ne zaman?<\/span><\/h3>\n<ul>\n<li><strong>301 (Moved Permanently):<\/strong> Kal\u0131c\u0131 ta\u015f\u0131malar i\u00e7in kullan\u0131l\u0131r. Alan ad\u0131 de\u011fi\u015fiminde neredeyse her zaman 301 tercih etmelisiniz.<\/li>\n<li><strong>302 (Found \/ Temporary):<\/strong> Ge\u00e7ici y\u00f6nlendirmelerde kullan\u0131l\u0131r. Alan ad\u0131 ge\u00e7i\u015finde kullanman\u0131z, sinyallerin tam ta\u015f\u0131nmas\u0131n\u0131 geciktirir.<\/li>\n<li><strong>410 (Gone):<\/strong> Art\u0131k var olmayacak, yeni kar\u015f\u0131l\u0131\u011f\u0131 olmayan sayfalar i\u00e7in tercih edilebilir.<\/li>\n<\/ul>\n<p>Genel kural: Eski sitedeki her anlaml\u0131 sayfan\u0131n, <strong>m\u00fcmk\u00fcnse birebir kar\u015f\u0131l\u0131\u011f\u0131 olan yeni bir URL\u2019si olmal\u0131<\/strong> ve bu ge\u00e7i\u015f 301 ile yap\u0131lmal\u0131.<\/p>\n<h3><span id=\"2_Birebir_URL_eslestirme_mapping_tablosu\">2. Birebir URL e\u015fle\u015ftirme (mapping) tablosu<\/span><\/h3>\n<p>Haz\u0131rlad\u0131\u011f\u0131n\u0131z URL envanterinden yola \u00e7\u0131karak, bir <strong>eski \u2192 yeni URL tablosu<\/strong> haz\u0131rlay\u0131n. \u00d6rnek s\u00fctunlar:<\/p>\n<ul>\n<li>Eski URL (https:\/\/eskiad.com\/blog\/wordpress-seo-rehberi)<\/li>\n<li>Yeni URL (https:\/\/yeniad.com\/blog\/wordpress-seo-rehberi)<\/li>\n<li>Not (Tam e\u015fle\u015fme \/ Yak\u0131n i\u00e7erik \/ Art\u0131k yok)<\/li>\n<\/ul>\n<p>Art\u0131k kar\u015f\u0131l\u0131\u011f\u0131 olmayan sayfalar i\u00e7in:<\/p>\n<ul>\n<li>En yak\u0131n kategoriye 301 y\u00f6nlendirme yapabilir, ya da<\/li>\n<li>Ger\u00e7ekten gereksizse 410 ile arama motoruna \u201cbu i\u00e7erik kald\u0131r\u0131ld\u0131\u201d bilgisini verebilirsiniz.<\/li>\n<\/ul>\n<p>Ne olursa olsun, <strong>\u201cher \u015feyi ana sayfaya y\u00f6nlendirme\u201d<\/strong> hatas\u0131ndan ka\u00e7\u0131n\u0131n. Bu, hem kullan\u0131c\u0131 deneyimi a\u00e7\u0131s\u0131ndan k\u00f6t\u00fc, hem de arama motoru i\u00e7in spam sinyali gibi alg\u0131lanabilir.<\/p>\n<h3><span id=\"3_www_non-www_ve_http_https_tutarliligi\">3. www \/ non-www ve http \/ https tutarl\u0131l\u0131\u011f\u0131<\/span><\/h3>\n<p>Alan ad\u0131 de\u011fi\u015ftirirken, zaten var olan www \/ non-www ve http \/ https stratejinizi de g\u00f6zden ge\u00e7irin:<\/p>\n<ul>\n<li>Eski alan ad\u0131: http:\/\/example.com \u2192 https:\/\/www.example.com<\/li>\n<li>Yeni alan ad\u0131: https:\/\/www.yeniad.com<\/li>\n<\/ul>\n<p>Bu durumda \u015fu \u00fc\u00e7 katmanl\u0131 y\u00f6nlendirme zincirini istemiyoruz:<\/p>\n<ol>\n<li>http:\/\/example.com \u2192 https:\/\/example.com<\/li>\n<li>https:\/\/example.com \u2192 https:\/\/www.example.com<\/li>\n<li>https:\/\/www.example.com \u2192 https:\/\/www.yeniad.com<\/li>\n<\/ol>\n<p>Arama motoru i\u00e7in en ideali, <strong>tek ad\u0131mda 301<\/strong> yapmakt\u0131r:<\/p>\n<ul>\n<li>http ve https, www ve non-www d\u00e2hil t\u00fcm eski varyantlar \u2192 do\u011frudan yeni nihai URL<\/li>\n<\/ul>\n<p>Yani, <strong>zincirli 301\u2019leri<\/strong> (redirect chain) temizleyip, <strong>her \u015feyi bir hamlede yeni adrese<\/strong> y\u00f6nlendirecek kurallar\u0131 yaz\u0131n.<\/p>\n<h3><span id=\"4_Sunucu_tarafinda_301_kurulumu_Apache_Nginx_uygulama\">4. Sunucu taraf\u0131nda 301 kurulumu: Apache \/ Nginx \/ uygulama<\/span><\/h3>\n<p>Kulland\u0131\u011f\u0131n\u0131z platforma g\u00f6re 301\u2019leri farkl\u0131 katmanlarda kurabilirsiniz:<\/p>\n<ul>\n<li><strong>Apache (.htaccess):<\/strong> Eski domain i\u00e7in vhost i\u00e7inde RewriteRule ile alan ad\u0131 bazl\u0131 301.<\/li>\n<li><strong>Nginx:<\/strong> server_name eskiad.com; return 301 https:\/\/yeniad.com$request_uri; gibi bir direktif.<\/li>\n<li><strong>Uygulama i\u00e7i (WordPress, Laravel vb.):<\/strong> \u00c7o\u011fu durumda <strong>sunucu tarafl\u0131<\/strong> 301 daha performansl\u0131 ve sa\u011fl\u0131kl\u0131d\u0131r. Uygulama i\u00e7i y\u00f6nlendirmeleri sadece \u00f6zel durumlar i\u00e7in kullan\u0131n.<\/li>\n<\/ul>\n<p>E\u011fer WordPress \u00fczerinde \u00e7oklu site veya domain mapping kullan\u0131yorsan\u0131z, <a href='https:\/\/www.dchost.com\/blog\/wordpress-multisite-icin-vps-hosting-domain-mapping-ssl-ve-performans-ayarlari\/'>WordPress Multisite ve domain mapping \u00fczerine haz\u0131rlad\u0131\u011f\u0131m\u0131z rehber<\/a>, 301 senaryolar\u0131n\u0131z\u0131 planlarken size ciddi fikir verecektir.<\/p>\n<h3><span id=\"5_Canonical_ve_hreflang_etkilesimi\">5. Canonical ve hreflang etkile\u015fimi<\/span><\/h3>\n<p>Alan ad\u0131 de\u011fi\u015ftirirken s\u0131k yap\u0131lan hatalardan biri de <strong>canonical etiketlerini unutmak<\/strong>. Yeni sitede:<\/p>\n<ul>\n<li>T\u00fcm sayfalar\u0131n <strong>rel=&#8217;canonical&#8217;<\/strong> etiketi yeni alan ad\u0131na i\u015faret etmeli.<\/li>\n<li>Eski alan ad\u0131n\u0131 canonical olarak b\u0131rakmay\u0131n, aksi halde sinyaller kar\u0131\u015f\u0131r.<\/li>\n<\/ul>\n<p>E\u011fer \u00e7ok dilli bir siteniz ve <strong>hreflang<\/strong> yap\u0131n\u0131z varsa, hreflang etiketlerindeki t\u00fcm URL\u2019leri de yeni alan ad\u0131na g\u00f6re g\u00fcncelleyin. \u00c7ok dilli yap\u0131 ve ccTLD \/ alt dizin \/ alt alan stratejileri i\u00e7in <a href='https:\/\/www.dchost.com\/blog\/hreflangi-dogru-kurmanin-sirlari-cctld-alt-dizin-alt-alan-ve-x-default-ile-uluslararasi-seoyu-rayina-oturt\/'>hreflang\u2019i do\u011fru kurman\u0131n s\u0131rlar\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z rehberi<\/a> mutlaka g\u00f6zden ge\u00e7irin.<\/p>\n<h2><span id=\"DNS_ve_TTL_Plani_Yayilimi_Yonetmek_ve_Kesintiyi_Sifira_Yaklastirmak\">DNS ve TTL Plan\u0131: Yay\u0131l\u0131m\u0131 Y\u00f6netmek ve Kesintiyi S\u0131f\u0131ra Yakla\u015ft\u0131rmak<\/span><\/h2>\n<p>Alan ad\u0131 de\u011fi\u015ftirirken sadece web trafi\u011fini de\u011fil, t\u00fcm DNS altyap\u0131n\u0131z\u0131 d\u00fc\u015f\u00fcnmeniz gerekiyor. A, AAAA, CNAME, MX, TXT gibi kay\u0131tlar\u0131n tamam\u0131n\u0131n <strong>do\u011fru, tutarl\u0131 ve zamana yay\u0131lm\u0131\u015f bir \u015fekilde<\/strong> g\u00fcncellenmesi \u015fart.<\/p>\n<h3><span id=\"1_Mevcut_DNS_kayitlarini_analiz_etmek\">1. Mevcut DNS kay\u0131tlar\u0131n\u0131 analiz etmek<\/span><\/h3>\n<p>\u00d6nce mevcut alan ad\u0131n\u0131z\u0131n t\u00fcm DNS kay\u0131tlar\u0131n\u0131 \u00e7\u0131kar\u0131n:<\/p>\n<ul>\n<li>A \/ AAAA (web sunucunuzun IP adresleri)<\/li>\n<li>CNAME (alt alan adlar\u0131, CDN, third-party servisler)<\/li>\n<li>MX (e-posta sunucular\u0131)<\/li>\n<li>TXT (SPF, do\u011frulama kay\u0131tlar\u0131, \u00fc\u00e7\u00fcnc\u00fc taraf servisler)<\/li>\n<li>SRV \/ CAA gibi \u00f6zel kay\u0131tlar<\/li>\n<\/ul>\n<p>Bu kay\u0131tlar\u0131n ne i\u015fe yarad\u0131\u011f\u0131n\u0131 tam olarak bilmiyorsan\u0131z, <a href='https:\/\/www.dchost.com\/blog\/dns-kayitlari-adan-zye-a-aaaa-cname-mx-txt-srv-caa-ve-sizi-yakan-o-kucuk-hatalar\/'>DNS kay\u0131tlar\u0131 A\u2019dan Z\u2019ye anlatt\u0131\u011f\u0131m\u0131z rehberimizi<\/a> mutlaka okuyun. Alan ad\u0131 ge\u00e7i\u015finde yap\u0131lacak k\u00fc\u00e7\u00fck bir TXT veya MX hatas\u0131, hem SEO\u2019yu hem e-posta teslimini ciddi \u015fekilde etkileyebilir.<\/p>\n<h3><span id=\"2_TTL_stratejisi_Zero-downtimea_mumkun_oldugunca_yaklasmak\">2. TTL stratejisi: Zero-downtime\u2019a m\u00fcmk\u00fcn oldu\u011funca yakla\u015fmak<\/span><\/h3>\n<p>DNS ge\u00e7i\u015fleri s\u0131ras\u0131nda en kritik konu <strong>TTL (Time To Live)<\/strong> de\u011feridir. TTL, bir DNS kayd\u0131n\u0131n resolver\u2019lar taraf\u0131ndan ne kadar s\u00fcre cache\u2019lenece\u011fini belirler. Y\u00fcksek TTL, normalde performans i\u00e7in iyidir; ancak ge\u00e7i\u015f zaman\u0131 de\u011fi\u015fikliklerin ge\u00e7 yay\u0131lmas\u0131na neden olur.<\/p>\n<p>DCHost\u2019ta alan ad\u0131 veya sunucu ta\u015f\u0131ma yaparken genellikle \u015fu stratejiyi uyguluyoruz:<\/p>\n<ol>\n<li><strong>T-48 saat:<\/strong> Eski alan ad\u0131ndaki A \/ AAAA \/ MX gibi kritik kay\u0131tlar\u0131n TTL de\u011ferlerini d\u00fc\u015f\u00fcr (\u00f6rne\u011fin 3600sn \u2192 300sn).<\/li>\n<li><strong>T-0 an\u0131nda:<\/strong> IP veya hedef de\u011fi\u015fimini yap; d\u00fc\u015f\u00fck TTL sayesinde, \u00e7o\u011fu resolver 5\u201310 dakika i\u00e7inde yeni kayd\u0131 g\u00f6r\u00fcr.<\/li>\n<li><strong>T+48 saat:<\/strong> Her \u015fey stabil oldu\u011funda TTL\u2019leri yeniden makul bir seviyeye (3600\u201314400sn gibi) \u00e7ek.<\/li>\n<\/ol>\n<p>DNS yay\u0131l\u0131m\u0131n\u0131 h\u0131zland\u0131rma ve kesintiyi minimuma indirmek i\u00e7in daha detayl\u0131 bir yol haritas\u0131 isterseniz, <a href='https:\/\/www.dchost.com\/blog\/zero-downtime-tasima-icin-ttl-stratejileri-dns-yayilimini-gercekten-nasil-hizlandirirsin\/'>Zero-downtime ta\u015f\u0131ma i\u00e7in TTL stratejilerini anlatt\u0131\u011f\u0131m\u0131z makaleye<\/a> mutlaka g\u00f6z at\u0131n.<\/p>\n<h3><span id=\"3_Eski_ve_yeni_alan_adinin_DNS_yapilarini_senkron_tutmak\">3. Eski ve yeni alan ad\u0131n\u0131n DNS yap\u0131lar\u0131n\u0131 senkron tutmak<\/span><\/h3>\n<p>Alan ad\u0131 de\u011fi\u015fimi genelde \u015f\u00f6yle g\u00f6r\u00fcl\u00fcr:<\/p>\n<ul>\n<li>Eski alan ad\u0131: esas trafik, esas DNS.<\/li>\n<li>Yeni alan ad\u0131: yava\u015f yava\u015f devreye al\u0131nan yeni yap\u0131.<\/li>\n<\/ul>\n<p>Oysa en sa\u011fl\u0131kl\u0131s\u0131, ge\u00e7i\u015f s\u0131ras\u0131nda <strong>her iki alan ad\u0131n\u0131n da ayn\u0131 hedefe bakmas\u0131d\u0131r<\/strong>:<\/p>\n<ul>\n<li>Hem eski, hem yeni alan ad\u0131; ayn\u0131 web sunucusu IP\u2019sine (A\/AAAA) y\u00f6nelsin.<\/li>\n<li>Hem eski, hem yeni alan ad\u0131ndaki MX kay\u0131tlar\u0131; ayn\u0131 e-posta altyap\u0131s\u0131n\u0131 g\u00f6stersin.<\/li>\n<\/ul>\n<p>B\u00f6ylece 301\u2019ler, uygulama katman\u0131nda tutarl\u0131 \u00e7al\u0131\u015f\u0131r; DNS taraf\u0131nda b\u00f6l\u00fcnme ya\u015famazs\u0131n\u0131z.<\/p>\n<h2><span id=\"E-posta_Tasima_Plani_MX_SPF_DKIM_DMARC_ve_Testler\">E-posta Ta\u015f\u0131ma Plan\u0131: MX, SPF, DKIM, DMARC ve Testler<\/span><\/h2>\n<p>SEO odakl\u0131 alan ad\u0131 de\u011fi\u015fimlerinde \u00e7o\u011fu zaman <strong>e-posta taraf\u0131 ikinci plana at\u0131l\u0131yor<\/strong>. Sonra da \u201cAlan ad\u0131 ge\u00e7tikten sonra mailler spam\u2019e d\u00fc\u015fmeye ba\u015flad\u0131.\u201d \u015fik\u00e2yeti geliyor. \u00c7\u00fcnk\u00fc g\u00f6nderen alan ad\u0131n\u0131z de\u011fi\u015fti\u011finde, <strong>SPF, DKIM, DMARC ve rDNS<\/strong> zincirini ba\u015ftan ele almak gerekir.<\/p>\n<h3><span id=\"1_MX_kayitlarini_planlamak\">1. MX kay\u0131tlar\u0131n\u0131 planlamak<\/span><\/h3>\n<p>Yeni alan ad\u0131n\u0131zda e-posta kullanacaksan\u0131z \u015fu ad\u0131mlar\u0131 izleyin:<\/p>\n<ul>\n<li>Yeni alan ad\u0131 i\u00e7in MX kay\u0131tlar\u0131n\u0131, kullanaca\u011f\u0131n\u0131z e-posta sunucular\u0131na y\u00f6nlendirin.<\/li>\n<li>Eski alan ad\u0131ndaki MX kay\u0131tlar\u0131n\u0131 hemen silmeyin; bir s\u00fcre ikisini de paralel \u00e7al\u0131\u015ft\u0131rman\u0131z, ka\u00e7ak trafi\u011fi yakalaman\u0131z\u0131 sa\u011flar.<\/li>\n<li>E-posta istemcilerinizde (Outlook, mobil, webmail vb.) yeni e-posta adreslerini (info@yeniad.com gibi) ayn\u0131 anda tan\u0131mlay\u0131n.<\/li>\n<\/ul>\n<p>E\u011fer kendi e-posta sunucunuzu bir VPS \u00fczerinde y\u00f6netiyorsan\u0131z, e-posta ge\u00e7i\u015finden \u00f6nce ve sonra <strong>IP itibar\u0131n\u0131<\/strong> ve teslim edilebilirli\u011fi takip etmek i\u00e7in <a href='https:\/\/www.dchost.com\/blog\/e-posta-itibarini-kurtarma-rehberi-blacklist-delisting-postmaster-araclari-ve-guvenli-ip-isitma-nasil-kurtarici-olur\/'>e-posta itibar\u0131n\u0131 kurtarma rehberimize<\/a> mutlaka g\u00f6z at\u0131n.<\/p>\n<h3><span id=\"2_SPF_DKIM_DMARC_kayitlarini_guncellemek\">2. SPF, DKIM, DMARC kay\u0131tlar\u0131n\u0131 g\u00fcncellemek<\/span><\/h3>\n<p>G\u00f6nderen alan ad\u0131n\u0131z de\u011fi\u015fti\u011fi i\u00e7in, yeni domain\u2019de <strong>ba\u015ftan SPF, DKIM, DMARC yap\u0131land\u0131rmas\u0131<\/strong> yapmal\u0131s\u0131n\u0131z:<\/p>\n<ul>\n<li><strong>SPF:<\/strong> Hangi sunucular\u0131n yeni alan ad\u0131 ad\u0131na mail g\u00f6ndermeye yetkili oldu\u011funu tan\u0131mlay\u0131n.<\/li>\n<li><strong>DKIM:<\/strong> E-posta imzalama anahtar\u0131n\u0131 yeni alan ad\u0131n\u0131z i\u00e7in olu\u015fturup DNS\u2019e public key olarak ekleyin.<\/li>\n<li><strong>DMARC:<\/strong> dmarc.yeniad.com rapor kutusunu olu\u015fturun, politikay\u0131 \u00f6nce <em>p=none<\/em> ile ba\u015flay\u0131p zamanla s\u0131k\u0131la\u015ft\u0131r\u0131n.<\/li>\n<\/ul>\n<p>Bu \u00fc\u00e7l\u00fcn\u00fcn nas\u0131l birlikte \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 ve teknik kurulum ad\u0131mlar\u0131n\u0131, <a href='https:\/\/www.dchost.com\/blog\/spf-dkim-dmarc-ve-rdns-ile-e-posta-teslim-edilebilirligini-nasil-adim-adim-yukseltirsin\/'>SPF, DKIM, DMARC ve rDNS ile e-posta teslim edilebilirli\u011fini art\u0131rma rehberimizde<\/a> ad\u0131m ad\u0131m anlatt\u0131k. Alan ad\u0131 de\u011fi\u015ftirirken bu rehberi referans almak, spam kutusu riskini ciddi \u015fekilde azalt\u0131r.<\/p>\n<h3><span id=\"3_Gonderici_adi_From_ve_imzalari_guncellemek\">3. G\u00f6nderici ad\u0131 (From:) ve imzalar\u0131 g\u00fcncellemek<\/span><\/h3>\n<p>Teknik kay\u0131tlar kadar, <strong>kullan\u0131c\u0131 taraf\u0131ndaki g\u00f6r\u00fcn\u00fcm<\/strong> de \u00f6nemli:<\/p>\n<ul>\n<li>CRM, helpdesk, b\u00fclten arac\u0131 gibi t\u00fcm sistemlerde g\u00f6nderen adresinizi yeni alan ad\u0131na g\u00fcncelleyin (no-reply@, info@ vb.).<\/li>\n<li>E-posta imzalar\u0131ndaki site linklerini ve alan ad\u0131n\u0131 d\u00fczeltin.<\/li>\n<li>\u00d6nemli m\u00fc\u015fterilere, alan ad\u0131 de\u011fi\u015fikli\u011fini a\u00e7\u0131klayan k\u0131sa bir bilgilendirme maili g\u00f6nderin.<\/li>\n<\/ul>\n<h3><span id=\"4_E-posta_gecis_testleri\">4. E-posta ge\u00e7i\u015f testleri<\/span><\/h3>\n<p>Alan ad\u0131 ge\u00e7i\u015fi \u00f6ncesi ve sonras\u0131 mutlaka \u015fu testleri yap\u0131n:<\/p>\n<ul>\n<li>Yeni alan ad\u0131ndan Gmail, Outlook gibi pop\u00fcler sa\u011flay\u0131c\u0131lara test mail at\u0131n, spam kutusuna d\u00fc\u015f\u00fcp d\u00fc\u015fmedi\u011fini kontrol edin.<\/li>\n<li>Mail header\u2019lar\u0131n\u0131 inceleyerek SPF, DKIM ve DMARC sonu\u00e7lar\u0131n\u0131 kontrol edin (pass \/ fail).<\/li>\n<li>Farkl\u0131 istemcilerden (mobil, masa\u00fcst\u00fc) g\u00f6nderim ve al\u0131m\u0131 test edin.<\/li>\n<\/ul>\n<h2><span id=\"SEO_Sinyallerini_Koruma_Analytics_Search_Console_ve_Ic_Baglantilar\">SEO Sinyallerini Koruma: Analytics, Search Console ve \u0130\u00e7 Ba\u011flant\u0131lar<\/span><\/h2>\n<p>Alan ad\u0131 de\u011fi\u015fikli\u011fi, sadece teknik ta\u015f\u0131ma de\u011fil; <strong>SEO sinyallerinin yeniden adreslenmesi<\/strong> s\u00fcrecidir. Arama motorlar\u0131na bu de\u011fi\u015fimi d\u00fczg\u00fcn bildirmezseniz, 301 y\u00f6nlendirmeleriniz do\u011fru olsa bile toparlanma s\u00fcreniz uzar.<\/p>\n<h3><span id=\"1_Google_Search_Consoleda_adres_degisikligi\">1. Google Search Console\u2019da adres de\u011fi\u015fikli\u011fi<\/span><\/h3>\n<p>Hem eski, hem yeni alan ad\u0131n\u0131z\u0131 Google Search Console\u2019a m\u00fclk (property) olarak ekleyin. Ard\u0131ndan:<\/p>\n<ul>\n<li>Eski alan ad\u0131 m\u00fclk\u00fcnden \u201cAdres de\u011fi\u015fikli\u011fi\u201d arac\u0131n\u0131 kullanarak yeni alan ad\u0131n\u0131 i\u015faret edin.<\/li>\n<li>Yeni alan ad\u0131n\u0131z i\u00e7in XML sitemap\u2019leri ekleyin ve \u201c\u0130ndeksleme iste\u011fi\u201d g\u00f6nderin.<\/li>\n<\/ul>\n<p>Bu i\u015flem, Google\u2019a \u201cBu site yeni adrese ta\u015f\u0131nd\u0131, sinyalleri buraya devret.\u201d demenin resmi yoludur.<\/p>\n<h3><span id=\"2_Analytics_ve_hedefler\">2. Analytics ve hedefler<\/span><\/h3>\n<p>Google Analytics veya benzeri analitik arac\u0131n\u0131zda:<\/p>\n<ul>\n<li>Yeni alan ad\u0131n\u0131, ayn\u0131 \u00f6l\u00e7\u00fcm kimli\u011fi (Measurement ID) ile takip etmeye devam edin.<\/li>\n<li>Hedefler (Goals) veya d\u00f6n\u00fc\u015f\u00fcmler (Conversions) alan\u0131nda, URL tabanl\u0131 tan\u0131mlar yapt\u0131ysan\u0131z yeni URL yap\u0131s\u0131na g\u00f6re g\u00fcncelleyin.<\/li>\n<li>Filtre veya hostname bazl\u0131 raporlar\u0131n\u0131z varsa, yeni domain\u2019i de kapsad\u0131\u011f\u0131ndan emin olun.<\/li>\n<\/ul>\n<h3><span id=\"3_Ic_baglantilari_guncellemek\">3. \u0130\u00e7 ba\u011flant\u0131lar\u0131 g\u00fcncellemek<\/span><\/h3>\n<p>301 y\u00f6nlendirmeler i\u00e7 linkler i\u00e7in de \u00e7al\u0131\u015f\u0131r; ancak uzun vadede <strong>i\u00e7 ba\u011flant\u0131lar\u0131 do\u011frudan yeni alan ad\u0131na<\/strong> g\u00fcncellemek daha sa\u011fl\u0131kl\u0131d\u0131r. \u00d6zellikle:<\/p>\n<ul>\n<li>Men\u00fc ve footer linkleri<\/li>\n<li>Blog yaz\u0131lar\u0131ndaki dahili linkler<\/li>\n<li>\u00dcr\u00fcn sayfalar\u0131ndan di\u011fer \u00fcr\u00fcnlere \/ kategorilere giden linkler<\/li>\n<\/ul>\n<p>Bu ad\u0131m\u0131 belli bir s\u00fcreye yayabilirsiniz; ancak en az\u0131ndan <strong>global navigasyondaki linkleri<\/strong> ge\u00e7i\u015f an\u0131nda g\u00fcncellemek iyi bir pratiktir.<\/p>\n<h3><span id=\"4_Dis_baglantilari_backlink_guncellemek\">4. D\u0131\u015f ba\u011flant\u0131lar\u0131 (backlink) g\u00fcncellemek<\/span><\/h3>\n<p>301 y\u00f6nlendirmeler sayesinde, eski alan ad\u0131n\u0131za verilen linklerin otoritesi b\u00fcy\u00fck \u00f6l\u00e7\u00fcde yeni domaine akar. Yine de kritik kaynaklarda link g\u00fcncellemek faydal\u0131d\u0131r:<\/p>\n<ul>\n<li>Sizin kontrol\u00fcn\u00fczdeki di\u011fer sitelerde (\u015firketler, projeler, ki\u015fisel siteler) linkleri manuel olarak d\u00fczeltin.<\/li>\n<li>\u00d6nemli i\u015f ortaklar\u0131n\u0131za, alan ad\u0131 de\u011fi\u015fikli\u011fini duyurup linklerini g\u00fcncellemelerini rica edin.<\/li>\n<li>Sosyal medya profillerinizde, dizinlerde, Google Business profilinizde URL\u2019yi g\u00fcncelleyin.<\/li>\n<\/ul>\n<h2><span id=\"DCHost_ile_Ornek_Tasima_Senaryosu_Adim_Adim_Zaman_Cizelgesi\">DCHost ile \u00d6rnek Ta\u015f\u0131ma Senaryosu: Ad\u0131m Ad\u0131m Zaman \u00c7izelgesi<\/span><\/h2>\n<p>DCHost taraf\u0131nda s\u0131k\u00e7a uygulad\u0131\u011f\u0131m\u0131z tipik bir alan ad\u0131 de\u011fi\u015fikli\u011fi senaryosunu, zaman \u00e7izelgesi \u00fczerinden \u00f6zetleyelim. Bu senaryoda:<\/p>\n<ul>\n<li>Eski domain: eskiad.com<\/li>\n<li>Yeni domain: yeniad.com<\/li>\n<li>Site: WordPress + WooCommerce, DCHost VPS \u00fczerinde \u00e7al\u0131\u015f\u0131yor.<\/li>\n<\/ul>\n<h3><span id=\"T-7_gun_Hazirlik\">T-7 g\u00fcn: Haz\u0131rl\u0131k<\/span><\/h3>\n<ul>\n<li>T\u00fcm \u00f6nemli URL\u2019lerin envanterini \u00e7\u0131kar\u0131yoruz (Analytics + Search Console + loglar).<\/li>\n<li>Eski \u2192 yeni URL mapping tablosunu haz\u0131rl\u0131yoruz.<\/li>\n<li>Yeni alan ad\u0131 <strong>yeniad.com<\/strong>, DCHost\u2019ta ayn\u0131 VPS\u2019e i\u015faret ediyor; staging ortam\u0131nda t\u00fcm sayfalar test ediliyor.<\/li>\n<li>DNS sa\u011flay\u0131c\u0131 \u00fczerinde mevcut kay\u0131tlar ve TTL de\u011ferleri not al\u0131n\u0131yor.<\/li>\n<li>Alan ad\u0131 g\u00fcvenli\u011fi (Registrar Lock, 2FA, Whois gizlili\u011fi, DNSSEC) gibi konular, yeni alan ad\u0131 i\u00e7in de kontrol ediliyor. Bu a\u015famada <a href='https:\/\/www.dchost.com\/blog\/alan-adi-guvenligi-rehberi-registrar-lock-dnssec-whois-gizliligi-ve-2fa\/'>alan ad\u0131 g\u00fcvenli\u011fi rehberimizdeki ad\u0131mlar\u0131<\/a> referans almak \u00e7ok faydal\u0131.<\/li>\n<\/ul>\n<h3><span id=\"T-48_saat_TTL_dusurme_ve_DNS_hazirligi\">T-48 saat: TTL d\u00fc\u015f\u00fcrme ve DNS haz\u0131rl\u0131\u011f\u0131<\/span><\/h3>\n<ul>\n<li>eskiad.com \u00fczerindeki A \/ AAAA \/ MX gibi kritik kay\u0131tlar\u0131n TTL\u2019leri 300 saniyeye \u00e7ekiliyor.<\/li>\n<li>yeniad.com \u00fczerinde, eskiad.com ile tamamen ayn\u0131 DNS kay\u0131t yap\u0131s\u0131 olu\u015fturuluyor (sadece alan adlar\u0131 farkl\u0131).<\/li>\n<li>SSL sertifikalar\u0131, hem eski hem yeni alan ad\u0131n\u0131 kapsayacak \u015fekilde ayarlan\u0131yor (gerekirse SAN veya ayr\u0131 sertifikalar).<\/li>\n<\/ul>\n<h3><span id=\"T-0_Gecis_ani\">T-0: Ge\u00e7i\u015f an\u0131<\/span><\/h3>\n<ul>\n<li>Nginx \/ Apache konfig\u00fcrasyonunda, eskiad.com i\u00e7in gelen t\u00fcm istekler, mapping tablosuna g\u00f6re yeniad.com\u2019daki birebir URL\u2019lere 301 ile y\u00f6nlendiriliyor.<\/li>\n<li>WordPress i\u00e7inde site URL ayarlar\u0131 yeniad.com olarak g\u00fcncelleniyor.<\/li>\n<li>Men\u00fc, footer ve sabit linklerdeki dahili URL\u2019ler m\u00fcmk\u00fcn olan \u00f6l\u00e7\u00fcde yeni domain\u2019e g\u00f6re g\u00fcncelleniyor.<\/li>\n<li>Google Search Console\u2019da adres de\u011fi\u015fikli\u011fi bildirimi yap\u0131l\u0131yor; yeni sitemap\u2019ler g\u00f6nderiliyor.<\/li>\n<li>Analytics taraf\u0131nda yeni domain\u2019in d\u00fczg\u00fcn izlenip izlenmedi\u011fi kontrol ediliyor.<\/li>\n<\/ul>\n<h3><span id=\"T24_saat_Izleme\">T+24 saat: \u0130zleme<\/span><\/h3>\n<ul>\n<li>Sunucu loglar\u0131ndan 404 hatalar\u0131 taran\u0131yor; mapping tablosunda eksik kalan URL\u2019ler tespit edilip ek 301 kurallar\u0131 yaz\u0131l\u0131yor.<\/li>\n<li>Arama sonu\u00e7lar\u0131ndan t\u0131klanan ve hataya d\u00fc\u015fen sayfalar olup olmad\u0131\u011f\u0131 kontrol ediliyor.<\/li>\n<li>E-posta g\u00f6nderimlerinde SPF \/ DKIM \/ DMARC sonu\u00e7lar\u0131 test ediliyor; spam \/ inbox oranlar\u0131 g\u00f6zlemleniyor.<\/li>\n<\/ul>\n<h3><span id=\"T7_gun_Stabilizasyon\">T+7 g\u00fcn: Stabilizasyon<\/span><\/h3>\n<ul>\n<li>Eski alan ad\u0131ndaki i\u00e7erik tamamen 301 ile yeni adrese y\u00f6nleniyor, eski sitede direkt i\u00e7erik g\u00f6sterimi b\u0131rak\u0131lm\u0131yor.<\/li>\n<li>TTL de\u011ferleri, tekrar makul seviyelere y\u00fckseltiliyor (performans ve dayan\u0131kl\u0131l\u0131k i\u00e7in).<\/li>\n<li>Backlink\u2019lerin \u00f6nemli bir k\u0131sm\u0131 manuel olarak g\u00fcncellenmi\u015f oluyor.<\/li>\n<\/ul>\n<h2><span id=\"Alan_Adi_Transferi_ve_Barindirma_Tarafini_Unutmamak\">Alan Ad\u0131 Transferi ve Bar\u0131nd\u0131rma Taraf\u0131n\u0131 Unutmamak<\/span><\/h2>\n<p>Alan ad\u0131 de\u011fi\u015fimi \u00e7o\u011fu zaman <strong>alan ad\u0131 transferi<\/strong> veya <strong>hosting ta\u015f\u0131ma<\/strong> s\u00fcreciyle birlikte y\u00fcr\u00fct\u00fcl\u00fcyor. E\u011fer domain\u2019i ba\u015fka bir registrardan DCHost\u2019a transfer ediyorsan\u0131z, mutlaka:<\/p>\n<ul>\n<li>EPP kodu, transfer kilidi, Whois bilgileri ve olas\u0131 ek g\u00fcvenlik \u00f6nlemlerini ba\u015ftan planlay\u0131n.<\/li>\n<li>Transfer s\u00fcresince DNS\u2019in nereden y\u00f6netilece\u011fini netle\u015ftirin (eski mi, yeni mi, ara bir DNS mi?).<\/li>\n<\/ul>\n<p>Bu konularda ad\u0131m ad\u0131m ilerlemek i\u00e7in <a href='https:\/\/www.dchost.com\/blog\/alan-adi-transferi-nasil-yapilir-epp-kodu-transfer-kilidi-ve-kesintisiz-gecise-sakin-bir-rehber\/'>alan ad\u0131 transferi rehberimize<\/a> g\u00f6z atabilirsiniz. E\u011fer alan ad\u0131n\u0131 de\u011fi\u015ftirirken ayn\u0131 anda hosting altyap\u0131n\u0131z\u0131 da yenilemeyi d\u00fc\u015f\u00fcn\u00fcyorsan\u0131z, DCHost\u2019un payla\u015f\u0131ml\u0131 hosting, VPS, fiziksel sunucu ve colocation \u00e7\u00f6z\u00fcmleri ile ge\u00e7i\u015fi tek merkezden y\u00f6netmek i\u015fleri ciddi anlamda sadele\u015ftirir.<\/p>\n<h2><span id=\"Hizli_Kontrol_Listesi_Alan_Adi_Degistirirken_SEO_Kaybetmemek_Icin\">H\u0131zl\u0131 Kontrol Listesi: Alan Ad\u0131 De\u011fi\u015ftirirken SEO Kaybetmemek \u0130\u00e7in<\/span><\/h2>\n<p>Toparlamak i\u00e7in, alan ad\u0131 de\u011fi\u015fiminde kendinize \u015fu sorular\u0131 sorabilece\u011finiz bir kontrol listesi b\u0131rakal\u0131m:<\/p>\n<ul>\n<li>T\u00fcm \u00f6nemli URL\u2019lerin envanterini \u00e7\u0131kard\u0131m m\u0131?<\/li>\n<li>Eski \u2192 yeni URL mapping tablom eksiksiz mi?<\/li>\n<li>301 y\u00f6nlendirmeler zincirsiz, tek ad\u0131mda \u00e7al\u0131\u015f\u0131yor mu?<\/li>\n<li>Canonical etiketleri yeni alan ad\u0131na i\u015faret ediyor mu?<\/li>\n<li>hreflang, sitemap ve robots.txt dosyalar\u0131 yeni domain i\u00e7in g\u00fcncel mi?<\/li>\n<li>DNS kay\u0131tlar\u0131n\u0131 (A, AAAA, CNAME, MX, TXT, CAA) yeni domain i\u00e7in do\u011fru kurdum mu?<\/li>\n<li>TTL de\u011ferlerini ge\u00e7i\u015ften \u00f6nce d\u00fc\u015f\u00fcrd\u00fcm, sonra tekrar y\u00fckselttim mi?<\/li>\n<li>MX, SPF, DKIM, DMARC kay\u0131tlar\u0131 yeni alan ad\u0131 i\u00e7in do\u011fru \u00e7al\u0131\u015f\u0131yor mu?<\/li>\n<li>Google Search Console\u2019da adres de\u011fi\u015fikli\u011fini bildirdim mi?<\/li>\n<li>Analytics taraf\u0131nda yeni domain sorunsuz takip ediliyor mu?<\/li>\n<li>\u0130\u00e7 ba\u011flant\u0131lar\u0131m\u0131 ve en kritik d\u0131\u015f ba\u011flant\u0131lar\u0131 g\u00fcncelledim mi?<\/li>\n<li>Ge\u00e7i\u015f sonras\u0131 404 loglar\u0131n\u0131 takip edip eksik 301\u2019leri tamamlad\u0131m m\u0131?<\/li>\n<\/ul>\n<h2><span id=\"Sonuc_Dogru_Planla_Alan_Adi_Degisimi_Korkulacak_Bir_Is_Degil\">Sonu\u00e7: Do\u011fru Planla Alan Ad\u0131 De\u011fi\u015fimi Korkulacak Bir \u0130\u015f De\u011fil<\/span><\/h2>\n<p>Alan ad\u0131 de\u011fi\u015fikli\u011fi, plans\u0131z yap\u0131ld\u0131\u011f\u0131nda can yakar; ama <strong>iyi bir 301 stratejisi, bilin\u00e7li DNS \/ TTL plan\u0131 ve temiz bir e-posta ta\u015f\u0131ma ak\u0131\u015f\u0131yla<\/strong> asl\u0131nda son derece kontroll\u00fc y\u00f6netilebilen bir s\u00fcre\u00e7tir. \u00d6nemli olan, bunu \u201csadece domain de\u011fi\u015ftirdik\u201d diye g\u00f6rmemek; SEO, e-posta, marka ve kullan\u0131c\u0131 deneyimini birlikte ele almakt\u0131r.<\/p>\n<p>DCHost\u2019ta her g\u00fcn benzer ge\u00e7i\u015fler yaparken g\u00f6rd\u00fc\u011f\u00fcm\u00fcz \u015fey \u015fu: Aceleye getirilen, \u201cnas\u0131lsa Google anlar\u201d diye d\u00fc\u015f\u00fcn\u00fclen ta\u015f\u0131malarda kaybedilen trafi\u011fi geri toplamak, ba\u015ftan d\u00fczg\u00fcn bir plan yapmaktan \u00e7ok daha maliyetli oluyor. \u00d6te yandan, yukar\u0131da anlatt\u0131\u011f\u0131m\u0131z ad\u0131mlar\u0131 izleyip, \u00f6zellikle <strong>301 haritan\u0131z\u0131 ve DNS \/ e-posta yap\u0131land\u0131rman\u0131z\u0131 titizlikle<\/strong> haz\u0131rlad\u0131\u011f\u0131n\u0131zda; \u00e7o\u011fu projede ge\u00e7i\u015ften 1\u20132 hafta sonra trafi\u011fin b\u00fcy\u00fck k\u0131sm\u0131 yeni domain\u2019e sa\u011fl\u0131kl\u0131 \u015fekilde ta\u015f\u0131nm\u0131\u015f oluyor.<\/p>\n<p>E\u011fer alan ad\u0131 de\u011fi\u015fikli\u011fi, ayn\u0131 zamanda altyap\u0131n\u0131z\u0131 da yenilemek i\u00e7in bir f\u0131rsatsa; DCHost\u2019un payla\u015f\u0131ml\u0131 hosting, NVMe VPS, fiziksel sunucu ve colocation \u00e7\u00f6z\u00fcmleriyle hem performans taraf\u0131nda kazan\u00e7 sa\u011flayabilir, hem de ge\u00e7i\u015f s\u00fcrecini tek elden ve sakin bir \u015fekilde y\u00f6netebilirsiniz. Bir sonraki alan ad\u0131 projenizde, bu yaz\u0131daki kontrol listesini yan\u0131n\u0131za al\u0131p ad\u0131m ad\u0131m ilerleyin; SEO taraf\u0131nda \u201cke\u015fke\u201d deme ihtimaliniz ciddi \u015fekilde azalacakt\u0131r.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Alan Ad\u0131 De\u011fi\u015ftirirken Neden SEO Kayb\u0131 Ya\u015fan\u0131yor?2 Ge\u00e7i\u015f \u00d6ncesi Planlama: Envanter, Zamanlama ve Test Ortam\u01312.1 1. URL envanteri \u00e7\u0131karma2.2 2. Yeni URL yap\u0131s\u0131n\u0131 netle\u015ftirmek2.3 3. Zamanlama ve d\u00fc\u015f\u00fck trafik penceresi2.4 4. Test ortam\u0131 (staging) kurmak3 301 Y\u00f6nlendirme Stratejisi: Eski URL\u2019den Yenisini Kaybetmeden Ta\u015f\u0131mak3.1 1. 301 vs 302 vs 410: Hangisi ne zaman?3.2 2. Birebir [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":2147,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-2146","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\/2146","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=2146"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/2146\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/2147"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=2146"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=2146"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=2146"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}