{"id":5156,"date":"2026-09-09T13:59:33","date_gmt":"2026-09-09T10:59:33","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/?p=5156"},"modified":"2026-09-09T06:26:22","modified_gmt":"2026-09-09T03:26:22","slug":"wordpress-site-sagligi-raporu-nasil-okunur","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/wordpress-site-sagligi-raporu-nasil-okunur\/","title":{"rendered":"WordPress Site Sa\u011fl\u0131\u011f\u0131 Raporu Nas\u0131l Okunur?"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><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=\"#WordPress_Site_Sagligi_raporu_nasil_okunur\"><span class=\"toc_number toc_depth_1\">1.<\/span> WordPress Site Sa\u011fl\u0131\u011f\u0131 raporu nas\u0131l okunur?<\/a><\/li><li><a href=\"#Site_Sagligi_ekraninda_hangi_bolumler_var\"><span class=\"toc_number toc_depth_1\">2.<\/span> Site Sa\u011fl\u0131\u011f\u0131 ekran\u0131nda hangi b\u00f6l\u00fcmler var?<\/a><ul><li><a href=\"#Kritik_sorunlar\"><span class=\"toc_number toc_depth_2\">2.1.<\/span> Kritik sorunlar<\/a><\/li><li><a href=\"#Onerilen_iyilestirmeler\"><span class=\"toc_number toc_depth_2\">2.2.<\/span> \u00d6nerilen iyile\u015ftirmeler<\/a><\/li><li><a href=\"#Basarili_testler\"><span class=\"toc_number toc_depth_2\">2.3.<\/span> Ba\u015far\u0131l\u0131 testler<\/a><\/li><\/ul><\/li><li><a href=\"#Kirmizi_uyariyi_gorur_gormez_eklenti_kurmayin\"><span class=\"toc_number toc_depth_1\">3.<\/span> K\u0131rm\u0131z\u0131 uyar\u0131y\u0131 g\u00f6r\u00fcr g\u00f6rmez eklenti kurmay\u0131n<\/a><\/li><li><a href=\"#En_sik_gorulen_kontrolleri_tek_tek_okuyalim\"><span class=\"toc_number toc_depth_1\">4.<\/span> En s\u0131k g\u00f6r\u00fclen kontrolleri tek tek okuyal\u0131m<\/a><ul><li><a href=\"#WordPress_tema_ve_eklentiler_guncel_mi\"><span class=\"toc_number toc_depth_2\">4.1.<\/span> WordPress, tema ve eklentiler g\u00fcncel mi?<\/a><\/li><li><a href=\"#PHP_surumu_ve_bellek_siniri\"><span class=\"toc_number toc_depth_2\">4.2.<\/span> PHP s\u00fcr\u00fcm\u00fc ve bellek s\u0131n\u0131r\u0131<\/a><\/li><li><a href=\"#HTTPS_ve_guvenli_baglanti\"><span class=\"toc_number toc_depth_2\">4.3.<\/span> HTTPS ve g\u00fcvenli ba\u011flant\u0131<\/a><\/li><li><a href=\"#REST_API_ve_loopback_istekleri\"><span class=\"toc_number toc_depth_2\">4.4.<\/span> REST API ve loopback istekleri<\/a><\/li><li><a href=\"#Zamanlanmis_gorevler_ve_WP-Cron\"><span class=\"toc_number toc_depth_2\">4.5.<\/span> Zamanlanm\u0131\u015f g\u00f6revler ve WP-Cron<\/a><\/li><li><a href=\"#Kalici_nesne_onbellegi\"><span class=\"toc_number toc_depth_2\">4.6.<\/span> Kal\u0131c\u0131 nesne \u00f6nbelle\u011fi<\/a><\/li><\/ul><\/li><li><a href=\"#Bilgi_sekmesi_destek_biletini_kisaltir\"><span class=\"toc_number toc_depth_1\">5.<\/span> Bilgi sekmesi destek biletini k\u0131salt\u0131r<\/a><\/li><li><a href=\"#Site_Sagligi_raporu_ile_performans_raporu_ayni_sey_degil\"><span class=\"toc_number toc_depth_1\">6.<\/span> Site Sa\u011fl\u0131\u011f\u0131 raporu ile performans raporu ayn\u0131 \u015fey de\u011fil<\/a><\/li><li><a href=\"#Uyari_goruldugunde_uygulanacak_guvenli_sira\"><span class=\"toc_number toc_depth_1\">7.<\/span> Uyar\u0131 g\u00f6r\u00fcld\u00fc\u011f\u00fcnde uygulanacak g\u00fcvenli s\u0131ra<\/a><\/li><li><a href=\"#WordPress_Site_Sagligi_raporu_ne_zaman_ciddiye_alinmali\"><span class=\"toc_number toc_depth_1\">8.<\/span> WordPress Site Sa\u011fl\u0131\u011f\u0131 raporu ne zaman ciddiye al\u0131nmal\u0131?<\/a><\/li><li><a href=\"#Sik_Sorulan_Sorular\"><span class=\"toc_number toc_depth_1\">9.<\/span> S\u0131k Sorulan Sorular<\/a><ul><li><a href=\"#WordPress_Site_Sagligi_raporundaki_kirmizi_uyari_siteyi_kapatir_mi\"><span class=\"toc_number toc_depth_2\">9.1.<\/span> WordPress Site Sa\u011fl\u0131\u011f\u0131 raporundaki k\u0131rm\u0131z\u0131 uyar\u0131 siteyi kapat\u0131r m\u0131?<\/a><\/li><li><a href=\"#WordPress_Site_Sagligi_puani_SEO_siralamasini_etkiler_mi\"><span class=\"toc_number toc_depth_2\">9.2.<\/span> WordPress Site Sa\u011fl\u0131\u011f\u0131 puan\u0131 SEO s\u0131ralamas\u0131n\u0131 etkiler mi?<\/a><\/li><li><a href=\"#REST_API_hatasi_nasil_duzeltilir\"><span class=\"toc_number toc_depth_2\">9.3.<\/span> REST API hatas\u0131 nas\u0131l d\u00fczeltilir?<\/a><\/li><li><a href=\"#Site_Sagligi_raporu_ne_siklikla_kontrol_edilmeli\"><span class=\"toc_number toc_depth_2\">9.4.<\/span> Site Sa\u011fl\u0131\u011f\u0131 raporu ne s\u0131kl\u0131kla kontrol edilmeli?<\/a><\/li><\/ul><\/li><\/ul><\/div>\n<h2><span id=\"WordPress_Site_Sagligi_raporu_nasil_okunur\">WordPress Site Sa\u011fl\u0131\u011f\u0131 raporu nas\u0131l okunur?<\/span><\/h2>\n<p>WordPress y\u00f6netim panelinde <strong>Ara\u00e7lar &gt; Site Sa\u011fl\u0131\u011f\u0131<\/strong> ekran\u0131n\u0131 a\u00e7t\u0131\u011f\u0131n\u0131zda g\u00f6rd\u00fc\u011f\u00fcn\u00fcz renkler, sitenizin tek bir puanla \u00f6l\u00e7\u00fclen genel notu de\u011fildir. PHP s\u00fcr\u00fcm\u00fcnden HTTPS yap\u0131land\u0131rmas\u0131na, REST API eri\u015fiminden zamanlanm\u0131\u015f g\u00f6revlere kadar farkl\u0131 kontrollerin sonu\u00e7lar\u0131 burada toplan\u0131r.<\/p>\n<p>K\u0131rm\u0131z\u0131, turuncu ve ye\u015fil i\u015faretler ilk bak\u0131\u015fta gere\u011finden fazla tela\u015f yaratabiliyor. Destek ekibindeyken bir m\u00fc\u015fteri, &ldquo;Site sa\u011fl\u0131\u011f\u0131m y\u00fczde 82, Google bizi cezaland\u0131racak m\u0131?&rdquo; diye sormu\u015ftu. WordPress Site Sa\u011fl\u0131\u011f\u0131 bir SEO puan\u0131 de\u011fildir. Hosting performans\u0131na karar vermek i\u00e7in de tek ba\u015f\u0131na yeterli say\u0131lmaz.<\/p>\n<p>\u015e\u00f6yle anlatay\u0131m: Bu ekran\u0131 bir ar\u0131za panosu gibi d\u00fc\u015f\u00fcn\u00fcn. Hangi konunun incelenmesi gerekti\u011fini g\u00f6sterir; her uyar\u0131n\u0131n etkisini ise sitenizin yap\u0131s\u0131na bakarak de\u011ferlendirmeniz gerekir.<\/p>\n<h2><span id=\"Site_Sagligi_ekraninda_hangi_bolumler_var\">Site Sa\u011fl\u0131\u011f\u0131 ekran\u0131nda hangi b\u00f6l\u00fcmler var?<\/span><\/h2>\n<p>WordPress, Site Sa\u011fl\u0131\u011f\u0131 b\u00f6l\u00fcm\u00fcn\u00fc iki ana sekmede sunar:<\/p>\n<ul>\n<li><strong>Durum:<\/strong> WordPress&#8217;in otomatik kontrollerini, kritik sorunlar\u0131 ve \u00f6nerilen iyile\u015ftirmeleri g\u00f6sterir.<\/li>\n<li><strong>Bilgi:<\/strong> Sunucu, WordPress, tema, eklenti, veritaban\u0131 ve dosya sistemi hakk\u0131nda daha teknik ayr\u0131nt\u0131lar sunar.<\/li>\n<\/ul>\n<p>Durum sekmesi g\u00fcnl\u00fck kullan\u0131mda daha anla\u015f\u0131l\u0131rd\u0131r. Bilgi sekmesi ise destek bileti a\u00e7arken, ta\u015f\u0131ma planlarken veya bir geli\u015ftiriciyle \u00e7al\u0131\u015f\u0131rken ciddi zaman kazand\u0131r\u0131r. Buradaki ayr\u0131nt\u0131lar\u0131 kopyalay\u0131p payla\u015fabilirsiniz; yine de alan ad\u0131, dosya yolu, sunucu ad\u0131 ve e-posta adresi gibi bilgileri g\u00f6ndermeden \u00f6nce kontrol edin.<\/p>\n<h3><span id=\"Kritik_sorunlar\">Kritik sorunlar<\/span><\/h3>\n<p>K\u0131rm\u0131z\u0131 i\u015faretli bir kontrol genellikle g\u00fcvenlik, g\u00fcncelleme, HTTPS veya sitenin temel i\u015flevleriyle ilgilidir. Burada &ldquo;site \u015fu anda kesin bozuk&rdquo; anlam\u0131 aramay\u0131n. Daha do\u011fru sorular \u015funlard\u0131r: Bu durum sald\u0131r\u0131 y\u00fczeyini art\u0131r\u0131yor mu? G\u00fcncellemeleri engelliyor mu? Ziyaret\u00e7inin temel i\u015flemlerini bozuyor mu?<\/p>\n<p>WordPress s\u00fcr\u00fcm\u00fcn\u00fcn g\u00fcncel olmamas\u0131, destek d\u0131\u015f\u0131 bir PHP s\u00fcr\u00fcm\u00fcn\u00fcn kullan\u0131lmas\u0131 veya HTTPS&#8217;in d\u00fczg\u00fcn \u00e7al\u0131\u015fmamas\u0131 ger\u00e7ekten \u00f6nceliklidir. Bir eklentinin g\u00fcncelleme sunucusuna ba\u011flanamamas\u0131 ise WordPress.org taraf\u0131ndaki ge\u00e7ici bir a\u011f probleminden kaynaklan\u0131yorsa ayn\u0131 a\u011f\u0131rl\u0131kta de\u011ferlendirilmemelidir.<\/p>\n<h3><span id=\"Onerilen_iyilestirmeler\">\u00d6nerilen iyile\u015ftirmeler<\/span><\/h3>\n<p>Turuncu veya sar\u0131 uyar\u0131lar \u00e7o\u011fu zaman sitenin \u00e7al\u0131\u015fmas\u0131n\u0131 hemen durdurmaz. Kal\u0131c\u0131 nesne \u00f6nbelle\u011finin bulunmamas\u0131, otomatik g\u00fcncellemelerin s\u0131n\u0131rl\u0131 olmas\u0131 ya da baz\u0131 yap\u0131land\u0131rma tercihlerinin \u00f6nerilmemesi bu alanda g\u00f6r\u00fclebilir.<\/p>\n<p>&ldquo;Uyar\u0131y\u0131 kald\u0131rmak&rdquo; ile &ldquo;sorunu \u00e7\u00f6zmek&rdquo; ayn\u0131 \u015fey de\u011fildir. Kal\u0131c\u0131 nesne \u00f6nbelle\u011fi \u00f6nerisi g\u00f6rd\u00fc\u011f\u00fcn\u00fczde rastgele bir cache eklentisi kurup raporu ye\u015file \u00e7evirmeye \u00e7al\u0131\u015fmay\u0131n. Sunucunuz Redis veya Memcached sunuyor mu, mevcut sayfa \u00f6nbelle\u011fiyle \u00e7ak\u0131\u015f\u0131r m\u0131, WooCommerce oturumlar\u0131n\u0131 etkiler mi; \u00f6nce bunlara bak\u0131n.<\/p>\n<h3><span id=\"Basarili_testler\">Ba\u015far\u0131l\u0131 testler<\/span><\/h3>\n<p>Ye\u015fil kontroller iyi bir i\u015farettir, fakat kusursuzluk belgesi de\u011fildir. WordPress&#8217;in HTTPS&#8217;i, g\u00fcncelleme ba\u011flant\u0131s\u0131n\u0131 ve baz\u0131 temel yap\u0131land\u0131rmalar\u0131 olumlu test etmesi, ger\u00e7ek kullan\u0131c\u0131 deneyiminin de iyi oldu\u011fu anlam\u0131na gelmez.<\/p>\n<p>Bir sayfan\u0131n TTFB de\u011feri y\u00fcksek olabilir, veritaban\u0131 sorgular\u0131 yava\u015f \u00e7al\u0131\u015fabilir veya \u00f6deme ad\u0131m\u0131 JavaScript hatas\u0131 verebilir. Site Sa\u011fl\u0131\u011f\u0131 bunlar\u0131n hepsini \u00f6l\u00e7mez. Performans i\u00e7in sunucu loglar\u0131, taray\u0131c\u0131 geli\u015ftirici ara\u00e7lar\u0131, ger\u00e7ek kullan\u0131c\u0131 \u00f6l\u00e7\u00fcmleri ve gerekti\u011finde <code>mtr<\/code> gibi ara\u00e7lar gerekir.<\/p>\n<h2><span id=\"Kirmizi_uyariyi_gorur_gormez_eklenti_kurmayin\">K\u0131rm\u0131z\u0131 uyar\u0131y\u0131 g\u00f6r\u00fcr g\u00f6rmez eklenti kurmay\u0131n<\/span><\/h2>\n<p>Site Sa\u011fl\u0131\u011f\u0131 raporundaki her bildirim ayn\u0131 aciliyete sahip de\u011fil. Ben destek ak\u0131\u015f\u0131mda uyar\u0131lar\u0131 d\u00f6rt soruyla s\u0131n\u0131fland\u0131r\u0131yorum:<\/p>\n<ol>\n<li>Bu sorun ziyaret\u00e7inin siteyi kullanmas\u0131n\u0131 engelliyor mu?<\/li>\n<li>G\u00fcvenlik veya veri kayb\u0131 riski olu\u015fturuyor mu?<\/li>\n<li>G\u00fcncelleme, yedekleme ya da zamanlanm\u0131\u015f g\u00f6revleri etkiliyor mu?<\/li>\n<li>Sorun s\u00fcrekli mi, yoksa ge\u00e7ici bir ba\u011flant\u0131 hatas\u0131 m\u0131?<\/li>\n<\/ol>\n<p>&ldquo;REST API beklenmeyen bir yan\u0131t d\u00f6nd\u00fcrd\u00fc&rdquo; uyar\u0131s\u0131 buna iyi bir \u00f6rnektir. Gutenberg edit\u00f6r\u00fc, baz\u0131 bloklar, WooCommerce i\u015flemleri ve harici entegrasyonlar REST API&#8217;ye ihtiya\u00e7 duyabilir. Fakat yaln\u0131zca Site Sa\u011fl\u0131\u011f\u0131 testinin ba\u015far\u0131s\u0131z olmas\u0131, b\u00fct\u00fcn REST isteklerinin \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 kan\u0131tlamaz.<\/p>\n<p>\u00d6nce taray\u0131c\u0131 geli\u015ftirici ara\u00e7lar\u0131nda ilgili iste\u011fin HTTP durum koduna bak\u0131n. Ard\u0131ndan g\u00fcvenlik eklentisinin engelleme kayd\u0131n\u0131, web sunucusu loglar\u0131n\u0131 ve varsa CDN veya WAF kurallar\u0131n\u0131 inceleyin. Uyar\u0131y\u0131 yaln\u0131zca gizleyen bir eklenti \u00e7\u00f6z\u00fcm de\u011fildir.<\/p>\n<h2><span id=\"En_sik_gorulen_kontrolleri_tek_tek_okuyalim\">En s\u0131k g\u00f6r\u00fclen kontrolleri tek tek okuyal\u0131m<\/span><\/h2>\n<h3><span id=\"WordPress_tema_ve_eklentiler_guncel_mi\">WordPress, tema ve eklentiler g\u00fcncel mi?<\/span><\/h3>\n<p>Site Sa\u011fl\u0131\u011f\u0131 g\u00fcncel olmayan bile\u015fenleri g\u00f6sterdi\u011finde ilk i\u015f yedek almakt\u0131r. \u00dcretim sitelerinde &ldquo;hepsini g\u00fcncelle&rdquo; d\u00fc\u011fmesine basmadan \u00f6nce PHP s\u00fcr\u00fcm\u00fc, tema uyumlulu\u011fu, \u00f6zel kodlar ve WooCommerce s\u00fcr\u00fcm\u00fc kontrol edilmelidir.<\/p>\n<p>Ben g\u00fcncelleme \u00f6ncesinde en az\u0131ndan veritaban\u0131 d\u0131\u015fa aktar\u0131m\u0131n\u0131 al\u0131r\u0131m. WP-CLI kulland\u0131\u011f\u0131m bir sunucuda temel kontrol \u015fu \u015fekilde:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">wp core version\nwp plugin list --update=available\nwp theme list --update=available\nwp db export \/var\/backups\/site-before-update.sql<\/code><\/pre>\n<p>\u0130lk \u00fc\u00e7 komut bekleyen g\u00fcncellemeleri ve s\u00fcr\u00fcmleri g\u00f6sterir; son komut veritaban\u0131n\u0131 SQL dosyas\u0131na aktar\u0131r. Dosyan\u0131n ger\u00e7ekten olu\u015ftu\u011funu ve geri d\u00f6nd\u00fcr\u00fclebilir oldu\u011funu ayr\u0131ca kontrol edin. Ayn\u0131 diskte duran, hi\u00e7 denenmemi\u015f bir SQL dosyas\u0131na tek ba\u015f\u0131na yedek demek beni h\u00e2l\u00e2 huzursuz ediyor.<\/p>\n<p>Bir ta\u015f\u0131ma s\u0131ras\u0131nda m\u00fc\u015fterinin &ldquo;yede\u011fimiz var&rdquo; dedi\u011fi klas\u00f6r\u00fc a\u00e7t\u0131\u011f\u0131mda dosyalar\u0131n bulundu\u011funu, fakat kullan\u0131labilir bir veritaban\u0131 \u00e7\u0131kt\u0131s\u0131n\u0131n olmad\u0131\u011f\u0131n\u0131 g\u00f6rm\u00fc\u015ft\u00fcm. Geri d\u00f6n\u00fc\u015f gerekti\u011finde klas\u00f6r bo\u015f de\u011fildi; yine de i\u015fe yaram\u0131yordu. O g\u00fcnden beri yede\u011fi yaln\u0131zca olu\u015fturulmu\u015f dosya olarak de\u011fil, geri y\u00fcklenebilen bir kopya olarak de\u011ferlendiriyorum.<\/p>\n<h3><span id=\"PHP_surumu_ve_bellek_siniri\">PHP s\u00fcr\u00fcm\u00fc ve bellek s\u0131n\u0131r\u0131<\/span><\/h3>\n<p>PHP s\u00fcr\u00fcm\u00fc hem g\u00fcvenlik hem de uygulama uyumlulu\u011fu a\u00e7\u0131s\u0131ndan \u00f6nemlidir. Daha yeni bir s\u00fcr\u00fcme ge\u00e7meden \u00f6nce tema ve eklentilerin destek durumunu kontrol edin. Bir sitenin PHP 8.3 ile \u00e7al\u0131\u015fabilmesi, eski bir eklentinin sessizce bozulmayaca\u011f\u0131 anlam\u0131na gelmez.<\/p>\n<p><code>WP_MEMORY_LIMIT<\/code> veya <code>memory_limit<\/code> uyar\u0131s\u0131 g\u00f6r\u00fcyorsan\u0131z de\u011feri rastgele y\u00fckseltmeyin. Daha fazla bellek, hatal\u0131 bir sorgunun veya gereksiz d\u00f6ng\u00fcn\u00fcn nedenini ortadan kald\u0131rmaz. Bir destek biletinde yaln\u0131zca <code>memory_limit<\/code> art\u0131r\u0131lmas\u0131 istenmi\u015fti; inceleyince rapor eklentisinin <code>WHERE<\/code> ko\u015fulu olmadan b\u00fcy\u00fck bir tabloyu tarad\u0131\u011f\u0131n\u0131 bulmu\u015ftum. Belle\u011fi art\u0131rmak siteyi k\u0131sa s\u00fcre rahatlat\u0131rd\u0131, as\u0131l problemi de\u011fil.<\/p>\n<h3><span id=\"HTTPS_ve_guvenli_baglanti\">HTTPS ve g\u00fcvenli ba\u011flant\u0131<\/span><\/h3>\n<p>HTTPS uyar\u0131s\u0131 varsa sertifikan\u0131n ge\u00e7erli olup olmad\u0131\u011f\u0131n\u0131, alan ad\u0131n\u0131n do\u011fru sertifikaya y\u00f6nlenip y\u00f6nlenmedi\u011fini ve HTTP&#8217;den HTTPS&#8217;e y\u00f6nlendirmenin d\u00fczg\u00fcn \u00e7al\u0131\u015f\u0131p \u00e7al\u0131\u015fmad\u0131\u011f\u0131n\u0131 inceleyin. CDN, reverse proxy veya load balancer kullan\u0131l\u0131yorsa WordPress&#8217;in d\u0131\u015far\u0131dan HTTPS g\u00f6rd\u00fc\u011f\u00fcnden emin olun.<\/p>\n<p><code>wp-config.php<\/code> i\u00e7inde sabitlenmi\u015f eski bir <code>siteurl<\/code> veya <code>home<\/code> adresi, yanl\u0131\u015f y\u00f6nlendirme d\u00f6ng\u00fclerine neden olabilir. Bu de\u011ferleri de\u011fi\u015ftirmeden \u00f6nce veritaban\u0131 yede\u011fi al\u0131n. WordPress&#8217;in URL de\u011ferlerini g\u00f6rmek i\u00e7in:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">wp option get home\nwp option get siteurl<\/code><\/pre>\n<p>\u00c7\u0131kt\u0131da <code>https:\/\/<\/code> bulunmas\u0131 tek ba\u015f\u0131na yeterli de\u011fildir. Sayfa kaynaklar\u0131nda veya taray\u0131c\u0131n\u0131n a\u011f sekmesinde HTTP kaynaklar\u0131 kalm\u0131\u015fsa karma i\u00e7erik devam edebilir.<\/p>\n<h3><span id=\"REST_API_ve_loopback_istekleri\">REST API ve loopback istekleri<\/span><\/h3>\n<p>Loopback iste\u011fi, sitenin kendisine HTTP \u00fczerinden ula\u015farak WordPress&#8217;in arka plandaki i\u015flerini \u00e7al\u0131\u015ft\u0131rabildi\u011fini test eder. Zamanlanm\u0131\u015f g\u00f6revler, baz\u0131 bak\u0131m i\u015flemleri ve eklentilerin arka plan \u00e7a\u011fr\u0131lar\u0131 bundan etkilenebilir.<\/p>\n<p>Ba\u015far\u0131s\u0131zl\u0131\u011f\u0131n yayg\u0131n nedenleri aras\u0131nda g\u00fcvenlik eklentisinin sunucunun kendi isteklerini engellemesi, hatal\u0131 DNS, SSL do\u011frulama problemi, PHP fatal error, d\u00fc\u015f\u00fck zaman a\u015f\u0131m\u0131 ve reverse proxy yap\u0131land\u0131rmas\u0131 bulunur. Sunucuda ilk bakt\u0131\u011f\u0131m yerlerden biri PHP-FPM ve web sunucusu loglar\u0131d\u0131r. Siteye d\u0131\u015far\u0131dan HTTP iste\u011fi g\u00f6ndermek i\u00e7in \u015fu kontrol\u00fc kullanabilirsiniz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">curl -I https:\/\/example.com\/wp-json\/<\/code><\/pre>\n<p>Burada 200 veya baz\u0131 yap\u0131land\u0131rmalarda 3xx g\u00f6rmek tek ba\u015f\u0131na her \u015feyi kan\u0131tlamaz; fakat 403, 404, 500 ve 502 kodlar\u0131 ara\u015ft\u0131rma y\u00f6n\u00fcn\u00fc daralt\u0131r. Ger\u00e7ek alan ad\u0131n\u0131z\u0131 kullan\u0131n ve \u00fcretim sisteminde arka arkaya yo\u011fun test yapmay\u0131n.<\/p>\n<p>REST API ba\u011flant\u0131 sorunlar\u0131nda <a href=\"https:\/\/www.dchost.com\/blog\/wordpress-veritabani-baglanti-hatasi-5-cozum\/\">WordPress Veritaban\u0131 Ba\u011flant\u0131 Hatas\u0131: 5 \u00c7\u00f6z\u00fcm<\/a> ba\u015fl\u0131\u011f\u0131ndaki veritaban\u0131 ve uygulama logu kontrolleri de i\u015finize yarayabilir. REST iste\u011fi veritaban\u0131na ula\u015fam\u0131yorsa raporda g\u00f6r\u00fcnen hata yaln\u0131zca a\u011f katman\u0131na bak\u0131larak \u00e7\u00f6z\u00fclemez.<\/p>\n<h3><span id=\"Zamanlanmis_gorevler_ve_WP-Cron\">Zamanlanm\u0131\u015f g\u00f6revler ve WP-Cron<\/span><\/h3>\n<p>WP-Cron, klasik sistem cron&#8217;u gibi sabit aral\u0131klarla \u00e7al\u0131\u015fan bir servis de\u011fildir. Genellikle siteye gelen bir istek s\u0131ras\u0131nda tetiklenir. Trafi\u011fi d\u00fc\u015f\u00fck sitelerde g\u00f6revler gecikebilir; yo\u011fun sitelerde ise gere\u011finden fazla cron \u00e7a\u011fr\u0131s\u0131 olu\u015fabilir.<\/p>\n<p>Bekleyen g\u00f6revleri WP-CLI ile listeleyebilirsiniz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">wp cron event list --fields=hook,time_gmt,interval<\/code><\/pre>\n<p>Bu komut hook ad\u0131n\u0131, bir sonraki \u00e7al\u0131\u015fma zaman\u0131n\u0131 ve varsa aral\u0131\u011f\u0131 g\u00f6sterir. Daha geni\u015f \u00e7\u0131kt\u0131 gerekti\u011finde alan filtresini kald\u0131rman\u0131z yeterli:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">wp cron event list<\/code><\/pre>\n<p>\u00c7\u0131kt\u0131da ayn\u0131 hook&#8217;un \u00e7ok say\u0131da birikmesi, g\u00f6revin \u00e7al\u0131\u015famad\u0131\u011f\u0131n\u0131 veya bir eklentinin s\u00fcrekli yeni g\u00f6rev olu\u015fturdu\u011funu d\u00fc\u015f\u00fcnd\u00fcr\u00fcr. Bir g\u00f6revi silmeden \u00f6nce hangi eklentinin olu\u015fturdu\u011funu bulun. Rastgele cron temizli\u011fi, WooCommerce e-postalar\u0131n\u0131 veya sipari\u015f i\u015flemlerini bozabilir.<\/p>\n<h3><span id=\"Kalici_nesne_onbellegi\">Kal\u0131c\u0131 nesne \u00f6nbelle\u011fi<\/span><\/h3>\n<p>Site Sa\u011fl\u0131\u011f\u0131, kal\u0131c\u0131 nesne \u00f6nbelle\u011fi bulunmad\u0131\u011f\u0131nda bunu \u00f6neri olarak g\u00f6sterebilir. Redis gibi bir sistem, veritaban\u0131ndan tekrar tekrar okunacak se\u00e7enekleri ve sorgu sonu\u00e7lar\u0131n\u0131 bellekte tutabilir. Bu yap\u0131 sayfa \u00f6nbelle\u011fiyle ayn\u0131 i\u015fi yapmaz.<\/p>\n<p>Kal\u0131c\u0131 \u00f6nbellek yok diye site mutlaka yava\u015ft\u0131r denemez. K\u00fc\u00e7\u00fck ve d\u00fc\u015f\u00fck trafikli bir sitenin as\u0131l darbo\u011faz\u0131 b\u00fcy\u00fck bir g\u00f6rsel, k\u00f6t\u00fc yaz\u0131lm\u0131\u015f bir eklenti veya yava\u015f bir harici API olabilir. WooCommerce sepet ve kullan\u0131c\u0131 oturumlar\u0131nda cache kurallar\u0131 dikkatle haz\u0131rlanmal\u0131d\u0131r.<\/p>\n<h2><span id=\"Bilgi_sekmesi_destek_biletini_kisaltir\">Bilgi sekmesi destek biletini k\u0131salt\u0131r<\/span><\/h2>\n<p>Destek ekibine yaln\u0131zca &ldquo;Site sa\u011fl\u0131\u011f\u0131nda hata var&rdquo; yazmak yerine Bilgi sekmesindeki ilgili b\u00f6l\u00fcm\u00fc payla\u015fman\u0131z te\u015fhisi h\u0131zland\u0131r\u0131r. WordPress s\u00fcr\u00fcm\u00fc, PHP s\u00fcr\u00fcm\u00fc, sunucu yaz\u0131l\u0131m\u0131, veritaban\u0131 s\u00fcr\u00fcm\u00fc, aktif tema, eklentiler ve dosya sistemi bilgisi burada g\u00f6r\u00fcn\u00fcr.<\/p>\n<p>\u015eifre, API anahtar\u0131 veya veritaban\u0131 parolas\u0131 bu ekranda normalde a\u00e7\u0131k \u015fekilde bulunmamal\u0131d\u0131r; yine de d\u0131\u015far\u0131 aktard\u0131\u011f\u0131n\u0131z metni g\u00f6zden ge\u00e7irin. Gereksiz t\u00fcm bilgileri g\u00f6ndermek yerine hatayla ili\u015fkili b\u00f6l\u00fcmleri payla\u015fmak daha g\u00fcvenlidir.<\/p>\n<p>WordPress ve PHP s\u00fcr\u00fcm\u00fcn\u00fc terminalden de kontrol edebilirsiniz:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">wp core version\nphp -v<\/code><\/pre>\n<p>Bu \u00e7\u0131kt\u0131lar yaln\u0131zca s\u00fcr\u00fcm\u00fc g\u00f6sterir. Sunucuda birden fazla PHP s\u00fcr\u00fcm\u00fc varsa komut sat\u0131r\u0131ndaki <code>php -v<\/code> ile web sitesinin kulland\u0131\u011f\u0131 PHP s\u00fcr\u00fcm\u00fc farkl\u0131 olabilir. Bu ayr\u0131m \u00f6zellikle payla\u015f\u0131ml\u0131 hosting ortamlar\u0131nda kolayca g\u00f6zden ka\u00e7ar.<\/p>\n<h2><span id=\"Site_Sagligi_raporu_ile_performans_raporu_ayni_sey_degil\">Site Sa\u011fl\u0131\u011f\u0131 raporu ile performans raporu ayn\u0131 \u015fey de\u011fil<\/span><\/h2>\n<p>Site Sa\u011fl\u0131\u011f\u0131; yap\u0131land\u0131rma, g\u00fcvenlik ve WordPress&#8217;in temel \u00e7al\u0131\u015fma ko\u015fullar\u0131 hakk\u0131nda sinyal verir. Sayfa y\u00fckleme s\u00fcresini, ger\u00e7ek ziyaret\u00e7ilerin ba\u011flant\u0131 kalitesini veya Google arama trafi\u011fini b\u00fct\u00fcn ayr\u0131nt\u0131lar\u0131yla \u00f6l\u00e7mez.<\/p>\n<p>Bir site sa\u011fl\u0131kl\u0131 g\u00f6r\u00fcn\u00fcp yava\u015f olabilir. Ana sayfadaki \u00fcr\u00fcn sorgusu 4 saniye s\u00fcr\u00fcyorsa WordPress&#8217;in HTTPS, REST API ve g\u00fcncelleme testleri ba\u015far\u0131l\u0131 \u00e7\u0131ksa bile ziyaret\u00e7i beklemek zorunda kal\u0131r.<\/p>\n<p>Arama g\u00f6r\u00fcn\u00fcrl\u00fc\u011f\u00fcn\u00fc de\u011ferlendirmek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/google-search-console-performans-raporu-nasil-okunur\/\">Google Search Console Performans Raporu Nas\u0131l Okunur?<\/a> ba\u015fl\u0131\u011f\u0131ndaki t\u0131klama, g\u00f6sterim, sorgu ve sayfa ayr\u0131mlar\u0131na bakmak gerekir. Site Sa\u011fl\u0131\u011f\u0131&#8217;ndaki ye\u015fil i\u015faret, organik trafi\u011fin iyi oldu\u011funu s\u00f6ylemez; iki ekran farkl\u0131 sorulara cevap verir.<\/p>\n<p>Hosting kaynakl\u0131 bir \u015f\u00fcphe varsa CPU, RAM, disk I\/O, PHP-FPM yo\u011funlu\u011fu ve web sunucusu loglar\u0131n\u0131 ayr\u0131ca inceleyin. Kendi lab ortam\u0131mda bile &ldquo;site yava\u015f&rdquo; demeden \u00f6nce <code>mtr<\/code>, web sunucusu eri\u015fim logu ve veritaban\u0131 sorgu s\u00fcresini ayr\u0131 ayr\u0131 kontrol ederim. Tek bir renkli uyar\u0131ya bakarak altyap\u0131y\u0131 su\u00e7lamak te\u015fhisi genellikle uzat\u0131r.<\/p>\n<h2><span id=\"Uyari_goruldugunde_uygulanacak_guvenli_sira\">Uyar\u0131 g\u00f6r\u00fcld\u00fc\u011f\u00fcnde uygulanacak g\u00fcvenli s\u0131ra<\/span><\/h2>\n<ol>\n<li><strong>Mesaj\u0131n tamam\u0131n\u0131 okuyun.<\/strong> K\u0131rm\u0131z\u0131 ba\u015fl\u0131k kadar a\u00e7\u0131klama ve \u00f6nerilen eylem de \u00f6nemlidir.<\/li>\n<li><strong>De\u011fi\u015fiklikten \u00f6nce yedek al\u0131n.<\/strong> PHP, tema, eklenti veya HTTPS yap\u0131land\u0131rmas\u0131na dokunuyorsan\u0131z geri d\u00f6n\u00fc\u015f yolunuz olsun.<\/li>\n<li><strong>Staging ortam\u0131nda do\u011frulay\u0131n.<\/strong> \u00dcretim sitesinde eklenti kapat\u0131p a\u00e7arak rastgele denemeler yapmay\u0131n.<\/li>\n<li><strong>Loglara bak\u0131n.<\/strong> <code>500<\/code> hatas\u0131, REST problemi ve loopback ba\u015far\u0131s\u0131zl\u0131\u011f\u0131 \u00e7o\u011fu zaman loglarda daha a\u00e7\u0131k g\u00f6r\u00fcn\u00fcr.<\/li>\n<li><strong>Tek de\u011fi\u015fiklik yap\u0131n.<\/strong> Ayn\u0131 anda be\u015f eklentiyi kapat\u0131rsan\u0131z hangisinin sorunu d\u00fczeltti\u011fini anlayamazs\u0131n\u0131z.<\/li>\n<li><strong>Uyar\u0131y\u0131 tekrar test edin.<\/strong> D\u00fczeltme sonras\u0131 Site Sa\u011fl\u0131\u011f\u0131 ekran\u0131n\u0131 yenileyin; ard\u0131ndan sitenin ger\u00e7ek i\u015f ak\u0131\u015f\u0131n\u0131 da deneyin.<\/li>\n<\/ol>\n<p>Geri d\u00f6n\u00fc\u015f plan\u0131 burada \u00f6zellikle \u00f6nemlidir. Yedekleme konusunda daha \u00f6nce bo\u015f bir klas\u00f6r\u00fcn &ldquo;yedek&rdquo; san\u0131ld\u0131\u011f\u0131n\u0131 g\u00f6rd\u00fcm; ta\u015f\u0131ma s\u0131ras\u0131nda geri d\u00f6nmek gerekti\u011finde dosya vard\u0131 ama kullan\u0131labilir bir veritaban\u0131 yoktu. Bu y\u00fczden g\u00fcncelleme \u00f6ncesinde yaln\u0131zca dosya ve veritaban\u0131 \u00e7\u0131kt\u0131s\u0131n\u0131 de\u011fil, m\u00fcmk\u00fcnse k\u00fc\u00e7\u00fck bir geri y\u00fckleme provas\u0131n\u0131 da planlar\u0131m.<\/p>\n<h2><span id=\"WordPress_Site_Sagligi_raporu_ne_zaman_ciddiye_alinmali\">WordPress Site Sa\u011fl\u0131\u011f\u0131 raporu ne zaman ciddiye al\u0131nmal\u0131?<\/span><\/h2>\n<p>G\u00fcvenlik g\u00fcncellemesi yap\u0131lam\u0131yorsa, PHP s\u00fcr\u00fcm\u00fc destek d\u0131\u015f\u0131ysa, HTTPS yanl\u0131\u015fsa, loopback ve REST API hatalar\u0131 sitenin i\u015f ak\u0131\u015f\u0131n\u0131 etkiliyorsa veya cron g\u00f6revleri birikiyorsa beklemeyin. Bunlar raporun rengi de\u011fi\u015fsin diye de\u011fil, sitenin \u00e7al\u0131\u015fma ko\u015fullar\u0131 bozulabilece\u011fi i\u00e7in \u00f6nceliklidir.<\/p>\n<p>Yaln\u0131zca kal\u0131c\u0131 nesne \u00f6nbelle\u011fi \u00f6nerisi veya otomatik g\u00fcncelleme tercihi g\u00f6r\u00fcyorsan\u0131z \u00f6nce sitenizin ihtiya\u00e7lar\u0131n\u0131 de\u011ferlendirin. Her \u00f6neriyi uygulamak zorunda de\u011filsiniz; fakat neden uygulamad\u0131\u011f\u0131n\u0131z\u0131 bilmeniz gerekir.<\/p>\n<p>Benim pratik kontrol\u00fcm \u015fu: Site Sa\u011fl\u0131\u011f\u0131 ekran\u0131n\u0131 a\u00e7ar\u0131m, k\u0131rm\u0131z\u0131 maddeleri \u00f6nem s\u0131ras\u0131na dizerim, Bilgi sekmesinden teknik ba\u011flam\u0131 \u00e7\u0131kar\u0131r\u0131m, sonra log ve ger\u00e7ek kullan\u0131c\u0131 ak\u0131\u015f\u0131yla kar\u015f\u0131la\u015ft\u0131r\u0131r\u0131m. Ye\u015fil ekran\u0131 g\u00f6r\u00fcnce i\u015fi bitmi\u015f saymam. Sepete \u00fcr\u00fcn ekleme, ileti\u015fim formu, y\u00f6netici giri\u015fi ve e-posta g\u00f6nderimi de \u00e7al\u0131\u015f\u0131yor mu; as\u0131l cevap oradad\u0131r.<\/p>\n<h2><span id=\"Sik_Sorulan_Sorular\">S\u0131k Sorulan Sorular<\/span><\/h2>\n<h3><span id=\"WordPress_Site_Sagligi_raporundaki_kirmizi_uyari_siteyi_kapatir_mi\">WordPress Site Sa\u011fl\u0131\u011f\u0131 raporundaki k\u0131rm\u0131z\u0131 uyar\u0131 siteyi kapat\u0131r m\u0131?<\/span><\/h3>\n<p>Her k\u0131rm\u0131z\u0131 uyar\u0131 sitenin hemen kapanaca\u011f\u0131 anlam\u0131na gelmez. G\u00fcvenlik, HTTPS, PHP uyumlulu\u011fu, REST API veya g\u00fcncelleme sorunlar\u0131 temel i\u015flevleri etkileyebilece\u011fi i\u00e7in a\u00e7\u0131klamay\u0131 ve loglar\u0131 gecikmeden incelemek gerekir.<\/p>\n<h3><span id=\"WordPress_Site_Sagligi_puani_SEO_siralamasini_etkiler_mi\">WordPress Site Sa\u011fl\u0131\u011f\u0131 puan\u0131 SEO s\u0131ralamas\u0131n\u0131 etkiler mi?<\/span><\/h3>\n<p>Site Sa\u011fl\u0131\u011f\u0131 ekran\u0131ndaki renk veya genel durum, Google&#8217;da kullan\u0131lan do\u011frudan bir s\u0131ralama puan\u0131 de\u011fildir. Yine de bozuk HTTPS, yava\u015f sunucu, eri\u015filemeyen sayfalar veya \u00e7al\u0131\u015fmayan kullan\u0131c\u0131 ak\u0131\u015flar\u0131 SEO&#8217;yu ve d\u00f6n\u00fc\u015f\u00fcmleri dolayl\u0131 olarak etkileyebilir.<\/p>\n<h3><span id=\"REST_API_hatasi_nasil_duzeltilir\">REST API hatas\u0131 nas\u0131l d\u00fczeltilir?<\/span><\/h3>\n<p>\u00d6nce <code>\/wp-json\/<\/code> adresinin HTTP durum kodunu, g\u00fcvenlik eklentisi kay\u0131tlar\u0131n\u0131, web sunucusu loglar\u0131n\u0131 ve SSL yap\u0131land\u0131rmas\u0131n\u0131 kontrol edin. 403, 500 veya 502 gibi kodun kayna\u011f\u0131 bulunmadan eklenti kapat\u0131p a\u00e7mak kal\u0131c\u0131 \u00e7\u00f6z\u00fcm sa\u011flamaz.<\/p>\n<h3><span id=\"Site_Sagligi_raporu_ne_siklikla_kontrol_edilmeli\">Site Sa\u011fl\u0131\u011f\u0131 raporu ne s\u0131kl\u0131kla kontrol edilmeli?<\/span><\/h3>\n<p>G\u00fcncelleme, PHP s\u00fcr\u00fcm\u00fc de\u011fi\u015fikli\u011fi, ta\u015f\u0131ma veya g\u00fcvenlik yap\u0131land\u0131rmas\u0131 sonras\u0131nda mutlaka kontrol edin. Normal sitelerde ayda bir bakmak ve kritik bildirimleri e-posta ya da izleme sistemi \u00fczerinden takip etmek pratik bir d\u00fczendir.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>WordPress Site Sa\u011fl\u0131\u011f\u0131 raporundaki kritik sorunlar\u0131 ve \u00f6nerileri nas\u0131l yorumlayaca\u011f\u0131n\u0131z\u0131; PHP, HTTPS, REST API, WP-Cron ve \u00f6nbellek kontrollerini a\u00e7\u0131kl\u0131yorum.<\/p>\n","protected":false},"author":4,"featured_media":5152,"comment_status":"closed","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23],"tags":[41,476,474,116,475,477],"class_list":["post-5156","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-wordpress","tag-php","tag-rest-api","tag-site-sagligi","tag-wordpress","tag-wordpress-guvenligi","tag-wp-cron"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5156","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=5156"}],"version-history":[{"count":1,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5156\/revisions"}],"predecessor-version":[{"id":5158,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/5156\/revisions\/5158"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/5152"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=5156"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=5156"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=5156"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}