{"id":4055,"date":"2026-01-03T15:10:02","date_gmt":"2026-01-03T12:10:02","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/www-mi-ciplak-alan-adi-mi-canonical-domain-301-ve-hsts-icin-dogru-ayarlar\/"},"modified":"2026-01-03T15:10:02","modified_gmt":"2026-01-03T12:10:02","slug":"www-mi-ciplak-alan-adi-mi-canonical-domain-301-ve-hsts-icin-dogru-ayarlar","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/www-mi-ciplak-alan-adi-mi-canonical-domain-301-ve-hsts-icin-dogru-ayarlar\/","title":{"rendered":"www mi \u00c7\u0131plak Alan Ad\u0131 m\u0131? Canonical Domain, 301 ve HSTS i\u00e7in Do\u011fru Ayarlar"},"content":{"rendered":"<div class=\"dchost-blog-content-wrapper\"><div id=\"toc_container\" class=\"toc_transparent no_bullets\"><p class=\"toc_title\">\u0130&ccedil;indekiler<\/p><ul class=\"toc_list\"><li><a href=\"#www_mi_Ciplak_Alan_Adi_mi_Asil_Sorun_Sandiginizdan_Farkli\"><span class=\"toc_number toc_depth_1\">1<\/span> www mi \u00c7\u0131plak Alan Ad\u0131 m\u0131? As\u0131l Sorun Sand\u0131\u011f\u0131n\u0131zdan Farkl\u0131<\/a><\/li><li><a href=\"#www_ve_Ciplak_Alan_Adi_Arasindaki_Gercek_Fark_Nedir\"><span class=\"toc_number toc_depth_1\">2<\/span> www ve \u00c7\u0131plak Alan Ad\u0131 Aras\u0131ndaki Ger\u00e7ek Fark Nedir?<\/a><ul><li><a href=\"#DNS_tarafinda_farklar\"><span class=\"toc_number toc_depth_2\">2.1<\/span> DNS taraf\u0131nda farklar<\/a><\/li><li><a href=\"#Tarayici_ve_cookie_davranisi\"><span class=\"toc_number toc_depth_2\">2.2<\/span> Taray\u0131c\u0131 ve cookie davran\u0131\u015f\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Canonical_Domain_Nedir_ve_Neden_Kritik\"><span class=\"toc_number toc_depth_1\">3<\/span> Canonical Domain Nedir ve Neden Kritik?<\/a><\/li><li><a href=\"#SEO_Acisindan_www_vs_Ciplak_Alan_Adi\"><span class=\"toc_number toc_depth_1\">4<\/span> SEO A\u00e7\u0131s\u0131ndan www vs \u00c7\u0131plak Alan Ad\u0131<\/a><ul><li><a href=\"#Yanlis_kurulumun_tipik_sonuclari\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Yanl\u0131\u015f kurulumun tipik sonu\u00e7lar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#Dogru_301_Yonlendirme_Stratejisi_Tum_Yollar_Tek_Adrese\"><span class=\"toc_number toc_depth_1\">5<\/span> Do\u011fru 301 Y\u00f6nlendirme Stratejisi: T\u00fcm Yollar Tek Adrese<\/a><ul><li><a href=\"#Apache_htaccess_icin_ornek_301_kurallari\"><span class=\"toc_number toc_depth_2\">5.1<\/span> Apache (.htaccess) i\u00e7in \u00f6rnek 301 kurallar\u0131<\/a><\/li><li><a href=\"#Nginx_icin_ornek_301_kurallari\"><span class=\"toc_number toc_depth_2\">5.2<\/span> Nginx i\u00e7in \u00f6rnek 301 kurallar\u0131<\/a><\/li><\/ul><\/li><li><a href=\"#HTTPS_HSTS_ve_Canonical_Domain_Iliskisi\"><span class=\"toc_number toc_depth_1\">6<\/span> HTTPS, HSTS ve Canonical Domain \u0130li\u015fkisi<\/a><ul><li><a href=\"#HSTS_nasil_calisir\"><span class=\"toc_number toc_depth_2\">6.1<\/span> HSTS nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/a><\/li><li><a href=\"#HSTS_acmadan_once_dikkat_edilmesi_gerekenler\"><span class=\"toc_number toc_depth_2\">6.2<\/span> HSTS a\u00e7madan \u00f6nce dikkat edilmesi gerekenler<\/a><\/li><\/ul><\/li><li><a href=\"#Farkli_Senaryolar_Icin_www_Non-www_Karar_Rehberi\"><span class=\"toc_number toc_depth_1\">7<\/span> Farkl\u0131 Senaryolar \u0130\u00e7in www \/ Non-www Karar Rehberi<\/a><ul><li><a href=\"#1_Yeni_kurulan_kurumsal_site_blog\"><span class=\"toc_number toc_depth_2\">7.1<\/span> 1. Yeni kurulan kurumsal site \/ blog<\/a><\/li><li><a href=\"#2_CDN_ve_coklu_alt_alan_kullanilan_projeler\"><span class=\"toc_number toc_depth_2\">7.2<\/span> 2. CDN ve \u00e7oklu alt alan kullan\u0131lan projeler<\/a><\/li><li><a href=\"#3_Halihazirda_index_almis_yillardir_yayinda_olan_site\"><span class=\"toc_number toc_depth_2\">7.3<\/span> 3. Halihaz\u0131rda index alm\u0131\u015f, y\u0131llard\u0131r yay\u0131nda olan site<\/a><\/li><\/ul><\/li><li><a href=\"#cPanel_Paylasimli_Hosting_ve_VPSDedicated_Ortamlarinda_Uygulama\"><span class=\"toc_number toc_depth_1\">8<\/span> cPanel, Payla\u015f\u0131ml\u0131 Hosting ve VPS\/Dedicated Ortamlar\u0131nda Uygulama<\/a><ul><li><a href=\"#cPanel_Paylasimli_Hostingte_pratik_kurulum\"><span class=\"toc_number toc_depth_2\">8.1<\/span> cPanel \/ Payla\u015f\u0131ml\u0131 Hosting\u2019te pratik kurulum<\/a><\/li><li><a href=\"#VPS_dedicated_sunucularda_manuel_konfigurasyon\"><span class=\"toc_number toc_depth_2\">8.2<\/span> VPS \/ dedicated sunucularda manuel konfig\u00fcrasyon<\/a><\/li><\/ul><\/li><li><a href=\"#Sik_Yapilan_Hatalar_ve_Kisa_Kontrol_Listesi\"><span class=\"toc_number toc_depth_1\">9<\/span> S\u0131k Yap\u0131lan Hatalar ve K\u0131sa Kontrol Listesi<\/a><ul><li><a href=\"#En_sik_gordugumuz_hatalar\"><span class=\"toc_number toc_depth_2\">9.1<\/span> En s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalar<\/a><\/li><li><a href=\"#Hizli_kontrol_listesi\"><span class=\"toc_number toc_depth_2\">9.2<\/span> H\u0131zl\u0131 kontrol listesi<\/a><\/li><\/ul><\/li><li><a href=\"#Ozet_ve_DCHost_Tarafinda_Nasil_Yardimci_Oluyoruz\"><span class=\"toc_number toc_depth_1\">10<\/span> \u00d6zet ve DCHost Taraf\u0131nda Nas\u0131l Yard\u0131mc\u0131 Oluyoruz?<\/a><\/li><\/ul><\/div>\n<h2><span id=\"www_mi_Ciplak_Alan_Adi_mi_Asil_Sorun_Sandiginizdan_Farkli\">www mi \u00c7\u0131plak Alan Ad\u0131 m\u0131? As\u0131l Sorun Sand\u0131\u011f\u0131n\u0131zdan Farkl\u0131<\/span><\/h2>\n<p>Yeni bir alan ad\u0131 a\u00e7arken ya da y\u0131llard\u0131r yay\u0131nda olan bir projeyi ta\u015f\u0131rken kar\u015f\u0131n\u0131za mutlaka \u015fu soru \u00e7\u0131kar: <strong>www mi kullanal\u0131m, yoksa \u00e7\u0131plak alan ad\u0131 (non-www) m\u0131?<\/strong> D\u0131\u015far\u0131dan bak\u0131nca bu sadece estetik bir tercih gibi g\u00f6r\u00fcn\u00fcr; oysa i\u015fin i\u00e7inde <strong>canonical domain<\/strong>, <strong>301 y\u00f6nlendirme<\/strong>, <strong>HTTPS ve HSTS<\/strong>, taray\u0131c\u0131 \u00f6nbelle\u011fi, hatta uzun vadeli <strong>SEO stratejisi<\/strong> var. DCHost taraf\u0131nda hem k\u00fc\u00e7\u00fck kurumsal sitelerde hem y\u00fcksek trafikli projelerde en \u00e7ok m\u00fcdahale etti\u011fimiz yanl\u0131\u015flardan biri, yanl\u0131\u015f kurgulanm\u0131\u015f domain y\u00f6nlendirmeleri ve eksik HSTS ayarlar\u0131.<\/p>\n<p>Bu yaz\u0131da; www \/ non-www se\u00e7iminin teknik farklar\u0131n\u0131, <strong>canonical domain<\/strong> kavram\u0131n\u0131, do\u011fru 301 kurulumunu, HSTS\u2019in ne zaman a\u00e7\u0131lmas\u0131 gerekti\u011fini ve t\u00fcm bunlar\u0131n SEO\u2019ya etkisini ad\u0131m ad\u0131m, pratik \u00f6rneklerle toparlayaca\u011f\u0131z. Amac\u0131m\u0131z, alan ad\u0131n\u0131z i\u00e7in <strong>tek, temiz ve kal\u0131c\u0131 bir adres stratejisi<\/strong> belirlemenize yard\u0131mc\u0131 olmak. Yaz\u0131n\u0131n sonunda, hem <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a> hem de VPS\/dedicated ortamlar\u0131nda do\u011frudan uygulayabilece\u011finiz bir <strong>kontrol listesi<\/strong> ve karar rehberi bulacaks\u0131n\u0131z.<\/p>\n<h2><span id=\"www_ve_Ciplak_Alan_Adi_Arasindaki_Gercek_Fark_Nedir\">www ve \u00c7\u0131plak Alan Ad\u0131 Aras\u0131ndaki Ger\u00e7ek Fark Nedir?<\/span><\/h2>\n<p>\u00d6nce terimleri netle\u015ftirelim:<\/p>\n<ul>\n<li><strong>\u00c7\u0131plak alan ad\u0131 (root \/ apex domain):<\/strong> ornek.com<\/li>\n<li><strong>www alt alan ad\u0131:<\/strong> www.ornek.com (teknik olarak bir subdomain)<\/li>\n<\/ul>\n<p>Kullan\u0131c\u0131 a\u00e7\u0131s\u0131ndan ikisi de ayn\u0131 site gibi g\u00f6r\u00fcn\u00fcr; ama DNS ve taray\u0131c\u0131 d\u00fcnyas\u0131nda durum farkl\u0131d\u0131r.<\/p>\n<h3><span id=\"DNS_tarafinda_farklar\">DNS taraf\u0131nda farklar<\/span><\/h3>\n<p>\u00c7\u0131plak alan ad\u0131nda (ornek.com) geleneksel DNS sunucular\u0131nda <strong>CNAME<\/strong> kullanamazs\u0131n\u0131z; genellikle <strong>A<\/strong> veya <strong>AAAA<\/strong> kayd\u0131 ile do\u011frudan IP adresine i\u015faret etmeniz gerekir. www alt alan ad\u0131nda ise CNAME, ba\u015fka bir hostname\u2019e (\u00f6rne\u011fin CDN ya da reverse proxy) y\u00f6nlendirmek i\u00e7in rahat\u00e7a kullan\u0131labilir.<\/p>\n<p>Modern DNS sa\u011flay\u0131c\u0131lar\u0131nda <strong>ALIAS\/ANAME<\/strong> gibi \u00f6zel kay\u0131t t\u00fcrleriyle apex domain\u2019i de esnek bir hedefe i\u015faret etmek m\u00fcmk\u00fcn olsa da, h\u00e2l\u00e2 bir\u00e7ok mimaride www kullanmak <strong>esneklik<\/strong> kazand\u0131r\u0131r. \u00d6zellikle CDN, WAF, \u00e7ok b\u00f6lgeli mimari gibi yap\u0131larda www alt alan\u0131n\u0131 canonical yapmak i\u015fleri basitle\u015ftirebilir.<\/p>\n<h3><span id=\"Tarayici_ve_cookie_davranisi\">Taray\u0131c\u0131 ve cookie davran\u0131\u015f\u0131<\/span><\/h3>\n<p>Cookie domain kapsam\u0131 da \u00f6nemli bir farkt\u0131r:<\/p>\n<ul>\n<li>Cookie\u2019yi <strong>.ornek.com<\/strong> i\u00e7in ayarlarsan\u0131z, hem ornek.com hem de t\u00fcm alt alanlarda (www.ornek.com, api.ornek.com vb.) ge\u00e7erli olur.<\/li>\n<li>Cookie\u2019yi sadece <strong>www.ornek.com<\/strong> i\u00e7in ayarlarsan\u0131z, ornek.com \u00fczerinde ge\u00e7erli olmaz.<\/li>\n<\/ul>\n<p>Bu, \u00f6zellikle <strong>statik i\u00e7erik i\u00e7in ayr\u0131 CDN alt alanlar\u0131<\/strong> kullan\u0131yorsan\u0131z ve gereksiz cookie ta\u015f\u0131mak istemiyorsan\u0131z i\u015finize yarar. www\u2019yi site i\u00e7in, statik.ornek.com\u2019u statikler i\u00e7in kullan\u0131p cookie kapsam\u0131n\u0131 do\u011fru tasarlayabilirsiniz.<\/p>\n<h2><span id=\"Canonical_Domain_Nedir_ve_Neden_Kritik\">Canonical Domain Nedir ve Neden Kritik?<\/span><\/h2>\n<p><strong>Canonical domain<\/strong>, sitenizin arama motorlar\u0131 ve taray\u0131c\u0131lar g\u00f6z\u00fcnde \u201cresmi\u201d ana adresidir. Temel hedef, \u015fu varyasyonlar\u0131n hepsinin <strong>tek bir adreste birle\u015ftirilmesidir<\/strong>:<\/p>\n<ul>\n<li>http:\/\/ornek.com<\/li>\n<li>http:\/\/www.ornek.com<\/li>\n<li>https:\/\/ornek.com<\/li>\n<li>https:\/\/www.ornek.com<\/li>\n<\/ul>\n<p>Do\u011fru kurulumda kullan\u0131c\u0131 hangi adresi yazarsa yazs\u0131n, saniyenin alt\u0131nda s\u00fcrede <strong>tek, tutarl\u0131 bir URL\u2019ye 301 ile y\u00f6nlendirilmelidir<\/strong>. \u00c7o\u011fu projede bizim tavsiyemiz, <strong>HTTPS zorunlu<\/strong> ve <strong>tek bir host ad\u0131<\/strong> se\u00e7mektir:<\/p>\n<ul>\n<li>Tercih 1: https:\/\/ornek.com<\/li>\n<li>Tercih 2: https:\/\/www.ornek.com<\/li>\n<\/ul>\n<p>SEO taraf\u0131nda canonical kavram\u0131 sadece y\u00f6nlendirmeyle bitmiyor. HTML i\u00e7inde kullan\u0131lan <code>&lt;link rel=\"canonical\"&gt;<\/code> etiketleri de bu resmi adresi teyit eder. Ancak \u00f6ncelik her zaman <strong>301 y\u00f6nlendirmede<\/strong> olmal\u0131, rel=&#8221;canonical&#8221; ise destekleyici bir sinyal olarak d\u00fc\u015f\u00fcn\u00fclmelidir.<\/p>\n<p>URL de\u011fi\u015fiklikleriyle ilgili daha derin bir teknik rehbere ihtiyac\u0131n\u0131z varsa, haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/seo-kaybi-olmadan-url-yapisini-degistirmek-htaccess-ve-nginx-301-yonlendirme-rehberi\/\">SEO kayb\u0131 olmadan URL yap\u0131s\u0131n\u0131 de\u011fi\u015ftirme ve 301 y\u00f6nlendirme rehberi<\/a>ni mutlaka g\u00f6zden ge\u00e7irin.<\/p>\n<h2><span id=\"SEO_Acisindan_www_vs_Ciplak_Alan_Adi\">SEO A\u00e7\u0131s\u0131ndan www vs \u00c7\u0131plak Alan Ad\u0131<\/span><\/h2>\n<p>Arama motorlar\u0131 i\u00e7in kritik olan \u015fey, <strong>tutarl\u0131l\u0131k<\/strong> ve <strong>teklik<\/strong>tir. www ya da non-www se\u00e7iminin tek ba\u015f\u0131na SEO\u2019da \u201cdaha iyi\u201d ya da \u201cdaha k\u00f6t\u00fc\u201d oldu\u011funa dair bir kural yok; as\u0131l \u00f6nemli olan:<\/p>\n<ul>\n<li>T\u00fcm varyasyonlar\u0131n tek bir canonical host\u2019a 301 ile y\u00f6nlendirilmesi<\/li>\n<li>\u0130\u00e7 linklerin, sitemap.xml\u2019in ve canonical etiketlerin bu host ile uyumlu olmas\u0131<\/li>\n<li>Google Search Console ve benzeri ara\u00e7larda <strong>do\u011fru property<\/strong>lerin tan\u0131mlanmas\u0131<\/li>\n<\/ul>\n<h3><span id=\"Yanlis_kurulumun_tipik_sonuclari\">Yanl\u0131\u015f kurulumun tipik sonu\u00e7lar\u0131<\/span><\/h3>\n<p>DCHost\u2019ta s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalar \u015funlar:<\/p>\n<ul>\n<li>www ve non-www varyasyonlar\u0131n\u0131n bazen 301, bazen 302 ile birbirine atlamas\u0131<\/li>\n<li>http \u2192 https y\u00f6nlendirmesinin sadece bir varyasyonda olmas\u0131 (\u00f6rne\u011fin http:\/\/ornek.com y\u00f6nleniyor, ama http:\/\/www.ornek.com y\u00f6nlenmiyor)<\/li>\n<li>Canonical etiketi https:\/\/www.ornek.com iken siteyi https:\/\/ornek.com\u2019a ta\u015f\u0131mak ve g\u00fcncellemeyi unutmak<\/li>\n<li>Alan ad\u0131 de\u011fi\u015fimi s\u0131ras\u0131nda eski domenin www ve non-www varyasyonlar\u0131n\u0131 eksik y\u00f6nlendirmek<\/li>\n<\/ul>\n<p>Sonu\u00e7ta Google taraf\u0131nda \u201cayn\u0131 i\u00e7eri\u011fin farkl\u0131 host isimlerinde farkl\u0131 URL\u2019ler\u201d olarak g\u00f6r\u00fcnmesi, link otoritesinin par\u00e7alanmas\u0131, hatta nadiren de olsa <strong>duplicate content<\/strong> problemlerine yol a\u00e7abiliyor.<\/p>\n<p>Alan ad\u0131 de\u011fi\u015fimi gibi b\u00fcy\u00fck operasyonlara haz\u0131rlan\u0131yorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-degistirirken-seo-kaybetmemek\/\">alan ad\u0131 de\u011fi\u015ftirirken SEO kaybetmemek i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z rehber<\/a> de i\u015finizi ciddi anlamda kolayla\u015ft\u0131racakt\u0131r.<\/p>\n<h2><span id=\"Dogru_301_Yonlendirme_Stratejisi_Tum_Yollar_Tek_Adrese\">Do\u011fru 301 Y\u00f6nlendirme Stratejisi: T\u00fcm Yollar Tek Adrese<\/span><\/h2>\n<p>\u015eimdi i\u015fin en kritik ve pratik k\u0131sm\u0131na gelelim: <strong>hangi adresi se\u00e7erseniz se\u00e7in<\/strong>, di\u011fer t\u00fcm varyasyonlar oraya <strong>kal\u0131c\u0131 (301) y\u00f6nlendirme<\/strong> ile akmal\u0131. \u00d6rnek bir karar:<\/p>\n<ul>\n<li>Canonical domaininiz: <strong>https:\/\/www.ornek.com<\/strong><\/li>\n<\/ul>\n<p>Bu durumda ideal y\u00f6nlendirme matrisi:<\/p>\n<ul>\n<li>http:\/\/ornek.com \u2192 301 \u2192 https:\/\/www.ornek.com<\/li>\n<li>http:\/\/www.ornek.com \u2192 301 \u2192 https:\/\/www.ornek.com<\/li>\n<li>https:\/\/ornek.com \u2192 301 \u2192 https:\/\/www.ornek.com<\/li>\n<\/ul>\n<p>Yani HTTP \u2192 HTTPS, non-www \u2192 www ayn\u0131 anda \u00e7\u00f6z\u00fclmeli, <strong>tek seferde<\/strong> y\u00f6nlendirilmelidir. Kullan\u0131c\u0131 ya da bot, asla 2\u20133 ad\u0131ml\u0131 y\u00f6nlendirme zincirine maruz kalmamal\u0131.<\/p>\n<h3><span id=\"Apache_htaccess_icin_ornek_301_kurallari\">Apache (.htaccess) i\u00e7in \u00f6rnek 301 kurallar\u0131<\/span><\/h3>\n<p>A\u015fa\u011f\u0131daki \u00f6rnek, canonical domain olarak <strong>https:\/\/www.ornek.com<\/strong> se\u00e7ildi\u011fi senaryoya g\u00f6redir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">RewriteEngine On\n\n# HTTP'yi HTTPS'e ve non-www'yi www'ye tek ad\u0131mda y\u00f6nlendir\nRewriteCond %{HTTPS} off [OR]\nRewriteCond %{HTTP_HOST} !^www.ornek.com$ [NC]\nRewriteRule ^(.*)$ https:\/\/www.ornek.com\/$1 [L,R=301]\n<\/code><\/pre>\n<p>Bu kuralla birlikte hem http:\/\/ornek.com hem de http:\/\/www.ornek.com ile https:\/\/ornek.com, do\u011frudan https:\/\/www.ornek.com adresine 301 ile ta\u015f\u0131n\u0131r.<\/p>\n<h3><span id=\"Nginx_icin_ornek_301_kurallari\">Nginx i\u00e7in \u00f6rnek 301 kurallar\u0131<\/span><\/h3>\n<p>Benzer mant\u0131\u011f\u0131 Nginx \u00fczerinde tipik olarak \u015f\u00f6yle uygular\u0131z:<\/p>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\">server {\n    listen 80;\n    server_name ornek.com www.ornek.com;\n    return 301 https:\/\/www.ornek.com$request_uri;\n}\n\nserver {\n    listen 443 ssl http2;\n    server_name ornek.com;\n\n    ssl_certificate     \/etc\/ssl\/certs\/ornek.com.pem;\n    ssl_certificate_key \/etc\/ssl\/private\/ornek.com.key;\n\n    return 301 https:\/\/www.ornek.com$request_uri;\n}\n\nserver {\n    listen 443 ssl http2;\n    server_name www.ornek.com;\n\n    ssl_certificate     \/etc\/ssl\/certs\/ornek.com.pem;\n    ssl_certificate_key \/etc\/ssl\/private\/ornek.com.key;\n\n    # As\u0131l site konfig\u00fcrasyonu burada\n    root \/var\/www\/ornek;\n}\n<\/code><\/pre>\n<p>Burada da HTTP\u2019den gelen t\u00fcm istekler ve HTTPS \u00fczerindeki non-www istekler, tek ad\u0131mda canonical host\u2019a d\u00f6nd\u00fcr\u00fcl\u00fcyor.<\/p>\n<p>Apache ve Nginx taraf\u0131nda daha geli\u015fmi\u015f senaryolar (alt dizin de\u011fi\u015ftirme, dil klas\u00f6r\u00fc yakalama vb.) i\u00e7in, detayl\u0131 kurallar anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/seo-kaybi-olmadan-url-yapisini-degistirmek-htaccess-ve-nginx-301-yonlendirme-rehberi\/\">301 y\u00f6nlendirme rehberimizi<\/a> inceleyebilirsiniz.<\/p>\n<h2><span id=\"HTTPS_HSTS_ve_Canonical_Domain_Iliskisi\">HTTPS, HSTS ve Canonical Domain \u0130li\u015fkisi<\/span><\/h2>\n<p>Art\u0131k HTTP kullanmak pratikte kabul edilebilir de\u011fil; <strong>HTTPS zorunlu<\/strong> kabul ediliyor. Burada devreye <strong>HSTS (HTTP Strict Transport Security)<\/strong> giriyor. HSTS, taray\u0131c\u0131ya \u201cBu domaine <strong>sadece HTTPS \u00fczerinden<\/strong> ba\u011flan, asla HTTP deneme\u201d mesaj\u0131 veren bir HTTP ba\u015fl\u0131\u011f\u0131d\u0131r.<\/p>\n<h3><span id=\"HSTS_nasil_calisir\">HSTS nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/span><\/h3>\n<p>Tipik bir HSTS ba\u015fl\u0131\u011f\u0131 \u015fu \u015fekildedir:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">Strict-Transport-Security: max-age=31536000; includeSubDomains; preload\n<\/code><\/pre>\n<ul>\n<li><strong>max-age=31536000<\/strong> \u2192 1 y\u0131l boyunca bu kural\u0131 hat\u0131rla<\/li>\n<li><strong>includeSubDomains<\/strong> \u2192 T\u00fcm alt alanlarda da sadece HTTPS kullan\u0131laca\u011f\u0131n\u0131 varsay<\/li>\n<li><strong>preload<\/strong> \u2192 Taray\u0131c\u0131lar\u0131n HSTS preload listesine dahil olmak i\u00e7in sinyal<\/li>\n<\/ul>\n<p>Buradaki kritik nokta: HSTS\u2019in etkisi <strong>domain baz\u0131nda<\/strong>d\u0131r. especially <code>includeSubDomains<\/code> ve <code>preload<\/code> kulland\u0131\u011f\u0131n\u0131zda, hem ornek.com hem de www.ornek.com (ve t\u00fcm alt alanlar) geri d\u00f6n\u00fc\u015f\u00fc zor bir \u015fekilde HTTPS\u2019e kilitlenir.<\/p>\n<h3><span id=\"HSTS_acmadan_once_dikkat_edilmesi_gerekenler\">HSTS a\u00e7madan \u00f6nce dikkat edilmesi gerekenler<\/span><\/h3>\n<p>DCHost taraf\u0131nda HSTS\u2019i \u00fcretimde a\u00e7madan \u00f6nce mutlaka \u015fu checklist\u2019i uyguluyoruz:<\/p>\n<ul>\n<li>Hem <strong>ornek.com<\/strong> hem de <strong>www.ornek.com<\/strong> i\u00e7in ge\u00e7erli, hatas\u0131z <a href=\"https:\/\/www.dchost.com\/tr\/ssl\">SSL sertifikas\u0131<\/a><\/li>\n<li>T\u00fcm HTTP isteklerinin kal\u0131c\u0131 301 ile HTTPS\u2019e y\u00f6nlendirilmesi<\/li>\n<li>www \/ non-www canonical karar\u0131 netle\u015fmi\u015f ve her yerde (sitemap, canonical tag, i\u00e7 linkler) uygulanm\u0131\u015f<\/li>\n<li>En az birka\u00e7 hafta boyunca farkl\u0131 taray\u0131c\u0131larda ve cihazlarda test yap\u0131lm\u0131\u015f<\/li>\n<\/ul>\n<p>HSTS ve di\u011fer HTTP g\u00fcvenlik ba\u015fl\u0131klar\u0131n\u0131 daha derinlemesine ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/http-guvenlik-basliklari-rehberi-hsts-csp-x-frame-options-ve-referrer-policy-dogru-nasil-kurulur\/\">HTTP g\u00fcvenlik ba\u015fl\u0131klar\u0131 rehberimiz<\/a> de \u00f6zellikle teknik ekibiniz i\u00e7in olduk\u00e7a faydal\u0131 olacakt\u0131r. Ayr\u0131ca s\u0131rf HTTP\u2192HTTPS ge\u00e7i\u015f s\u00fcreci i\u00e7in ad\u0131m ad\u0131m haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/httpden-httpse-gecis-rehberi-301-yonlendirme-hsts-ve-seoyu-korumak\/\">HTTP&#8217;den HTTPS&#8217;e ge\u00e7i\u015f rehberinde<\/a> de HSTS ve 301 etkile\u015fimini detayl\u0131 olarak anlatt\u0131k.<\/p>\n<h2><span id=\"Farkli_Senaryolar_Icin_www_Non-www_Karar_Rehberi\">Farkl\u0131 Senaryolar \u0130\u00e7in www \/ Non-www Karar Rehberi<\/span><\/h2>\n<p>\u015eimdi i\u015fin teorisini pratik senaryolara d\u00f6kelim. Hangi durumda hangi se\u00e7imi \u00f6neriyoruz?<\/p>\n<h3><span id=\"1_Yeni_kurulan_kurumsal_site_blog\">1. Yeni kurulan kurumsal site \/ blog<\/span><\/h3>\n<p>Yeni bir site kuruyorsan\u0131z ve \u00f6zel bir teknik gereksiniminiz yoksa iki yol da ge\u00e7erli:<\/p>\n<ul>\n<li>Marka sade g\u00f6r\u00fcn\u00fcm seviyorsan\u0131z: canonical \u2192 https:\/\/ornek.com<\/li>\n<li>\u0130leride CDN, WAF, \u00e7oklu alt alan gibi planlar\u0131n\u0131z varsa: canonical \u2192 https:\/\/www.ornek.com<\/li>\n<\/ul>\n<p>\u00d6nemli olan, <strong>karar\u0131 en ba\u015fta verip bir daha de\u011fi\u015ftirmemek<\/strong>. Hosting taraf\u0131nda domain kurulumunu yaparken, DCHost panelinizde ekledi\u011finiz alan ad\u0131n\u0131n www ve non-www varyasyonlar\u0131n\u0131 ayn\u0131 dizine i\u015faret edecek \u015fekilde ayarlay\u0131n ve az \u00f6nceki 301 senaryosunu uygulay\u0131n.<\/p>\n<h3><span id=\"2_CDN_ve_coklu_alt_alan_kullanilan_projeler\">2. CDN ve \u00e7oklu alt alan kullan\u0131lan projeler<\/span><\/h3>\n<p>E\u011fer:<\/p>\n<ul>\n<li>statik.ornek.com veya cdn.ornek.com gibi alt alanlardan statik dosya servis edecekseniz,<\/li>\n<li>api.ornek.com, panel.ornek.com gibi ayr\u0131 uygulamalar\u0131n\u0131z varsa,<\/li>\n<li>\u0130leride <strong>\u00e7ok b\u00f6lgeli DNS ve CDN<\/strong> senaryolar\u0131na gitmeyi d\u00fc\u015f\u00fcn\u00fcyorsan\u0131z,<\/li>\n<\/ul>\n<p>Bu tip yap\u0131larda www canonical kullanmak genellikle daha esnektir. \u00c7\u00fcnk\u00fc:<\/p>\n<ul>\n<li>www.ornek.com\u2019u CDN veya reverse proxy arkas\u0131na almak kolayd\u0131r (CNAME ile)<\/li>\n<li>ornek.com\u2019u sadece www\u2019ye y\u00f6nlendiren minimal bir layer olarak tutabilirsiniz<\/li>\n<\/ul>\n<p>Global \u00f6l\u00e7ekli projelerde <a href=\"https:\/\/www.dchost.com\/blog\/geodns-ve-cok-bolgeli-hosting-mimarisi-ile-global-ziyaretcilere-yakinlasmak\/\">GeoDNS ve \u00e7ok b\u00f6lgeli hosting mimarisi<\/a> gibi \u00e7\u00f6z\u00fcmleri d\u00fc\u015f\u00fcn\u00fcyorsan\u0131z, domain mimarinizi en ba\u015ftan bu esnekli\u011fe g\u00f6re tasarlamak b\u00fcy\u00fck avantaj sa\u011flar.<\/p>\n<h3><span id=\"3_Halihazirda_index_almis_yillardir_yayinda_olan_site\">3. Halihaz\u0131rda index alm\u0131\u015f, y\u0131llard\u0131r yay\u0131nda olan site<\/span><\/h3>\n<p>E\u011fer siteniz 3\u20135 y\u0131ld\u0131r yay\u0131ndaysa ve Google\u2019da y\u00fczlerce \/ binlerce sayfa index ald\u0131ysa, <strong>en iyi se\u00e7im genellikle \u015fu anki durumu korumakt\u0131r<\/strong>. Yani:<\/p>\n<ul>\n<li>Bug\u00fcn Google\u2019da sayfalar\u0131n\u0131z a\u011f\u0131rl\u0131kl\u0131 olarak https:\/\/www.ornek.com\/&#8230; \u015feklindeyse, canonical olarak www\u2019yi b\u0131rak\u0131n.<\/li>\n<li>Non-www a\u011f\u0131rl\u0131kl\u0131ysa, canonical\u2019\u0131 non-www korumak daha az risklidir.<\/li>\n<\/ul>\n<p>Bu durumda yap\u0131lacak i\u015f, mevcut se\u00e7imi <strong>sertle\u015ftirip netle\u015ftirmektir<\/strong>:<\/p>\n<ul>\n<li>T\u00fcm HTTP varyasyonlar\u0131n\u0131 do\u011fru 301 ile canonical\u2019a ta\u015f\u0131mak<\/li>\n<li>Canonical etiketleri ve sitemap\u2019i g\u00fcncellemek<\/li>\n<li>HSTS ve g\u00fcvenlik ba\u015fl\u0131klar\u0131n\u0131 d\u00fczg\u00fcnce eklemek<\/li>\n<\/ul>\n<p>Yeni markaya ge\u00e7i\u015f gibi daha radikal operasyonlarda ise, hem eski hem yeni alan adlar\u0131n\u0131 kapsayan bir strateji gerekir. Bunun i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/marka-degisiminde-alan-adi-tasima-seo-ve-e-postayi-korumak\/\">marka de\u011fi\u015fiminde alan ad\u0131 ta\u015f\u0131ma rehberimizi<\/a> izlemeniz, SEO ve e-posta taraf\u0131nda riskleri ciddi bi\u00e7imde azalt\u0131r.<\/p>\n<h2><span id=\"cPanel_Paylasimli_Hosting_ve_VPSDedicated_Ortamlarinda_Uygulama\">cPanel, Payla\u015f\u0131ml\u0131 Hosting ve VPS\/Dedicated Ortamlar\u0131nda Uygulama<\/span><\/h2>\n<h3><span id=\"cPanel_Paylasimli_Hostingte_pratik_kurulum\">cPanel \/ Payla\u015f\u0131ml\u0131 Hosting\u2019te pratik kurulum<\/span><\/h3>\n<p>DCHost payla\u015f\u0131ml\u0131 hosting paketlerinde tipik ak\u0131\u015f \u015fu \u015fekilde olur:<\/p>\n<ol>\n<li>Alan ad\u0131n\u0131 ana hesap domaini olarak ekleyin.<\/li>\n<li>SSL\u2019yi (Let\u2019s Encrypt veya \u00fccretli sertifika) hem ornek.com hem de www.ornek.com i\u00e7in etkinle\u015ftirin.<\/li>\n<li>cPanel i\u00e7indeki \u201cY\u00f6nlendirmeler\u201d b\u00f6l\u00fcm\u00fcnden, non-www \u2192 www (veya tersi) 301 y\u00f6nlendirmesini tan\u0131mlay\u0131n.<\/li>\n<li>Gerekirse .htaccess i\u00e7ine az \u00f6nce verdi\u011fimiz daha kapsaml\u0131 kurallar\u0131 ekleyin.<\/li>\n<\/ol>\n<p>Bu a\u015famada Google Search Console\u2019a do\u011fru host varyasyonunu eklemeyi, sitemap.xml i\u00e7erisinde de canonical domaini kullanmay\u0131 unutmay\u0131n. E\u011fer web hosting kavramlar\u0131na yeniyseniz, <a href=\"https:\/\/www.dchost.com\/blog\/web-hosting-nedir-domain-dns-sunucu-ve-ssl-nasil-birlikte-calisir\/\">domain, DNS, sunucu ve SSL\u2019in birlikte nas\u0131l \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z rehber<\/a> akl\u0131n\u0131zdaki bir\u00e7ok temel soruyu temizleyecektir.<\/p>\n<h3><span id=\"VPS_dedicated_sunucularda_manuel_konfigurasyon\">VPS \/ <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a>larda manuel konfig\u00fcrasyon<\/span><\/h3>\n<p>VPS veya dedicated bir sunucuda \u00e7al\u0131\u015f\u0131yorsan\u0131z, web sunucunuzu (Nginx, Apache, LiteSpeed vb.) bizzat siz yap\u0131land\u0131r\u0131yorsunuz demektir. Bu durumda:<\/p>\n<ul>\n<li>T\u00fcm server block \/ virtual host tan\u0131mlar\u0131n\u0131 g\u00f6zden ge\u00e7irin<\/li>\n<li>HTTP (80) portundaki t\u00fcm domain varyasyonlar\u0131n\u0131 <strong>tek bir HTTPS host\u2019a<\/strong> 301 ile y\u00f6nlendirin<\/li>\n<li>HTTPS host\u2019lar i\u00e7inde de non-www \u2192 www (veya tersini) net bir kuralla sabitleyin<\/li>\n<li>HSTS, HTTPS redirect ve canonical domainin \u00e7eli\u015fmedi\u011finden emin olun<\/li>\n<\/ul>\n<p>Yeni bir VPS ald\u0131ysan\u0131z ve hen\u00fcz ba\u015flang\u0131\u00e7taysan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/yeni-vpste-ilk-24-saat-guncelleme-guvenlik-duvari-ve-kullanici-hesaplari\/\">yeni VPS\u2019te ilk 24 saatte neler yap\u0131lmal\u0131<\/a> rehberimizde g\u00fcvenlik ve temel ayarlar\u0131; <a href=\"https:\/\/www.dchost.com\/blog\/vps-sunucu-guvenligi-pratik-olceklenebilir-ve-dogrulanabilir-yaklasimlar\/\">VPS sunucu g\u00fcvenli\u011fi rehberimizde<\/a> ise daha ileri seviye koruma ad\u0131mlar\u0131n\u0131 bulabilirsiniz.<\/p>\n<h2><span id=\"Sik_Yapilan_Hatalar_ve_Kisa_Kontrol_Listesi\">S\u0131k Yap\u0131lan Hatalar ve K\u0131sa Kontrol Listesi<\/span><\/h2>\n<h3><span id=\"En_sik_gordugumuz_hatalar\">En s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalar<\/span><\/h3>\n<ul>\n<li><strong>301 yerine 302\/307 kullanmak:<\/strong> Ge\u00e7ici y\u00f6nlendirme kodlar\u0131 (302, 307) uzun vadede canonical sinyalini zay\u0131flatabilir.<\/li>\n<li><strong>Y\u00f6nlendirme zinciri olu\u015fturmak:<\/strong> http:\/\/ornek.com \u2192 http:\/\/www.ornek.com \u2192 https:\/\/www.ornek.com gibi iki ad\u0131ml\u0131 y\u00f6nlendirmeler TTFB\u2019yi uzat\u0131r, SEO ve performans\u0131 olumsuz etkiler.<\/li>\n<li><strong>HSTS\u2019i erken a\u00e7mak:<\/strong> SSL veya y\u00f6nlendirme problemleri devam ederken HSTS + preload devreye almak, kullan\u0131c\u0131lar\u0131 geri d\u00f6nd\u00fcrmesi zor hatalarla kar\u015f\u0131 kar\u015f\u0131ya b\u0131rakabilir.<\/li>\n<li><strong>Canonical\/URL de\u011fi\u015fimini par\u00e7a par\u00e7a yapmak:<\/strong> Bir g\u00fcn y\u00f6nlendirme, bir g\u00fcn sitemap, bir hafta sonra canonical tag de\u011fi\u015ftirmek yerine planl\u0131 ve tek seferde de\u011fi\u015fiklik yapmak gerekir.<\/li>\n<li><strong>\u0130kincil alan adlar\u0131n\u0131 unutmuk:<\/strong> .com.tr, .net, eski marka domaini gibi alanlar\u0131n da www\/non-www varyasyonlar\u0131n\u0131n eksiksiz 301 ile yeni canonical\u2019a ta\u015f\u0131nmas\u0131 gerekir.<\/li>\n<\/ul>\n<p>Birden fazla alan ad\u0131n\u0131 ayn\u0131 siteye y\u00f6nlendirme konusunu daha derinlemesine ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/birden-fazla-alan-adini-ayni-siteye-yonlendirmek-seo-301-canonical-ve-park-alan-adi-stratejileri\/\">park alan ad\u0131, 301 ve canonical stratejileri rehberine<\/a> de mutlaka g\u00f6z atman\u0131z\u0131 \u00f6neririz.<\/p>\n<h3><span id=\"Hizli_kontrol_listesi\">H\u0131zl\u0131 kontrol listesi<\/span><\/h3>\n<p>A\u015fa\u011f\u0131daki listeyi, canl\u0131ya \u00e7\u0131kmadan \u00f6nce veya mevcut siteyi iyile\u015ftirirken checklist olarak kullanabilirsiniz:<\/p>\n<ul>\n<li>Canonical domain karar\u0131 net mi? (https:\/\/ornek.com veya https:\/\/www.ornek.com)<\/li>\n<li>http:\/\/ornek.com \u2192 tek ad\u0131mda canonical\u2019a 301 ile gidiyor mu?<\/li>\n<li>http:\/\/www.ornek.com \u2192 tek ad\u0131mda canonical\u2019a 301 ile gidiyor mu?<\/li>\n<li>https:\/\/ornek.com \u2192 tek ad\u0131mda canonical\u2019a 301 ile gidiyor mu?<\/li>\n<li>HTML &lt;head&gt; i\u00e7inde rel=&#8221;canonical&#8221; etiketi canonical domain ile uyumlu mu?<\/li>\n<li>sitemap.xml i\u00e7inde t\u00fcm URL\u2019ler canonical domain ile mi ba\u015fl\u0131yor?<\/li>\n<li>Google Search Console\u2019da do\u011fru host varyasyonu tan\u0131ml\u0131 m\u0131?<\/li>\n<li>SSL sertifikas\u0131 hem ornek.com hem www.ornek.com i\u00e7in ge\u00e7erli mi?<\/li>\n<li>HSTS kullan\u0131yorsan\u0131z, y\u00f6nlendirme ve sertifikalar tam olarak sorunsuz mu?<\/li>\n<\/ul>\n<p>HTTP durum kodlar\u0131n\u0131n SEO etkisini ve 301\/302 farklar\u0131n\u0131 daha iyi anlamak istiyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/http-durum-kodlari-seo-ve-hosting-icin-301-302-404-410-ve-5xx-rehberi\/\">HTTP durum kodlar\u0131 ve SEO rehberi<\/a> de g\u00fczel bir tamamlay\u0131c\u0131 kaynak olacakt\u0131r.<\/p>\n<h2><span id=\"Ozet_ve_DCHost_Tarafinda_Nasil_Yardimci_Oluyoruz\">\u00d6zet ve DCHost Taraf\u0131nda Nas\u0131l Yard\u0131mc\u0131 Oluyoruz?<\/span><\/h2>\n<p>www mi yoksa \u00e7\u0131plak alan ad\u0131 m\u0131 sorusunun tek bir do\u011fru cevab\u0131 yok; ama <strong>her senaryo i\u00e7in de\u011fi\u015fmeyen iki kural<\/strong> var: <strong>tutarl\u0131l\u0131k<\/strong> ve <strong>basitlik<\/strong>. \u00d6nce markan\u0131za ve teknik mimarinize uygun bir canonical host se\u00e7in, ard\u0131ndan t\u00fcm HTTP\/HTTPS, www\/non-www varyasyonlar\u0131n\u0131 bu adrese tek ad\u0131mda 301 ile toplay\u0131n. Sonra SSL ve HSTS ile bu karar\u0131 g\u00fcvence alt\u0131na al\u0131n; sitemap, canonical etiketleri ve Search Console ayarlar\u0131yla da arama motorlar\u0131na net bir sinyal verin.<\/p>\n<p>DCHost olarak payla\u015f\u0131ml\u0131 hosting, VPS, dedicated sunucu ve colocation altyap\u0131m\u0131zda, g\u00fcnl\u00fck operasyonlarda en \u00e7ok dokundu\u011fumuz alanlardan biri tam da bu domain ve y\u00f6nlendirme katman\u0131. \u0130ster yeni bir proje ba\u015flat\u0131yor olun, ister y\u0131llard\u0131r \u00e7al\u0131\u015fan bir siteyi ta\u015f\u0131yor olun; <strong>do\u011fru canonical domain, 301 ve HSTS<\/strong> ayarlar\u0131yla hem SEO taraf\u0131nda hem de kullan\u0131c\u0131 deneyiminde uzun vadeli bir rahatl\u0131k sa\u011flamak m\u00fcmk\u00fcn. Mevcut sitenizi g\u00f6zden ge\u00e7irmek isterseniz, yukar\u0131daki checklist\u2019i uygulay\u0131n; tak\u0131ld\u0131\u011f\u0131n\u0131z bir noktada ise DCHost destek ekibine konfig\u00fcrasyon detaylar\u0131yla birlikte ula\u015fman\u0131z yeterli.<\/p>\n<p>Do\u011fru ayarlanm\u0131\u015f bir alan ad\u0131 ve y\u00f6nlendirme katman\u0131; g\u00fc\u00e7l\u00fc bir altyap\u0131, sa\u011fl\u0131kl\u0131 DNS ve g\u00fcvenli HTTPS \u00fc\u00e7l\u00fcs\u00fcn\u00fcn olmazsa olmaz tamamlay\u0131c\u0131s\u0131d\u0131r. Bu katman\u0131 bir kere temiz kurdu\u011funuzda, y\u0131llarca tekrar d\u00fc\u015f\u00fcnmek zorunda kalmazs\u0131n\u0131z.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 www mi \u00c7\u0131plak Alan Ad\u0131 m\u0131? As\u0131l Sorun Sand\u0131\u011f\u0131n\u0131zdan Farkl\u01312 www ve \u00c7\u0131plak Alan Ad\u0131 Aras\u0131ndaki Ger\u00e7ek Fark Nedir?2.1 DNS taraf\u0131nda farklar2.2 Taray\u0131c\u0131 ve cookie davran\u0131\u015f\u01313 Canonical Domain Nedir ve Neden Kritik?4 SEO A\u00e7\u0131s\u0131ndan www vs \u00c7\u0131plak Alan Ad\u01314.1 Yanl\u0131\u015f kurulumun tipik sonu\u00e7lar\u01315 Do\u011fru 301 Y\u00f6nlendirme Stratejisi: T\u00fcm Yollar Tek Adrese5.1 Apache (.htaccess) i\u00e7in [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4056,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4055","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-teknoloji"],"_links":{"self":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4055","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/comments?post=4055"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4055\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4056"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4055"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4055"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4055"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}