{"id":5740,"date":"2026-09-23T09:16:44","date_gmt":"2026-09-23T06:16:44","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/?p=5740"},"modified":"2026-09-23T06:17:25","modified_gmt":"2026-09-23T03:17:25","slug":"googlebot-5xx-hatalari-hosting-kaynakli-crawl-sorunlari","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/googlebot-5xx-hatalari-hosting-kaynakli-crawl-sorunlari\/","title":{"rendered":"Googlebot 5xx Hatalar\u0131: Hosting Kaynakl\u0131 Crawl Sorunlar\u0131"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div class=\"aiw-summary\">\n<p class=\"aiw-box-title\">H\u0131zl\u0131 \u00f6zet<\/p>\n<p>Googlebot 5xx hatalar\u0131, Googlebot&#8217;un sitenizden 500, 502, 503, 504 gibi sunucu tarafl\u0131 hata yan\u0131tlar\u0131 almas\u0131d\u0131r. Sorun; uygulama, hosting kaynaklar\u0131, a\u011f ge\u00e7idi, g\u00fcvenlik katman\u0131 veya ge\u00e7ici eri\u015fim kesintilerinden kaynaklanabilir.<\/p>\n<ul>\n<li>Search Console verisini sunucu eri\u015fim loglar\u0131, uptime kay\u0131tlar\u0131 ve uygulama loglar\u0131yla ayn\u0131 zaman aral\u0131\u011f\u0131nda kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/li>\n<li>5xx t\u00fcr\u00fcn\u00fc ay\u0131r\u0131n: 500 uygulama veya yap\u0131land\u0131rma hatas\u0131na, 502 ve 504 upstream sorunlar\u0131na, 503 ise ge\u00e7ici kapasite ya da bak\u0131m durumuna i\u015faret edebilir.<\/li>\n<li>PHP-FPM web i\u015f\u00e7ileri ile CLI cron veya kuyruk i\u015f\u00e7ilerini ayr\u0131 de\u011ferlendirin. HTTP \u00e7a\u011fr\u0131s\u0131 yapmayan bir CLI i\u015fi FPM i\u015f\u00e7isi t\u00fcketmez; ortak CPU, RAM, disk veya veritaban\u0131 kaynaklar\u0131n\u0131 yine de etkileyebilir.<\/li>\n<li>Kaynak limitini art\u0131rmadan \u00f6nce hangi s\u0131n\u0131r\u0131n doldu\u011funu kan\u0131tlay\u0131n. Dar kapsaml\u0131 de\u011fi\u015fiklikten sonra ayn\u0131 URL t\u00fcr\u00fc ve zaman aral\u0131\u011f\u0131yla sonucu do\u011frulay\u0131n.<\/li>\n<\/ul>\n<\/div>\n<p>Google Search Console&#8217;da tarama istatistiklerinde 5xx hatalar\u0131 g\u00f6r\u00fcyorsan\u0131z \u00f6nce Googlebot&#8217;u engelleyen bir SEO ayar\u0131 aramak yerine, sunucunun ilgili iste\u011fe hangi yan\u0131t\u0131 verdi\u011fini bulun. Googlebot 5xx hatalar\u0131 \u00e7o\u011funlukla robots.txt veya meta robots kural\u0131ndan de\u011fil, HTTP iste\u011finin sunucu taraf\u0131nda ba\u015far\u0131s\u0131z olmas\u0131ndan kaynaklan\u0131r.<\/p>\n<p>Hata k\u0131sa s\u00fcreliyse Google yeniden deneme yapabilir. Belirli URL&#8217;lerde veya saatlerde tekrarlanan hatalar ise tarama kapasitesini azaltabilir, yeni i\u00e7eriklerin ke\u015ffini geciktirebilir ve ayn\u0131 sayfalarda kullan\u0131c\u0131 hatalar\u0131na yol a\u00e7abilir. Te\u015fhisi Googlebot&#8217;a \u00f6zel varsay\u0131mlarla de\u011fil, zaman e\u015fle\u015ftirilmi\u015f sunucu kan\u0131tlar\u0131yla y\u00fcr\u00fct\u00fcn.<\/p>\n<div id=\"toc_container\" role=\"navigation\" aria-label=\"Table of Contents\" data-nosnippet class=\"toc_transparent no_bullets toc_numbered toc_title_center\"><p class=\"toc_title\">\u0130\u00e7indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#Googlebot_5xx_hatalari_ne_anlama_gelir\"><span class=\"toc_number toc_depth_1\">1.<\/span> Googlebot 5xx hatalar\u0131 ne anlama gelir?<\/a><ul><li><a href=\"#5xx_kodlarini_birbirinden_ayirin\"><span class=\"toc_number toc_depth_2\">1.1.<\/span> 5xx kodlar\u0131n\u0131 birbirinden ay\u0131r\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#Once_hatanin_zamanini_ve_kapsamini_belirleyin\"><span class=\"toc_number toc_depth_1\">2.<\/span> \u00d6nce hatan\u0131n zaman\u0131n\u0131 ve kapsam\u0131n\u0131 belirleyin<\/a><ul><li><a href=\"#Search_Console_verisini_daraltin\"><span class=\"toc_number toc_depth_2\">2.1.<\/span> Search Console verisini daralt\u0131n<\/a><\/li><li><a href=\"#Erisim_loglarinda_Googlebot_istegini_bulun\"><span class=\"toc_number toc_depth_2\">2.2.<\/span> Eri\u015fim loglar\u0131nda Googlebot iste\u011fini bulun<\/a><\/li><\/ul><\/li><li><a href=\"#Hosting_kaynaklari_ve_uygulama_katmanini_inceleyin\"><span class=\"toc_number toc_depth_1\">3.<\/span> Hosting kaynaklar\u0131 ve uygulama katman\u0131n\u0131 inceleyin<\/a><ul><li><a href=\"#PHP-FPM_web_iscileri_ile_CLI_islerini_ayirin\"><span class=\"toc_number toc_depth_2\">3.1.<\/span> PHP-FPM web i\u015f\u00e7ileri ile CLI i\u015flerini ay\u0131r\u0131n<\/a><\/li><li><a href=\"#Kaynak_limitlerini_kanitlayin\"><span class=\"toc_number toc_depth_2\">3.2.<\/span> Kaynak limitlerini kan\u0131tlay\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#Timeout_ve_proxy_zincirini_kontrol_edin\"><span class=\"toc_number toc_depth_1\">4.<\/span> Timeout ve proxy zincirini kontrol edin<\/a><ul><li><a href=\"#Timeout_degerlerini_dar_kapsamda_ele_alin\"><span class=\"toc_number toc_depth_2\">4.1.<\/span> Timeout de\u011ferlerini dar kapsamda ele al\u0131n<\/a><\/li><\/ul><\/li><li><a href=\"#Gecici_5xx_artislarini_nasil_dogrularsiniz\"><span class=\"toc_number toc_depth_1\">5.<\/span> Ge\u00e7ici 5xx art\u0131\u015flar\u0131n\u0131 nas\u0131l do\u011frulars\u0131n\u0131z?<\/a><\/li><li><a href=\"#Googlebot8217a_ozel_engelleme_ile_5xx_sorununu_ayirin\"><span class=\"toc_number toc_depth_1\">6.<\/span> Googlebot&#8217;a \u00f6zel engelleme ile 5xx sorununu ay\u0131r\u0131n<\/a><\/li><li><a href=\"#Dar_kapsamli_duzeltme_ve_dogrulama_plani\"><span class=\"toc_number toc_depth_1\">7.<\/span> Dar kapsaml\u0131 d\u00fczeltme ve do\u011frulama plan\u0131<\/a><\/li><li><a href=\"#Sik_Sorulan_Sorular\"><span class=\"toc_number toc_depth_1\">8.<\/span> S\u0131k Sorulan Sorular<\/a><ul><li><a href=\"#Googlebot_5xx_hatalari_siralamayi_hemen_dusurur_mu\"><span class=\"toc_number toc_depth_2\">8.1.<\/span> Googlebot 5xx hatalar\u0131 s\u0131ralamay\u0131 hemen d\u00fc\u015f\u00fcr\u00fcr m\u00fc?<\/a><\/li><li><a href=\"#Googlebot_icin_ayri_bir_sunucu_plani_gerekir_mi\"><span class=\"toc_number toc_depth_2\">8.2.<\/span> Googlebot i\u00e7in ayr\u0131 bir sunucu plan\u0131 gerekir mi?<\/a><\/li><li><a href=\"#5xx_hatasi_icin_URL8217yi_Search_Console8217da_tekrar_test_etmek_yeterli_midir\"><span class=\"toc_number toc_depth_2\">8.3.<\/span> 5xx hatas\u0131 i\u00e7in URL&#8217;yi Search Console&#8217;da tekrar test etmek yeterli midir?<\/a><\/li><li><a href=\"#CDN_kullanmak_5xx_sorununu_tamamen_cozer_mi\"><span class=\"toc_number toc_depth_2\">8.4.<\/span> CDN kullanmak 5xx sorununu tamamen \u00e7\u00f6zer mi?<\/a><\/li><\/ul><\/li><li><a href=\"#Son_kontrol_listesi\"><span class=\"toc_number toc_depth_1\">9.<\/span> Son kontrol listesi<\/a><\/li><\/ul><\/div>\n<h2><span id=\"Googlebot_5xx_hatalari_ne_anlama_gelir\">Googlebot 5xx hatalar\u0131 ne anlama gelir?<\/span><\/h2>\n<p>HTTP 5xx kodlar\u0131, iste\u011fi alan sunucunun iste\u011fi ba\u015far\u0131yla tamamlayamad\u0131\u011f\u0131n\u0131 g\u00f6sterir. Googlebot bir sayfay\u0131, g\u00f6rseli, JavaScript dosyas\u0131n\u0131 veya robots.txt dosyas\u0131n\u0131 isterken 5xx yan\u0131t\u0131 alabilir. Search Console&#8217;daki kay\u0131t, Google&#8217;\u0131n tarama an\u0131ndaki g\u00f6zlemidir; tek ba\u015f\u0131na hatan\u0131n hosting sa\u011flay\u0131c\u0131s\u0131ndan kaynakland\u0131\u011f\u0131n\u0131 kan\u0131tlamaz.<\/p>\n<p>Uygulama veritaban\u0131 ba\u011flant\u0131s\u0131 kuram\u0131yor, ters proxy upstream sunucudan zaman\u0131nda yan\u0131t alam\u0131yor veya i\u015fletim sistemi yeni bir i\u015flem olu\u015fturmak i\u00e7in yeterli kaynak bulam\u0131yor olabilir. Ayn\u0131 URL&#8217;yi taray\u0131c\u0131da a\u00e7t\u0131\u011f\u0131n\u0131zda ba\u015far\u0131l\u0131 g\u00f6rmeniz de sorunu d\u0131\u015flamaz. Hata yaln\u0131zca yo\u011fun trafik an\u0131nda, belirli veri merkezlerinden gelen isteklerde veya y\u00fcksek maliyetli sayfalarda ortaya \u00e7\u0131kabilir.<\/p>\n<h3><span id=\"5xx_kodlarini_birbirinden_ayirin\">5xx kodlar\u0131n\u0131 birbirinden ay\u0131r\u0131n<\/span><\/h3>\n<ul>\n<li><strong>500 Internal Server Error:<\/strong> Uygulama istisnas\u0131, hatal\u0131 PHP kodu, bozuk yap\u0131land\u0131rma veya yakalanmam\u0131\u015f bir sunucu hatas\u0131 g\u00f6r\u00fclebilir.<\/li>\n<li><strong>502 Bad Gateway:<\/strong> Nginx, Apache veya ba\u015fka bir proxy; PHP-FPM, uygulama sunucusu ya da upstream servisten ge\u00e7erli yan\u0131t alamam\u0131\u015f olabilir.<\/li>\n<li><strong>503 Service Unavailable:<\/strong> Bak\u0131m modu, ge\u00e7ici kapasite yetersizli\u011fi, a\u015f\u0131r\u0131 y\u00fck veya uygulaman\u0131n iste\u011fi kabul etmemesi s\u00f6z konusu olabilir.<\/li>\n<li><strong>504 Gateway Timeout:<\/strong> Upstream bile\u015fen, proxy&#8217;nin belirledi\u011fi s\u00fcre i\u00e7inde yan\u0131t vermemi\u015ftir. Yava\u015f veritaban\u0131 sorgusu ve kilitlenmi\u015f i\u015flem olas\u0131 nedenler aras\u0131ndad\u0131r.<\/li>\n<li><strong>508 ve benzeri kodlar:<\/strong> D\u00f6ng\u00fc, kaynak s\u0131n\u0131r\u0131 veya platforma \u00f6zg\u00fc bir koruma mekanizmas\u0131 devreye girmi\u015f olabilir. Kodun anlam\u0131n\u0131 hosting sa\u011flay\u0131c\u0131n\u0131z\u0131n altyap\u0131 dok\u00fcmantasyonuyla do\u011frulay\u0131n.<\/li>\n<\/ul>\n<p>HTTP durum kodlar\u0131n\u0131n SEO ve hosting a\u00e7\u0131s\u0131ndan nas\u0131l yorumland\u0131\u011f\u0131n\u0131 g\u00f6rmek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/http-durum-kodlari-seo-ve-hosting-icin-301-302-404-410-ve-5xx-rehberi\/\">HTTP Durum Kodlar\u0131<\/a>: SEO ve Hosting \u0130\u00e7in 301, 302, 404, 410 ve 5xx Rehberi i\u00e7eri\u011fine de bakabilirsiniz. Buradaki ama\u00e7 kodu ezberlemek de\u011fil, iste\u011fi hangi bile\u015fenin sonland\u0131rd\u0131\u011f\u0131n\u0131 belirlemektir.<\/p>\n<h2><span id=\"Once_hatanin_zamanini_ve_kapsamini_belirleyin\">\u00d6nce hatan\u0131n zaman\u0131n\u0131 ve kapsam\u0131n\u0131 belirleyin<\/span><\/h2>\n<p>Search Console grafi\u011fi bir d\u00f6nem ve e\u011filim g\u00f6sterir; sunucu logu ise tek tek isteklerin zaman\u0131n\u0131, URL&#8217;sini ve yan\u0131t kodunu g\u00f6sterir. \u0130ki kayna\u011f\u0131 ayn\u0131 saat dilimine getirerek ba\u015flay\u0131n. Saat dilimleri farkl\u0131ysa ayn\u0131 olay\u0131 yanl\u0131\u015f aral\u0131kta arayabilirsiniz.<\/p>\n<h3><span id=\"Search_Console_verisini_daraltin\">Search Console verisini daralt\u0131n<\/span><\/h3>\n<p>Hatan\u0131n hangi raporda g\u00f6r\u00fcnd\u00fc\u011f\u00fcn\u00fc ve hangi URL grubunu etkiledi\u011fini not edin. Sitenin tamam\u0131nda art\u0131\u015f varsa genel kapasite, a\u011f, DNS veya platform sorunu olas\u0131l\u0131\u011f\u0131 y\u00fckselir. Hata yaln\u0131zca \u00fcr\u00fcn filtreleri, arama sonu\u00e7lar\u0131 veya belirli bir eklentinin \u00fcretti\u011fi URL&#8217;lerdeyse uygulama maliyetine odaklan\u0131n.<\/p>\n<p>T\u00fcm URL&#8217;leri yeniden taratmak yerine birka\u00e7 temsilci URL se\u00e7in: ana sayfa, hata g\u00f6r\u00fclen bir i\u00e7erik, kategori veya \u00fcr\u00fcn sayfas\u0131 ve m\u00fcmk\u00fcnse robots.txt. Bu kar\u015f\u0131la\u015ft\u0131rma, sorunun i\u00e7erik t\u00fcr\u00fcne, URL parametresine veya t\u00fcm sanal host&#8217;a yay\u0131ld\u0131\u011f\u0131n\u0131 ay\u0131rman\u0131za yard\u0131mc\u0131 olur.<\/p>\n<h3><span id=\"Erisim_loglarinda_Googlebot_istegini_bulun\">Eri\u015fim loglar\u0131nda Googlebot iste\u011fini bulun<\/span><\/h3>\n<p>Log sat\u0131r\u0131nda genellikle istemci IP&#8217;si, zaman, istek yolu, HTTP y\u00f6ntemi, durum kodu, yan\u0131t boyutu ve User-Agent bulunur. User-Agent i\u00e7inde Googlebot yazmas\u0131 tek ba\u015f\u0131na iste\u011fin ger\u00e7ekten Google&#8217;a ait oldu\u011funu kan\u0131tlamaz. G\u00fcvenlik incelemesinde ters DNS ve ileri DNS do\u011frulamas\u0131 ayr\u0131ca yap\u0131lmal\u0131d\u0131r; ilk teknik te\u015fhiste ise ayn\u0131 URL ve zaman dilimindeki kay\u0131tlar\u0131 e\u015fle\u015ftirmek yeterli bir ba\u015flang\u0131\u00e7t\u0131r.<\/p>\n<p>Apache veya Nginx log format\u0131n\u0131zda yan\u0131t s\u00fcresi yoksa, altyap\u0131 y\u00f6neticinizden upstream ve toplam istek s\u00fcresini i\u00e7eren bir format isteyin. Mevcut kay\u0131t ak\u0131\u015f\u0131n\u0131 de\u011fi\u015ftirmeden \u00f6nce yap\u0131land\u0131rmay\u0131 yedekleyin. De\u011fi\u015fiklikten sonra yeni sat\u0131rlar\u0131n beklenen alanlar\u0131 i\u00e7erdi\u011fini kontrol edin.<\/p>\n<p>Sunucu loglar\u0131n\u0131 okumaya yeni ba\u015fl\u0131yorsan\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/hosting-sunucu-loglarini-okumayi-ogrenin-apache-ve-nginx-ile-4xx-5xx\/\">Hosting Sunucu Loglar\u0131n\u0131 Okumay\u0131 \u00d6\u011frenin<\/a> ifadesiyle ili\u015fkili rehber, Apache ve Nginx kay\u0131tlar\u0131ndaki alanlar\u0131 yorumlamak i\u00e7in yararl\u0131 bir ba\u015fvuru olabilir.<\/p>\n<div class=\"aiw-note aiw-note-example\">\n<p class=\"aiw-box-title\">\u00d6rnek senaryo<\/p>\n<p>Varsayal\u0131m ki Search Console&#8217;da son iki saat i\u00e7inde \u00fcr\u00fcn URL&#8217;lerinde 504 art\u0131\u015f\u0131 g\u00f6r\u00fcyorsunuz. Ayn\u0131 saatlerde eri\u015fim loglar\u0131nda bu URL&#8217;ler i\u00e7in 504, y\u00fcksek upstream s\u00fcresi ve veritaban\u0131 sorgu uyar\u0131lar\u0131 bulunuyor; ana sayfa ise 200 d\u00f6n\u00fcyor. Bu varsay\u0131msal tablo, Googlebot&#8217;un engellendi\u011fini de\u011fil, \u00fcr\u00fcn sayfas\u0131n\u0131n belirli bir ba\u011f\u0131ml\u0131l\u0131k nedeniyle zaman\u0131nda \u00fcretilemedi\u011fini d\u00fc\u015f\u00fcnd\u00fcr\u00fcr.<\/p>\n<\/div>\n<h2><span id=\"Hosting_kaynaklari_ve_uygulama_katmanini_inceleyin\">Hosting kaynaklar\u0131 ve uygulama katman\u0131n\u0131 inceleyin<\/span><\/h2>\n<p>Bir 5xx yan\u0131t\u0131n\u0131n hosting kaynakl\u0131 olup olmad\u0131\u011f\u0131n\u0131 anlamak i\u00e7in yaln\u0131zca CPU kullan\u0131m\u0131na bakmay\u0131n. CPU, RAM, PHP-FPM i\u015f\u00e7i say\u0131s\u0131, i\u015flem ba\u015flatma limiti, disk alan\u0131, disk I\/O, veritaban\u0131 ba\u011flant\u0131 havuzu ve s\u00fcre\u00e7 ba\u015f\u0131na bellek s\u0131n\u0131r\u0131 farkl\u0131 darbo\u011fazlard\u0131r. Hata an\u0131nda hangi de\u011ferin s\u0131n\u0131r\u0131 a\u015ft\u0131\u011f\u0131n\u0131 bulman\u0131z gerekir.<\/p>\n<h3><span id=\"PHP-FPM_web_iscileri_ile_CLI_islerini_ayirin\">PHP-FPM web i\u015f\u00e7ileri ile CLI i\u015flerini ay\u0131r\u0131n<\/span><\/h3>\n<p>PHP-FPM, web sunucusunun PHP isteklerini \u00e7al\u0131\u015ft\u0131ran i\u015f\u00e7i havuzudur. Bir istek uzun s\u00fcrerse veya havuzdaki t\u00fcm i\u015f\u00e7iler doluysa yeni HTTP istekleri bekleyebilir; proxy bekleme s\u00fcresini a\u015farsa 502 ya da 504 g\u00f6r\u00fclebilir. Bu nedenle FPM durumunu, aktif i\u015f\u00e7i say\u0131s\u0131n\u0131, bekleyen istekleri ve yava\u015f istek kay\u0131tlar\u0131n\u0131 hata zaman\u0131yla kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<p>CLI cron g\u00f6revleri ve kuyruk i\u015f\u00e7ileri komut sat\u0131r\u0131nda \u00e7al\u0131\u015fan ayr\u0131 s\u00fcre\u00e7lerdir. HTTP \u00e7a\u011fr\u0131s\u0131 yapmayan bir CLI i\u015fi FPM i\u015f\u00e7isi t\u00fcketmez. Bununla birlikte ayn\u0131 CPU, RAM, disk veya veritaban\u0131 gibi ortak kaynaklar\u0131 kullanarak web isteklerini dolayl\u0131 bi\u00e7imde yava\u015flatabilir. Her s\u00fcrecin hangi kayna\u011f\u0131 t\u00fcketti\u011fini \u00f6l\u00e7meden cron \u00e7al\u0131\u015f\u0131yor diye FPM havuzunun doldu\u011funu varsaymay\u0131n.<\/p>\n<h3><span id=\"Kaynak_limitlerini_kanitlayin\">Kaynak limitlerini kan\u0131tlay\u0131n<\/span><\/h3>\n<p>Hata zaman\u0131nda a\u015fa\u011f\u0131daki g\u00f6stergeleri birlikte inceleyin:<\/p>\n<ul>\n<li>FPM havuzu maksimum \u00e7ocuk s\u00fcre\u00e7 say\u0131s\u0131na ula\u015fm\u0131\u015f m\u0131?<\/li>\n<li>\u0130stekler kuyrukta bekliyor veya yava\u015f istek e\u015fi\u011fini a\u015f\u0131yor mu?<\/li>\n<li>RAM t\u00fckenmesi, i\u015fletim sistemi taraf\u0131ndan s\u00fcre\u00e7 sonland\u0131r\u0131lmas\u0131 veya swap kullan\u0131m\u0131 g\u00f6r\u00fcl\u00fcyor mu?<\/li>\n<li>Disk alan\u0131, inode veya ge\u00e7ici dosya alan\u0131 dolu mu?<\/li>\n<li>Veritaban\u0131 ba\u011flant\u0131 say\u0131s\u0131, kilitlenme veya sorgu s\u00fcresi y\u00fckselmi\u015f mi?<\/li>\n<li>Hosting hesab\u0131n\u0131n CPU, I\/O, i\u015flem veya e\u015fzamanl\u0131 ba\u011flant\u0131 limiti a\u015f\u0131lm\u0131\u015f m\u0131?<\/li>\n<\/ul>\n<p>Payla\u015f\u0131ml\u0131 hosting ortam\u0131nda bu g\u00f6stergelerin tamam\u0131na eri\u015femeyebilirsiniz. Bu durumda sa\u011flay\u0131c\u0131ya tam hata zaman\u0131n\u0131, etkilenen alan ad\u0131n\u0131, URL&#8217;yi ve m\u00fcmk\u00fcnse istek kimli\u011fini vererek kaynak kullan\u0131m\u0131 ile platform loglar\u0131n\u0131n incelenmesini isteyin. Belirli zaman ve URL bilgisi, genel bir 5xx bildiriminden daha yararl\u0131 bir te\u015fhis ba\u015flang\u0131c\u0131 sa\u011flar.<\/p>\n<div class=\"aiw-note aiw-note-warning\">\n<p class=\"aiw-box-title\">Dikkat<\/p>\n<p>FPM i\u015f\u00e7i say\u0131s\u0131n\u0131, PHP memory_limit de\u011ferini veya proxy timeout&#8217;unu do\u011frudan y\u00fckseltmek her zaman \u00e7\u00f6z\u00fcm de\u011fildir. Yava\u015f bir sorguyu daha uzun s\u00fcre bekletmek 504 say\u0131s\u0131n\u0131 azaltabilir; ayn\u0131 anda daha fazla i\u015f\u00e7inin dolmas\u0131na ve kaynak bask\u0131s\u0131n\u0131n b\u00fcy\u00fcmesine de neden olabilir. De\u011fi\u015fiklikten \u00f6nce yap\u0131land\u0131rmay\u0131 yedekleyin, mevcut de\u011ferleri not edin ve geri d\u00f6n\u00fc\u015f ad\u0131m\u0131n\u0131 haz\u0131rlay\u0131n.<\/p>\n<\/div>\n<h2><span id=\"Timeout_ve_proxy_zincirini_kontrol_edin\">Timeout ve proxy zincirini kontrol edin<\/span><\/h2>\n<p>504 g\u00f6rd\u00fc\u011f\u00fcn\u00fczde yaln\u0131zca sunucunun yava\u015f oldu\u011funu s\u00f6ylemek yeterli de\u011fildir. \u0130stek CDN veya y\u00fck dengeleyici, web sunucusu, PHP-FPM ya da uygulama sunucusu ve veritaban\u0131 gibi birden fazla katmandan ge\u00e7ebilir. Her katman\u0131n ba\u011flant\u0131 ve yan\u0131t bekleme s\u00fcresi farkl\u0131d\u0131r.<\/p>\n<p>\u00d6nce 504&#8217;\u00fc hangi katman\u0131n \u00fcretti\u011fini belirleyin. Yan\u0131t g\u00f6vdesindeki varsay\u0131lan proxy sayfas\u0131, response header&#8217;lar\u0131, web sunucusu logu ve upstream logu ipucu verebilir. Ayn\u0131 zaman damgas\u0131nda web sunucusunda 504, FPM taraf\u0131nda ise hi\u00e7 kay\u0131t yoksa istek FPM&#8217;e ula\u015fmadan kesilmi\u015f olabilir. FPM&#8217;de i\u015flem ba\u015flad\u0131 fakat tamamlanmad\u0131ysa uygulama veya veritaban\u0131 s\u00fcresini inceleyin.<\/p>\n<h3><span id=\"Timeout_degerlerini_dar_kapsamda_ele_alin\">Timeout de\u011ferlerini dar kapsamda ele al\u0131n<\/span><\/h3>\n<p>\u0130lk d\u00fczeltme, t\u00fcm site i\u00e7in timeout&#8217;u b\u00fcy\u00fctmek yerine sorunlu endpoint&#8217;i veya yava\u015f i\u015flemi hedeflemelidir. \u00d6nce yava\u015f sorguyu, d\u0131\u015f API \u00e7a\u011fr\u0131s\u0131n\u0131, dosya i\u015flemini veya eklenti kancas\u0131n\u0131 bulun. \u0130\u015f web iste\u011fi i\u00e7inde \u00e7al\u0131\u015fmak zorundaysa sorguyu iyile\u015ftirin, sonucu \u00f6nbelle\u011fe al\u0131n veya i\u015flemi asenkron kuyru\u011fa ta\u015f\u0131y\u0131n. Kuyruk i\u015f\u00e7isinin FPM i\u015f\u00e7isi olmad\u0131\u011f\u0131n\u0131 ve ayr\u0131 kaynak t\u00fcketti\u011fini izleme plan\u0131nda ayr\u0131ca de\u011ferlendirin.<\/p>\n<p>Yap\u0131land\u0131rma de\u011fi\u015fikli\u011fi i\u00e7in gerekli y\u00f6netici eri\u015fiminiz ve geri y\u00fcklenebilir bir kopyan\u0131z olmal\u0131d\u0131r. De\u011fi\u015fiklikten sonra yap\u0131land\u0131rma s\u00f6zdizimini do\u011frulay\u0131n, kontroll\u00fc bir istek g\u00f6nderin ve hata oran\u0131n\u0131 \u00f6nceki d\u00f6nemle kar\u015f\u0131la\u015ft\u0131r\u0131n. Servisi yeniden ba\u015flatmak gerekiyorsa bak\u0131m penceresi ve geri d\u00f6n\u00fc\u015f ad\u0131m\u0131 belirlenmeden uygulamay\u0131n.<\/p>\n<h2><span id=\"Gecici_5xx_artislarini_nasil_dogrularsiniz\">Ge\u00e7ici 5xx art\u0131\u015flar\u0131n\u0131 nas\u0131l do\u011frulars\u0131n\u0131z?<\/span><\/h2>\n<p>Ge\u00e7ici bir a\u011f veya platform sorunu k\u0131sa s\u00fcreli bir 5xx dalgas\u0131 yaratabilir. Bunu incelemek i\u00e7in yaln\u0131zca taray\u0131c\u0131dan manuel kontrol yapmay\u0131n. Ayn\u0131 URL&#8217;yi birka\u00e7 farkl\u0131 zamanda isteyin; her denemede durum kodunu, yan\u0131t s\u00fcresini ve m\u00fcmk\u00fcnse istek kimli\u011fini kaydedin. Kontrolleri d\u00fc\u015f\u00fck s\u0131kl\u0131kta tutun; testleriniz yeni bir y\u00fck olu\u015fturmamal\u0131d\u0131r.<\/p>\n<p>Uptime izleme kay\u0131tlar\u0131 sitenin d\u0131\u015far\u0131dan eri\u015filebilir olup olmad\u0131\u011f\u0131n\u0131 g\u00f6sterir. Ancak yaln\u0131zca ana sayfay\u0131 kontrol etmek, \u00fcr\u00fcn sayfas\u0131ndaki veritaban\u0131 sorununu yakalamayabilir. Kritik URL t\u00fcrleri i\u00e7in d\u00fc\u015f\u00fck s\u0131kl\u0131kl\u0131 ve uygun aral\u0131kl\u0131 kontroller daha anlaml\u0131d\u0131r. \u0130zleme kayd\u0131 ile Search Console&#8217;daki hata zaman\u0131n\u0131 ayn\u0131 saat diliminde kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/p>\n<p>User-Agent de\u011fi\u015ftirerek yap\u0131lan testler, uygulaman\u0131n farkl\u0131 istemci ba\u015fl\u0131klar\u0131na g\u00f6re davran\u0131p davranmad\u0131\u011f\u0131n\u0131 g\u00f6sterebilir; Google&#8217;\u0131n ger\u00e7ek tarama iste\u011fini veya a\u011f yolunu b\u00fct\u00fcn\u00fcyle temsil etmez. Bu nedenle Googlebot&#8217;a 5xx d\u00f6nd\u00fc\u011f\u00fc iddias\u0131n\u0131 bu testle kan\u0131tlamay\u0131n. As\u0131l kan\u0131t, eri\u015fim loglar\u0131 ile altyap\u0131 kay\u0131tlar\u0131n\u0131n zaman ve URL bak\u0131m\u0131ndan e\u015fle\u015fmesidir.<\/p>\n<h2><span id=\"Googlebot8217a_ozel_engelleme_ile_5xx_sorununu_ayirin\">Googlebot&#8217;a \u00f6zel engelleme ile 5xx sorununu ay\u0131r\u0131n<\/span><\/h2>\n<p>robots.txt&#8217;de Disallow kullan\u0131lmas\u0131 taramay\u0131 k\u0131s\u0131tlayabilir, fakat normalde sunucunun 5xx yan\u0131t\u0131 \u00fcretmesine neden olmaz. WAF veya g\u00fcvenlik katman\u0131 Googlebot benzeri User-Agent&#8217;lar\u0131 engelliyorsa 403, ba\u011flant\u0131 kesilmesi veya platforma \u00f6zg\u00fc bir hata g\u00f6r\u00fclebilir. 5xx ile robots.txt kural\u0131n\u0131 ayn\u0131 sorun gibi ele almay\u0131n.<\/p>\n<p>Googlebot istekleri i\u00e7in h\u0131z s\u0131n\u0131rlama, bot korumas\u0131 veya IP itibar\u0131 kural\u0131 kullan\u0131yorsan\u0131z g\u00fcvenlik loglar\u0131nda e\u015fle\u015fen bir kay\u0131t aray\u0131n. Kural\u0131 tamamen kapatmak yerine yaln\u0131zca etkilenen alan ad\u0131 ve URL grubu i\u00e7in kontroll\u00fc bir istisna de\u011ferlendirin. Ger\u00e7ek Googlebot do\u011frulamas\u0131 gerekiyorsa IP listelerini sabit kabul etmeyin; Google&#8217;\u0131n g\u00fcncel do\u011frulama y\u00f6ntemini uygulay\u0131n.<\/p>\n<h2><span id=\"Dar_kapsamli_duzeltme_ve_dogrulama_plani\">Dar kapsaml\u0131 d\u00fczeltme ve do\u011frulama plan\u0131<\/span><\/h2>\n<p>Te\u015fhisten sonra ayn\u0131 anda birden fazla ayar\u0131 de\u011fi\u015ftirmeyin. B\u00f6ylece hangi de\u011fi\u015fikli\u011fin sonucu etkiledi\u011fini koruyabilirsiniz:<\/p>\n<ol>\n<li><strong>Kan\u0131t\u0131 sabitleyin:<\/strong> Hata zaman\u0131n\u0131, URL&#8217;yi, 5xx kodunu, yan\u0131t s\u00fcresini, User-Agent&#8217;\u0131 ve ilgili log sat\u0131rlar\u0131n\u0131 kaydedin.<\/li>\n<li><strong>Katman\u0131 se\u00e7in:<\/strong> Uygulama logu 500 g\u00f6steriyorsa kod veya eklentiye, upstream zaman a\u015f\u0131m\u0131 g\u00f6steriyorsa ba\u011f\u0131ml\u0131l\u0131k ve timeout zincirine, kaynak limiti g\u00f6steriyorsa kapasiteye odaklan\u0131n.<\/li>\n<li><strong>En dar d\u00fczeltmeyi uygulay\u0131n:<\/strong> Sorunlu sorgu, endpoint, eklenti, kuyruk g\u00f6revi veya g\u00fcvenlik kural\u0131 i\u00e7in de\u011fi\u015fiklik yap\u0131n. T\u00fcm sitenin ayarlar\u0131n\u0131 de\u011fi\u015ftirmeyi son se\u00e7enek olarak de\u011ferlendirin.<\/li>\n<li><strong>Geri d\u00f6n\u00fc\u015f\u00fc haz\u0131rlay\u0131n:<\/strong> Yap\u0131land\u0131rma ve uygulama de\u011fi\u015fikliklerinden \u00f6nce yedek al\u0131n, mevcut de\u011ferleri not edin ve geri alma ad\u0131mlar\u0131n\u0131 belirleyin.<\/li>\n<li><strong>Sonucu \u00f6l\u00e7\u00fcn:<\/strong> Ayn\u0131 URL t\u00fcrlerinde 5xx oran\u0131n\u0131, yan\u0131t s\u00fcresini, FPM beklemesini ve kaynak kullan\u0131m\u0131n\u0131 de\u011fi\u015fiklik \u00f6ncesi d\u00f6nemle kar\u015f\u0131la\u015ft\u0131r\u0131n.<\/li>\n<li><strong>Search Console&#8217;u yeniden de\u011ferlendirin:<\/strong> Sunucu taraf\u0131 d\u00fczeldikten sonra Google&#8217;\u0131n yeni tarama verilerinin olu\u015fmas\u0131 zaman alabilir. Search Console&#8217;daki do\u011frulama se\u00e7ene\u011fini kullanmadan \u00f6nce canl\u0131 teknik kan\u0131t\u0131n d\u00fczeldi\u011finden emin olun.<\/li>\n<\/ol>\n<p>WordPress kullan\u0131yorsan\u0131z son y\u00fcklenen eklentileri, tema de\u011fi\u015fikliklerini, otomatik g\u00f6revleri ve a\u011f\u0131r sorgu \u00fcreten \u00f6zellikleri hata zaman\u0131yla e\u015fle\u015ftirin. WooCommerce \u00fcr\u00fcn, sepet veya \u00f6deme ak\u0131\u015flar\u0131n\u0131 test ederken ger\u00e7ek sipari\u015f olu\u015fturmadan staging ortam\u0131n\u0131 ya da g\u00fcvenli bir test \u00fcr\u00fcn\u00fcn\u00fc kullan\u0131n. Veri de\u011fi\u015ftiren i\u015flemlerden \u00f6nce veritaban\u0131 ve dosya yede\u011finin geri y\u00fcklenebilir oldu\u011funu kontrol edin.<\/p>\n<h2><span id=\"Sik_Sorulan_Sorular\">S\u0131k Sorulan Sorular<\/span><\/h2>\n<h3><span id=\"Googlebot_5xx_hatalari_siralamayi_hemen_dusurur_mu\">Googlebot 5xx hatalar\u0131 s\u0131ralamay\u0131 hemen d\u00fc\u015f\u00fcr\u00fcr m\u00fc?<\/span><\/h3>\n<p>Tek ve k\u0131sa s\u00fcreli bir hata otomatik olarak kal\u0131c\u0131 s\u0131ralama kayb\u0131 anlam\u0131na gelmez. Hatalar tekrarl\u0131, yayg\u0131n veya uzun s\u00fcreliyse Google sayfalar\u0131 daha az tarayabilir; bu durum yeni ve g\u00fcncellenmi\u015f i\u00e7eri\u011fin ke\u015ffini geciktirebilir.<\/p>\n<h3><span id=\"Googlebot_icin_ayri_bir_sunucu_plani_gerekir_mi\">Googlebot i\u00e7in ayr\u0131 bir sunucu plan\u0131 gerekir mi?<\/span><\/h3>\n<p>Gereklilik, Googlebot say\u0131s\u0131ndan \u00e7ok sitenizin toplam istek paterni ve sayfa \u00fcretim maliyetiyle ilgilidir. \u00d6nce darbo\u011faz\u0131 \u00f6l\u00e7\u00fcn. Kaynak limiti s\u00fcrekli a\u015f\u0131l\u0131yorsa optimizasyon, \u00f6nbellekleme veya uygun kapasite planlamas\u0131 de\u011ferlendirilir.<\/p>\n<h3><span id=\"5xx_hatasi_icin_URL8217yi_Search_Console8217da_tekrar_test_etmek_yeterli_midir\">5xx hatas\u0131 i\u00e7in URL&#8217;yi Search Console&#8217;da tekrar test etmek yeterli midir?<\/span><\/h3>\n<p>Hay\u0131r. URL testi anl\u0131k bir kontrol sa\u011flar ve ge\u00e7mi\u015fteki hata an\u0131n\u0131 a\u00e7\u0131klamaz. Eri\u015fim loglar\u0131, uygulama kay\u0131tlar\u0131 ve uptime verileriyle zaman \u00e7izelgesi olu\u015fturman\u0131z gerekir.<\/p>\n<h3><span id=\"CDN_kullanmak_5xx_sorununu_tamamen_cozer_mi\">CDN kullanmak 5xx sorununu tamamen \u00e7\u00f6zer mi?<\/span><\/h3>\n<p>CDN baz\u0131 i\u00e7erikleri \u00f6nbellekten sunarak origin y\u00fck\u00fcn\u00fc azaltabilir; dinamik sayfa, veritaban\u0131 veya origin yap\u0131land\u0131rma hatalar\u0131n\u0131 ortadan kald\u0131rmaz. CDN ile origin aras\u0131ndaki 5xx kay\u0131tlar\u0131n\u0131 ayr\u0131ca inceleyin.<\/p>\n<h2><span id=\"Son_kontrol_listesi\">Son kontrol listesi<\/span><\/h2>\n<ul>\n<li>Search Console&#8217;da etkilenen URL t\u00fcrlerini ve hata zaman aral\u0131\u011f\u0131n\u0131 not ettiniz mi?<\/li>\n<li>Sunucu saat dilimini Search Console verisiyle e\u015fle\u015ftirdiniz mi?<\/li>\n<li>\u0130lgili eri\u015fim logunda durum kodu, URL, yan\u0131t s\u00fcresi ve User-Agent kayd\u0131n\u0131 buldunuz mu?<\/li>\n<li>Hatan\u0131n web sunucusu, PHP-FPM, uygulama, veritaban\u0131, proxy veya g\u00fcvenlik katman\u0131ndan hangisinde olu\u015ftu\u011funu belirlediniz mi?<\/li>\n<li>CPU, RAM, disk, FPM, veritaban\u0131 ve hosting limitlerinden hangisinin ger\u00e7ekten a\u015f\u0131ld\u0131\u011f\u0131n\u0131 do\u011frulad\u0131n\u0131z m\u0131?<\/li>\n<li>De\u011fi\u015fiklikten \u00f6nce yedek ve geri d\u00f6n\u00fc\u015f ad\u0131m\u0131n\u0131 haz\u0131rlad\u0131n\u0131z m\u0131?<\/li>\n<li>Dar kapsaml\u0131 d\u00fczeltmeden sonra ayn\u0131 URL t\u00fcrlerinde 5xx ve yan\u0131t s\u00fcresini yeniden \u00f6l\u00e7t\u00fcn\u00fcz m\u00fc?<\/li>\n<\/ul>\n<p>\u0130lk sonraki ad\u0131m\u0131n\u0131z, Search Console&#8217;daki bir hata zaman aral\u0131\u011f\u0131n\u0131 se\u00e7ip ayn\u0131 dakikalardaki eri\u015fim ve uygulama loglar\u0131n\u0131 yan yana koymak olsun. Tek bir 500 veya 504 sat\u0131r\u0131n\u0131 de\u011fi\u015ftirmeye \u00e7al\u0131\u015fmak yerine tekrar eden \u00f6r\u00fcnt\u00fcy\u00fc buldu\u011funuzda hosting sa\u011flay\u0131c\u0131n\u0131za kan\u0131tl\u0131 ve \u00e7\u00f6z\u00fclebilir bir destek talebi iletebilirsiniz.<\/p>\n<p>Emre<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>Googlebot 5xx hatalar\u0131n\u0131 Search Console, eri\u015fim loglar\u0131, timeout de\u011ferleri ve hosting kaynaklar\u0131yla te\u015fhis edip dar kapsaml\u0131 \u00e7\u00f6z\u00fcm uygulay\u0131n.<\/p>\n","protected":false},"author":4,"featured_media":5736,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[583,450,582,124,272,584],"class_list":["post-5740","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-dijital-pazarlama","tag-5xx-hatalari","tag-google-search-console","tag-googlebot","tag-hosting","tag-seo","tag-sunucu-loglari"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5740","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\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=5740"}],"version-history":[{"count":1,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5740\/revisions"}],"predecessor-version":[{"id":5742,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5740\/revisions\/5742"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/5736"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=5740"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=5740"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=5740"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}