{"id":764,"date":"2026-09-15T20:13:13","date_gmt":"2026-09-15T20:13:13","guid":{"rendered":"https:\/\/www.vps.tc\/blog\/?p=764"},"modified":"2026-09-15T20:13:13","modified_gmt":"2026-09-15T20:13:13","slug":"301-yonlendirme-nedir-seo-kullanim-rehberi","status":"publish","type":"post","link":"https:\/\/www.vps.tc\/blog\/tr\/301-yonlendirme-nedir-seo-kullanim-rehberi\/","title":{"rendered":"301 Y\u00f6nlendirme Nedir? SEO \u0130\u00e7in Kullan\u0131m Rehberi"},"content":{"rendered":"<div class=\"aiw-summary\" id=\"aiw-ozet\">\n<p class=\"aiw-summary-title\">H\u0131zl\u0131 \u00d6zet &#8211; 301 Y\u00f6nlendirme<\/p>\n<p>301 y\u00f6nlendirme, kal\u0131c\u0131 olarak ta\u015f\u0131nan bir URL&#039;nin yeni adresini istemciye ve arama motoruna bildiren HTTP yan\u0131t\u0131d\u0131r. Do\u011fru hedef ve test ad\u0131mlar\u0131, trafik kayb\u0131 ile y\u00f6nlendirme d\u00f6ng\u00fclerini \u00f6nler.<\/p>\n<ul>\n<li><strong>Kal\u0131c\u0131 ta\u015f\u0131nma<\/strong> \u2014 Eski URL uzun s\u00fcre kullan\u0131lmayacaksa yeni adrese 301 ile y\u00f6nlendirin.<\/li>\n<li><strong>SEO sinyalleri<\/strong> \u2014 \u0130\u00e7erik e\u015fle\u015fiyorsa eski URL&#039;nin sinyalleri yeni adresle ili\u015fkilendirilebilir.<\/li>\n<li><strong>Kod se\u00e7imi<\/strong> \u2014 Ge\u00e7ici i\u015flemlerde 302, metodu koruyan i\u015flemlerde 307 veya 308 de\u011ferlendirilmelidir.<\/li>\n<li><strong>Do\u011fru hedef<\/strong> \u2014 Her eski adresi konu bak\u0131m\u0131ndan en yak\u0131n yeni sayfaya g\u00f6nderin.<\/li>\n<li><strong>Zincir kontrol\u00fc<\/strong> \u2014 Birden fazla y\u00f6nlendirme halkas\u0131n\u0131 kald\u0131r\u0131p eski URL&#039;yi nihai hedefe ba\u011flay\u0131n.<\/li>\n<li><strong>Yay\u0131n sonras\u0131 test<\/strong> \u2014 curl, loglar, sitemap ve canonical etiketleriyle ge\u00e7i\u015fi do\u011frulay\u0131n.<\/li>\n<\/ul>\n<\/div>\n<p class=\"aiw-lead\">301 y\u00f6nlendirme, kal\u0131c\u0131 olarak de\u011fi\u015fen bir URL&#039;nin yeni adresini taray\u0131c\u0131ya ve arama motoruna bildiren HTTP yan\u0131t\u0131d\u0131r. Eski sayfadan yeni sayfaya do\u011frudan ge\u00e7i\u015f sa\u011flar; SEO sinyallerinin aktar\u0131lmas\u0131na yard\u0131mc\u0131 olur. Ancak hedef yanl\u0131\u015fsa, zincir uzunsa veya yeni sayfa eri\u015filemiyorsa tek ba\u015f\u0131na trafik kayb\u0131n\u0131 \u00f6nlemez.<\/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=\"#301-yonlendirme-tam-olarak-ne-yapar\">301 y\u00f6nlendirme tam olarak ne yapar?<\/a><\/li>\n<li><a href=\"#301-ile-302-307-ve-308-arasindaki-fark-nedir\">301 ile 302, 307 ve 308 aras\u0131ndaki fark nedir?<\/a><\/li>\n<li><a href=\"#301-yonlendirme-seo-acisindan-neden-onemlidir\">301 y\u00f6nlendirme SEO a\u00e7\u0131s\u0131ndan neden \u00f6nemlidir?<\/a><\/li>\n<li><a href=\"#apache-ve-nginx-uzerinde-301-nasil-yapilandirilir\">Apache ve Nginx \u00fczerinde 301 nas\u0131l yap\u0131land\u0131r\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#wordpresste-301-yonlendirme-nasil-yapilir\">WordPress&#039;te 301 y\u00f6nlendirme nas\u0131l yap\u0131l\u0131r?<\/a><\/li>\n<li><a href=\"#httpden-httpsye-geciste-301-nasil-kullanilmali\">HTTP&#039;den HTTPS&#039;ye ge\u00e7i\u015fte 301 nas\u0131l kullan\u0131lmal\u0131?<\/a><\/li>\n<li><a href=\"#301-zinciri-ve-yonlendirme-dongusu-nasil-bulunur\">301 zinciri ve y\u00f6nlendirme d\u00f6ng\u00fcs\u00fc nas\u0131l bulunur?<\/a><\/li>\n<li><a href=\"#301-uygulamasindan-sonra-hangi-kontroller-yapilmali\">301 uygulamas\u0131ndan sonra hangi kontroller yap\u0131lmal\u0131?<\/a><\/li>\n<li><a href=\"#301-yonlendirmede-hangi-hatalardan-kacinilmali\">301 y\u00f6nlendirmede hangi hatalardan ka\u00e7\u0131n\u0131lmal\u0131?<\/a><\/li>\n<li><a href=\"#301-kuralini-yayina-almadan-once-kontrol-edin\">301 Kural\u0131n\u0131 Yay\u0131na Almadan \u00d6nce 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=\"301-yonlendirme-tam-olarak-ne-yapar\">301 y\u00f6nlendirme tam olarak ne yapar?<\/h2>\n<p>Bir URL kal\u0131c\u0131 olarak de\u011fi\u015fti\u011finde, eski adresi ziyaret eden taray\u0131c\u0131y\u0131 ve arama motoru botunu yeni adrese g\u00f6ndermek i\u00e7in HTTP <code>301 Moved Permanently<\/code> yan\u0131t\u0131 kullan\u0131l\u0131r. Sunucu, yan\u0131t ba\u015fl\u0131\u011f\u0131nda yeni adresi <code>Location<\/code> alan\u0131yla belirtir. Kullan\u0131c\u0131 yeni sayfay\u0131 g\u00f6r\u00fcr; arama motoru ise eski URL&#8217;nin sinyallerini yeni URL ile ili\u015fkilendirmeye \u00e7al\u0131\u015f\u0131r.<\/p>\n<p>301 y\u00f6nlendirme yaln\u0131zca bir SEO ayar\u0131 de\u011fildir. Alan ad\u0131 de\u011fi\u015fikli\u011fi, HTTP&#8217;den HTTPS&#8217;ye ge\u00e7i\u015f, URL yap\u0131s\u0131n\u0131n yenilenmesi, \u00fcr\u00fcn veya makale adreslerinin sadele\u015ftirilmesi gibi i\u015flemlerde eri\u015filebilirli\u011fi koruyan bir HTTP mekanizmas\u0131d\u0131r. Yanl\u0131\u015f kurgulan\u0131rsa y\u00f6nlendirme d\u00f6ng\u00fcs\u00fc, zincir ve gereksiz tarama y\u00fck\u00fc olu\u015fturabilir.<\/p>\n<h3>301 yan\u0131t\u0131nda hangi bilgiler bulunur?<\/h3>\n<p>RFC 9110&#8217;a g\u00f6re 301, hedef kayna\u011f\u0131n kal\u0131c\u0131 olarak ba\u015fka bir URI&#8217;ye ta\u015f\u0131nd\u0131\u011f\u0131n\u0131 belirtir. Tipik bir yan\u0131t \u015fu mant\u0131ktad\u0131r:<\/p>\n<pre><code>HTTP\/1.1 301 Moved Permanently\nLocation: https:\/\/www.example.com\/yeni-adres<\/code><\/pre>\n<p>Buradaki <code>Location<\/code> ba\u015fl\u0131\u011f\u0131 kritik bilgidir. \u0130stemci, y\u00f6nlendirme politikas\u0131na g\u00f6re bu adrese yeni bir istek g\u00f6nderir. MDN dok\u00fcmantasyonunda da 301 yan\u0131t\u0131n\u0131n kal\u0131c\u0131 ta\u015f\u0131nma i\u00e7in kullan\u0131ld\u0131\u011f\u0131, istemcilerin yeni adresi gelecekte tercih edebilece\u011fi belirtilir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Kal\u0131c\u0131 ta\u015f\u0131nmay\u0131 yaln\u0131zca yeni URL ger\u00e7ekten uzun s\u00fcre kullan\u0131lacaksa 301 ile bildirin.<\/p>\n<h2 id=\"301-ile-302-307-ve-308-arasindaki-fark-nedir\">301 ile 302, 307 ve 308 aras\u0131ndaki fark nedir?<\/h2>\n<p>Her y\u00f6nlendirme kodu ayn\u0131 anlama gelmez. 302 ge\u00e7ici ta\u015f\u0131nmay\u0131, 301 ise kal\u0131c\u0131 ta\u015f\u0131nmay\u0131 ifade eder. 307 ve 308 kodlar\u0131, HTTP metodunu koruma davran\u0131\u015f\u0131n\u0131 daha a\u00e7\u0131k tan\u0131mlar. \u00d6zellikle POST isteklerinde yaln\u0131zca kod numaras\u0131na g\u00fcvenmek yerine uygulaman\u0131n ve istemcinin davran\u0131\u015f\u0131 test edilmelidir.<\/p>\n<table>\n<thead>\n<tr>\n<th>Kod<\/th>\n<th>Anlam<\/th>\n<th>Tipik kullan\u0131m<\/th>\n<th>Metot davran\u0131\u015f\u0131<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>301<\/td>\n<td>Kal\u0131c\u0131 ta\u015f\u0131nma<\/td>\n<td>Eski URL&#8217;nin yeni URL&#8217;ye al\u0131nmas\u0131<\/td>\n<td>\u0130stemciye g\u00f6re POST, GET&#8217;e \u00e7evrilebilir<\/td>\n<\/tr>\n<tr>\n<td>302<\/td>\n<td>Ge\u00e7ici ta\u015f\u0131nma<\/td>\n<td>K\u0131sa s\u00fcreli kampanya veya bak\u0131m<\/td>\n<td>\u0130stemciye g\u00f6re de\u011fi\u015febilir<\/td>\n<\/tr>\n<tr>\n<td>307<\/td>\n<td>Ge\u00e7ici ta\u015f\u0131nma<\/td>\n<td>Metodun korunmas\u0131 gereken ge\u00e7ici y\u00f6nlendirme<\/td>\n<td>Metot ve g\u00f6vde korunur<\/td>\n<\/tr>\n<tr>\n<td>308<\/td>\n<td>Kal\u0131c\u0131 ta\u015f\u0131nma<\/td>\n<td>Metodun korunmas\u0131 gereken kal\u0131c\u0131 y\u00f6nlendirme<\/td>\n<td>Metot ve g\u00f6vde korunur<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>\u00d6rne\u011fin bir \u00f6deme formunun POST iste\u011fini yanl\u0131\u015fl\u0131kla 301 ile y\u00f6nlendirmek, baz\u0131 istemcilerde iste\u011fin GET olarak tekrarlanmas\u0131na yol a\u00e7abilir. Sayfa adresi de\u011fi\u015fikliklerinde 301 \u00e7o\u011fu zaman uygundur; API ve form isteklerinde 307 veya 308 daha dikkatli bir se\u00e7im olabilir.<\/p>\n<p>301 ile 302 aras\u0131ndaki fark yaln\u0131zca SEO a\u00e7\u0131s\u0131ndan d\u00fc\u015f\u00fcn\u00fclmemeli. Taray\u0131c\u0131 \u00f6nbelle\u011fi, istemci uygulamalar\u0131, CDN davran\u0131\u015f\u0131 ve form verisinin korunmas\u0131 da karar\u0131n par\u00e7as\u0131d\u0131r.<\/p>\n<h2 id=\"301-yonlendirme-seo-acisindan-neden-onemlidir\">301 y\u00f6nlendirme SEO a\u00e7\u0131s\u0131ndan neden \u00f6nemlidir?<\/h2>\n<p>Google Search Central, kal\u0131c\u0131 ta\u015f\u0131nmalarda sunucu taraf\u0131 y\u00f6nlendirmeleri ve \u00f6zellikle 301 veya 308 kodlar\u0131n\u0131 \u00f6nerilen y\u00f6ntemler aras\u0131nda sayar. Arama motoru eski URL&#8217;nin yerine yeni URL&#8217;yi de\u011ferlendirmeye ba\u015flar; ancak bu, b\u00fct\u00fcn s\u0131ralama sinyallerinin an\u0131nda ve eksiksiz aktar\u0131laca\u011f\u0131 anlam\u0131na gelmez.<\/p>\n<p>Bir URL de\u011fi\u015fti\u011finde yaln\u0131zca y\u00f6nlendirme kural\u0131 eklemek yeterli de\u011fildir. Yeni sayfan\u0131n i\u00e7eri\u011fi eski sayfayla anlaml\u0131 bi\u00e7imde e\u015fle\u015fmeli, canonical etiketi yeni adresi g\u00f6stermeli, XML sitemap g\u00fcncellenmeli ve dahili ba\u011flant\u0131lar yeni URL&#8217;ye \u00e7evrilmelidir. Eski adresi alakas\u0131z bir ana sayfaya g\u00f6ndermek, kullan\u0131c\u0131 beklentisini kar\u015f\u0131lamaz ve arama motoru a\u00e7\u0131s\u0131ndan zay\u0131f bir sinyal olu\u015fturabilir.<\/p>\n<p>Alan ad\u0131 de\u011fi\u015fikliklerinde Google Search Console \u00fczerindeki adres de\u011fi\u015fikli\u011fi i\u015flemi ayr\u0131ca de\u011ferlendirilebilir. DNS kay\u0131tlar\u0131, TLS sertifikas\u0131 ve e-posta hizmetleri bu i\u015flemden ba\u011f\u0131ms\u0131z g\u00f6r\u00fcnse de ge\u00e7i\u015f plan\u0131n\u0131n par\u00e7as\u0131d\u0131r. Alan ad\u0131 ve DNS ili\u015fkisini anlamak i\u00e7in <a href=\"https:\/\/www.vps.tc\/blog\/tr\/dns-probe-finished-nxdomain-hatasi-nasil-cozulur\/\">DNS_PROBE_FINISHED_NXDOMAIN Hatas\u0131 Nas\u0131l \u00c7\u00f6z\u00fcl\u00fcr?<\/a> ba\u015fl\u0131kl\u0131 i\u00e7eri\u011fe de bak\u0131labilir.<\/p>\n<h3>301 y\u00f6nlendirme SEO de\u011ferini otomatik ta\u015f\u0131r m\u0131?<\/h3>\n<p>Hay\u0131r. 301, arama motoruna kal\u0131c\u0131 de\u011fi\u015fikli\u011fi bildiren g\u00fc\u00e7l\u00fc bir teknik sinyaldir; garanti belgesi de\u011fildir. \u0130\u00e7erik b\u00fcy\u00fck \u00f6l\u00e7\u00fcde de\u011fi\u015fmi\u015fse, yeni sayfa yan\u0131t vermiyorsa, y\u00f6nlendirme zinciri uzunsa veya eski URL&#8217;lerin tamam\u0131 tek bir alakas\u0131z sayfaya g\u00f6nderiliyorsa beklenen de\u011fer aktar\u0131m\u0131 ger\u00e7ekle\u015fmeyebilir.<\/p>\n<p>Ba\u015fl\u0131k etiketleri, i\u00e7erik e\u015fle\u015fmesi ve canonical kontrol\u00fc birlikte yap\u0131lmal\u0131d\u0131r. Sayfa ba\u015fl\u0131\u011f\u0131 de\u011fi\u015fikli\u011finde <a href=\"https:\/\/www.vps.tc\/blog\/tr\/title-ne-demek-title-etiketi-ne-ise-yarar\/\">Title Ne Demek? Title Etiketi Ne Ama\u00e7la Kullan\u0131l\u0131r?<\/a> i\u00e7eri\u011findeki temel kontroller yol g\u00f6sterir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Her eski URL i\u00e7in i\u00e7erik a\u00e7\u0131s\u0131ndan en yak\u0131n yeni hedefi belirleyin ve ana sayfaya toplu y\u00f6nlendirmeden ka\u00e7\u0131n\u0131n.<\/p>\n<h2 id=\"apache-ve-nginx-uzerinde-301-nasil-yapilandirilir\">Apache ve Nginx \u00fczerinde 301 nas\u0131l yap\u0131land\u0131r\u0131l\u0131r?<\/h2>\n<h3>Apache .htaccess \u00f6rne\u011fi<\/h3>\n<p>Apache kullan\u0131l\u0131yorsa, <code>mod_rewrite<\/code> ile belirli bir eski adres yeni adrese g\u00f6nderilebilir. <code>.htaccess<\/code> dosyas\u0131n\u0131n ilgili sanal host taraf\u0131ndan okunabildi\u011finden emin olun.<\/p>\n<pre><code>RewriteEngine On\nRewriteRule ^eski-sayfa\/?$ https:\/\/www.example.com\/yeni-sayfa [R=301,L]<\/code><\/pre>\n<p><code>R=301<\/code> kal\u0131c\u0131 y\u00f6nlendirmeyi, <code>L<\/code> ise kural e\u015fle\u015fti\u011finde ayn\u0131 kural setinde i\u015flemeyi durdurmay\u0131 belirtir. Apache yap\u0131land\u0131rmas\u0131nda <code>AllowOverride<\/code> ve mod\u00fcl durumu kontrol edilmeden yaln\u0131zca dosyaya kural eklemek yeterli de\u011fildir.<\/p>\n<h3>Nginx server blo\u011fu<\/h3>\n<p>Nginx \u00fczerinde tek bir URL i\u00e7in daha do\u011frudan bir <code>return<\/code> kural\u0131 kullan\u0131labilir:<\/p>\n<pre><code>server {\n    listen 80;\n    server_name example.com;\n\n    return 301 https:\/\/www.example.com$request_uri;\n}<\/code><\/pre>\n<p><code>$request_uri<\/code>, sorgu dizesiyle birlikte istenen yolu korur. B\u00f6ylece <code>\/urun?id=42<\/code> iste\u011fi yeni alan ad\u0131na ta\u015f\u0131n\u0131rken yol ve sorgu bilgisi kaybolmaz. Yap\u0131land\u0131rmay\u0131 etkinle\u015ftirmeden \u00f6nce mutlaka \u015fu iki kontrol \u00e7al\u0131\u015ft\u0131r\u0131lmal\u0131d\u0131r:<\/p>\n<pre><code>sudo nginx -t\nsudo systemctl reload nginx<\/code><\/pre>\n<p>\u0130lk komut s\u00f6zdizimini test eder, ikinci komut \u00e7al\u0131\u015fan Nginx s\u00fcrecini kesmeden yap\u0131land\u0131rmay\u0131 yeniden y\u00fckler. <code>nginx -t<\/code> ba\u015far\u0131s\u0131zsa reload \u00e7al\u0131\u015ft\u0131rmay\u0131n.<\/p>\n<p>Apache veya Nginx se\u00e7imi, y\u00f6nlendirmenin SEO anlam\u0131n\u0131 de\u011fi\u015ftirmez; kural\u0131n do\u011fru sanal host i\u00e7inde bulunmas\u0131 ve her eski URL&#8217;yi beklenen hedefe g\u00f6ndermesi \u00f6nemlidir.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Yap\u0131land\u0131rmay\u0131 yay\u0131nlamadan \u00f6nce s\u00f6zdizimini test edin, ard\u0131ndan hem HTTP hem HTTPS isteklerini ayr\u0131 ayr\u0131 do\u011frulay\u0131n.<\/p>\n<h2 id=\"wordpresste-301-yonlendirme-nasil-yapilir\">WordPress&#8217;te 301 y\u00f6nlendirme nas\u0131l yap\u0131l\u0131r?<\/h2>\n<p>WordPress&#8217;te basit URL de\u011fi\u015fiklikleri bir SEO eklentisi, \u00f6zel eklenti veya sunucu katman\u0131 \u00fczerinden y\u00f6netilebilir. Trafi\u011fi y\u00fcksek sitelerde y\u00f6nlendirmeyi m\u00fcmk\u00fcn oldu\u011funca Nginx ya da Apache katman\u0131nda yapmak, WordPress PHP s\u00fcrecini gereksiz yere \u00e7al\u0131\u015ft\u0131rmaktan ka\u00e7\u0131nabilir.<\/p>\n<p>Eklenti kullan\u0131l\u0131yorsa kural\u0131n eski URL&#8217;yi tam olarak yakalad\u0131\u011f\u0131n\u0131 kontrol edin. Sonundaki slash, b\u00fcy\u00fck-k\u00fc\u00e7\u00fck harf, URL kodlamas\u0131 ve sorgu parametreleri farkl\u0131 davran\u0131\u015flar do\u011furabilir. \u00d6rne\u011fin <code>\/blog\/yazi<\/code> ile <code>\/blog\/yazi\/<\/code> uygulamada ayr\u0131 rotalar olarak ele al\u0131n\u0131yorsa tek bir canonical URL belirlenmelidir.<\/p>\n<p>Y\u00f6nlendirme eklentileriyle ilgili karar verirken <a href=\"https:\/\/www.vps.tc\/blog\/tr\/wordpress-seo-eklentileri-en-iyi-secenekler\/\">WordPress SEO Eklentileri Nelerdir? En \u0130yi Se\u00e7enekler<\/a> i\u00e7eri\u011findeki eklenti ve yap\u0131land\u0131rma ayr\u0131m\u0131n\u0131 dikkate al\u0131n. Bir eklentide tutulan binlerce kural, ta\u015f\u0131nma sonras\u0131nda sunucuya aktar\u0131lmadan kalabilir; bu nedenle d\u0131\u015fa aktarma ve geri d\u00f6n\u00fc\u015f plan\u0131 olu\u015fturulmal\u0131d\u0131r.<\/p>\n<h3>WordPress&#8217;te s\u0131k g\u00f6r\u00fclen d\u00f6ng\u00fc<\/h3>\n<p>WordPress HTTPS arkas\u0131nda, Nginx ise bir reverse proxy arkas\u0131nda \u00e7al\u0131\u015f\u0131yorsa uygulama ger\u00e7ek ba\u011flant\u0131n\u0131n HTTPS oldu\u011funu alg\u0131lamayabilir. Bu durumda WordPress HTTP&#8217;ye, proxy tekrar HTTPS&#8217;ye y\u00f6nlendirir ve taray\u0131c\u0131da <code>ERR_TOO_MANY_REDIRECTS<\/code> g\u00f6r\u00fcl\u00fcr. <code>X-Forwarded-Proto<\/code> ba\u015fl\u0131\u011f\u0131n\u0131n proxy ve uygulama taraf\u0131ndan g\u00fcvenli bi\u00e7imde ele al\u0131nmas\u0131 gerekir.<\/p>\n<p>Y\u00f6nlendirme ekledikten sonra giri\u015f sayfas\u0131, y\u00f6netim paneli, g\u00f6rseller ve canonical etiketleri birlikte test edilmelidir. Yaln\u0131zca ana sayfan\u0131n a\u00e7\u0131lmas\u0131 yeterli kan\u0131t de\u011fildir.<\/p>\n<h2 id=\"httpden-httpsye-geciste-301-nasil-kullanilmali\">HTTP&#8217;den HTTPS&#8217;ye ge\u00e7i\u015fte 301 nas\u0131l kullan\u0131lmal\u0131?<\/h2>\n<p>HTTPS ge\u00e7i\u015finde genellikle port 80&#8217;deki HTTP sanal host, ayn\u0131 yolu koruyarak port 443&#8217;teki HTTPS adrese y\u00f6nlendirilir. \u00d6nce sertifika, zincir, sanal host ve uygulama i\u00e7indeki mutlak URL&#8217;ler haz\u0131rlanmal\u0131d\u0131r. Sertifika haz\u0131r de\u011filken HTTP trafi\u011fini HTTPS&#8217;ye y\u00f6nlendirmek kullan\u0131c\u0131lar\u0131 TLS hatas\u0131na g\u00f6t\u00fcr\u00fcr.<\/p>\n<pre><code>server {\n    listen 80;\n    server_name example.com www.example.com;\n\n    return 301 https:\/\/www.example.com$request_uri;\n}<\/code><\/pre>\n<p>HTTPS sanal host i\u00e7inde <code>www<\/code> veya k\u00f6k alan ad\u0131 i\u00e7in tek bir tercih belirleyin. Hem <code>https:\/\/example.com<\/code> hem de <code>https:\/\/www.example.com<\/code> farkl\u0131 i\u00e7erik sunuyorsa canonical ve y\u00f6nlendirme stratejisi da\u011f\u0131l\u0131r.<\/p>\n<p>HSTS, taray\u0131c\u0131lar\u0131n gelecekte HTTP iste\u011fi yapmadan HTTPS kullanmas\u0131n\u0131 sa\u011flar; ancak yanl\u0131\u015f yap\u0131land\u0131r\u0131ld\u0131\u011f\u0131nda geri d\u00f6n\u00fc\u015f\u00fc zorla\u015ft\u0131rabilir. \u00d6nce 301 kurallar\u0131n\u0131, sertifikay\u0131 ve alt alan adlar\u0131n\u0131 test edin. HSTS politikas\u0131n\u0131 daha sonra, kapsam\u0131 ve <code>includeSubDomains<\/code> etkisi anla\u015f\u0131l\u0131nca uygulay\u0131n.<\/p>\n<p>SSL kurulumu s\u0131ras\u0131nda yaln\u0131zca y\u00f6nlendirmeye odaklanmay\u0131n. <a href=\"https:\/\/www.vps.tc\/blog\/tr\/vps-ssl-sertifikasi-kurulumu-lets-encrypt\/\">VPS&#8217;te SSL Sertifikas\u0131 Kurulumu: Let&#8217;s Encrypt Rehberi<\/a> \u00fczerinden sertifika yenileme ve sanal host kontrollerini de g\u00f6zden ge\u00e7irin.<\/p>\n<div class=\"aiw-callout aiw-callout-field\">\n<p class=\"aiw-callout-label\">Sahadan not<\/p>\n<p>Bayram sabah\u0131 bir sitenin HTTPS sertifikas\u0131n\u0131n s\u00fcresi doldu\u011fu alarm\u0131n\u0131 ald\u0131m. \/var\/log\/letsencrypt\/letsencrypt.log i\u00e7inde renewal g\u00f6revinin sertifika do\u011frulama hatas\u0131 verdi\u011fini, systemctl status certbot.timer \u00e7\u0131kt\u0131s\u0131nda ise zamanlay\u0131c\u0131n\u0131n ba\u015far\u0131s\u0131z kald\u0131\u011f\u0131n\u0131 g\u00f6rd\u00fcm; HTTP&#039;den HTTPS&#039;ye 301 ge\u00e7i\u015fi \u00e7al\u0131\u015f\u0131yordu ama hedef TLS sunucusu sertifika hatas\u0131 d\u00f6nd\u00fcr\u00fcyordu.<\/p>\n<\/div>\n<h2 id=\"301-zinciri-ve-yonlendirme-dongusu-nasil-bulunur\">301 zinciri ve y\u00f6nlendirme d\u00f6ng\u00fcs\u00fc nas\u0131l bulunur?<\/h2>\n<p>Eski URL&#8217;nin \u00f6nce ba\u015fka bir eski URL&#8217;ye, ard\u0131ndan son hedefe gitmesi y\u00f6nlendirme zinciridir. A&#8217;dan B&#8217;ye, B&#8217;den C&#8217;ye giden \u00fc\u00e7 a\u015famal\u0131 bir zincir \u00e7al\u0131\u015fabilir; fakat her ek istek gecikme, hata ve tarama maliyeti ekler. A&#8217;n\u0131n do\u011frudan C&#8217;ye gitmesi daha temizdir.<\/p>\n<p>D\u00f6ng\u00fcde ise URL&#8217;ler birbirlerini tekrar \u00e7a\u011f\u0131r\u0131r. \u00d6rne\u011fin HTTP HTTPS&#8217;ye, HTTPS de yanl\u0131\u015f bir proxy alg\u0131s\u0131 nedeniyle HTTP&#8217;ye y\u00f6nlendiriyorsa taray\u0131c\u0131 sonland\u0131rma yapar. Komut sat\u0131r\u0131ndan ba\u015fl\u0131klar\u0131 g\u00f6rmek i\u00e7in:<\/p>\n<pre><code>curl -I http:\/\/example.com\/eski-sayfa\ncurl -IL --max-redirs 10 http:\/\/example.com\/eski-sayfa<\/code><\/pre>\n<p><code>-I<\/code> yaln\u0131zca ba\u015fl\u0131klar\u0131 ister. <code>-L<\/code> y\u00f6nlendirmeleri izler; \u00e7\u0131kt\u0131daki her <code>HTTP\/<\/code> ve <code>Location:<\/code> sat\u0131r\u0131 zincirin bir halkas\u0131n\u0131 g\u00f6sterir. <code>--max-redirs 10<\/code> sonsuz takip riskini s\u0131n\u0131rlamak i\u00e7in kullan\u0131l\u0131r.<\/p>\n<p>Taray\u0131c\u0131 \u00f6nbelle\u011fi ve CDN \u00f6nbelle\u011fi testleri yan\u0131ltabilir. Farkl\u0131 bir istemci, temiz profil veya uygun bir g\u00f6zlem noktas\u0131yla deneme yap\u0131n. Sunucunun ger\u00e7ekten g\u00f6nderdi\u011fi durum kodunu g\u00f6rmek i\u00e7in <code>curl -sS -D - -o \/dev\/null URL<\/code> komutu da kullan\u0131labilir.<\/p>\n<p>\u0130\u00e7 ba\u011flant\u0131lar h\u00e2l\u00e2 eski URL&#8217;leri g\u00f6steriyorsa her t\u0131klamada 301 \u00e7al\u0131\u015f\u0131r. Bu ba\u011flant\u0131lar\u0131 yeni hedefe \u00e7evirin; 301 yaln\u0131zca d\u0131\u015far\u0131dan gelen eski ba\u011flant\u0131lar\u0131 kar\u015f\u0131lamak i\u00e7in geride kals\u0131n.<\/p>\n<p><strong>Ne yap\u0131lmal\u0131<\/strong> &#8211; Her eski URL&#8217;nin tek bir 301 ile nihai, 200 d\u00f6nen ve konu bak\u0131m\u0131ndan e\u015fle\u015fen sayfaya ula\u015ft\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-tip\">\n<p class=\"aiw-callout-label\">\u0130pucu<\/p>\n<p>Tek bir URL&#039;yi h\u0131zl\u0131ca test etmek i\u00e7in curl -I kullan\u0131n; Location ba\u015fl\u0131\u011f\u0131n\u0131 ve durum kodunu birlikte g\u00f6r\u00fcn. \u00c7oklu ge\u00e7i\u015fte curl -IL &#8211;max-redirs 10 komutu zinciri s\u0131n\u0131rl\u0131 bi\u00e7imde izler.<\/p>\n<\/div>\n<h2 id=\"301-uygulamasindan-sonra-hangi-kontroller-yapilmali\">301 uygulamas\u0131ndan sonra hangi kontroller yap\u0131lmal\u0131?<\/h2>\n<p>Ge\u00e7i\u015fi yaln\u0131zca taray\u0131c\u0131da birka\u00e7 sayfa a\u00e7arak tamamlanm\u0131\u015f saymay\u0131n. Eski URL listesi, sunucu eri\u015fim loglar\u0131, Search Console raporlar\u0131, sitemap ve canonical de\u011ferleri birlikte incelenmelidir.<\/p>\n<ul>\n<li>Eski URL&#8217;lerin 301 d\u00f6nd\u00fcrd\u00fc\u011f\u00fcn\u00fc kontrol edin.<\/li>\n<li>Yeni URL&#8217;lerin son a\u015famada 200 d\u00f6nd\u00fcrd\u00fc\u011f\u00fcn\u00fc do\u011frulay\u0131n.<\/li>\n<li>Y\u00f6nlendirme zinciri ve d\u00f6ng\u00fcs\u00fc bulunmad\u0131\u011f\u0131n\u0131 test edin.<\/li>\n<li>\u0130\u00e7 ba\u011flant\u0131lar\u0131, canonical etiketlerini ve XML sitemap&#8217;i g\u00fcncelleyin.<\/li>\n<li>G\u00f6rsel, CSS, JavaScript ve form yollar\u0131n\u0131 ayr\u0131 ayr\u0131 deneyin.<\/li>\n<li>Loglarda beklenmeyen 404, 5xx ve a\u015f\u0131r\u0131 y\u00f6nlendirme art\u0131\u015f\u0131n\u0131 izleyin.<\/li>\n<\/ul>\n<p>Ta\u015f\u0131nan sayfalar\u0131n yeni URL&#8217;lerinde <code>noindex<\/code> bulunmad\u0131\u011f\u0131ndan da emin olun. Eski adresin 301, yeni adresin 200 ve indekslenebilir olmas\u0131 beklenen temel dizidir. Bir hata sayfas\u0131 y\u00f6nlendirmesi g\u00f6r\u00fcyorsan\u0131z <a href=\"https:\/\/www.vps.tc\/blog\/tr\/404-hatasi-nedir-sebepleri-ve-cozum-yollari\/\">404 Hatas\u0131 Nedir? Sebepleri ve \u00c7\u00f6z\u00fcm Yollar\u0131<\/a> i\u00e7eri\u011findeki durum kodu kontrolleri yard\u0131mc\u0131 olur.<\/p>\n<p>Sunucu taraf\u0131nda y\u00f6nlendirme oran\u0131n\u0131 loglardan takip etmek, kural\u0131n beklenmeyen URL&#8217;leri de yakalay\u0131p yakalamad\u0131\u011f\u0131n\u0131 g\u00f6sterir. \u00d6zellikle regex i\u00e7eren genel kurallar, resim veya y\u00f6netim paneli yollar\u0131n\u0131 istemeden etkileyebilir.<\/p>\n<div class=\"aiw-callout aiw-callout-warn\">\n<p class=\"aiw-callout-label\">Dikkat<\/p>\n<p>B\u00fct\u00fcn eski URL&#039;leri ana sayfaya y\u00f6nlendirmek kolayd\u0131r ama \u00e7o\u011fu durumda do\u011fru de\u011fildir. Kullan\u0131c\u0131n\u0131n bekledi\u011fi i\u00e7eri\u011fe en yak\u0131n yeni sayfay\u0131 se\u00e7in ve alakas\u0131z hedeflerde 301 kullanmay\u0131n.<\/p>\n<\/div>\n<h2 id=\"301-yonlendirmede-hangi-hatalardan-kacinilmali\">301 y\u00f6nlendirmede hangi hatalardan ka\u00e7\u0131n\u0131lmal\u0131?<\/h2>\n<p>En yayg\u0131n hata, b\u00fct\u00fcn eski sayfalar\u0131 ana sayfaya g\u00f6ndermektir. Kullan\u0131c\u0131 eski bir \u00fcr\u00fcn veya rehber ba\u011flant\u0131s\u0131n\u0131 a\u00e7t\u0131\u011f\u0131nda alakas\u0131z bir ana sayfa g\u00f6r\u00fcr; arama motoru da bu hedefi anlaml\u0131 bir e\u015fle\u015fme olarak de\u011ferlendirmeyebilir.<\/p>\n<p>\u0130kinci hata, y\u00f6nlendirmeleri aylarca b\u00fcy\u00fcyen bir listeye d\u00f6n\u00fc\u015ft\u00fcrmektir. Kural eklemek kolayd\u0131r, eski zinciri temizlemek daha zahmetlidir. Her de\u011fi\u015fiklikten sonra eski hedefi do\u011frudan nihai URL&#8217;ye ba\u011flay\u0131n.<\/p>\n<p>301&#8217;i ge\u00e7ici kampanya, A\/B testi veya k\u0131sa s\u00fcreli bak\u0131m i\u00e7in kullanmak da do\u011fru de\u011fildir. Bu senaryolarda 302, 307 veya uygulamaya uygun ba\u015fka bir y\u00f6ntem d\u00fc\u015f\u00fcn\u00fclmelidir. Ayr\u0131ca y\u00f6nlendirme kural\u0131n\u0131 \u00fcretim ortam\u0131nda test etmeden reload etmek, yaz\u0131m hatas\u0131yla b\u00fct\u00fcn sanal host&#8217;u etkileyebilir.<\/p>\n<p>Son bir ayr\u0131nt\u0131: sorgu parametrelerini otomatik silen kurallar kampanya \u00f6l\u00e7\u00fcm\u00fcn\u00fc veya uygulama oturumlar\u0131n\u0131 bozabilir. <code>utm_source<\/code> gibi pazarlama parametreleri ile uygulaman\u0131n ger\u00e7ekten ihtiya\u00e7 duydu\u011fu <code>?id=<\/code> benzeri parametreleri ayn\u0131 kefeye koymay\u0131n.<\/p>\n<div class=\"aiw-callout aiw-callout-example\">\n<p class=\"aiw-callout-label\">\u00d6rnek<\/p>\n<p>Bir ma\u011fazada \/urun\/eski-model adresi \/urun\/yeni-model adresine ta\u015f\u0131nd\u0131ysa do\u011frudan tek bir 301 tan\u0131mlay\u0131n. Yeni \u00fcr\u00fcn art\u0131k yoksa benzer \u00fcr\u00fcn veya a\u00e7\u0131klay\u0131c\u0131 kategori hedeflenebilir; ana sayfaya toplu g\u00f6nderim son se\u00e7enek olmal\u0131d\u0131r.<\/p>\n<\/div>\n<h2 id=\"301-kuralini-yayina-almadan-once-kontrol-edin\">301 Kural\u0131n\u0131 Yay\u0131na Almadan \u00d6nce Kontrol Edin<\/h2>\n<ul class=\"aiw-checklist\">\n<li>Eski ve yeni URL&#039;leri bir tabloya \u00e7\u0131kar\u0131n.<\/li>\n<li>Her eski URL i\u00e7in konu bak\u0131m\u0131ndan e\u015fle\u015fen hedef belirleyin.<\/li>\n<li>301 ile 302, 307 veya 308 aras\u0131ndan do\u011fru kodu se\u00e7in.<\/li>\n<li>Apache veya Nginx yap\u0131land\u0131rmas\u0131n\u0131 test edin.<\/li>\n<li>curl ile Location ba\u015fl\u0131\u011f\u0131n\u0131 ve t\u00fcm zinciri do\u011frulay\u0131n.<\/li>\n<li>Yeni URL&#039;lerin 200 ve indekslenebilir oldu\u011funu kontrol edin.<\/li>\n<li>Sitemap, canonical ve dahili ba\u011flant\u0131lar\u0131 g\u00fcncelleyin.<\/li>\n<\/ul>\n<div class=\"aiw-cta\">\n<p>URL ta\u015f\u0131ma plan\u0131n\u0131z\u0131 k\u00fc\u00e7\u00fck bir listeyle ba\u015flat\u0131n: eski adres, yeni hedef ve beklenen HTTP kodu. Yay\u0131ndan \u00f6nce bu listeyi curl \u00e7\u0131kt\u0131lar\u0131yla kar\u015f\u0131la\u015ft\u0131rmak, sonradan log av\u0131na \u00e7\u0131kmaktan \u00e7ok daha k\u0131sa s\u00fcrer.<\/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>301 y\u00f6nlendirme SEO&#039;ya zarar verir mi?<\/summary>\n<p>Do\u011fru hedefe yap\u0131lan tek bir 301 genellikle URL de\u011fi\u015fikli\u011finin arama motorlar\u0131na bildirilmesi i\u00e7in uygun y\u00f6ntemdir. Zarar; alakas\u0131z sayfaya y\u00f6nlendirme, zincir, d\u00f6ng\u00fc, toplu ana sayfa y\u00f6nlendirmesi veya yeni hedefin eri\u015filememesi gibi uygulama hatalar\u0131ndan do\u011far. Ge\u00e7i\u015f sonras\u0131nda indeksleme ve trafik raporlar\u0131n\u0131 izlemek gerekir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>301 y\u00f6nlendirme ne kadar s\u00fcrede etkili olur?<\/summary>\n<p>Sunucu yan\u0131t\u0131 teknik olarak kural yay\u0131nland\u0131\u011f\u0131 anda \u00e7al\u0131\u015f\u0131r. Arama motorunun yeni URL&#039;yi taramas\u0131 ve indekslemesi ise sitenin tarama s\u0131kl\u0131\u011f\u0131na, sitemap durumuna, ba\u011flant\u0131lara ve de\u011fi\u015fikli\u011fin kapsam\u0131na g\u00f6re farkl\u0131 s\u00fcrelerde ger\u00e7ekle\u015febilir. Eski URL&#039;yi hemen kald\u0131rmak yerine bir s\u00fcre 301 ile eri\u015filebilir b\u0131rakmak gerekir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>301 ile 302 aras\u0131ndaki fark nedir?<\/summary>\n<p>301 kal\u0131c\u0131 ta\u015f\u0131nmay\u0131, 302 ge\u00e7ici ta\u015f\u0131nmay\u0131 bildirir. Sayfa kal\u0131c\u0131 olarak yeni adrese ge\u00e7tiyse 301; k\u0131sa s\u00fcreli kampanya, bak\u0131m veya test yap\u0131l\u0131yorsa 302 daha uygun olabilir. Yanl\u0131\u015f kod, arama motorunun hangi URL&#039;yi esas alaca\u011f\u0131 ve tarama davran\u0131\u015f\u0131 konusunda belirsizlik olu\u015fturabilir.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Bir URL&#039;yi ana sayfaya 301 ile y\u00f6nlendirmek do\u011fru mu?<\/summary>\n<p>Genellikle hay\u0131r. Eski URL&#039;deki i\u00e7erikle anlaml\u0131 bi\u00e7imde e\u015fle\u015fen yeni sayfa varsa hedef olarak onu se\u00e7in. \u0130\u00e7erik tamamen kald\u0131r\u0131lm\u0131\u015f ve e\u015fde\u011fer bir sayfa yoksa 404 veya 410 daha d\u00fcr\u00fcst bir yan\u0131t olabilir. Ana sayfaya y\u00fczlerce alakas\u0131z y\u00f6nlendirme yapmak kullan\u0131c\u0131 beklentisini kar\u015f\u0131lamaz.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>301 y\u00f6nlendirme zinciri nas\u0131l d\u00fczeltilir?<\/summary>\n<p>\u00d6nce curl -IL veya benzeri bir ara\u00e7la her Location ba\u015fl\u0131\u011f\u0131n\u0131 listeleyin. Eski URL&#039;nin ara adresleri atlay\u0131p do\u011frudan nihai, 200 d\u00f6nen URL&#039;ye gitmesini sa\u011flay\u0131n. \u0130\u00e7 ba\u011flant\u0131lar\u0131 da yeni hedefe \u00e7evirin. B\u00f6ylece ziyaret\u00e7iler, botlar ve CDN her istekte gereksiz ek y\u00f6nlendirme takip etmez.<\/p>\n<\/details>\n<details class=\"aiw-faq-item\">\n<summary>Nginx&#039;te 301 y\u00f6nlendirme yapt\u0131ktan sonra neden d\u00f6ng\u00fc olu\u015fur?<\/summary>\n<p>En yayg\u0131n neden, HTTPS arkas\u0131ndaki reverse proxy&#039;nin ba\u011flant\u0131 protokol\u00fcn\u00fc uygulamaya do\u011fru aktarmamas\u0131d\u0131r. Uygulama iste\u011fi HTTP san\u0131p HTTPS&#039;ye y\u00f6nlendirirken proxy tekrar HTTPS iste\u011fi g\u00f6nderebilir. X-Forwarded-Proto, TLS sonland\u0131rma ve server bloklar\u0131n\u0131 kontrol edin; curl -IL \u00e7\u0131kt\u0131s\u0131yla iki adres aras\u0131nda tekrar olup olmad\u0131\u011f\u0131n\u0131 do\u011frulay\u0131n.<\/p>\n<\/details>\n<\/div>\n<h2 id=\"kaynaklar\">Kaynaklar<\/h2>\n<ul class=\"aiw-sources\">\n<li><a href=\"https:\/\/www.rfc-editor.org\/rfc\/rfc9110.html\" target=\"_blank\" rel=\"noopener\">IETF RFC 9110 &#8211; HTTP Semantics<\/a> \u2014 rfc-editor.org<\/li>\n<li><a href=\"https:\/\/developer.mozilla.org\/en-US\/docs\/Web\/HTTP\/Reference\/Status\/301\" target=\"_blank\" rel=\"noopener\">MDN &#8211; 301 Moved Permanently<\/a> \u2014 developer.mozilla.org<\/li>\n<li><a href=\"https:\/\/developers.google.com\/search\/docs\/crawling-indexing\/301-redirects\" target=\"_blank\" rel=\"noopener\">Google Search Central &#8211; Redirects and Google Search<\/a> \u2014 developers.google.com<\/li>\n<li><a href=\"https:\/\/nginx.org\/en\/docs\/http\/ngx_http_rewrite_module.html\" target=\"_blank\" rel=\"noopener\">nginx.org &#8211; Rewrite Module<\/a> \u2014 nginx.org<\/li>\n<\/ul>\n","protected":false},"excerpt":{"rendered":"<p>301 y\u00f6nlendirme, kal\u0131c\u0131 olarak de\u011fi\u015fen URL&#8217;leri yeni adreslerine ta\u015f\u0131rken kullan\u0131c\u0131 eri\u015fimini ve arama motoru sinyallerini korumaya yard\u0131mc\u0131 olur. Do\u011fru kod se\u00e7imi, sunucu yap\u0131land\u0131rmas\u0131 ve test ad\u0131mlar\u0131yla zincir ve d\u00f6ng\u00fc hatalar\u0131n\u0131 \u00f6nleyebilirsiniz.<\/p>\n","protected":false},"author":2,"featured_media":762,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[111],"tags":[],"class_list":["post-764","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-domain"],"lang":"tr","translations":{"tr":764,"en":765},"pll_sync_post":[],"_links":{"self":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/764","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=764"}],"version-history":[{"count":2,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/764\/revisions"}],"predecessor-version":[{"id":768,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/posts\/764\/revisions\/768"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media\/762"}],"wp:attachment":[{"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/media?parent=764"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/categories?post=764"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.vps.tc\/blog\/wp-json\/wp\/v2\/tags?post=764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}