{"id":1033,"date":"2026-10-04T15:58:52","date_gmt":"2026-10-04T15:58:52","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=1033"},"modified":"2026-10-04T09:21:40","modified_gmt":"2026-10-04T09:21:40","slug":"wordpress-bakim-modu-nasil-acilir","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/wordpress-bakim-modu-nasil-acilir\/","title":{"rendered":"WordPress Bak\u0131m Modu Nas\u0131l A\u00e7\u0131l\u0131r?"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; WordPress Bak\u0131m Modu<\/p>\n<p>K\u0131sa g\u00fcncellemelerde WordPress&#039;in yerle\u015fik bak\u0131m mekanizmas\u0131 yeterlidir. Uzun veya \u00f6zel eri\u015fim gerektiren i\u015flemlerde 503 yan\u0131t\u0131n\u0131, yede\u011fi ve geri d\u00f6n\u00fc\u015f plan\u0131n\u0131 birlikte haz\u0131rlay\u0131n.<\/p>\n<ul>\n<li><strong>H\u0131zl\u0131 y\u00f6ntem<\/strong> \u2014 WordPress k\u00f6k dizininde .maintenance dosyas\u0131 olu\u015fturun veya WP-CLI ile maintenance-mode activate komutunu \u00e7al\u0131\u015ft\u0131r\u0131n.<\/li>\n<li><strong>Kapatma i\u015flemi<\/strong> \u2014 G\u00fcncelleme bitince wp maintenance-mode deactivate \u00e7al\u0131\u015ft\u0131r\u0131n ya da yaln\u0131zca do\u011fru dizindeki .maintenance dosyas\u0131n\u0131 kald\u0131r\u0131n.<\/li>\n<li><strong>Do\u011fru yan\u0131t<\/strong> \u2014 Bak\u0131m sayfas\u0131 ge\u00e7ici durum i\u00e7in 503 Service Unavailable d\u00f6nd\u00fcrmelidir.<\/li>\n<li><strong>\u00d6n haz\u0131rl\u0131k<\/strong> \u2014 Dosya ve veritaban\u0131 yede\u011fi al\u0131n, etkin eklentileri kaydedin ve geri d\u00f6n\u00fc\u015f yolunu belirleyin.<\/li>\n<li><strong>Cache kontrol\u00fc<\/strong> \u2014 Bak\u0131m sonras\u0131nda CDN, reverse proxy ve taray\u0131c\u0131 cache&#039;inin eski sayfay\u0131 sunmad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/li>\n<li><strong>Sa\u011fl\u0131k testi<\/strong> \u2014 Ana sayfa, wp-admin, formlar, webhook&#039;lar ve izleme URL&#039;sini bak\u0131m bitince ayr\u0131 ayr\u0131 test edin.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">WordPress bak\u0131m modunu a\u00e7man\u0131n pratik yolu, kurulum dizininde .maintenance dosyas\u0131 olu\u015fturmak veya WP-CLI ile wp maintenance-mode activate komutunu \u00e7al\u0131\u015ft\u0131rmakt\u0131r. \u0130\u015flem tamamland\u0131\u011f\u0131nda modu a\u00e7\u0131k\u00e7a kapat\u0131n, 503 yan\u0131t\u0131n\u0131 do\u011frulay\u0131n ve cache katmanlar\u0131n\u0131 kontrol edin; aksi h\u00e2lde site g\u00fcncel olsa bile ziyaret\u00e7iler bak\u0131m ekran\u0131 g\u00f6rebilir.<\/p>\n<div class=\"aiw-toc\" style=\"border:1px solid #dbe3ea;border-radius:8px;padding:16px 20px;margin:0 0 28px\">\n<p class=\"aiw-toc-head\"><strong>\u0130\u00e7indekiler<\/strong><span class=\"aiw-toc-meta\"> \u00b7 11 dk okuma<\/span><\/p>\n<ol style=\"margin:10px 0 0;padding-left:22px\">\n<li><a href=\"#wordpress-bakim-modu-ne-zaman-kullanilmali\">WordPress bak\u0131m modu ne zaman kullan\u0131lmal\u0131?<\/a><\/li>\n<li><a href=\"#wordpress-bakim-modu-nasil-acilir\">WordPress bak\u0131m modu nas\u0131l a\u00e7\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#bakim-modu-hangi-yontemle-acilmali\">Bak\u0131m modu hangi y\u00f6ntemle a\u00e7\u0131lmal\u0131?<\/a><\/li>\n<li><a href=\"#wordpress-bakim-modu-acilmadan-once-neler-kontrol-edilmeli\">WordPress bak\u0131m modu a\u00e7\u0131lmadan \u00f6nce neler kontrol edilmeli?<\/a><\/li>\n<li><a href=\"#bakim-ekrani-ziyaretcilere-nasil-gosterilir\">Bak\u0131m ekran\u0131 ziyaret\u00e7ilere nas\u0131l g\u00f6sterilir?<\/a><\/li>\n<li><a href=\"#yonetici-erisimi-nasil-korunur\">Y\u00f6netici eri\u015fimi nas\u0131l korunur?<\/a><\/li>\n<li><a href=\"#bakim-modu-kapanmiyorsa-ne-yapilir\">Bak\u0131m modu kapanm\u0131yorsa ne yap\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#bakim-modu-seo-ve-guvenlik-acisindan-sorun-cikarir-mi\">Bak\u0131m modu SEO ve g\u00fcvenlik a\u00e7\u0131s\u0131ndan sorun \u00e7\u0131kar\u0131r m\u0131?<\/a><\/li>\n<li><a href=\"#bakim-modunu-acmadan-once-sunlari-kontrol-edin\">Bak\u0131m Modunu A\u00e7madan \u00d6nce \u015eunlar\u0131 Kontrol Edin<\/a><\/li>\n<li><a href=\"#sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/a><\/li>\n<li><a href=\"#kaynaklar\">Kaynaklar<\/a><\/li>\n<\/ol>\n<\/div>\n<h2 id=\"wordpress-bakim-modu-ne-zaman-kullanilmali\">WordPress bak\u0131m modu ne zaman kullan\u0131lmal\u0131?<\/h2>\n<p>WordPress bak\u0131m modu, g\u00fcncelleme veya ta\u015f\u0131ma s\u0131ras\u0131nda ziyaret\u00e7iye sitenin ge\u00e7ici olarak kullan\u0131lamad\u0131\u011f\u0131n\u0131 bildirir. K\u0131sa i\u015flemlerde WordPress&#8217;in yerle\u015fik <code>.maintenance<\/code> mekanizmas\u0131 yeterlidir. Daha uzun \u00e7al\u0131\u015fmalarda HTTP <code>503 Service Unavailable<\/code> yan\u0131t\u0131, a\u00e7\u0131k bir bilgilendirme sayfas\u0131 ve y\u00f6neticiler i\u00e7in kontroll\u00fc eri\u015fim birlikte planlanmal\u0131d\u0131r.<\/p>\n<p>Bak\u0131m modunu a\u00e7madan \u00f6nce i\u015flemin tahmini s\u00fcresini ve geri d\u00f6n\u00fc\u015f yolunu belirleyin. Bir eklenti g\u00fcncellemesi birka\u00e7 saniyede bitebilir; veritaban\u0131 ta\u015f\u0131mas\u0131 veya tema de\u011fi\u015fikli\u011fi dakikalar s\u00fcrebilir. Ayn\u0131 y\u00f6ntemi her senaryoda kullanmak, ziyaret\u00e7iye bo\u015f bir sayfa g\u00f6sterebilir ya da bak\u0131m ekran\u0131n\u0131n gere\u011finden uzun kalmas\u0131na neden olabilir.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>K\u0131sa bir bak\u0131m i\u00e7in WP-CLI kullan\u0131n: wp maintenance-mode activate. \u0130\u015f bitti\u011finde deactivate komutunu \u00e7al\u0131\u015ft\u0131rmak, dosya ad\u0131n\u0131 elle aramaktan daha az hata \u00fcretir.<\/p>\n<\/div>\n<h2 id=\"wordpress-bakim-modu-nasil-acilir\">WordPress bak\u0131m modu nas\u0131l a\u00e7\u0131l\u0131r?<\/h2>\n<p>En h\u0131zl\u0131 y\u00f6ntem, WordPress kurulum dizininde <code>.maintenance<\/code> adl\u0131 dosya olu\u015fturmakt\u0131r. WordPress bu dosyay\u0131 alg\u0131lad\u0131\u011f\u0131nda yerle\u015fik bak\u0131m ekran\u0131n\u0131 g\u00f6sterir. Dosya WordPress&#8217;in k\u00f6k dizininde bulunmal\u0131d\u0131r; VPS kurulumlar\u0131nda bu dizin \u00e7o\u011funlukla <code>\/var\/www\/html<\/code>, baz\u0131 hosting hesaplar\u0131nda ise <code>public_html<\/code> olur.<\/p>\n<p>\u00d6nce do\u011fru dizini ve WordPress kurulumunu do\u011frulay\u0131n:<\/p>\n<pre><code>cd \/var\/www\/html\nwp core is-installed\npwd\nls -la wp-config.php<\/code><\/pre>\n<p><code>wp core is-installed<\/code> komutu ba\u015far\u0131l\u0131 d\u00f6n\u00fcyorsa WP-CLI do\u011fru WordPress dizininde \u00e7al\u0131\u015f\u0131yor demektir. <code>wp-config.php<\/code> dosyas\u0131n\u0131n listelenmesi de kontrol\u00fc destekler; tek ba\u015f\u0131na kesin kan\u0131t say\u0131lmaz.<\/p>\n<p>WP-CLI kuruluysa bak\u0131m modunu \u015fu \u015fekilde a\u00e7abilirsiniz:<\/p>\n<pre><code>wp maintenance-mode activate\nwp maintenance-mode status<\/code><\/pre>\n<p>Durum \u00e7\u0131kt\u0131s\u0131nda bak\u0131m modunun etkin oldu\u011fu ve olu\u015fturulma zaman\u0131 g\u00f6r\u00fcn\u00fcr. WP-CLI kullan\u0131lam\u0131yorsa dosya y\u00f6ntemi uygulanabilir:<\/p>\n<pre><code>cd \/var\/www\/html\nprintf '&lt;?php $upgrading = time(); ?&gt;' &gt; .maintenance\nchmod 644 .maintenance\nls -l .maintenance<\/code><\/pre>\n<p>PHP sat\u0131r\u0131, WordPress&#8217;in bekledi\u011fi bak\u0131m dosyas\u0131 bi\u00e7imidir. Dosya sahipli\u011fini mevcut WordPress dosyalar\u0131yla kar\u015f\u0131la\u015ft\u0131r\u0131n; dosyay\u0131 <code>chmod 777<\/code> ile yaz\u0131labilir h\u00e2le getirmek izin sorununu \u00e7\u00f6zmez, gereksiz eri\u015fim a\u00e7ar.<\/p>\n<p>Bak\u0131m tamamland\u0131\u011f\u0131nda modu kapatmak i\u00e7in WP-CLI komutunu tercih edin:<\/p>\n<pre><code>wp maintenance-mode deactivate\nwp maintenance-mode status<\/code><\/pre>\n<p>Dosya y\u00f6ntemi kullan\u0131ld\u0131ysa:<\/p>\n<pre><code>rm -f \/var\/www\/html\/.maintenance\ntest ! -e \/var\/www\/html\/.maintenance &amp;&amp; echo 'Bak\u0131m modu kapal\u0131'<\/code><\/pre>\n<p>Silme komutundan \u00f6nce <code>pwd<\/code> ve <code>hostname<\/code> \u00e7\u0131kt\u0131s\u0131n\u0131 kontrol edin. Yanl\u0131\u015f sunucuda i\u015flem yapmak, bak\u0131m ekran\u0131ndan \u00e7ok daha pahal\u0131 bir hata \u00e7\u0131karabilir.<\/p>\n<p><strong>Kontrol noktas\u0131<\/strong> &#8211; Bak\u0131m dosyas\u0131n\u0131 olu\u015fturmadan \u00f6nce WordPress k\u00f6k dizinini <code>wp core is-installed<\/code> ile do\u011frulay\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>Bak\u0131m dosyas\u0131n\u0131 yanl\u0131\u015f dizinde olu\u015fturmak s\u0131k g\u00f6r\u00fcl\u00fcr. Komuttan \u00f6nce pwd, hostname ve wp core is-installed \u00e7\u0131kt\u0131s\u0131n\u0131 kontrol edin; chmod 777 kullanarak izin sorununu \u00f6rtmeye \u00e7al\u0131\u015fmay\u0131n.<\/p>\n<\/div>\n<h2 id=\"bakim-modu-hangi-yontemle-acilmali\">Bak\u0131m modu hangi y\u00f6ntemle a\u00e7\u0131lmal\u0131?<\/h2>\n<p>Y\u00f6ntem, i\u015flemin niteli\u011fine g\u00f6re se\u00e7ilmelidir. WordPress \u00e7ekirde\u011finin kendi mekanizmas\u0131 k\u00fc\u00e7\u00fck ve k\u0131sa bak\u0131m pencereleri i\u00e7in yeterlidir. Y\u00f6netim panelinden kullan\u0131labilen bak\u0131m eklentileri \u00f6zel mesaj, geri say\u0131m veya yetkili kullan\u0131c\u0131 istisnas\u0131 gerekti\u011finde i\u015f g\u00f6r\u00fcr. Sunucu d\u00fczeyindeki Nginx ya da CDN kurallar\u0131, WordPress cevap vermese bile bak\u0131m sayfas\u0131 g\u00f6sterebilir.<\/p>\n<table>\n<thead>\n<tr>\n<th>Y\u00f6ntem<\/th>\n<th>Uygun oldu\u011fu durum<\/th>\n<th>Dikkat edilmesi gereken<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td><code>.maintenance<\/code><\/td>\n<td>K\u0131sa g\u00fcncelleme ve eklenti i\u015flemleri<\/td>\n<td>\u00d6zel tasar\u0131m ve y\u00f6netici istisnas\u0131 s\u0131n\u0131rl\u0131d\u0131r<\/td>\n<\/tr>\n<tr>\n<td>WP-CLI<\/td>\n<td>SSH eri\u015fimi olan VPS ve hosting hesaplar\u0131<\/td>\n<td>Do\u011fru WordPress dizininde \u00e7al\u0131\u015ft\u0131r\u0131lmal\u0131d\u0131r<\/td>\n<\/tr>\n<tr>\n<td>Bak\u0131m eklentisi<\/td>\n<td>\u00d6zel mesaj, logo veya geri say\u0131m gereken siteler<\/td>\n<td>Eklenti \u00e7ak\u0131\u015fmalar\u0131 ve cache etkisi test edilmelidir<\/td>\n<\/tr>\n<tr>\n<td>Nginx veya CDN<\/td>\n<td>Uygulama katman\u0131n\u0131n da de\u011fi\u015ftirilece\u011fi uzun bak\u0131mlar<\/td>\n<td>Y\u00f6netici ve sa\u011fl\u0131k kontrol\u00fc yollar\u0131 yanl\u0131\u015fl\u0131kla engellenebilir<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>Bak\u0131m eklentisi kurmak yaln\u0131zca bir d\u00fc\u011fmeye basmaktan ibaret de\u011fildir. Eklenti etkinle\u015ftirilmeden \u00f6nce mevcut cache katmanlar\u0131n\u0131, g\u00fcvenlik eklentilerini ve CDN davran\u0131\u015f\u0131n\u0131 inceleyin. Cloudflare veya ba\u015fka bir reverse proxy eski bak\u0131m sayfas\u0131n\u0131 \u00f6nbellekte tutarsa, bak\u0131m sona erdi\u011fi h\u00e2lde ziyaret\u00e7iler ayn\u0131 ekran\u0131 g\u00f6rmeye devam edebilir.<\/p>\n<p>\u00d6zel bak\u0131m sayfas\u0131 kullan\u0131lacaksa yan\u0131t kodu genellikle <code>503 Service Unavailable<\/code> olmal\u0131d\u0131r. <code>200 OK<\/code> yan\u0131t\u0131, arama motorlar\u0131na sayfan\u0131n normal ve kal\u0131c\u0131 i\u00e7erik oldu\u011fu izlenimini verebilir. HTTP 503 yan\u0131t\u0131na tahmini biti\u015f zaman\u0131n\u0131 belirten <code>Retry-After<\/code> ba\u015fl\u0131\u011f\u0131 eklenebilir; s\u00fcre kesin de\u011filse ba\u015fl\u0131\u011f\u0131 kullanmamak daha g\u00fcvenlidir.<\/p>\n<p>Siteyi yaln\u0131zca y\u00f6neticinin g\u00f6rmesini sa\u011flamak da dikkat ister. WordPress oturumu olmayan ziyaret\u00e7iyle, ayn\u0131 sunucudaki izleme servisi veya \u00f6deme webhook&#8217;u ayn\u0131 kurallara tabi tutulmamal\u0131d\u0131r.<\/p>\n<p><strong>Kontrol noktas\u0131<\/strong> &#8211; K\u0131sa i\u015flemlerde WP-CLI veya <code>.maintenance<\/code>, \u00f6zel eri\u015fim kurallar\u0131 gereken uzun i\u015flemlerde sunucu ya da CDN katman\u0131n\u0131 se\u00e7in.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>Be\u015f dakikal\u0131k eklenti g\u00fcncellemesinde yerle\u015fik mekanizma yeterlidir. Veritaban\u0131 ta\u015f\u0131mas\u0131 otuz dakika s\u00fcrecekse \u00f6zel 503 sayfas\u0131, izleme plan\u0131 ve y\u00f6netici eri\u015fimi ayr\u0131ca tasarlanmal\u0131d\u0131r.<\/p>\n<\/div>\n<h2 id=\"wordpress-bakim-modu-acilmadan-once-neler-kontrol-edilmeli\">WordPress bak\u0131m modu a\u00e7\u0131lmadan \u00f6nce neler kontrol edilmeli?<\/h2>\n<p>Bak\u0131m modunun kendisi basittir; haz\u0131rl\u0131k k\u0131sm\u0131 de\u011fildir. G\u00fcncelleme ba\u015flamadan \u00f6nce tam dosya ve veritaban\u0131 yede\u011fi al\u0131n. VPS \u00fczerindeki snapshot h\u0131zl\u0131 geri d\u00f6n\u00fc\u015f sa\u011flayabilir, fakat tek ba\u015f\u0131na yedekleme stratejisi de\u011fildir. Ayr\u0131nt\u0131lar i\u00e7in <em><a href=\"https:\/\/www.vps.tc\/blog\/tr\/vps-snapshot-nedir-anlik-yedekleme-rehberi\/\">VPS Snapshot Nedir? Anl\u0131k Yedekleme Rehberi<\/a><\/em> ba\u015fl\u0131kl\u0131 i\u00e7eri\u011fe bakabilirsiniz.<\/p>\n<p>Veritaban\u0131 yede\u011finin \u00fcretildi\u011fini ve okunabilir bir dosya olu\u015fturdu\u011funu kontrol edin:<\/p>\n<pre><code>wp db export \/var\/backups\/wordpress-$(date +%F-%H%M).sql\nls -lh \/var\/backups\/wordpress-*.sql\nhead -n 5 \/var\/backups\/wordpress-2026-10-04-0300.sql<\/code><\/pre>\n<p>Dosya ad\u0131ndaki tarih yaln\u0131zca \u00f6rnektir; ger\u00e7ek dosya ad\u0131n\u0131 <code>ls<\/code> \u00e7\u0131kt\u0131s\u0131ndan do\u011frulay\u0131n. <code>head<\/code> komutu dosyan\u0131n bo\u015f olup olmad\u0131\u011f\u0131n\u0131 h\u0131zl\u0131ca g\u00f6sterir, tam geri d\u00f6n\u00fc\u015f testi yapmaz. \u0130\u00e7eri aktarma provas\u0131 staging ortam\u0131nda ger\u00e7ekle\u015ftirilmelidir.<\/p>\n<p>G\u00fcncelleme \u00f6ncesinde etkin eklentileri ve s\u00fcr\u00fcmleri kaydetmek geri d\u00f6n\u00fc\u015f\u00fc kolayla\u015ft\u0131r\u0131r:<\/p>\n<pre><code>wp core version\nwp plugin list --status=active --format=table\nwp theme list --status=active --format=table\nphp -v<\/code><\/pre>\n<p>PHP s\u00fcr\u00fcm\u00fcyle eklenti ve tema uyumlulu\u011funu ayr\u0131ca kontrol edin. Bak\u0131m modu PHP uyumsuzlu\u011funu d\u00fczeltmez; yaln\u0131zca g\u00fcncelleme s\u0131ras\u0131nda ziyaret\u00e7iye ara ekran g\u00f6sterir.<\/p>\n<p>Dosya y\u00fckleme veya medya i\u015f ak\u0131\u015f\u0131 de\u011fi\u015fecekse <em><a href=\"https:\/\/www.vps.tc\/blog\/tr\/wordpress-dosya-yukleme-limiti-nasil-artirilir\/\">WordPress Dosya Y\u00fckleme Limiti Nas\u0131l Art\u0131r\u0131l\u0131r?<\/a><\/em> i\u00e7eri\u011findeki PHP ve web sunucusu katmanlar\u0131n\u0131 birlikte de\u011ferlendirme yakla\u015f\u0131m\u0131 i\u015finize yarayabilir. Bak\u0131m plan\u0131na Nginx, PHP-FPM ve veritaban\u0131 servislerini de dahil edin.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Bir gece yanl\u0131\u015f sunucuda rm -rf komutunu \u00e7al\u0131\u015ft\u0131rmak \u00fczereydim. Prompt&#039;ta g\u00f6r\u00fcnen hostname bekledi\u011fim makineyle uyu\u015fmay\u0131nca Enter&#039;a basmadan durdum ve \u00f6nce hostnamectl ile kimli\u011fi do\u011frulad\u0131m. O g\u00fcnden beri y\u0131k\u0131c\u0131 komutlardan \u00f6nce sunucu ad\u0131n\u0131 ve \u00e7al\u0131\u015fma dizinini iki kez kontrol ediyorum.<\/p>\n<\/div>\n<h2 id=\"bakim-ekrani-ziyaretcilere-nasil-gosterilir\">Bak\u0131m ekran\u0131 ziyaret\u00e7ilere nas\u0131l g\u00f6sterilir?<\/h2>\n<p>Yerle\u015fik bak\u0131m ekran\u0131 temel bir mesaj verir ve tasar\u0131m \u00fczerinde s\u0131n\u0131rl\u0131 kontrol sunar. Birka\u00e7 saniyelik eklenti veya \u00e7ekirdek g\u00fcncellemesinde bu ekran yeterlidir. Daha uzun bak\u0131mda ziyaret\u00e7iye ne oldu\u011funu, ne zaman yeniden denemesi gerekti\u011fini ve varsa destek kanal\u0131n\u0131 a\u00e7\u0131klayan sade bir sayfa g\u00f6sterin.<\/p>\n<p>WordPress&#8217;in bak\u0131m dosyas\u0131 g\u00fcncelleme s\u0131ras\u0131nda ge\u00e7ici olarak olu\u015fturulur. \u00c7ekirdek, dosyadaki zaman bilgisini kullan\u0131r ve dosyan\u0131n yakla\u015f\u0131k 10 dakikadan uzun s\u00fcre kalmas\u0131n\u0131 eski bir bak\u0131m durumu olarak de\u011ferlendirebilir. Bu davran\u0131\u015f uzun bak\u0131m planlamak i\u00e7in g\u00fcvenilir bir zamanlay\u0131c\u0131 de\u011fildir; i\u015flem bitti\u011finde dosyay\u0131 a\u00e7\u0131k\u00e7a kald\u0131r\u0131n.<\/p>\n<p>Bak\u0131m ekran\u0131 g\u00f6r\u00fcnm\u00fcyorsa taray\u0131c\u0131 cache&#8217;ini, CDN cache&#8217;ini ve reverse proxy yan\u0131t\u0131n\u0131 ayr\u0131 ayr\u0131 kontrol edin:<\/p>\n<pre><code>curl -I https:\/\/example.com\/\ncurl -sS -o \/dev\/null -w '%{http_code}\\n' https:\/\/example.com\/<\/code><\/pre>\n<p>\u0130lk komut yan\u0131t ba\u015fl\u0131klar\u0131n\u0131, ikinci komut yaln\u0131zca HTTP durum kodunu g\u00f6sterir. \u00d6zel bak\u0131m tasar\u0131m\u0131nda beklenen kod <code>503<\/code>&#8216;t\u00fcr. <code>200<\/code> d\u00f6n\u00fcyorsa WordPress&#8217;e ula\u015fmadan \u00f6nce ba\u015fka bir katman\u0131n yan\u0131t verdi\u011fi veya bak\u0131m kural\u0131n\u0131n yanl\u0131\u015f yaz\u0131ld\u0131\u011f\u0131 d\u00fc\u015f\u00fcn\u00fclebilir.<\/p>\n<p>Nginx yap\u0131land\u0131rmas\u0131 de\u011fi\u015ftirilecekse \u00f6nce s\u00f6zdizimi testi yap\u0131n:<\/p>\n<pre><code>sudo nginx -t\nsudo systemctl reload nginx<\/code><\/pre>\n<p><code>reload<\/code> \u00e7al\u0131\u015fan i\u015f\u00e7ileri hemen sonland\u0131rmadan yap\u0131land\u0131rmay\u0131 yeniler. Yine de bak\u0131m kural\u0131n\u0131n kapsam\u0131n\u0131, y\u00f6netici eri\u015fimini ve sa\u011fl\u0131k kontrol\u00fcn\u00fc test edin. Nginx kurulumu ve temel yap\u0131land\u0131rma ayr\u0131nt\u0131lar\u0131 i\u00e7in <em><a href=\"https:\/\/www.vps.tc\/blog\/tr\/ubuntu-nginx-kurulumu-ilk-yapilandirma\/\">Ubuntu&#8217;da Nginx Kurulumu ve \u0130lk Yap\u0131land\u0131rma Rehberi<\/a><\/em> ilgili bir ba\u015fvuru noktas\u0131d\u0131r.<\/p>\n<p><strong>Kontrol noktas\u0131<\/strong> &#8211; Bak\u0131m ekran\u0131n\u0131 normal taray\u0131c\u0131da, gizli pencerede ve <code>curl -I<\/code> ile do\u011frulay\u0131n.<\/p>\n<h2 id=\"yonetici-erisimi-nasil-korunur\">Y\u00f6netici eri\u015fimi nas\u0131l korunur?<\/h2>\n<p>Bak\u0131m modu a\u00e7\u0131kken sitenin davran\u0131\u015f\u0131n\u0131 test etmek gerekebilir. Yerle\u015fik <code>.maintenance<\/code> mekanizmas\u0131 \u00e7o\u011fu durumda ziyaret\u00e7iye ve y\u00f6neticiye ayn\u0131 ekran\u0131 g\u00f6sterir; tema veya eklenti geli\u015ftiren ekipler bu nedenle staging ortam\u0131n\u0131 tercih etmelidir. Canl\u0131 sitede istisna gerekiyorsa IP allowlist, HTTP Basic Authentication veya uygulama i\u00e7i bak\u0131m eklentisi kullan\u0131labilir.<\/p>\n<p>IP adresine dayal\u0131 istisnalar, mobil ba\u011flant\u0131larda ve de\u011fi\u015fken IP kullanan ofislerde sorun \u00e7\u0131karabilir. Ayr\u0131ca IP kontrol\u00fc kimlik do\u011frulamas\u0131n\u0131n yerini tutmaz. Y\u00f6netim panelini do\u011frudan internete a\u00e7mak yerine VPN veya ek bir kimlik do\u011frulama katman\u0131 de\u011ferlendirin.<\/p>\n<p>\u00d6zel bak\u0131m sayfas\u0131nda a\u015fa\u011f\u0131daki yollar\u0131n davran\u0131\u015f\u0131n\u0131 ayr\u0131 test edin:<\/p>\n<ul>\n<li>Site ana sayfas\u0131 ve birka\u00e7 i\u00e7erik URL&#8217;si<\/li>\n<li><code>\/wp-admin\/<\/code> ve giri\u015f ekran\u0131<\/li>\n<li>REST API u\u00e7 noktalar\u0131<\/li>\n<li>\u00d6deme, form ve webhook adresleri<\/li>\n<li>Uptime Kuma veya benzeri sa\u011fl\u0131k kontrol\u00fc URL&#8217;si<\/li>\n<\/ul>\n<p>\u0130zleme sistemi yaln\u0131zca HTTP 200 bekliyorsa bak\u0131m s\u0131ras\u0131nda alarm \u00fcretebilir. Alarm\u0131 tamamen kapatmak yerine bak\u0131m penceresine \u00f6zel bir plan tan\u0131mlay\u0131n. Sa\u011fl\u0131k kontrol\u00fcn\u00fc silmek, ger\u00e7ek bir kesintiyi g\u00f6r\u00fcnmez h\u00e2le getirebilir.<\/p>\n<p>Yeni davran\u0131\u015f\u0131 canl\u0131ya almadan \u00f6nce staging ortam\u0131nda deneyin. \u00d6zellikleri kademeli a\u00e7ma yakla\u015f\u0131m\u0131 i\u00e7in <em><a href=\"https:\/\/www.vps.tc\/blog\/tr\/feature-flag-nedir-guvenli-yayina-alma-rehberi\/\">Feature Flag Nedir? G\u00fcvenli Yay\u0131na Alma Rehberi<\/a><\/em> ba\u015fl\u0131\u011f\u0131ndaki prensipler WordPress bak\u0131m senaryolar\u0131nda da kullan\u0131labilir: de\u011fi\u015fikli\u011fi k\u00fc\u00e7\u00fck bir kullan\u0131c\u0131 grubuyla s\u0131nay\u0131n, loglar\u0131 izleyin ve geri d\u00f6n\u00fc\u015f komutunu haz\u0131r tutun.<\/p>\n<h2 id=\"bakim-modu-kapanmiyorsa-ne-yapilir\">Bak\u0131m modu kapanm\u0131yorsa ne yap\u0131l\u0131r?<\/h2>\n<p>WordPress g\u00fcncellemesi yar\u0131da kesildi\u011finde <code>.maintenance<\/code> dosyas\u0131 kalabilir. Ziyaret\u00e7iler s\u00fcrekli &#8220;Briefly unavailable for scheduled maintenance&#8221; benzeri bir ekran g\u00f6r\u00fcr. \u0130lk kontrol, dosyan\u0131n ger\u00e7ekten WordPress k\u00f6k dizininde olup olmad\u0131\u011f\u0131d\u0131r:<\/p>\n<pre><code>cd \/var\/www\/html\npwd\nfind . -maxdepth 1 -name '.maintenance' -ls\nwp maintenance-mode status<\/code><\/pre>\n<p>Dosya bulunuyor ve devam eden bir g\u00fcncelleme yoksa kald\u0131r\u0131labilir:<\/p>\n<pre><code>rm -f .maintenance\nwp core verify-checksums<\/code><\/pre>\n<p><code>wp core verify-checksums<\/code> \u00e7ekirdek dosyalar\u0131ndaki beklenmeyen de\u011fi\u015fiklikleri ara\u015ft\u0131r\u0131r. Komut ba\u015far\u0131s\u0131z olursa dosyalar\u0131 hemen \u00fczerine yazmay\u0131n; baz\u0131 g\u00fcvenlik veya \u00f6zelle\u015ftirme i\u015flemleri \u00e7ekirdek dosyalar\u0131n\u0131 de\u011fi\u015ftirmi\u015f olabilir.<\/p>\n<p>Dosya silindikten sonra bak\u0131m ekran\u0131 g\u00f6r\u00fcnmeye devam ederse \u015fu katmanlar\u0131 s\u0131rayla inceleyin:<\/p>\n<ol>\n<li>WordPress k\u00f6k dizininde ikinci bir <code>.maintenance<\/code> dosyas\u0131 olup olmad\u0131\u011f\u0131n\u0131 kontrol edin.<\/li>\n<li>PHP-FPM ve Nginx loglar\u0131nda yeni hata olup olmad\u0131\u011f\u0131n\u0131 inceleyin.<\/li>\n<li>CDN ve reverse proxy cache&#8217;ini temizleyin.<\/li>\n<li>Bak\u0131m eklentisinin h\u00e2l\u00e2 etkin veya bozuk olup olmad\u0131\u011f\u0131n\u0131 kontrol edin.<\/li>\n<li>Farkl\u0131 a\u011fdan ve farkl\u0131 bir HTTP istemcisinden test yap\u0131n.<\/li>\n<\/ol>\n<p>Log okumadan PHP-FPM&#8217;i veya t\u00fcm sunucuyu yeniden ba\u015flatmak as\u0131l hatay\u0131 gizleyebilir. \u00d6nce <code>journalctl<\/code>, Nginx hata logu ve WordPress debug logunu kar\u015f\u0131la\u015ft\u0131r\u0131n; yaln\u0131zca gerekli servisi yeniden y\u00fckleyin.<\/p>\n<p><strong>Kontrol noktas\u0131<\/strong> &#8211; Bak\u0131m ekran\u0131 kal\u0131rsa \u00f6nce <code>.maintenance<\/code>, ard\u0131ndan cache ve uygulama loglar\u0131n\u0131 kontrol edin; sunucuyu son \u00e7are olarak yeniden ba\u015flat\u0131n.<\/p>\n<h2 id=\"bakim-modu-seo-ve-guvenlik-acisindan-sorun-cikarir-mi\">Bak\u0131m modu SEO ve g\u00fcvenlik a\u00e7\u0131s\u0131ndan sorun \u00e7\u0131kar\u0131r m\u0131?<\/h2>\n<p>K\u0131sa s\u00fcreli ve do\u011fru yap\u0131land\u0131r\u0131lm\u0131\u015f bak\u0131m, tek ba\u015f\u0131na SEO sorunu olu\u015fturmaz. Arama motoru botlar\u0131na ge\u00e7ici durumun bildirilebilmesi i\u00e7in <code>503<\/code> yan\u0131t\u0131 \u00f6nemlidir. Uzun s\u00fcre <code>200<\/code> d\u00f6nen bo\u015f bir bak\u0131m sayfas\u0131, i\u00e7eri\u011fin ge\u00e7ici mi kal\u0131c\u0131 m\u0131 oldu\u011funu belirsizle\u015ftirir.<\/p>\n<p>Bak\u0131m sayfas\u0131nda y\u00f6netim parolas\u0131, veritaban\u0131 bilgisi, sunucu yolu veya ayr\u0131nt\u0131l\u0131 hata \u00e7\u0131kt\u0131s\u0131 g\u00f6stermeyin. PHP hata raporlamas\u0131n\u0131 canl\u0131 sitede ziyaret\u00e7iye a\u00e7\u0131k b\u0131rakmak da bilgi s\u0131z\u0131nt\u0131s\u0131 yaratabilir. Hata ayr\u0131nt\u0131lar\u0131n\u0131 loga yaz\u0131n, kullan\u0131c\u0131ya k\u0131sa ve anla\u015f\u0131l\u0131r bir mesaj g\u00f6sterin.<\/p>\n<p>Bak\u0131m s\u0131ras\u0131nda g\u00fcvenlik eklentisini devre d\u0131\u015f\u0131 b\u0131rakmak zorunda kal\u0131rsan\u0131z i\u015flem biter bitmez etkinlik durumunu kontrol edin. G\u00fcncelleme sonras\u0131nda dosya izinlerini, sahipli\u011fi, cron g\u00f6revlerini ve kritik form ak\u0131\u015flar\u0131n\u0131 da test edin. Ana sayfan\u0131n a\u00e7\u0131lmas\u0131 tek ba\u015f\u0131na yeterli de\u011fildir.<\/p>\n<p>Bak\u0131m penceresi sonunda temel do\u011frulama i\u00e7in \u015fu komutlar kullan\u0131labilir:<\/p>\n<pre><code>wp maintenance-mode status\ncurl -sS -o \/dev\/null -w 'HTTP %{http_code}\\n' https:\/\/example.com\/\nwp cron event list --due-now\nwp plugin list --update=available<\/code><\/pre>\n<p>G\u00fcncelleme listesinde \u00f6\u011fe kalmas\u0131 her zaman hata de\u011fildir; hedeflenen eklentilerin s\u00fcr\u00fcmlerini ayr\u0131ca do\u011frulay\u0131n. <code>wp cron event list --due-now<\/code> \u00e7\u0131kt\u0131s\u0131, bak\u0131m s\u0131ras\u0131nda biriken zamanlanm\u0131\u015f g\u00f6revleri g\u00f6rmeye yard\u0131mc\u0131 olur.<\/p>\n<p>Bak\u0131m bitti\u011finde izleme alarm\u0131n\u0131n normale d\u00f6nd\u00fc\u011f\u00fcn\u00fc, form g\u00f6nderiminin \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 ve giri\u015f yap\u0131labildi\u011fini do\u011frulay\u0131n. K\u00fc\u00e7\u00fck bir kontrol, gece yar\u0131s\u0131 yap\u0131lan acele bir d\u00fczeltmeden daha ucuzdur.<\/p>\n<h2 id=\"bakim-modunu-acmadan-once-sunlari-kontrol-edin\">Bak\u0131m Modunu A\u00e7madan \u00d6nce \u015eunlar\u0131 Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>WordPress k\u00f6k dizinini ve hostname bilgisini do\u011frulay\u0131n.<\/li>\n<li>Dosya ve veritaban\u0131 yede\u011fi al\u0131p yede\u011fin boyutunu kontrol edin.<\/li>\n<li>Etkin eklenti, tema, WordPress ve PHP s\u00fcr\u00fcmlerini kaydedin.<\/li>\n<li>Bak\u0131m y\u00f6ntemini ve tahmini i\u015flem s\u00fcresini belirleyin.<\/li>\n<li>Y\u00f6netici, webhook ve sa\u011fl\u0131k kontrol\u00fc eri\u015fimlerini test edin.<\/li>\n<li>Bak\u0131m yan\u0131t\u0131n\u0131n 503 d\u00f6nd\u00fcrd\u00fc\u011f\u00fcn\u00fc curl ile do\u011frulay\u0131n.<\/li>\n<li>\u0130\u015f bitince bak\u0131m modunu kapat\u0131p ana sayfa ve formlar\u0131 kontrol edin.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>Bir sonraki bak\u0131m penceresinden \u00f6nce komutlar\u0131 staging ortam\u0131nda deneyin ve geri d\u00f6n\u00fc\u015f ad\u0131mlar\u0131n\u0131 ayn\u0131 notta saklay\u0131n. K\u00fc\u00e7\u00fck bir prova, canl\u0131 sitede unutulmu\u015f bir .maintenance dosyas\u0131ndan daha ucuzdur.<\/p>\n<p class=\"aiw-cta-action\"><a href=\"https:\/\/www.vps.tc\/tr\/vps\">VPS paketlerini inceleyin<\/a><\/p>\n<\/div>\n<h2 id=\"sik-sorulan-sorular\">S\u0131k Sorulan Sorular<\/h2>\n<div class=\"aiw-faq\">\n<details class=\"aiw-faq-item\" open>\n<summary>WordPress bak\u0131m modu nas\u0131l a\u00e7\u0131l\u0131r?<\/summary>\n<p>SSH ile WordPress k\u00f6k dizinine girip wp maintenance-mode activate komutunu \u00e7al\u0131\u015ft\u0131rabilirsiniz. WP-CLI yoksa ayn\u0131 dizinde .maintenance adl\u0131 dosya olu\u015fturun ve i\u00e7ine &lt;?php $upgrading = time(); ?&gt; yaz\u0131n. \u0130\u015flem tamamland\u0131\u011f\u0131nda wp maintenance-mode deactivate komutunu \u00e7al\u0131\u015ft\u0131r\u0131n veya do\u011fru dizindeki .maintenance dosyas\u0131n\u0131 kald\u0131r\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress bak\u0131m modu nas\u0131l kapat\u0131l\u0131r?<\/summary>\n<p>WP-CLI kullan\u0131lan kurulumlarda wp maintenance-mode deactivate komutu yeterlidir. Dosya y\u00f6ntemiyle a\u00e7\u0131lan mod i\u00e7in WordPress k\u00f6k dizinindeki .maintenance dosyas\u0131n\u0131 rm -f .maintenance komutuyla kald\u0131r\u0131n. Ard\u0131ndan curl -I ile yan\u0131t\u0131 ve taray\u0131c\u0131dan siteyi kontrol edin; bak\u0131m ekran\u0131 s\u00fcr\u00fcyorsa CDN veya reverse proxy cache&#039;ini de inceleyin.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress bak\u0131m modu neden kapanm\u0131yor?<\/summary>\n<p>En yayg\u0131n neden, g\u00fcncelleme kesildi\u011finde .maintenance dosyas\u0131n\u0131n kalmas\u0131d\u0131r. \u00d6nce do\u011fru WordPress dizinini do\u011frulay\u0131n, dosyay\u0131 aray\u0131n ve devam eden bir i\u015flem yoksa kald\u0131r\u0131n. Ekran devam ederse bak\u0131m eklentisini, Nginx veya CDN cache&#039;ini ve PHP-FPM loglar\u0131n\u0131 kontrol edin. Sunucuyu do\u011frudan yeniden ba\u015flatmak yerine \u00f6nce loglar\u0131 okuyun.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress bak\u0131m modu SEO a\u00e7\u0131s\u0131ndan zararl\u0131 m\u0131?<\/summary>\n<p>K\u0131sa s\u00fcreli bak\u0131mda do\u011fru HTTP 503 yan\u0131t\u0131 kullan\u0131l\u0131rsa genellikle kal\u0131c\u0131 SEO sorunu olu\u015fmaz. Bak\u0131m sayfas\u0131n\u0131n 200 OK d\u00f6nd\u00fcrmesi veya g\u00fcnlerce a\u00e7\u0131k kalmas\u0131 daha risklidir; arama motorlar\u0131 ge\u00e7ici durum ile kal\u0131c\u0131 i\u00e7erik aras\u0131ndaki ayr\u0131m\u0131 zor yapabilir. Bak\u0131m bitti\u011finde 200 yan\u0131t\u0131n\u0131 ve normal i\u00e7erik ba\u015fl\u0131klar\u0131n\u0131 do\u011frulay\u0131n.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress bak\u0131m modunda site y\u00f6neticisi giri\u015f yapabilir mi?<\/summary>\n<p>Yerle\u015fik .maintenance y\u00f6ntemi \u00e7o\u011fu durumda ziyaret\u00e7i ve y\u00f6neticiyi ayn\u0131 bak\u0131m ekran\u0131na y\u00f6nlendirir. Y\u00f6netici istisnas\u0131 gerekiyorsa bak\u0131m eklentisinin yetkili kullan\u0131c\u0131 \u00f6zelli\u011fini, VPN eri\u015fimini veya kontroll\u00fc IP allowlist kural\u0131n\u0131 kullan\u0131n. Bu istisnay\u0131 canl\u0131ya almadan \u00f6nce gizli taray\u0131c\u0131 penceresinde ziyaret\u00e7i davran\u0131\u015f\u0131n\u0131 ayr\u0131ca test edin.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>WordPress bak\u0131m modu i\u00e7in eklenti kullanmak gerekli mi?<\/summary>\n<p>Hay\u0131r. K\u0131sa \u00e7ekirdek, tema veya eklenti g\u00fcncellemelerinde WP-CLI ya da .maintenance dosyas\u0131 yeterlidir. \u00d6zel tasar\u0131m, geri say\u0131m, yetkili kullan\u0131c\u0131 istisnas\u0131 veya ayr\u0131nt\u0131l\u0131 bak\u0131m mesaj\u0131 gerekiyorsa eklenti tercih edilebilir. Eklenti kullan\u0131rken cache, g\u00fcvenlik eklentisi ve HTTP 503 davran\u0131\u015f\u0131n\u0131 birlikte test edin.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/developer.wordpress.org\/cli\/commands\/maintenance-mode\/\" target=\"_blank\" rel=\"noopener\">WP-CLI &#8211; maintenance-mode<\/a> \u2014 developer.wordpress.org<\/li>\n<li><a href=\"https:\/\/developer.wordpress.org\/reference\/functions\/wp_maintenance\/\" target=\"_blank\" rel=\"noopener\">WordPress Developer Resources &#8211; wp_maintenance<\/a> \u2014 developer.wordpress.org<\/li>\n<li><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTTP\/Status\/503\" target=\"_blank\" rel=\"noopener\">MDN &#8211; 503 Service Unavailable<\/a> \u2014 developer.mozilla.org<\/li>\n<li><a href=\"https:\/\/nginx.org\/en\/docs\/\" target=\"_blank\" rel=\"noopener\">nginx Documentation<\/a> \u2014 nginx.org<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>WordPress bak\u0131m modunu k\u0131sa g\u00fcncellemelerde a\u00e7ma ve kapatma y\u00f6ntemlerini, 503 yan\u0131t\u0131n\u0131, yedek haz\u0131rl\u0131\u011f\u0131n\u0131 ve kapanmayan bak\u0131m ekran\u0131n\u0131 anlat\u0131r.<\/p>\n","protected":false},"author":2,"featured_media":1031,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[666],"tags":[],"class_list":["post-1033","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-cms"],"lang":"tr","translations":{"tr":1033,"en":1034},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/1033","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/comments?post=1033"}],"version-history":[{"count":1,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/1033\/revisions"}],"predecessor-version":[{"id":1035,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/1033\/revisions\/1035"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/1031"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=1033"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=1033"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=1033"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}