{"id":4031,"date":"2026-01-02T21:47:49","date_gmt":"2026-01-02T18:47:49","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/bakim-modu-ve-planli-kesinti-yonetimi-seo-kaybi-yasamadan-maintenance-page-yayinlama-rehberi\/"},"modified":"2026-01-02T21:47:49","modified_gmt":"2026-01-02T18:47:49","slug":"bakim-modu-ve-planli-kesinti-yonetimi-seo-kaybi-yasamadan-maintenance-page-yayinlama-rehberi","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/bakim-modu-ve-planli-kesinti-yonetimi-seo-kaybi-yasamadan-maintenance-page-yayinlama-rehberi\/","title":{"rendered":"Bak\u0131m Modu ve Planl\u0131 Kesinti Y\u00f6netimi: SEO Kayb\u0131 Ya\u015famadan Maintenance Page Yay\u0131nlama Rehberi"},"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=\"#Bakim_Modu_Neden_Bu_Kadar_Onemli\"><span class=\"toc_number toc_depth_1\">1<\/span> Bak\u0131m Modu Neden Bu Kadar \u00d6nemli?<\/a><\/li><li><a href=\"#Yanlis_Bakim_Sayfasinin_SEOya_Verdigi_Zarar\"><span class=\"toc_number toc_depth_1\">2<\/span> Yanl\u0131\u015f Bak\u0131m Sayfas\u0131n\u0131n SEO\u2019ya Verdi\u011fi Zarar<\/a><ul><li><a href=\"#En_sik_yapilan_hatalar\"><span class=\"toc_number toc_depth_2\">2.1<\/span> En s\u0131k yap\u0131lan hatalar<\/a><\/li><li><a href=\"#Dogru_yaklasim_503_Service_Unavailable_Retry-After\"><span class=\"toc_number toc_depth_2\">2.2<\/span> Do\u011fru yakla\u015f\u0131m: 503 Service Unavailable + Retry-After<\/a><\/li><\/ul><\/li><li><a href=\"#Planli_vs_Plansiz_Kesinti_Strateji_Nasil_Degisir\"><span class=\"toc_number toc_depth_1\">3<\/span> Planl\u0131 vs Plans\u0131z Kesinti: Strateji Nas\u0131l De\u011fi\u015fir?<\/a><ul><li><a href=\"#Planli_bakim_ornek_versiyon_yukseltme_altyapi_degisikligi\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Planl\u0131 bak\u0131m (\u00f6rnek: versiyon y\u00fckseltme, altyap\u0131 de\u011fi\u015fikli\u011fi)<\/a><\/li><li><a href=\"#Plansiz_kesinti_ornek_donanim_arizasi_ani_yazilim_hatasi\"><span class=\"toc_number toc_depth_2\">3.2<\/span> Plans\u0131z kesinti (\u00f6rnek: donan\u0131m ar\u0131zas\u0131, ani yaz\u0131l\u0131m hatas\u0131)<\/a><\/li><\/ul><\/li><li><a href=\"#SEO_Dostu_Maintenance_Page_Icin_Teknik_Temeller\"><span class=\"toc_number toc_depth_1\">4<\/span> SEO Dostu Maintenance Page \u0130\u00e7in Teknik Temeller<\/a><ul><li><a href=\"#1_Dogru_HTTP_statu_kodunu_kullanmak\"><span class=\"toc_number toc_depth_2\">4.1<\/span> 1. Do\u011fru HTTP stat\u00fc kodunu kullanmak<\/a><\/li><li><a href=\"#2_Retry-After_basligi_ile_botlari_dogru_yonlendirmek\"><span class=\"toc_number toc_depth_2\">4.2<\/span> 2. Retry-After ba\u015fl\u0131\u011f\u0131 ile bot\u2019lar\u0131 do\u011fru y\u00f6nlendirmek<\/a><\/li><li><a href=\"#3_robotstxt_ve_meta_robots_ayarlari\"><span class=\"toc_number toc_depth_2\">4.3<\/span> 3. robots.txt ve meta robots ayarlar\u0131<\/a><\/li><li><a href=\"#4_Canonical_ve_yapilandirilmis_veri\"><span class=\"toc_number toc_depth_2\">4.4<\/span> 4. Canonical ve yap\u0131land\u0131r\u0131lm\u0131\u015f veri<\/a><\/li><li><a href=\"#5_Tarayici_ve_proxy_onbellegi_Cache-Control\"><span class=\"toc_number toc_depth_2\">4.5<\/span> 5. Taray\u0131c\u0131 ve proxy \u00f6nbelle\u011fi (Cache-Control)<\/a><\/li><\/ul><\/li><li><a href=\"#Uygulama_Duzeyinde_Bakim_Modu_WordPress_Laravel_ve_Ozel_Yazilimlar\"><span class=\"toc_number toc_depth_1\">5<\/span> Uygulama D\u00fczeyinde Bak\u0131m Modu: WordPress, Laravel ve \u00d6zel Yaz\u0131l\u0131mlar<\/a><ul><li><a href=\"#WordPress_bakim_modunda_sik_yapilan_hatalar\"><span class=\"toc_number toc_depth_2\">5.1<\/span> WordPress bak\u0131m modunda s\u0131k yap\u0131lan hatalar<\/a><\/li><li><a href=\"#Framework_tabanli_uygulamalar_Laravel_Symfony_vb\"><span class=\"toc_number toc_depth_2\">5.2<\/span> Framework tabanl\u0131 uygulamalar (Laravel, Symfony vb.)<\/a><\/li><li><a href=\"#Statik_siteler_ve_headless_mimariler\"><span class=\"toc_number toc_depth_2\">5.3<\/span> Statik siteler ve headless mimariler<\/a><\/li><\/ul><\/li><li><a href=\"#DNS_ve_Altyapi_Perspektifinden_Planli_Kesinti_Yonetimi\"><span class=\"toc_number toc_depth_1\">6<\/span> DNS ve Altyap\u0131 Perspektifinden Planl\u0131 Kesinti Y\u00f6netimi<\/a><ul><li><a href=\"#TTL_stratejisi_Tasima_ve_bakim_oncesi_olmazsa_olmaz\"><span class=\"toc_number toc_depth_2\">6.1<\/span> TTL stratejisi: Ta\u015f\u0131ma ve bak\u0131m \u00f6ncesi olmazsa olmaz<\/a><\/li><li><a href=\"#Anycast_cok_bolgeli_mimari_ve_bakim\"><span class=\"toc_number toc_depth_2\">6.2<\/span> Anycast, \u00e7ok b\u00f6lgeli mimari ve bak\u0131m<\/a><\/li><li><a href=\"#Uptime_izleme_ve_bakim_surecinin_olculmesi\"><span class=\"toc_number toc_depth_2\">6.3<\/span> Uptime izleme ve bak\u0131m s\u00fcrecinin \u00f6l\u00e7\u00fclmesi<\/a><\/li><\/ul><\/li><li><a href=\"#Sifira_Yakin_Kesinti_Icin_Blue-Green_Canary_ve_Staging_Stratejileri\"><span class=\"toc_number toc_depth_1\">7<\/span> S\u0131f\u0131ra Yak\u0131n Kesinti \u0130\u00e7in Blue-Green, Canary ve Staging Stratejileri<\/a><ul><li><a href=\"#Blue-Green_deployment\"><span class=\"toc_number toc_depth_2\">7.1<\/span> Blue-Green deployment<\/a><\/li><li><a href=\"#Canary_release\"><span class=\"toc_number toc_depth_2\">7.2<\/span> Canary release<\/a><\/li><li><a href=\"#Staging_ortami_ve_bakim_provasi\"><span class=\"toc_number toc_depth_2\">7.3<\/span> Staging ortam\u0131 ve bak\u0131m provas\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Cache_CDN_ve_stale-while-revalidate_ile_Bakim_Etkisini_Azaltmak\"><span class=\"toc_number toc_depth_1\">8<\/span> Cache, CDN ve stale-while-revalidate ile Bak\u0131m Etkisini Azaltmak<\/a><ul><li><a href=\"#stale-while-revalidate_ve_stale-if-error_kullanimi\"><span class=\"toc_number toc_depth_2\">8.1<\/span> stale-while-revalidate ve stale-if-error kullan\u0131m\u0131<\/a><\/li><li><a href=\"#Bakim_sirasinda_hangi_icerikler_cacheten_servis_edilebilir\"><span class=\"toc_number toc_depth_2\">8.2<\/span> Bak\u0131m s\u0131ras\u0131nda hangi i\u00e7erikler cache\u2019ten servis edilebilir?<\/a><\/li><\/ul><\/li><li><a href=\"#Adim_Adim_SEO_Kaybi_Yasamadan_Bakim_Modu_Uygulama_Kontrol_Listesi\"><span class=\"toc_number toc_depth_1\">9<\/span> Ad\u0131m Ad\u0131m: SEO Kayb\u0131 Ya\u015famadan Bak\u0131m Modu Uygulama Kontrol Listesi<\/a><ul><li><a href=\"#Bakim_oncesi\"><span class=\"toc_number toc_depth_2\">9.1<\/span> Bak\u0131m \u00f6ncesi<\/a><\/li><li><a href=\"#Bakim_sirasinda\"><span class=\"toc_number toc_depth_2\">9.2<\/span> Bak\u0131m s\u0131ras\u0131nda<\/a><\/li><li><a href=\"#Bakim_sonrasi\"><span class=\"toc_number toc_depth_2\">9.3<\/span> Bak\u0131m sonras\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_Olarak_Bakim_ve_Planli_Kesintileri_Nasil_Yonetiyoruz\"><span class=\"toc_number toc_depth_1\">10<\/span> DCHost Olarak Bak\u0131m ve Planl\u0131 Kesintileri Nas\u0131l Y\u00f6netiyoruz?<\/a><ul><li><a href=\"#1_Oncelik_Iletisim\"><span class=\"toc_number toc_depth_2\">10.1<\/span> 1. \u00d6ncelik: \u0130leti\u015fim<\/a><\/li><li><a href=\"#2_Teknik_dogruluk_HTTP_DNS_ve_cache_katmaninda_tutarlilik\"><span class=\"toc_number toc_depth_2\">10.2<\/span> 2. Teknik do\u011fruluk: HTTP, DNS ve cache katman\u0131nda tutarl\u0131l\u0131k<\/a><\/li><li><a href=\"#3_Olcum_ve_surekli_iyilestirme\"><span class=\"toc_number toc_depth_2\">10.3<\/span> 3. \u00d6l\u00e7\u00fcm ve s\u00fcrekli iyile\u015ftirme<\/a><\/li><\/ul><\/li><li><a href=\"#Sonuc_Bakim_Modu_Dogru_Kuruldugunda_SEO_Dusmaniniz_Degil_En_Iyi_Dostunuz\"><span class=\"toc_number toc_depth_1\">11<\/span> Sonu\u00e7: Bak\u0131m Modu Do\u011fru Kuruldu\u011funda SEO D\u00fc\u015fman\u0131n\u0131z De\u011fil, En \u0130yi Dostunuz<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Bakim_Modu_Neden_Bu_Kadar_Onemli\">Bak\u0131m Modu Neden Bu Kadar \u00d6nemli?<\/span><\/h2>\n<p>Bir projeyi planlarken mimari tasar\u0131m, kapasite analizi, veritaban\u0131 optimizasyonu ya da g\u00fcvenlik sertle\u015ftirmesi konu\u015fuldu\u011funda, masada genelde iki soru eksik kal\u0131r: \u201cBu de\u011fi\u015fiklikleri ne zaman canl\u0131ya alaca\u011f\u0131z?\u201d ve \u201cO s\u0131rada kullan\u0131c\u0131 ne g\u00f6recek?\u201d. Bak\u0131m modu ve planl\u0131 kesinti y\u00f6netimi tam da bu iki sorunun cevab\u0131d\u0131r. Do\u011fru kurgulanan bir maintenance page, hem SEO\u2019yu korur hem de kullan\u0131c\u0131ya profesyonel bir deneyim sunar. Yanl\u0131\u015f kurgulanan bir bak\u0131m sayfas\u0131 ise arama motorlar\u0131 g\u00f6z\u00fcnde sitenizi ge\u00e7ici sorun ya\u015fayan bir proje olmaktan \u00e7\u0131kar\u0131p kal\u0131c\u0131 olarak \u201cproblemli\u201d etiketine sokabilir.<\/p>\n<p>DCHost taraf\u0131nda y\u00fczlerce web sitesi, e-ticaret projesi ve SaaS uygulamas\u0131n\u0131n bak\u0131m s\u00fcre\u00e7lerine e\u015flik ederken g\u00f6rd\u00fc\u011f\u00fcm\u00fcz en kritik ger\u00e7ek \u015fu: <strong>Bak\u0131m modunu son dakikada a\u00e7\u0131lan bir eklenti ayar\u0131 gibi g\u00f6rmek, uzun vadeli SEO kayb\u0131n\u0131n en kestirme yolu<\/strong>. Oysa do\u011fru HTTP durum kodu, do\u011fru cache stratejisi, iyi planlanm\u0131\u015f DNS ve net bir ileti\u015fimle bak\u0131m s\u00fcreci hem arama motorlar\u0131 hem de kullan\u0131c\u0131lar i\u00e7in olduk\u00e7a p\u00fcr\u00fczs\u00fcz y\u00f6netilebilir. Bu rehberde, s\u0131f\u0131rdan u\u00e7tan uca bir \u201cbak\u0131m modu ve planl\u0131 kesinti\u201d stratejisini, sahada ger\u00e7ekten i\u015fe yarayan pratiklerle beraber ad\u0131m ad\u0131m ele alaca\u011f\u0131z.<\/p>\n<h2><span id=\"Yanlis_Bakim_Sayfasinin_SEOya_Verdigi_Zarar\">Yanl\u0131\u015f Bak\u0131m Sayfas\u0131n\u0131n SEO\u2019ya Verdi\u011fi Zarar<\/span><\/h2>\n<p>Maintenance page, \u00e7o\u011fu zaman \u201clogo, k\u0131sa bir metin, belki bir geri say\u0131m sayac\u0131\u201d gibi g\u00f6rsel detaylarla d\u00fc\u015f\u00fcn\u00fcl\u00fcr. Oysa SEO a\u00e7\u0131s\u0131ndan kritik olan; bu sayfay\u0131 <strong>hangi URL\u2019lerde, hangi HTTP stat\u00fc koduyla, hangi s\u00fcreyle ve nas\u0131l \u00f6nbelle\u011fe al\u0131nm\u0131\u015f halde<\/strong> sundu\u011funuzdur.<\/p>\n<h3><span id=\"En_sik_yapilan_hatalar\">En s\u0131k yap\u0131lan hatalar<\/span><\/h3>\n<ul>\n<li><strong>200 OK ile bak\u0131m sayfas\u0131 d\u00f6nmek:<\/strong> Arama motorlar\u0131 i\u00e7in her \u015fey yolunda mesaj\u0131 verirsiniz; halbuki ger\u00e7ekte kullan\u0131c\u0131ya i\u00e7erik sunmuyorsunuz. Bu, \u00f6zellikle saatler s\u00fcren bak\u0131mlarda ciddi s\u0131ralama kay\u0131plar\u0131na neden olabilir.<\/li>\n<li><strong>T\u00fcm siteyi 302 y\u00f6nlendirme ile \/bakim gibi tek sayfaya atmak:<\/strong> Arama motorlar\u0131 bu ge\u00e7ici y\u00f6nlendirmeleri s\u0131k g\u00f6r\u00fcrse, siteyi istikrars\u0131z ve sorunlu alg\u0131layabilir. Ayr\u0131ca canonical ve i\u00e7erik ba\u011flam\u0131 tamamen bozulur.<\/li>\n<li><strong>Uzun s\u00fcren 5xx hatalar\u0131:<\/strong> Sunucu hatalar\u0131 (\u00f6zellikle 500 ve 502) s\u0131k ve uzun s\u00fcreli g\u00f6r\u00fcl\u00fcrse, bot\u2019lar tarama frekans\u0131n\u0131 azalt\u0131r; kritik sayfalar\u0131n\u0131z daha seyrek g\u00fcncellenir, yeni i\u00e7erikleriniz ge\u00e7 indekslenir.<\/li>\n<li><strong>Bak\u0131m sayfas\u0131n\u0131 robots.txt ile tamamen kapatmak:<\/strong> K\u0131sa s\u00fcreli bak\u0131mlarda arama motorlar\u0131n\u0131n siteyi hi\u00e7 tarayamamas\u0131 gereksiz risk olu\u015fturur; yanl\u0131\u015f kurgulanm\u0131\u015f bir robots.txt, bak\u0131m sonras\u0131 bile taramay\u0131 bloke etmeye devam edebilir.<\/li>\n<\/ul>\n<p>HTTP stat\u00fc kodlar\u0131n\u0131n SEO ve tarama davran\u0131\u015f\u0131na etkisini daha derin okumak isterseniz, <a href='https:\/\/www.dchost.com\/blog\/http-durum-kodlari-seo-ve-hosting-icin-301-302-404-410-ve-5xx-rehberi\/'>HTTP durum kodlar\u0131n\u0131n SEO etkilerini ayr\u0131nt\u0131l\u0131 anlatt\u0131\u011f\u0131m\u0131z rehbere<\/a> mutlaka g\u00f6z at\u0131n.<\/p>\n<h3><span id=\"Dogru_yaklasim_503_Service_Unavailable_Retry-After\">Do\u011fru yakla\u015f\u0131m: 503 Service Unavailable + Retry-After<\/span><\/h3>\n<p>Arama motorlar\u0131na \u201c\u015fu an bak\u0131mday\u0131m ama bu durum ge\u00e7ici\u201d demenin standart yolu, <strong>503 Service Unavailable<\/strong> stat\u00fc kodudur. Bu yan\u0131ta ekleyece\u011finiz <strong>Retry-After<\/strong> ba\u015fl\u0131\u011f\u0131, bot\u2019lara ne zaman yeniden denemeleri gerekti\u011fini bildirir.<\/p>\n<p>\u00d6rnek HTTP ba\u015fl\u0131klar\u0131:<\/p>\n<pre>\nHTTP\/1.1 503 Service Unavailable\nRetry-After: 3600\nContent-Type: text\/html; charset=utf-8\n<\/pre>\n<p>Buradaki <code>Retry-After: 3600<\/code> de\u011feri, 3600 saniye (1 saat) sonra tekrar denemelerini \u00f6nerir. Bak\u0131m s\u00fcrenizi biliyorsan\u0131z, bu de\u011feri dakikaya yak\u0131n bir \u015fekilde ayarlamak idealdir. B\u00f6ylece Google gibi bot\u2019lar, bak\u0131m sonras\u0131 hemen geri gelmeye \u00e7al\u0131\u015f\u0131r ve SEO etkisini minimumda tutars\u0131n\u0131z.<\/p>\n<h2><span id=\"Planli_vs_Plansiz_Kesinti_Strateji_Nasil_Degisir\">Planl\u0131 vs Plans\u0131z Kesinti: Strateji Nas\u0131l De\u011fi\u015fir?<\/span><\/h2>\n<p>Bir bak\u0131m senaryosunu tasarlarken \u00f6nce \u015fu ayr\u0131m\u0131 netle\u015ftirmeniz gerekir: <strong>Planl\u0131 kesinti mi, plans\u0131z ar\u0131za m\u0131?<\/strong> \u00c7\u00fcnk\u00fc arama motorlar\u0131 ve kullan\u0131c\u0131lar a\u00e7\u0131s\u0131ndan verece\u011finiz mesaj farkl\u0131d\u0131r.<\/p>\n<h3><span id=\"Planli_bakim_ornek_versiyon_yukseltme_altyapi_degisikligi\">Planl\u0131 bak\u0131m (\u00f6rnek: versiyon y\u00fckseltme, altyap\u0131 de\u011fi\u015fikli\u011fi)<\/span><\/h3>\n<ul>\n<li>Bak\u0131m zaman\u0131 \u00f6nden duyurulabilir.<\/li>\n<li>Gece ge\u00e7 saatler veya trafi\u011fin d\u00fc\u015f\u00fck oldu\u011fu zaman dilimleri se\u00e7ilebilir.<\/li>\n<li>Bak\u0131m sayfas\u0131 tasarlanabilir, A\/B test edilebilir.<\/li>\n<li>Uygulama, veritaban\u0131 ve DNS taraf\u0131nda <strong>kontroll\u00fc bir ge\u00e7i\u015f plan\u0131<\/strong> haz\u0131rlanabilir.<\/li>\n<\/ul>\n<p>Planl\u0131 bak\u0131m i\u00e7in <strong>zero-downtime yakla\u015f\u0131m\u0131<\/strong> da tercih edilebilir. \u00d6rne\u011fin Blue-Green da\u011f\u0131t\u0131m ya da canary release gibi y\u00f6ntemlerle, neredeyse hi\u00e7 kesinti ya\u015fanmadan versiyon g\u00fcncellemesi yapabilirsiniz. Bu konuyu, <a href='https:\/\/www.dchost.com\/blog\/blue-green-deployment-ile-woocommerce-ve-laravel-uygulamalarini-sifir-kesintiyle-guncellemek\/'>Blue-Green deployment ile WooCommerce ve Laravel uygulamalar\u0131n\u0131 s\u0131f\u0131r kesintiyle g\u00fcncelleme rehberimizde<\/a> olduk\u00e7a detayl\u0131 tart\u0131\u015ft\u0131k.<\/p>\n<h3><span id=\"Plansiz_kesinti_ornek_donanim_arizasi_ani_yazilim_hatasi\">Plans\u0131z kesinti (\u00f6rnek: donan\u0131m ar\u0131zas\u0131, ani yaz\u0131l\u0131m hatas\u0131)<\/span><\/h3>\n<ul>\n<li>\u00c7o\u011fu zaman \u00f6nceden haber veremezsiniz.<\/li>\n<li>\u0130lk hedef, <strong>h\u0131zla anla\u015f\u0131l\u0131r bir bak\u0131m\/ar\u0131za sayfas\u0131<\/strong> g\u00f6stermek ve kullan\u0131c\u0131y\u0131 bo\u015f ekrandan kurtarmakt\u0131r.<\/li>\n<li>Ard\u0131ndan olabildi\u011fince h\u0131zl\u0131 \u015fekilde kal\u0131c\u0131 \u00e7\u00f6z\u00fcm\u00fc uygulamak gerekir.<\/li>\n<\/ul>\n<p>Plans\u0131z kesintilerde de m\u00fcmk\u00fcn oldu\u011funca 5xx hatas\u0131 yerine, <strong>503 + basit bir bak\u0131m sayfas\u0131<\/strong> sunmak SEO a\u00e7\u0131s\u0131ndan \u00e7ok daha sa\u011fl\u0131kl\u0131d\u0131r. Bu nedenle bak\u0131m modu kurgusunu sadece planl\u0131 g\u00fcncellemeler i\u00e7in de\u011fil, acil durumlar i\u00e7in de haz\u0131r tutmak gerekir.<\/p>\n<h2><span id=\"SEO_Dostu_Maintenance_Page_Icin_Teknik_Temeller\">SEO Dostu Maintenance Page \u0130\u00e7in Teknik Temeller<\/span><\/h2>\n<p>\u0130yi bir bak\u0131m sayfas\u0131 sadece g\u00fczel g\u00f6z\u00fcken bir HTML sayfa de\u011fildir. Arama motorlar\u0131, taray\u0131c\u0131lar ve proxy\/cache katmanlar\u0131yla do\u011fru konu\u015fabilen, teknik olarak temiz bir yan\u0131tt\u0131r. Ad\u0131m ad\u0131m bakal\u0131m.<\/p>\n<h3><span id=\"1_Dogru_HTTP_statu_kodunu_kullanmak\">1. Do\u011fru HTTP stat\u00fc kodunu kullanmak<\/span><\/h3>\n<ul>\n<li><strong>503 Service Unavailable:<\/strong> K\u0131sa s\u00fcreli bak\u0131m veya ge\u00e7ici sorunlar i\u00e7in idealdir. Bot\u2019lara \u201cdaha sonra gel\u201d mesaj\u0131 verir.<\/li>\n<li><strong>200 OK:<\/strong> Bak\u0131m sayfas\u0131 i\u00e7in kullanman\u0131z <strong>\u00f6nerilmez<\/strong>. Sadece \u00e7ok k\u0131sa, birka\u00e7 saniyelik deploy i\u015flemlerinde ve reverse proxy cache stratejileriyle birlikte kullan\u0131labilir.<\/li>\n<li><strong>302\/307 Redirect:<\/strong> T\u00fcm siteyi \/bakim URL\u2019sine y\u00f6nlendirmek SEO taraf\u0131nda gereksiz karma\u015fa yarat\u0131r; zorunlu de\u011filseniz kullanmay\u0131n.<\/li>\n<li><strong>5xx (500, 502, 504):<\/strong> K\u0131sa s\u00fcreli, beklenmedik hatalarda do\u011fal olarak olu\u015fabilir; uzun s\u00fcre bu hatalar\u0131 vermek tarama b\u00fct\u00e7enizi olumsuz etkiler.<\/li>\n<\/ul>\n<h3><span id=\"2_Retry-After_basligi_ile_botlari_dogru_yonlendirmek\">2. Retry-After ba\u015fl\u0131\u011f\u0131 ile bot\u2019lar\u0131 do\u011fru y\u00f6nlendirmek<\/span><\/h3>\n<p>Planlad\u0131\u011f\u0131n\u0131z bak\u0131m s\u00fcresine g\u00f6re <code>Retry-After<\/code> ba\u015fl\u0131\u011f\u0131n\u0131 saniye cinsinden ayarlayabilirsiniz. \u00d6rne\u011fin 30-45 dakikal\u0131k bir bak\u0131m i\u00e7in 1800\u20133600 aras\u0131 de\u011ferler mant\u0131kl\u0131d\u0131r. \u00c7ok uzun bak\u0131mlarda (\u00f6rne\u011fin 8\u201312 saat) arama motorlar\u0131n\u0131n sitenizi tamamen \u201ckapal\u0131\u201d sanmamas\u0131 i\u00e7in, <strong>kritik sayfalar i\u00e7in alternatif sunma<\/strong> (\u00f6rne\u011fin statik read-only kopya) stratejisi d\u00fc\u015f\u00fcn\u00fclebilir.<\/p>\n<h3><span id=\"3_robotstxt_ve_meta_robots_ayarlari\">3. robots.txt ve meta robots ayarlar\u0131<\/span><\/h3>\n<p>K\u0131sa s\u00fcreli bak\u0131mda genelde <strong>robots.txt ile siteyi kapatmak \u00f6nerilmez<\/strong>. Zaten 503 yan\u0131t\u0131 veriyorsan\u0131z, arama motorlar\u0131 bu durumu anlayacakt\u0131r. Dikkat etmeniz gerekenler:<\/p>\n<ul>\n<li>Bak\u0131m s\u00fcresince robots.txt dosyan\u0131z\u0131 de\u011fi\u015ftirmeyin; sonradan geri almay\u0131 unutmak b\u00fcy\u00fck risktir.<\/li>\n<li>Bak\u0131m sayfas\u0131nda <code>&lt;meta name='robots' content='noindex, nofollow'&gt;<\/code> kullanabilirsiniz; b\u00f6ylece bak\u0131m sayfas\u0131n\u0131n kendisi indekslenmez.<\/li>\n<li>Ana URL\u2019lerin (\u00f6rne\u011fin \/, \/kategori\/ vs.) 503 d\u00f6nmesi yeterlidir, ayr\u0131ca noindex vermenize gerek yoktur.<\/li>\n<\/ul>\n<h3><span id=\"4_Canonical_ve_yapilandirilmis_veri\">4. Canonical ve yap\u0131land\u0131r\u0131lm\u0131\u015f veri<\/span><\/h3>\n<p>Bak\u0131m sayfas\u0131 i\u00e7in ekstra canonical etiketi kullanmak genelde gerekmez; \u00f6nemli olan, <strong>bak\u0131m s\u0131ras\u0131nda orijinal URL\u2019leri bozmamak<\/strong> ve ge\u00e7ici bir durum sundu\u011funuzu net g\u00f6steren 503 yan\u0131t\u0131d\u0131r. Yap\u0131land\u0131r\u0131lm\u0131\u015f veriler (schema.org vb.) bak\u0131m an\u0131nda kritik de\u011fildir; hatta karma\u015fay\u0131 art\u0131rmamak ad\u0131na sade bir sayfa kullanmak daha sa\u011fl\u0131kl\u0131d\u0131r.<\/p>\n<h3><span id=\"5_Tarayici_ve_proxy_onbellegi_Cache-Control\">5. Taray\u0131c\u0131 ve proxy \u00f6nbelle\u011fi (Cache-Control)<\/span><\/h3>\n<p>Bak\u0131m sayfas\u0131n\u0131n taray\u0131c\u0131 ve ara katmanlarda sonsuza kadar cache\u2019lenmesi b\u00fcy\u00fck bir tuzakt\u0131r. \u015eu noktalara dikkat edin:<\/p>\n<ul>\n<li>Bak\u0131m yan\u0131t\u0131 i\u00e7in <code>Cache-Control: no-store, no-cache, must-revalidate, max-age=0<\/code> gibi agresif bir ayar kullanabilirsiniz.<\/li>\n<li>CDN kullan\u0131yorsan\u0131z, bak\u0131m sayfas\u0131 i\u00e7in \u00f6zel bir cache kural\u0131 yazarak, <strong>\u00e7ok k\u0131sa s\u00fcreli veya hi\u00e7 cache\u2019lenmeyecek<\/strong> \u015fekilde ayarlay\u0131n.<\/li>\n<li>Baz\u0131 durumlarda, sadece belirli POP\u2019larda k\u0131sa s\u00fcreli cache isteyebilirsiniz; bu durumda stale-while-revalidate ve stale-if-error gibi geli\u015fmi\u015f ba\u015fl\u0131klar devreye girer (buna birazdan gelece\u011fiz).<\/li>\n<\/ul>\n<p>CDN ve taray\u0131c\u0131 \u00f6nbelle\u011fi taraf\u0131nda daha derin ayarlar yapmak istiyorsan\u0131z, <a href='https:\/\/www.dchost.com\/blog\/cdn-ve-tarayici-onbelleginde-cache-busting-stratejileri\/'>CDN ve taray\u0131c\u0131 \u00f6nbelle\u011finde cache busting stratejilerini anlatt\u0131\u011f\u0131m\u0131z yaz\u0131<\/a> iyi bir tamamlay\u0131c\u0131 rehber olacakt\u0131r.<\/p>\n<h2><span id=\"Uygulama_Duzeyinde_Bakim_Modu_WordPress_Laravel_ve_Ozel_Yazilimlar\">Uygulama D\u00fczeyinde Bak\u0131m Modu: WordPress, Laravel ve \u00d6zel Yaz\u0131l\u0131mlar<\/span><\/h2>\n<p>Bak\u0131m modunu sadece web sunucusu seviyesinde de\u011fil, uygulama seviyesinde de kurgulayabilirsiniz. Fakat burada da SEO\u2019yu korumak i\u00e7in dikkat edilmesi gereken noktalar var.<\/p>\n<h3><span id=\"WordPress_bakim_modunda_sik_yapilan_hatalar\">WordPress bak\u0131m modunda s\u0131k yap\u0131lan hatalar<\/span><\/h3>\n<ul>\n<li>Pek \u00e7ok \u201cmaintenance mode\u201d eklentisi, sayfay\u0131 200 OK olarak d\u00f6ner ve sadece HTML i\u00e7eri\u011fi de\u011fi\u015ftirir.<\/li>\n<li>Bu eklentiler \u00e7o\u011fu zaman 503 veya Retry-After ba\u015fl\u0131klar\u0131n\u0131 eklemez.<\/li>\n<li>CDN ve \u00f6nbellek katmanlar\u0131yla entegre olmad\u0131klar\u0131 i\u00e7in, baz\u0131 b\u00f6lge ve kullan\u0131c\u0131larda hala eski sayfalar, baz\u0131lar\u0131nda bak\u0131m sayfas\u0131 g\u00f6r\u00fcn\u00fcr.<\/li>\n<\/ul>\n<p>E\u011fer uygulama seviyesinde bir bak\u0131m eklentisi kullanacaksan\u0131z, \u015fu kriterlere dikkat edin:<\/p>\n<ul>\n<li>Sunucu yan\u0131t kodunu <strong>503<\/strong> olarak ayarlayabiliyor mu?<\/li>\n<li><strong>Retry-After<\/strong> ba\u015fl\u0131\u011f\u0131 ekleyebiliyor mu?<\/li>\n<li>IP beyaz listeleme (admin ve ajans IP\u2019leri i\u00e7in) sunuyor mu?<\/li>\n<li>CDN ve reverse proxy arkas\u0131nda test edildi mi?<\/li>\n<\/ul>\n<h3><span id=\"Framework_tabanli_uygulamalar_Laravel_Symfony_vb\">Framework tabanl\u0131 uygulamalar (Laravel, Symfony vb.)<\/span><\/h3>\n<p>Laravel gibi framework\u2019lerde, global exception handler veya middleware d\u00fczeyinde bak\u0131m modu olu\u015fturmak yayg\u0131n bir pratiktir. Burada dikkat etmeniz gerekenler:<\/p>\n<ul>\n<li>Belli bir environment flag\u2019i (\u00f6rne\u011fin <code>APP_MAINTENANCE=true<\/code>) devredeyken, t\u00fcm istekleri \u00f6zel bir maintenance controller\u2019a y\u00f6nlendirin.<\/li>\n<li>Bu controller\u2019\u0131n <strong>her zaman 503 + Retry-After<\/strong> d\u00f6nd\u00fc\u011f\u00fcnden emin olun.<\/li>\n<li>Admin paneli, health-check endpoint\u2019leri ve uptime izleme URL\u2019leri i\u00e7in \u00f6zel istisnalar tan\u0131mlay\u0131n.<\/li>\n<\/ul>\n<p>Laravel ve benzeri uygulamalar\u0131 s\u0131f\u0131r kesinti hedefiyle yay\u0131na almak i\u00e7in, <a href='https:\/\/www.dchost.com\/blog\/laravel-uygulamalarini-vpste-nasil-yayinlarim-nginx-php%e2%80%91fpm-horizon-ve-sifir-kesinti-dagitimin-sicacik-yol-haritasi\/'>Laravel uygulamalar\u0131n\u0131 VPS \u00fczerinde yay\u0131nlama ve s\u0131f\u0131r kesinti da\u011f\u0131t\u0131m rehberimiz<\/a> de bak\u0131m stratejinizi \u00f6nemli \u00f6l\u00e7\u00fcde zenginle\u015ftirebilir.<\/p>\n<h3><span id=\"Statik_siteler_ve_headless_mimariler\">Statik siteler ve headless mimariler<\/span><\/h3>\n<p>Jamstack ya da headless WordPress\/Next.js gibi mimarilerde, \u00e7o\u011fu g\u00fcncelleme <strong>build + deploy<\/strong> s\u00fcrecinden ibarettir ve asl\u0131nda ger\u00e7ek bir bak\u0131m moduna bile gerek kalmayabilir. Do\u011fru kurgulanm\u0131\u015f bir CI\/CD hatt\u0131yla, yeni versiyonu farkl\u0131 bir klas\u00f6re veya sunucuya deploy edip, son anda sembolik link ya da load balancer y\u00f6nlendirmesiyle trafi\u011fi yeni s\u00fcr\u00fcme alabilirsiniz. Bu yakla\u015f\u0131m\u0131n temelini, <a href='https:\/\/www.dchost.com\/blog\/vpse-sifir-kesinti-ci-cd-nasil-kurulur-rsync-sembolik-surumler-ve-systemd-ile-sicacik-bir-yolculuk\/'>VPS\u2019e s\u0131f\u0131r kesinti CI\/CD kurulumu rehberimizde<\/a> detayl\u0131 anlatt\u0131k.<\/p>\n<h2><span id=\"DNS_ve_Altyapi_Perspektifinden_Planli_Kesinti_Yonetimi\">DNS ve Altyap\u0131 Perspektifinden Planl\u0131 Kesinti Y\u00f6netimi<\/span><\/h2>\n<p>Bak\u0131m modunu yaln\u0131zca uygulama geli\u015ftiricilerin konusu gibi g\u00f6rmek b\u00fcy\u00fck bir eksiklik. DNS, load balancer, reverse proxy, hatta veri taban\u0131 replikasyonu bile bu hik\u00e2yenin i\u00e7inde. \u00d6zellikle sunucu veya veri merkezi ta\u015f\u0131ma gibi b\u00fcy\u00fck de\u011fi\u015fikliklerde, DNS planlamas\u0131 kritik hale geliyor.<\/p>\n<h3><span id=\"TTL_stratejisi_Tasima_ve_bakim_oncesi_olmazsa_olmaz\">TTL stratejisi: Ta\u015f\u0131ma ve bak\u0131m \u00f6ncesi olmazsa olmaz<\/span><\/h3>\n<p>Planl\u0131 bir bak\u0131m veya ta\u015f\u0131ma \u00f6ncesinde, ilgili DNS kay\u0131tlar\u0131n\u0131z\u0131n TTL de\u011ferlerini \u00f6nceden d\u00fc\u015f\u00fcrmek, kesinti s\u00fcresini dramatik bi\u00e7imde k\u0131saltabilir. \u00d6rne\u011fin normalde 3600 saniye (1 saat) TTL kulland\u0131\u011f\u0131n\u0131z bir A kayd\u0131n\u0131, ta\u015f\u0131ma i\u015fleminden 24\u201348 saat \u00f6nce 300 veya 120 gibi d\u00fc\u015f\u00fck bir de\u011fere indirerek, cutover an\u0131nda de\u011fi\u015fikli\u011fin \u00e7ok daha h\u0131zl\u0131 yay\u0131lmas\u0131n\u0131 sa\u011flayabilirsiniz.<\/p>\n<p>Bu yakla\u015f\u0131m\u0131 detayl\u0131 ad\u0131mlar ve senaryolarla anlatt\u0131\u011f\u0131m\u0131z <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 stratejileri rehberi<\/a> ve <a href='https:\/\/www.dchost.com\/blog\/dns-ttl-degerlerini-dogru-ayarlamak-a-mx-cname-ve-txt-kayitlari-icin-stratejik-rehber\/'>DNS TTL de\u011ferlerini stratejik olarak ayarlama yaz\u0131s\u0131<\/a>, bak\u0131m plan\u0131n\u0131z\u0131 DNS taraf\u0131nda g\u00fc\u00e7lendirmek i\u00e7in iyi bir ba\u015flang\u0131\u00e7 noktas\u0131d\u0131r.<\/p>\n<h3><span id=\"Anycast_cok_bolgeli_mimari_ve_bakim\">Anycast, \u00e7ok b\u00f6lgeli mimari ve bak\u0131m<\/span><\/h3>\n<p>Daha geli\u015fmi\u015f altyap\u0131larda (Anycast DNS, \u00e7ok b\u00f6lgeli CDN, GeoDNS vb.) bak\u0131m modunu b\u00f6lgesel olarak uygulama imk\u00e2n\u0131n\u0131z da olabilir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Avrupa veri merkezinde bak\u0131m yaparken, ABD b\u00f6lgesindeki sunuculardan yay\u0131na devam etmek,<\/li>\n<li>Belirli bir POP\u2019ta (\u00f6rne\u011fin \u0130stanbul) bak\u0131mdayken di\u011fer POP\u2019lara trafi\u011fi kayd\u0131rmak,<\/li>\n<li>GeoDNS ile belirli \u00fclkeleri ge\u00e7ici olarak farkl\u0131 IP bloklar\u0131na y\u00f6nlendirmek.<\/li>\n<\/ul>\n<p>B\u00f6ylesi karma\u015f\u0131k senaryolarda dahi, d\u0131\u015far\u0131ya sundu\u011funuz cevaplar\u0131n HTTP ve DNS seviyesinde tutarl\u0131 olmas\u0131 gerekir. Aksi halde, baz\u0131 kullan\u0131c\u0131lar ger\u00e7ek siteyi, baz\u0131lar\u0131 ise bak\u0131m sayfas\u0131n\u0131 g\u00f6r\u00fcr; bu da hem kullan\u0131c\u0131 deneyimini hem de cache kalitesini bozar.<\/p>\n<h3><span id=\"Uptime_izleme_ve_bakim_surecinin_olculmesi\">Uptime izleme ve bak\u0131m s\u00fcrecinin \u00f6l\u00e7\u00fclmesi<\/span><\/h3>\n<p>Bak\u0131m modunun ger\u00e7ekten ne kadar s\u00fcrd\u00fc\u011f\u00fcn\u00fc, hangi URL\u2019lerde ne kadar 503 d\u00f6nd\u00fc\u011f\u00fcn\u00fcz\u00fc \u00f6l\u00e7meden iyile\u015ftirme yapman\u0131z m\u00fcmk\u00fcn de\u011fil. Basit ping kontrolleri yerine, <strong>HTTP i\u00e7erik ve stat\u00fc kodu odakl\u0131 uptime izleme<\/strong> kurgulamak \u00f6nemli bir ad\u0131md\u0131r. Bu konuda, <a href='https:\/\/www.dchost.com\/blog\/web-sitesi-uptime-izleme-ve-alarm-kurma-rehberi\/'>web sitesi uptime izleme ve alarm kurma rehberimizde<\/a> pratik bir ba\u015flang\u0131\u00e7 \u00e7er\u00e7evesi bulabilirsiniz.<\/p>\n<h2><span id=\"Sifira_Yakin_Kesinti_Icin_Blue-Green_Canary_ve_Staging_Stratejileri\">S\u0131f\u0131ra Yak\u0131n Kesinti \u0130\u00e7in Blue-Green, Canary ve Staging Stratejileri<\/span><\/h2>\n<p>E\u011fer hedefiniz \u201chi\u00e7 bak\u0131m moduna girmeden bile g\u00fcncelleme yapabilmek\u201d ise, klasik bak\u0131m sayfas\u0131 yakla\u015f\u0131m\u0131n\u0131 a\u015fman\u0131z gerekir. DCHost taraf\u0131nda \u00f6zellikle y\u00fcksek trafikli WordPress, WooCommerce ve SaaS projelerinde \u015fu stratejileri s\u0131k\u00e7a kullan\u0131yoruz:<\/p>\n<h3><span id=\"Blue-Green_deployment\">Blue-Green deployment<\/span><\/h3>\n<ul>\n<li>Blue ortam\u0131: Canl\u0131da \u00e7al\u0131\u015fan mevcut s\u00fcr\u00fcm.<\/li>\n<li>Green ortam\u0131: Yeni s\u00fcr\u00fcm\u00fcn tamamen haz\u0131rland\u0131\u011f\u0131, test edildi\u011fi ama trafi\u011fin hen\u00fcz gitmedi\u011fi ortam.<\/li>\n<li>Cutover an\u0131nda, load balancer veya Nginx upstream ayarlar\u0131yla trafi\u011fi Blue\u2019dan Green\u2019e al\u0131rs\u0131n\u0131z.<\/li>\n<li>Bir sorun \u00e7\u0131karsa, h\u0131zla Blue ortama geri d\u00f6nebilirsiniz.<\/li>\n<\/ul>\n<p>B\u00f6yle bir senaryoda bak\u0131m moduna \u00e7o\u011fu zaman gerek kalmaz; sadece \u00e7ok k\u0131sa konfig\u00fcrasyon ge\u00e7i\u015flerinde, baz\u0131 kullan\u0131c\u0131lar i\u00e7in milisaniyelik kesintiler olabilir. <a href='https:\/\/www.dchost.com\/blog\/blue-green-deployment-ile-woocommerce-ve-laravel-uygulamalarini-sifir-kesintiyle-guncellemek\/'>Blue-Green da\u011f\u0131t\u0131m rehberimiz<\/a> bu mimariyi WooCommerce ve Laravel \u00f6zelinde \u00f6rnekliyor; kavramlar t\u00fcm modern web uygulamalar\u0131 i\u00e7in ge\u00e7erli.<\/p>\n<h3><span id=\"Canary_release\">Canary release<\/span><\/h3>\n<p>Canary yakla\u015f\u0131m\u0131nda, yeni s\u00fcr\u00fcm\u00fc \u00f6nce trafi\u011fin k\u00fc\u00e7\u00fck bir y\u00fczdesine (\u00f6rne\u011fin %5) a\u00e7ars\u0131n\u0131z. Hata oranlar\u0131 ve metrikler normalse bu oran\u0131 kademeli olarak y\u00fckseltirsiniz. B\u00f6ylece b\u00fcy\u00fck bir hatay\u0131 t\u00fcm kullan\u0131c\u0131lar\u0131n\u0131z yerine sadece s\u0131n\u0131rl\u0131 bir grupta yakalama \u015fans\u0131n\u0131z olur. Bak\u0131m sayfas\u0131 yerine, gerekli oldu\u011funda trafi\u011fi an\u0131nda eski s\u00fcr\u00fcme d\u00f6nd\u00fcrmek m\u00fcmk\u00fcn hale gelir.<\/p>\n<h3><span id=\"Staging_ortami_ve_bakim_provasi\">Staging ortam\u0131 ve bak\u0131m provas\u0131<\/span><\/h3>\n<p>Bak\u0131m modunu da canl\u0131ya \u00e7\u0131kmadan \u00f6nce staging ortam\u0131nda prova etmek \u00e7ok kritik bir ad\u0131md\u0131r:<\/p>\n<ul>\n<li>Baz\u0131 staging alan adlar\u0131na, test ama\u00e7l\u0131 503 d\u00f6nd\u00fcrebilir ve bot\u2019lar\u0131n davran\u0131\u015f\u0131n\u0131 g\u00f6zlemleyebilirsiniz.<\/li>\n<li>CDN, WAF ve reverse proxy katmanlar\u0131n\u0131z\u0131n bak\u0131m sayfas\u0131n\u0131 nas\u0131l cache\u2019ledi\u011fini, hangi b\u00f6lgelerde nas\u0131l davrand\u0131\u011f\u0131n\u0131 \u00f6l\u00e7ebilirsiniz.<\/li>\n<li>Deploy pipeline\u2019\u0131n\u0131z\u0131n \u201cbak\u0131m moduna al \u2192 update \u2192 bak\u0131m modundan \u00e7\u0131k\u201d s\u0131ras\u0131n\u0131 otomatikle\u015ftirebilirsiniz.<\/li>\n<\/ul>\n<h2><span id=\"Cache_CDN_ve_stale-while-revalidate_ile_Bakim_Etkisini_Azaltmak\">Cache, CDN ve stale-while-revalidate ile Bak\u0131m Etkisini Azaltmak<\/span><\/h2>\n<p>Bak\u0131m s\u0131ras\u0131nda siteyi tamamen kapatmak zorunda de\u011filsiniz. Do\u011fru \u00f6nbellek stratejileri ile, kullan\u0131c\u0131lar\u0131n b\u00fcy\u00fck b\u00f6l\u00fcm\u00fc i\u00e7in site \u201c\u00e7al\u0131\u015f\u0131yormu\u015f gibi\u201d g\u00f6r\u00fcnmeye devam edebilir.<\/p>\n<h3><span id=\"stale-while-revalidate_ve_stale-if-error_kullanimi\">stale-while-revalidate ve stale-if-error kullan\u0131m\u0131<\/span><\/h3>\n<p>HTTP cache ba\u015fl\u0131klar\u0131nda <code>stale-while-revalidate<\/code> ve <code>stale-if-error<\/code> direktiflerini kullanarak, backend\u2019iniz bak\u0131mdayken bile CDN veya reverse proxy katman\u0131ndan <strong>eski ama \u00e7al\u0131\u015f\u0131r bir kopya<\/strong> sunabilirsiniz. \u00d6rne\u011fin:<\/p>\n<pre>\nCache-Control: public, max-age=300, stale-while-revalidate=600, stale-if-error=86400\n<\/pre>\n<ul>\n<li>max-age=300: 5 dakika boyunca taze kabul edilir.<\/li>\n<li>stale-while-revalidate=600: 10 dakika boyunca, arka planda yenilenirken kullan\u0131c\u0131ya eski i\u00e7erik sunulabilir.<\/li>\n<li>stale-if-error=86400: Backend 5xx verdi\u011finde, 1 g\u00fcn boyunca dahi eski i\u00e7erik kullan\u0131labilir.<\/li>\n<\/ul>\n<p>Bu konuyu ger\u00e7ek senaryolarla anlatt\u0131\u011f\u0131m\u0131z <a href='https:\/\/www.dchost.com\/blog\/kesinti-caninizi-sikmasin-stale-while-revalidate-ve-stale-if-error-nasil-hayat-kurtarir\/'>stale-while-revalidate ve stale-if-error rehberimizi<\/a> \u00f6zellikle okuman\u0131z\u0131 \u00f6neririz; planl\u0131 bak\u0131m senaryolar\u0131 i\u00e7in adeta \u201csigorta poli\u00e7esi\u201d gibidir.<\/p>\n<h3><span id=\"Bakim_sirasinda_hangi_icerikler_cacheten_servis_edilebilir\">Bak\u0131m s\u0131ras\u0131nda hangi i\u00e7erikler cache\u2019ten servis edilebilir?<\/span><\/h3>\n<ul>\n<li>Statik sayfalar (blog yaz\u0131lar\u0131, kurumsal i\u00e7erikler).<\/li>\n<li>\u00dcr\u00fcn listeleri (stok ve fiyat anl\u0131k de\u011fi\u015fmiyorsa).<\/li>\n<li>\u00d6nceden haz\u0131rlanm\u0131\u015f statik HTML snapshot\u2019lar.<\/li>\n<\/ul>\n<p>\u00d6deme ad\u0131m\u0131, kullan\u0131c\u0131 profil sayfalar\u0131 gibi dinamik ve g\u00fcvenlik kritik b\u00f6l\u00fcmlerde ise genellikle bak\u0131m sayfas\u0131 g\u00f6stermek daha do\u011frudur. Bu ayr\u0131m\u0131 net yapmazsan\u0131z, bak\u0131m sonras\u0131 \u201chatal\u0131 sipari\u015f\u201d, \u201cyanl\u0131\u015f stok\u201d gibi daha ciddi problemler do\u011fabilir.<\/p>\n<h2><span id=\"Adim_Adim_SEO_Kaybi_Yasamadan_Bakim_Modu_Uygulama_Kontrol_Listesi\">Ad\u0131m Ad\u0131m: SEO Kayb\u0131 Ya\u015famadan Bak\u0131m Modu Uygulama Kontrol Listesi<\/span><\/h2>\n<p>\u015eimdiye kadar anlatt\u0131klar\u0131m\u0131z\u0131, pratikte uygulayabilece\u011finiz bir kontrol listesine d\u00f6n\u00fc\u015ft\u00fcrelim. DCHost taraf\u0131nda kendi i\u00e7 s\u00fcre\u00e7lerimizde de benzer bir checklist kullan\u0131yoruz.<\/p>\n<h3><span id=\"Bakim_oncesi\">Bak\u0131m \u00f6ncesi<\/span><\/h3>\n<ol>\n<li><strong>Kapsam\u0131 netle\u015ftirin:<\/strong> Hangi sunucular, hangi servisler, hangi URL\u2019ler etkilenecek?<\/li>\n<li><strong>Zaman\u0131 belirleyin:<\/strong> Trafi\u011fin en d\u00fc\u015f\u00fck oldu\u011fu saat aral\u0131\u011f\u0131n\u0131 se\u00e7in.<\/li>\n<li><strong>DNS TTL d\u00fc\u015f\u00fcr\u00fcn:<\/strong> Ta\u015f\u0131ma veya IP de\u011fi\u015fimi varsa, ilgili A\/AAAA\/CNAME kay\u0131tlar\u0131n\u0131n TTL de\u011ferlerini 24\u201348 saat \u00f6nceden d\u00fc\u015f\u00fcr\u00fcn.<\/li>\n<li><strong>Bak\u0131m sayfas\u0131n\u0131 haz\u0131rlay\u0131n:<\/strong> Markan\u0131za uygun, sade, h\u0131zl\u0131 y\u00fcklenen bir HTML \u015fablonu olu\u015fturun.<\/li>\n<li><strong>HTTP stat\u00fc kodunu test edin:<\/strong> Bak\u0131m sayfas\u0131 kesinlikle 503 d\u00f6nmeli; bunu staging ortam\u0131nda do\u011frulay\u0131n.<\/li>\n<li><strong>Retry-After s\u00fcresini belirleyin:<\/strong> Planlanan bak\u0131m s\u00fcresine g\u00f6re ger\u00e7ek\u00e7i bir de\u011fer hesaplay\u0131n.<\/li>\n<li><strong>CDN ve proxy kurallar\u0131n\u0131 yaz\u0131n:<\/strong> Bak\u0131m sayfas\u0131 i\u00e7in \u00f6zel cache kurallar\u0131 olu\u015fturun, a\u015f\u0131r\u0131 cache\u2019lenmesinin \u00f6n\u00fcne ge\u00e7in.<\/li>\n<li><strong>Uptime izleme ve alarm\u0131 haz\u0131rlay\u0131n:<\/strong> Bak\u0131m ba\u015flang\u0131c\u0131 ve biti\u015finde tetiklenecek alarmlar\u0131 \/ health-check endpoint\u2019lerini g\u00fcncelleyin.<\/li>\n<\/ol>\n<h3><span id=\"Bakim_sirasinda\">Bak\u0131m s\u0131ras\u0131nda<\/span><\/h3>\n<ol>\n<li>Uygulama veya web sunucusunu bak\u0131m moduna al\u0131n (503 + Retry-After + bak\u0131m sayfas\u0131).<\/li>\n<li>Admin ve teknik ekip IP\u2019lerini beyaz listeye alarak ger\u00e7ek siteyi g\u00f6rebilmelerini sa\u011flay\u0131n.<\/li>\n<li>Uptime ve log\u2019lar \u00fczerinden, beklenmeyen 5xx hatalar\u0131n\u0131, y\u00f6nlendirme d\u00f6ng\u00fclerini ve cache anomalilerini izleyin.<\/li>\n<li>Veritaban\u0131 ve dosya i\u015flemlerini planlad\u0131\u011f\u0131n\u0131z s\u0131raya g\u00f6re tamamlay\u0131n; gerekti\u011finde read-only moda ge\u00e7in.<\/li>\n<li>Bak\u0131m s\u00fcresini uzatman\u0131z gerekirse, Retry-After ba\u015fl\u0131\u011f\u0131n\u0131 g\u00fcncelleyin veya kullan\u0131c\u0131ya bak\u0131m sayfas\u0131 \u00fczerinde yeni tahmini s\u00fcreyi net \u015fekilde belirtin.<\/li>\n<\/ol>\n<h3><span id=\"Bakim_sonrasi\">Bak\u0131m sonras\u0131<\/span><\/h3>\n<ol>\n<li>Bak\u0131m modunu kapatmadan \u00f6nce, admin\/test kullan\u0131c\u0131lar\u0131 ile <strong>kritik ak\u0131\u015flar\u0131 manuel test edin<\/strong> (giri\u015f, sepet, \u00f6deme, form g\u00f6nderimi vb.).<\/li>\n<li>503 ve bak\u0131m sayfas\u0131 yan\u0131tlar\u0131n\u0131 devre d\u0131\u015f\u0131 b\u0131rak\u0131n; normal 200 yan\u0131tlar\u0131na geri d\u00f6n\u00fcn.<\/li>\n<li>CDN ve reverse proxy cache\u2019lerini k\u0131smen veya tamamen temizleyin; b\u00fcy\u00fck sitelerde kritik sayfalar i\u00e7in targeted purge uygulay\u0131n.<\/li>\n<li>DNS TTL de\u011ferlerini eski (daha y\u00fcksek) seviyelerine geri al\u0131n.<\/li>\n<li>Uptime ve log\u2019lar \u00fczerinden canl\u0131ya d\u00f6n\u00fc\u015f\u00fc izleyin; beklenmeyen 4xx\/5xx art\u0131\u015flar\u0131n\u0131 analiz edin.<\/li>\n<li>Bak\u0131m s\u00fcresini, ya\u015fanan sorunlar\u0131 ve al\u0131nan dersleri k\u0131sa bir \u201cpost-mortem\u201d dok\u00fcman\u0131na aktar\u0131n.<\/li>\n<\/ol>\n<p>Hosting taraf\u0131ndaki SEO ve performans kontrollerini sistematik hale getirmek i\u00e7in, yeni bir site yay\u0131na al\u0131rken dikkat edilmesi gerekenleri <a href='https:\/\/www.dchost.com\/blog\/yeni-web-sitesi-yayina-alirken-hosting-tarafinda-seo-ve-performans-kontrol-listesi\/'>ayr\u0131 bir SEO ve performans kontrol listesi<\/a> olarak detayland\u0131rd\u0131k; bak\u0131m sonras\u0131 kontrolleriniz i\u00e7in de iyi bir referans olacakt\u0131r.<\/p>\n<h2><span id=\"DCHost_Olarak_Bakim_ve_Planli_Kesintileri_Nasil_Yonetiyoruz\">DCHost Olarak Bak\u0131m ve Planl\u0131 Kesintileri Nas\u0131l Y\u00f6netiyoruz?<\/span><\/h2>\n<p>DCHost taraf\u0131nda, ister <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a> olsun ister <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a>, dedicated veya colocation altyap\u0131s\u0131, bak\u0131m ve planl\u0131 kesintileri her zaman <strong>\u201cileti\u015fim + teknik do\u011fruluk + \u00f6l\u00e7\u00fcm\u201d<\/strong> \u00fc\u00e7geninde ele al\u0131yoruz.<\/p>\n<h3><span id=\"1_Oncelik_Iletisim\">1. \u00d6ncelik: \u0130leti\u015fim<\/span><\/h3>\n<ul>\n<li>M\u00fcmk\u00fcn olan her durumda, m\u00fc\u015fterilerimizi bak\u0131m \u00f6ncesinde bilgilendiriyoruz.<\/li>\n<li>Tahmini s\u00fcre, etkilenen servisler ve olas\u0131 riskler hakk\u0131nda net ve sade bir dil kullan\u0131yoruz.<\/li>\n<li>Uzayan bak\u0131mlarda, g\u00fcncel durumu \u015feffaf \u015fekilde payla\u015f\u0131yoruz.<\/li>\n<\/ul>\n<h3><span id=\"2_Teknik_dogruluk_HTTP_DNS_ve_cache_katmaninda_tutarlilik\">2. Teknik do\u011fruluk: HTTP, DNS ve cache katman\u0131nda tutarl\u0131l\u0131k<\/span><\/h3>\n<ul>\n<li>Bak\u0131m sayfalar\u0131nda daima do\u011fru HTTP stat\u00fc kodlar\u0131n\u0131 kullanmaya \u00f6zen g\u00f6steriyoruz.<\/li>\n<li>DNS ve TTL planlamas\u0131n\u0131, b\u00fcy\u00fck ge\u00e7i\u015fler \u00f6ncesinde g\u00fcnler \u00f6ncesinden devreye al\u0131yoruz.<\/li>\n<li>CDN, WAF ve reverse proxy kurallar\u0131n\u0131 staging ortamlar\u0131nda test ederek s\u00fcrprizleri minimuma indiriyoruz.<\/li>\n<\/ul>\n<h3><span id=\"3_Olcum_ve_surekli_iyilestirme\">3. \u00d6l\u00e7\u00fcm ve s\u00fcrekli iyile\u015ftirme<\/span><\/h3>\n<ul>\n<li>Her bak\u0131m sonras\u0131nda ger\u00e7ekle\u015fen ger\u00e7ek kesinti s\u00fcresini, 5xx\/503 oranlar\u0131n\u0131 ve kullan\u0131c\u0131 geri bildirimlerini analiz ediyoruz.<\/li>\n<li>Gerekirse bak\u0131m s\u00fcre\u00e7lerimizi CI\/CD, blue-green veya canary mimarileriyle daha da otomatik hale getiriyoruz.<\/li>\n<li>\u00d6\u011frendi\u011fimiz dersleri hem i\u00e7 dok\u00fcmantasyonumuza hem de bu tarz rehber yaz\u0131lara yans\u0131t\u0131yoruz.<\/li>\n<\/ul>\n<h2><span id=\"Sonuc_Bakim_Modu_Dogru_Kuruldugunda_SEO_Dusmaniniz_Degil_En_Iyi_Dostunuz\">Sonu\u00e7: Bak\u0131m Modu Do\u011fru Kuruldu\u011funda SEO D\u00fc\u015fman\u0131n\u0131z De\u011fil, En \u0130yi Dostunuz<\/span><\/h2>\n<p>Bak\u0131m modu ve planl\u0131 kesinti y\u00f6netimi, \u00e7o\u011fu ekibin ancak sorun ya\u015fad\u0131ktan sonra ciddiye ald\u0131\u011f\u0131 bir konu. Oysa do\u011fru kurguland\u0131\u011f\u0131nda, bak\u0131m s\u00fcreci sitenizin g\u00fcvenilirli\u011fini, markan\u0131z\u0131n profesyonel alg\u0131s\u0131n\u0131 ve SEO sa\u011fl\u0131\u011f\u0131n\u0131z\u0131 g\u00fc\u00e7lendiren bir ara\u00e7 haline gelir. Do\u011fru HTTP stat\u00fc kodlar\u0131, iyi planlanm\u0131\u015f DNS TTL de\u011ferleri, ak\u0131ll\u0131 cache stratejileri ve m\u00fcmk\u00fcn oldu\u011funda s\u0131f\u0131r kesintiye yak\u0131n da\u011f\u0131t\u0131m y\u00f6ntemleriyle, kullan\u0131c\u0131lar\u0131n\u0131z\u0131n b\u00fcy\u00fck b\u00f6l\u00fcm\u00fc bak\u0131m\u0131n varl\u0131\u011f\u0131n\u0131 bile fark etmeyebilir.<\/p>\n<p>DCHost olarak deneyimimiz \u015funu g\u00f6steriyor: <strong>Bak\u0131m modunu \u201cpanik an\u0131nda a\u00e7\u0131lan bir switch\u201d de\u011fil, mimarinin tasar\u0131m a\u015famas\u0131nda planlanan bir bile\u015fen<\/strong> haline getirdi\u011finiz anda oyunun kurallar\u0131 de\u011fi\u015fiyor. \u0130ster k\u00fc\u00e7\u00fck bir blog, ister yo\u011fun trafikli bir e-ticaret sitesi veya SaaS \u00fcr\u00fcn\u00fc y\u00f6netin; bak\u0131m s\u00fcre\u00e7lerinizi \u015fimdiden tasarlamak, ileride ya\u015fayabilece\u011finiz SEO kay\u0131plar\u0131n\u0131 ve itibar risklerini b\u00fcy\u00fck \u00f6l\u00e7\u00fcde \u00f6nler.<\/p>\n<p>E\u011fer altyap\u0131n\u0131z\u0131 bak\u0131m dostu hale getirmek, zero-downtime da\u011f\u0131t\u0131m senaryolar\u0131 kurmak veya mevcut DCHost hizmetleriniz \u00fczerinde bak\u0131m s\u00fcrecini birlikte tasarlamak isterseniz, teknik ekibimiz bu rehberde anlatt\u0131\u011f\u0131m\u0131z prensipleri ger\u00e7ek projelerinize uygulaman\u0131za yard\u0131mc\u0131 olmaya haz\u0131r. Do\u011fru planlanm\u0131\u015f bir maintenance page ile, bir sonraki g\u00fcncellemenizi sakin ve kontroll\u00fc bir \u015fekilde hayata ge\u00e7irmeniz fazlas\u0131yla m\u00fcmk\u00fcn.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Bak\u0131m Modu Neden Bu Kadar \u00d6nemli?2 Yanl\u0131\u015f Bak\u0131m Sayfas\u0131n\u0131n SEO\u2019ya Verdi\u011fi Zarar2.1 En s\u0131k yap\u0131lan hatalar2.2 Do\u011fru yakla\u015f\u0131m: 503 Service Unavailable + Retry-After3 Planl\u0131 vs Plans\u0131z Kesinti: Strateji Nas\u0131l De\u011fi\u015fir?3.1 Planl\u0131 bak\u0131m (\u00f6rnek: versiyon y\u00fckseltme, altyap\u0131 de\u011fi\u015fikli\u011fi)3.2 Plans\u0131z kesinti (\u00f6rnek: donan\u0131m ar\u0131zas\u0131, ani yaz\u0131l\u0131m hatas\u0131)4 SEO Dostu Maintenance Page \u0130\u00e7in Teknik Temeller4.1 1. Do\u011fru [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4032,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4031","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\/4031","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=4031"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4031\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4032"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4031"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4031"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4031"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}