{"id":4590,"date":"2026-02-06T14:09:11","date_gmt":"2026-02-06T11:09:11","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/httpden-httpsye-gecis-rehberi-seo-kayipsiz-ssl-migrasyonu-hsts-ve-canonical-ayarlari\/"},"modified":"2026-02-06T14:09:11","modified_gmt":"2026-02-06T11:09:11","slug":"httpden-httpsye-gecis-rehberi-seo-kayipsiz-ssl-migrasyonu-hsts-ve-canonical-ayarlari","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/httpden-httpsye-gecis-rehberi-seo-kayipsiz-ssl-migrasyonu-hsts-ve-canonical-ayarlari\/","title":{"rendered":"HTTP&#8217;den HTTPS&#8217;ye Ge\u00e7i\u015f Rehberi: SEO Kay\u0131ps\u0131z SSL Migrasyonu, HSTS ve Canonical Ayarlar\u0131"},"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=\"#HTTPS8217e_Gecis_Neden_Sadece_Guvenlik_Degil_Stratejik_Bir_SEO_Karari\"><span class=\"toc_number toc_depth_1\">1<\/span> HTTPS&#8217;e Ge\u00e7i\u015f Neden Sadece G\u00fcvenlik De\u011fil, Stratejik Bir SEO Karar\u0131?<\/a><\/li><li><a href=\"#Gecis_Oncesi_Hazirlik_Envanter_Mimari_ve_Planlama\"><span class=\"toc_number toc_depth_1\">2<\/span> Ge\u00e7i\u015f \u00d6ncesi Haz\u0131rl\u0131k: Envanter, Mimari ve Planlama<\/a><ul><li><a href=\"#1_Mevcut_URL_ve_alan_adi_mimarinizi_netlestirin\"><span class=\"toc_number toc_depth_2\">2.1<\/span> 1. Mevcut URL ve alan ad\u0131 mimarinizi netle\u015ftirin<\/a><\/li><li><a href=\"#2_SEO_risk_analizi_yapin\"><span class=\"toc_number toc_depth_2\">2.2<\/span> 2. SEO risk analizi yap\u0131n<\/a><\/li><li><a href=\"#3_Dogru_SSL_sertifikasini_secin\"><span class=\"toc_number toc_depth_2\">2.3<\/span> 3. Do\u011fru SSL sertifikas\u0131n\u0131 se\u00e7in<\/a><\/li><\/ul><\/li><li><a href=\"#SSL_Kurulumu_ve_Test_Sunucu_Tarafinda_Yapilmasi_Gerekenler\"><span class=\"toc_number toc_depth_1\">3<\/span> SSL Kurulumu ve Test: Sunucu Taraf\u0131nda Yap\u0131lmas\u0131 Gerekenler<\/a><ul><li><a href=\"#1_DNS_ve_hosting_tarafi_onkontroller\"><span class=\"toc_number toc_depth_2\">3.1<\/span> 1. DNS ve hosting taraf\u0131 \u00f6nkontroller<\/a><\/li><li><a href=\"#2_Sunucuya_SSL_sertifikasi_kurma\"><span class=\"toc_number toc_depth_2\">3.2<\/span> 2. Sunucuya SSL sertifikas\u0131 kurma<\/a><\/li><li><a href=\"#3_Mixed_content_ve_guvensiz_icerik_testleri\"><span class=\"toc_number toc_depth_2\">3.3<\/span> 3. Mixed content ve g\u00fcvensiz i\u00e7erik testleri<\/a><\/li><\/ul><\/li><li><a href=\"#SEO_Kayipsiz_Gecis_Icin_301_Yonlendirme_ve_Canonical_Stratejisi\"><span class=\"toc_number toc_depth_1\">4<\/span> SEO Kay\u0131ps\u0131z Ge\u00e7i\u015f \u0130\u00e7in 301 Y\u00f6nlendirme ve Canonical Stratejisi<\/a><ul><li><a href=\"#1_Tek_bir_canonical_domain_secin\"><span class=\"toc_number toc_depth_2\">4.1<\/span> 1. Tek bir canonical domain se\u00e7in<\/a><\/li><li><a href=\"#2_HTTP_HTTPS_301_yonlendirme_kurallari\"><span class=\"toc_number toc_depth_2\">4.2<\/span> 2. HTTP \u2192 HTTPS 301 y\u00f6nlendirme kurallar\u0131<\/a><\/li><li><a href=\"#3_Canonical_etiketlerini_guncellemek\"><span class=\"toc_number toc_depth_2\">4.3<\/span> 3. Canonical etiketlerini g\u00fcncellemek<\/a><\/li><li><a href=\"#4_Sitemap_robotstxt_ve_dahili_linkler\"><span class=\"toc_number toc_depth_2\">4.4<\/span> 4. Sitemap, robots.txt ve dahili linkler<\/a><\/li><\/ul><\/li><li><a href=\"#HSTS_Preload_ve_HTTP_Guvenlik_Basliklari\"><span class=\"toc_number toc_depth_1\">5<\/span> HSTS, Preload ve HTTP G\u00fcvenlik Ba\u015fl\u0131klar\u0131<\/a><ul><li><a href=\"#1_HSTS_nedir_ne_ise_yarar\"><span class=\"toc_number toc_depth_2\">5.1<\/span> 1. HSTS nedir, ne i\u015fe yarar?<\/a><\/li><li><a href=\"#2_HSTS_basligini_nasil_eklersiniz\"><span class=\"toc_number toc_depth_2\">5.2<\/span> 2. HSTS ba\u015fl\u0131\u011f\u0131n\u0131 nas\u0131l eklersiniz?<\/a><\/li><li><a href=\"#3_HSTS_Preload_ne_zaman_mantikli\"><span class=\"toc_number toc_depth_2\">5.3<\/span> 3. HSTS Preload ne zaman mant\u0131kl\u0131?<\/a><\/li><\/ul><\/li><li><a href=\"#Test_Yayina_Alma_ve_Izleme_Stratejisi\"><span class=\"toc_number toc_depth_1\">6<\/span> Test, Yay\u0131na Alma ve \u0130zleme Stratejisi<\/a><ul><li><a href=\"#1_Staging_ortaminda_HTTPS_gecis_provasini_yapin\"><span class=\"toc_number toc_depth_2\">6.1<\/span> 1. Staging ortam\u0131nda HTTPS ge\u00e7i\u015f provas\u0131n\u0131 yap\u0131n<\/a><\/li><li><a href=\"#2_Search_Console_Analytics_ve_sitemap_guncellemeleri\"><span class=\"toc_number toc_depth_2\">6.2<\/span> 2. Search Console, Analytics ve sitemap g\u00fcncellemeleri<\/a><\/li><li><a href=\"#3_Sunucu_loglari_ve_hata_izleme\"><span class=\"toc_number toc_depth_2\">6.3<\/span> 3. Sunucu loglar\u0131 ve hata izleme<\/a><\/li><\/ul><\/li><li><a href=\"#DCHost_Musteri_Senaryolarindan_Ogrendiklerimiz\"><span class=\"toc_number toc_depth_1\">7<\/span> DCHost M\u00fc\u015fteri Senaryolar\u0131ndan \u00d6\u011frendiklerimiz<\/a><ul><li><a href=\"#1_KOBI_e-ticaret_sitesinde_HTTPS_gecisi_ve_sepet_donusum_orani\"><span class=\"toc_number toc_depth_2\">7.1<\/span> 1. KOB\u0130 e-ticaret sitesinde HTTPS ge\u00e7i\u015fi ve sepet d\u00f6n\u00fc\u015f\u00fcm oran\u0131<\/a><\/li><li><a href=\"#2_Kurumsal_B2B_sitede_HSTS_ve_preload_stratejisi\"><span class=\"toc_number toc_depth_2\">7.2<\/span> 2. Kurumsal B2B sitede HSTS ve preload stratejisi<\/a><\/li><\/ul><\/li><li><a href=\"#Sonuc_ve_DCHost_ile_Guvenli_HTTPS_Mimarisi\"><span class=\"toc_number toc_depth_1\">8<\/span> Sonu\u00e7 ve DCHost ile G\u00fcvenli HTTPS Mimarisi<\/a><\/li><\/ul><\/div>\n<h2><span id=\"HTTPS8217e_Gecis_Neden_Sadece_Guvenlik_Degil_Stratejik_Bir_SEO_Karari\">HTTPS&#8217;e Ge\u00e7i\u015f Neden Sadece G\u00fcvenlik De\u011fil, Stratejik Bir SEO Karar\u0131?<\/span><\/h2>\n<p>Art\u0131k modern taray\u0131c\u0131lar\u0131n neredeyse tamam\u0131 HTTP siteleri \u201cG\u00fcvenli de\u011fil\u201d olarak i\u015faretliyor, bir\u00e7ok kullan\u0131c\u0131 kredi kart\u0131 bile girmedi\u011fi kurumsal sitelerde dahi bu uyar\u0131dan rahats\u0131z olarak sayfay\u0131 terk ediyor. Ayn\u0131 anda arama motorlar\u0131 da HTTPS\u2019i uzun s\u00fcredir bir s\u0131ralama sinyali olarak kullan\u0131yor. Dolay\u0131s\u0131yla HTTP\u2019den HTTPS\u2019ye ge\u00e7i\u015f bug\u00fcn teknik bir ayr\u0131nt\u0131 de\u011fil, do\u011frudan gelir ve marka alg\u0131s\u0131 etkisi olan stratejik bir karar.<\/p>\n<p>Bu ge\u00e7i\u015fi yanl\u0131\u015f planlad\u0131\u011f\u0131n\u0131zda; k\u0131r\u0131k y\u00f6nlendirmeler, yanl\u0131\u015f canonical etiketleri, hatal\u0131 HSTS kullan\u0131m\u0131 ve mixed content sorunlar\u0131 nedeniyle hem SEO hem d\u00f6n\u00fc\u015f\u00fcm taraf\u0131nda ciddi kay\u0131plar ya\u015fayabilirsiniz. DCHost ekibi olarak onlarca HTTPS ge\u00e7i\u015finde g\u00f6rd\u00fc\u011f\u00fcm\u00fcz tipik hatalar\u0131 ve en iyi uygulamalar\u0131 bu rehberde toplad\u0131k. Ad\u0131m ad\u0131m ilerleyerek; SSL kurulumu, 301 y\u00f6nlendirme, HSTS, canonical ve Search Console ayarlar\u0131n\u0131 do\u011fru kurgulad\u0131\u011f\u0131n\u0131zda HTTP \u2192 HTTPS migrasyonunu neredeyse s\u0131f\u0131r SEO kayb\u0131yla tamamlayabilirsiniz.<\/p>\n<p>HTTP \u2192 HTTPS konusunda daha temel bir bak\u0131\u015f ar\u0131yorsan\u0131z, bu yaz\u0131y\u0131 okuduktan sonra <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 ad\u0131mlar\u0131n\u0131 \u00f6zetledi\u011fimiz rehberimize<\/a> de g\u00f6z atabilirsiniz.<\/p>\n<h2><span id=\"Gecis_Oncesi_Hazirlik_Envanter_Mimari_ve_Planlama\">Ge\u00e7i\u015f \u00d6ncesi Haz\u0131rl\u0131k: Envanter, Mimari ve Planlama<\/span><\/h2>\n<h3><span id=\"1_Mevcut_URL_ve_alan_adi_mimarinizi_netlestirin\">1. Mevcut URL ve alan ad\u0131 mimarinizi netle\u015ftirin<\/span><\/h3>\n<p>Ba\u015far\u0131l\u0131 bir HTTPS migrasyonunun ilk ad\u0131m\u0131, neleri ta\u015f\u0131d\u0131\u011f\u0131n\u0131z\u0131 tam olarak bilmek. \u015eu sorular\u0131n cevaplar\u0131n\u0131 mutlaka yaz\u0131l\u0131 hale getirin:<\/p>\n<ul>\n<li>Site i\u00e7in resmi (canonical) alan ad\u0131n\u0131z hangisi? <code>www.ornek.com<\/code> mu, yoksa <code>ornek.com<\/code> mu?<\/li>\n<li>Park etti\u011finiz veya y\u00f6nlendirdi\u011finiz ba\u015fka alan adlar\u0131 var m\u0131? (\u00f6rn. <code>orneksite.com<\/code> \u2192 <code>ornek.com<\/code>)<\/li>\n<li>Blog, ma\u011faza, panel gibi subdomain\u2019leriniz var m\u0131? (\u00f6rn. <code>blog.ornek.com<\/code>, <code>shop.ornek.com<\/code>)<\/li>\n<li>Statik i\u00e7erik veya CDN i\u00e7in ayr\u0131 bir alan ad\u0131n\u0131z var m\u0131? (\u00f6rn. <code>static.ornek.com<\/code>)<\/li>\n<\/ul>\n<p>Bu mimariyi d\u00fczg\u00fcn kurmak i\u00e7in daha \u00f6nce detayl\u0131 anlatt\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/www-mi-ciplak-alan-adi-mi-canonical-domain-301-ve-hsts-icin-dogru-ayarlar\/\">www mi \u00e7\u0131plak alan ad\u0131 m\u0131 tercih etmeniz gerekti\u011fini anlatan canonical domain rehberimizi<\/a> mutlaka okuman\u0131z\u0131 \u00f6neririz. Ayr\u0131ca birden fazla domain kullan\u0131yorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/birden-fazla-alan-adini-ayni-siteye-yonlendirmek-seo-301-canonical-ve-park-alan-adi-stratejileri\/\">birden fazla alan ad\u0131n\u0131 ayn\u0131 siteye y\u00f6nlendirme ve park domain stratejileri<\/a> yaz\u0131m\u0131z da i\u015finize yarayacakt\u0131r.<\/p>\n<h3><span id=\"2_SEO_risk_analizi_yapin\">2. SEO risk analizi yap\u0131n<\/span><\/h3>\n<p>HTTPS ge\u00e7i\u015fi teknik olarak \u201csite \u00e7ap\u0131nda URL de\u011fi\u015fikli\u011fi\u201d demektir. Yani Google\u2019\u0131n g\u00f6z\u00fcnde t\u00fcm sayfalar\u0131n\u0131z yeni bir adrese ta\u015f\u0131n\u0131yor. Bu nedenle:<\/p>\n<ul>\n<li>En \u00e7ok trafik alan ilk 100\u2013500 URL\u2019i listeleyin.<\/li>\n<li>Backlink gelen \u00f6nemli sayfalar\u0131 belirleyin.<\/li>\n<li>\u00d6zel kampanya, landing page ve \u00f6deme sayfalar\u0131n\u0131 ayr\u0131 not edin.<\/li>\n<\/ul>\n<p>Hedefiniz, bu sayfalar i\u00e7in <strong>1:1 bire bir 301 y\u00f6nlendirme<\/strong> sa\u011flamakt\u0131r. Genel bir \u201cher \u015feyi anasayfaya at\u201d kural\u0131, SEO a\u00e7\u0131s\u0131ndan b\u00fcy\u00fck kay\u0131plara yol a\u00e7ar. E\u011fer yak\u0131n zamanda alan ad\u0131 de\u011fi\u015fimi de yapmay\u0131 planl\u0131yorsan\u0131z, bunu tek seferde (HTTP \u2192 HTTPS ve eski domain \u2192 yeni domain) yapmak gerekir. Bu konuda detayl\u0131 bir perspektif i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/alan-adi-degistirirken-seo-kaybetmemek\/\">alan ad\u0131 de\u011fi\u015ftirirken SEO kayb\u0131n\u0131 \u00f6nleme rehberimizi<\/a> inceleyebilirsiniz.<\/p>\n<h3><span id=\"3_Dogru_SSL_sertifikasini_secin\">3. Do\u011fru <a href=\"https:\/\/www.dchost.com\/tr\/ssl\">SSL sertifikas\u0131<\/a>n\u0131 se\u00e7in<\/span><\/h3>\n<p>Tek domainli basit bir kurumsal siteden, onlarca subdomain kullanan SaaS uygulamas\u0131na kadar farkl\u0131 senaryolar i\u00e7in uygun sertifika t\u00fcr\u00fc de\u011fi\u015fir. K\u0131sa \u00f6zet:<\/p>\n<ul>\n<li><strong>DV (Domain Validation)<\/strong>: En yayg\u0131n, h\u0131zl\u0131 ve otomatik al\u0131nabilen sertifika t\u00fcr\u00fc. \u00c7o\u011fu blog, i\u00e7erik sitesi ve KOB\u0130 i\u00e7in yeterli.<\/li>\n<li><strong>OV (Organization Validation)<\/strong>: Organizasyon bilgisi do\u011frulan\u0131r, B2B kurumsal sitelerde tercih edilir.<\/li>\n<li><strong>EV (Extended Validation)<\/strong>: Daha kapsaml\u0131 \u015firket do\u011frulamas\u0131; y\u00fcksek reg\u00fclasyonlu alanlarda (finans, hukuk, sa\u011fl\u0131k) mant\u0131kl\u0131 olabilir.<\/li>\n<li><strong>Wildcard<\/strong>: <code>*.ornek.com<\/code> gibi, t\u00fcm subdomain\u2019leri kapsar.<\/li>\n<li><strong>SAN \/ Multi-domain<\/strong>: Birden \u00e7ok farkl\u0131 alan ad\u0131n\u0131 tek sertifikada toplar.<\/li>\n<\/ul>\n<p>Bu kararlar\u0131 daha sa\u011flam verebilmek i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/dv-ov-ve-ev-ssl-sertifikalari-arasindaki-farklar-kurumsal-ve-e-ticaret-siteleri-icin-yol-haritasi\/\">DV, OV ve EV SSL sertifikalar\u0131 aras\u0131ndaki farklar\u0131 anlatt\u0131\u011f\u0131m\u0131z detayl\u0131 yaz\u0131m\u0131za<\/a> ve B2B yap\u0131lar i\u00e7in haz\u0131rlad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/b2b-kurumsal-siteler-icin-ssl-ve-guven-mimarisi\/\">B2B kurumsal siteler i\u00e7in SSL ve g\u00fcven mimarisi rehberimize<\/a> g\u00f6z atabilirsiniz.<\/p>\n<h2><span id=\"SSL_Kurulumu_ve_Test_Sunucu_Tarafinda_Yapilmasi_Gerekenler\">SSL Kurulumu ve Test: Sunucu Taraf\u0131nda Yap\u0131lmas\u0131 Gerekenler<\/span><\/h2>\n<h3><span id=\"1_DNS_ve_hosting_tarafi_onkontroller\">1. DNS ve hosting taraf\u0131 \u00f6nkontroller<\/span><\/h3>\n<p>SSL kurulumuna ba\u015flamadan \u00f6nce:<\/p>\n<ul>\n<li>Alan ad\u0131n\u0131z\u0131n do\u011fru IP\u2019ye \u00e7\u00f6z\u00fcld\u00fc\u011f\u00fcnden emin olun (A \/ AAAA kay\u0131tlar\u0131).<\/li>\n<li>Reverse proxy \/ CDN (\u00f6rne\u011fin HTTP\/3 destekli bir CDN) kullan\u0131yorsan\u0131z, origin ve CDN aras\u0131ndaki SSL modunu planlay\u0131n.<\/li>\n<li>Test i\u00e7in d\u00fc\u015f\u00fck TTL (300s gibi) kullanman\u0131z, olas\u0131 geri al\u0131mlar\u0131 h\u0131zland\u0131r\u0131r.<\/li>\n<\/ul>\n<p>DNS mimariniz karma\u015f\u0131ksa, <a href=\"https:\/\/www.dchost.com\/blog\/cloudflare-dns-mi-hosting-dnsi-mi-en-dogru-nameserver-stratejisi\/\">nameserver ve DNS stratejisini do\u011fru kurma rehberimize<\/a> bakman\u0131z faydal\u0131 olacakt\u0131r.<\/p>\n<h3><span id=\"2_Sunucuya_SSL_sertifikasi_kurma\">2. Sunucuya SSL sertifikas\u0131 kurma<\/span><\/h3>\n<p>DCHost \u00fczerinde <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a>, y\u00f6netilen VPS veya <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> kullan\u0131yor olun; panel \u00fczerinden SSL kurulumunu birka\u00e7 ad\u0131mda tamamlayabilirsiniz. \u00d6rne\u011fin Let\u2019s Encrypt ile otomatik DV sertifikas\u0131 kullan\u0131yorsan\u0131z, cPanel\/DirectAdmin\u2019de ilgili alan ad\u0131 i\u00e7in \u201cAutoSSL\u201d veya e\u015fde\u011feri \u00f6zelli\u011fi aktif etmek yeterli olabilir. Bu s\u00fcreci daha detayl\u0131 g\u00f6rmek isterseniz <a href=\"https:\/\/www.dchost.com\/blog\/lets-encrypt-ile-ucretsiz-ssl-sertifikasi-kurulumu-cpanel-ve-directadminde-otomatik-yenileme-rehberi\/\">Let\u2019s Encrypt ile \u00fccretsiz SSL kurulumu rehberimizi<\/a> inceleyin.<\/p>\n<p>VPS veya dedicated \u00fczerinde manuel kurulum yap\u0131yorsan\u0131z tipik Nginx yap\u0131land\u0131rmas\u0131 \u015f\u00f6yle g\u00f6r\u00fcn\u00fcr:<\/p>\n<pre class=\"language-nginx line-numbers\"><code class=\"language-nginx\">server {\n    listen 443 ssl http2;\n    server_name ornek.com www.ornek.com;\n\n    ssl_certificate     \/etc\/ssl\/certs\/ornek.com.fullchain.pem;\n    ssl_certificate_key \/etc\/ssl\/private\/ornek.com.key;\n\n    # Modern TLS ayarlar\u0131\n    ssl_protocols TLSv1.2 TLSv1.3;\n    ssl_ciphers   HIGH:!aNULL:!MD5;\n\n    root \/var\/www\/ornek.com\/public;\n}\n<\/code><\/pre>\n<p>Apache i\u00e7in ise tipik bir VirtualHost \u00f6rne\u011fi:<\/p>\n<pre class=\"language-apache line-numbers\"><code class=\"language-apache\">&lt;VirtualHost *:443&gt;\n    ServerName ornek.com\n    ServerAlias www.ornek.com\n\n    DocumentRoot \/var\/www\/ornek.com\/public\n\n    SSLEngine on\n    SSLCertificateFile    \/etc\/ssl\/certs\/ornek.com.crt\n    SSLCertificateKeyFile \/etc\/ssl\/private\/ornek.com.key\n    SSLCertificateChainFile \/etc\/ssl\/certs\/ornek.com.ca-bundle\n&lt;\/VirtualHost&gt;\n<\/code><\/pre>\n<h3><span id=\"3_Mixed_content_ve_guvensiz_icerik_testleri\">3. Mixed content ve g\u00fcvensiz i\u00e7erik testleri<\/span><\/h3>\n<p>Taray\u0131c\u0131 adres \u00e7ubu\u011funda kilit simgesini g\u00f6rmeniz, sitenizin tamamen g\u00fcvenli oldu\u011fu anlam\u0131na gelmez. Sayfa HTML\u2019i HTTPS ile gelse bile, i\u00e7inde HTTP ile \u00e7a\u011fr\u0131lan g\u00f6rseller, CSS, JS veya iframe\u2019ler varsa <strong>mixed content<\/strong> hatalar\u0131 al\u0131rs\u0131n\u0131z. Bunlar hem g\u00fcvenlik hem de kullan\u0131c\u0131 deneyimi a\u00e7\u0131s\u0131ndan sorun \u00e7\u0131kar\u0131r.<\/p>\n<p>Bu a\u015famada:<\/p>\n<ul>\n<li>Taray\u0131c\u0131 konsolunda (F12 \u2192 Console \/ Security) mixed content uyar\u0131lar\u0131n\u0131 inceleyin.<\/li>\n<li>WordPress, Laravel gibi sistemlerde base URL ayarlar\u0131n\u0131 <code>https:\/\/<\/code> olacak \u015fekilde g\u00fcncelleyin.<\/li>\n<li>Veritaban\u0131nda g\u00f6m\u00fcl\u00fc HTTP linklerini aray\u0131p toplu g\u00fcncelleyin.<\/li>\n<\/ul>\n<p>\u00d6zellikle WordPress projelerinde bu konu s\u0131k kar\u015f\u0131m\u0131za \u00e7\u0131kt\u0131\u011f\u0131 i\u00e7in, <a href=\"https:\/\/www.dchost.com\/blog\/ssl-sonrasi-mixed-content-ve-guvensiz-icerik-hatalarini-duzeltmek\/\">SSL sonras\u0131 mixed content ve g\u00fcvensiz i\u00e7erik hatalar\u0131n\u0131 d\u00fczeltme rehberimizi<\/a> ad\u0131m ad\u0131m takip etmenizi \u00f6neririz.<\/p>\n<h2><span id=\"SEO_Kayipsiz_Gecis_Icin_301_Yonlendirme_ve_Canonical_Stratejisi\">SEO Kay\u0131ps\u0131z Ge\u00e7i\u015f \u0130\u00e7in 301 Y\u00f6nlendirme ve Canonical Stratejisi<\/span><\/h2>\n<h3><span id=\"1_Tek_bir_canonical_domain_secin\">1. Tek bir canonical domain se\u00e7in<\/span><\/h3>\n<p>Hem SEO hem de HSTS a\u00e7\u0131s\u0131ndan <strong>tek bir ana domain<\/strong> se\u00e7meniz gerekir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Resmi adresiniz <code>https:\/\/www.ornek.com<\/code> ise, <code>https:\/\/ornek.com<\/code> ve t\u00fcm HTTP varyasyonlar\u0131 buraya 301 ile y\u00f6nlenmelidir.<\/li>\n<li>Resmi adresiniz <code>https:\/\/ornek.com<\/code> ise, tersi \u015fekilde www\u2019den \u00e7\u0131pla\u011fa y\u00f6nlendirme yapmal\u0131s\u0131n\u0131z.<\/li>\n<\/ul>\n<p>Bu karar\u0131n art\u0131\/eksi\u2019lerini ve HSTS ile ili\u015fkisini detayl\u0131 a\u00e7\u0131klad\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/www-mi-ciplak-alan-adi-mi-canonical-domain-301-ve-hsts-icin-dogru-ayarlar\/\">www mi \u00e7\u0131plak alan m\u0131 sorusuna teknik cevap verdi\u011fimiz rehber<\/a>, ge\u00e7i\u015f \u00f6ncesi mutlaka g\u00f6z atman\u0131z gereken bir kaynak.<\/p>\n<h3><span id=\"2_HTTP_HTTPS_301_yonlendirme_kurallari\">2. HTTP \u2192 HTTPS 301 y\u00f6nlendirme kurallar\u0131<\/span><\/h3>\n<p>Hedefiniz, <strong>t\u00fcm HTTP isteklerini bire bir HTTPS muadil sayfaya 301 ile y\u00f6nlendirmek<\/strong> olmal\u0131. Yani:<\/p>\n<ul>\n<li><code>http:\/\/ornek.com\/urun\/kirmizi-elbise<\/code> \u2192 <code>https:\/\/ornek.com\/urun\/kirmizi-elbise<\/code><\/li>\n<li><code>http:\/\/www.ornek.com\/blog\/yazi<\/code> \u2192 <code>https:\/\/www.ornek.com\/blog\/yazi<\/code><\/li>\n<\/ul>\n<p>Apache (.htaccess) i\u00e7in tipik bir kural seti:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">RewriteEngine On\n\n# T\u00fcm HTTP'yi HTTPS'ye zorla\nRewriteCond %{HTTPS} off\nRewriteRule ^(.*)$ https:\/\/%{HTTP_HOST}\/$1 [L,R=301]\n<\/code><\/pre>\n<p>Canonical domaininizi de sabitlemek isterseniz, \u00f6rne\u011fin sadece <code>www.ornek.com<\/code> kullanacaksan\u0131z:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">RewriteEngine On\n\n# ornek.com'u www.ornek.com'a y\u00f6nlendir\nRewriteCond %{HTTP_HOST} ^ornek.com [NC]\nRewriteRule ^(.*)$ https:\/\/www.ornek.com\/$1 [L,R=301]\n\n# HTTP'yi HTTPS'ye zorla\nRewriteCond %{HTTPS} off\nRewriteRule ^(.*)$ https:\/\/www.ornek.com\/$1 [L,R=301]\n<\/code><\/pre>\n<p>Nginx i\u00e7in benzer bir kurgu:<\/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\n    return 301 https:\/\/www.ornek.com$request_uri;\n}\n<\/code><\/pre>\n<p>Burada en kritik nokta <strong>redirect loop olu\u015fturmamak<\/strong> ve t\u00fcm varyasyonlar\u0131n tek bir hedefe (canonical domain) gitmesini sa\u011flamak.<\/p>\n<h3><span id=\"3_Canonical_etiketlerini_guncellemek\">3. Canonical etiketlerini g\u00fcncellemek<\/span><\/h3>\n<p>HTTP \u2192 HTTPS ge\u00e7i\u015finde s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalardan biri, sayfa ba\u015fl\u0131klar\u0131nda h\u00e2l\u00e2 HTTP i\u00e7eren <code>rel=\"canonical\"<\/code> etiketlerinin kalmas\u0131. Bu durumda arama motoruna \u201cBu sayfan\u0131n asl\u0131 HTTP versiyonudur\u201d demi\u015f olursunuz ki, migrasyonu fiilen bo\u015fa \u00e7\u0131kar\u0131r.<\/p>\n<p>Yapman\u0131z gerekenler:<\/p>\n<ul>\n<li>Tema veya layout dosyan\u0131zda canonical etiketini \u00fcreten kodu bulun.<\/li>\n<li>Base URL\u2019yi <code>https:\/\/<\/code> ile ba\u015flayacak \u015fekilde d\u00fczeltin.<\/li>\n<li>Dil, filtre, sayfalama gibi parametreleri nas\u0131l ele ald\u0131\u011f\u0131n\u0131z\u0131 g\u00f6zden ge\u00e7irin.<\/li>\n<\/ul>\n<p>\u00d6rnek bir canonical etiketi:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">&lt;link rel=&quot;canonical&quot; href=&quot;https:\/\/www.ornek.com\/urun\/kirmizi-elbise&quot; \/&gt;\n<\/code><\/pre>\n<p>\u00d6zellikle \u00e7oklu domain veya subdomain kullanan yap\u0131larda canonical stratejisi, park domain ve 301 y\u00f6nlendirmelerle birlikte d\u00fc\u015f\u00fcn\u00fclmelidir. Bu a\u00e7\u0131dan <a href=\"https:\/\/www.dchost.com\/blog\/park-alan-adlari-nasil-yonetilir-parking-301-ve-canonical-icin-uygulanabilir-stratejiler\/\">park alan adlar\u0131n\u0131, 301 y\u00f6nlendirmeyi ve canonical kullan\u0131m\u0131 birlikte anlatt\u0131\u011f\u0131m\u0131z rehber<\/a> iyi bir tamamlay\u0131c\u0131d\u0131r.<\/p>\n<h3><span id=\"4_Sitemap_robotstxt_ve_dahili_linkler\">4. Sitemap, robots.txt ve dahili linkler<\/span><\/h3>\n<p>Ge\u00e7i\u015f s\u0131ras\u0131nda a\u015fa\u011f\u0131daki ad\u0131mlar\u0131 atlamay\u0131n:<\/p>\n<ul>\n<li><strong>sitemap.xml<\/strong> i\u00e7indeki t\u00fcm URL\u2019leri HTTPS olacak \u015fekilde g\u00fcncelleyin.<\/li>\n<li><strong>robots.txt<\/strong> i\u00e7inde referans verdi\u011finiz sitemap adresini HTTPS yap\u0131n.<\/li>\n<li>Site i\u00e7i men\u00fc, footer, breadcrumb ve i\u00e7erik linklerini m\u00fcmk\u00fcn oldu\u011funca HTTPS\u2019e \u00e7evirin.<\/li>\n<\/ul>\n<p>Tek tek URL d\u00fczeltmek yerine sadece 301\u2019e g\u00fcvenmek teoride \u00e7al\u0131\u015fsa da, pratikte her katmanda (HTML i\u00e7eri\u011fi, canonical, sitemap, y\u00f6nlendirme) tutarl\u0131 bir HTTPS kullan\u0131m\u0131 daha temiz ve izlenebilir bir mimari sunar. robots ve sitemap taraf\u0131n\u0131 do\u011fru kurmak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/robots-txt-ve-sitemap-xml-dogru-kurulumu-adim-adim-seo-ve-hosting-rehberi\/\">robots.txt ve sitemap.xml kurulum rehberimize<\/a> de g\u00f6z atabilirsiniz.<\/p>\n<h2><span id=\"HSTS_Preload_ve_HTTP_Guvenlik_Basliklari\">HSTS, Preload ve HTTP G\u00fcvenlik Ba\u015fl\u0131klar\u0131<\/span><\/h2>\n<h3><span id=\"1_HSTS_nedir_ne_ise_yarar\">1. HSTS nedir, ne i\u015fe yarar?<\/span><\/h3>\n<p><strong>HSTS (HTTP Strict Transport Security)<\/strong>, taray\u0131c\u0131ya \u201cBu alan ad\u0131yla &lt;emdaima<\/em> HTTPS \u00fczerinden konu\u015f\u201d talimat\u0131 verir. Taray\u0131c\u0131 bir kez bu ba\u015fl\u0131\u011f\u0131 g\u00f6rd\u00fckten sonra, kullan\u0131c\u0131 <code>http:\/\/<\/code> adresi yazsa bile, arka planda otomatik olarak <code>https:\/\/<\/code> iste\u011fi g\u00f6nderilir.<\/p>\n<p>Art\u0131lar\u0131:<\/p>\n<ul>\n<li>SSL strip gibi sald\u0131r\u0131lar\u0131 zorla\u015ft\u0131r\u0131r.<\/li>\n<li>Kullan\u0131c\u0131 deneyimini iyile\u015ftirir; HTTP iste\u011fi bile g\u00f6rmeden HTTPS\u2019e gider.<\/li>\n<\/ul>\n<p>Eksileri ve riskleri:<\/p>\n<ul>\n<li>Yanl\u0131\u015f bir sertifika veya y\u00f6nlendirme kurgusunu \u201ckilitlerseniz\u201d geri almak zor olur.<\/li>\n<li>\u00d6zellikle preload listesine al\u0131nd\u0131ysa, hata d\u00fczeltmesi haftalar\/aylar s\u00fcrebilir.<\/li>\n<\/ul>\n<p>Bu y\u00fczden HSTS\u2019i <strong>HTTPS ge\u00e7i\u015fi tamamen stabil hale geldikten sonra<\/strong> devreye almak en g\u00fcvenli yakla\u015f\u0131md\u0131r.<\/p>\n<h3><span id=\"2_HSTS_basligini_nasil_eklersiniz\">2. HSTS ba\u015fl\u0131\u011f\u0131n\u0131 nas\u0131l eklersiniz?<\/span><\/h3>\n<p>Temel 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<p>Nginx i\u00e7in \u00f6rnek konfig\u00fcrasyon:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">add_header Strict-Transport-Security &quot;max-age=31536000; includeSubDomains; preload&quot; always;\n<\/code><\/pre>\n<p>Apache i\u00e7in:<\/p>\n<pre class=\"language-bash line-numbers\"><code class=\"language-bash\">Header always set Strict-Transport-Security &quot;max-age=31536000; includeSubDomains; preload&quot;\n<\/code><\/pre>\n<p>Ba\u015flang\u0131\u00e7ta daha k\u0131sa bir <code>max-age<\/code> (\u00f6rne\u011fin 300 veya 86400 saniye) ile test edip, her \u015fey sorunsuz \u00e7al\u0131\u015f\u0131yorsa s\u00fcreyi 1 y\u0131la \u00e7\u0131kar\u0131p <code>includeSubDomains<\/code> ve <code>preload<\/code> eklemek daha g\u00fcvenli bir yakla\u015f\u0131md\u0131r.<\/p>\n<h3><span id=\"3_HSTS_Preload_ne_zaman_mantikli\">3. HSTS Preload ne zaman mant\u0131kl\u0131?<\/span><\/h3>\n<p>HSTS Preload, alan ad\u0131n\u0131z\u0131 taray\u0131c\u0131lar\u0131n dahili \u201cher zaman HTTPS\u201d listesine ald\u0131rman\u0131z anlam\u0131na gelir. Bunun i\u00e7in:<\/p>\n<ul>\n<li>T\u00fcm site ve subdomain\u2019lerinizin HTTPS ile sorunsuz \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olman\u0131z,<\/li>\n<li>Hi\u00e7bir \u015fekilde HTTP \u00fczerinden eri\u015fim gerektiren bir alt yap\u0131 kullanmaman\u0131z,<\/li>\n<li>HSTS ba\u015fl\u0131\u011f\u0131n\u0131z\u0131 gerekli parametrelerle (\u00f6zellikle <code>includeSubDomains<\/code> ve yeterli <code>max-age<\/code>) g\u00f6ndermeniz<\/li>\n<\/ul>\n<p>gerekir. Preload ba\u015fvurusu, geri d\u00f6n\u00fc\u015f\u00fc g\u00f6rece zor bir ad\u0131md\u0131r; bu y\u00fczden ancak mimariniz oturduktan sonra d\u00fc\u015f\u00fcn\u00fclmelidir.<\/p>\n<p>HSTS ile birlikte kullanman\u0131z gereken di\u011fer g\u00fcvenlik ba\u015fl\u0131klar\u0131n\u0131 (CSP, X-Frame-Options, Referrer-Policy vb.) daha derinlemesine anlamak i\u00e7in <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 rehberimizi<\/a> mutlaka inceleyin.<\/p>\n<h2><span id=\"Test_Yayina_Alma_ve_Izleme_Stratejisi\">Test, Yay\u0131na Alma ve \u0130zleme Stratejisi<\/span><\/h2>\n<h3><span id=\"1_Staging_ortaminda_HTTPS_gecis_provasini_yapin\">1. Staging ortam\u0131nda HTTPS ge\u00e7i\u015f provas\u0131n\u0131 yap\u0131n<\/span><\/h3>\n<p>Canl\u0131 site \u00fczerinde do\u011frudan HTTPS ge\u00e7i\u015fi yapmak yerine, ayn\u0131 uygulamay\u0131 staging ortam\u0131nda (\u00f6rn. <code>staging.ornek.com<\/code>) HTTPS\u2019e ge\u00e7irip t\u00fcm sorunlar\u0131 \u00f6nce burada g\u00f6rmek \u00e7ok daha sa\u011fl\u0131kl\u0131d\u0131r. \u00d6zellikle:<\/p>\n<ul>\n<li>Mixed content uyar\u0131lar\u0131,<\/li>\n<li>ESKI JS\/CSS path\u2019leri,<\/li>\n<li>3. parti entegrasyon URL\u2019leri (\u00f6deme, kargo, CRM vb.)<\/li>\n<\/ul>\n<p>genelde staging\u2019de ortaya \u00e7\u0131kar. Payla\u015f\u0131ml\u0131 hosting kullan\u0131yorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/paylasimli-hostingde-wordpress-staging-ortami-kurmak-adim-adim-uygulamali-rehber\/\">payla\u015f\u0131ml\u0131 hosting\u2019de WordPress staging ortam\u0131 kurma rehberimizde<\/a> bu s\u00fcreci ad\u0131m ad\u0131m anlatt\u0131k.<\/p>\n<h3><span id=\"2_Search_Console_Analytics_ve_sitemap_guncellemeleri\">2. Search Console, Analytics ve sitemap g\u00fcncellemeleri<\/span><\/h3>\n<p>HTTPS ge\u00e7i\u015finden hemen sonra:<\/p>\n<ul>\n<li>Google Search Console\u2019da <strong>HTTPS versiyonunuz i\u00e7in ayr\u0131 bir m\u00fclk<\/strong> ekleyin.<\/li>\n<li>G\u00fcncel HTTPS sitemap\u2019ini Search Console\u2019a g\u00f6nderin.<\/li>\n<li>Google Analytics ve benzeri ara\u00e7larda <code>https:\/\/<\/code> base URL ayarlar\u0131n\u0131 g\u00fcncelleyin.<\/li>\n<li>\u00dccretli reklam kampanyalar\u0131n\u0131zda (Google Ads, sosyal medya) linkleri HTTPS olacak \u015fekilde d\u00fczeltin.<\/li>\n<\/ul>\n<p>Bu ad\u0131mlar, Google\u2019\u0131n yeni URL yap\u0131n\u0131z\u0131 daha h\u0131zl\u0131 ve do\u011fru \u015fekilde taramas\u0131na yard\u0131mc\u0131 olur.<\/p>\n<h3><span id=\"3_Sunucu_loglari_ve_hata_izleme\">3. Sunucu loglar\u0131 ve hata izleme<\/span><\/h3>\n<p>Ge\u00e7i\u015fin hemen ard\u0131ndan sunucu loglar\u0131n\u0131 (access ve error log\u2019lar) mutlaka yak\u0131ndan izleyin. \u00d6zellikle:<\/p>\n<ul>\n<li>4xx (404, 410) hata oranlar\u0131ndaki art\u0131\u015f,<\/li>\n<li>5xx (\u00f6zellikle 502, 503) sunucu hata kodlar\u0131,<\/li>\n<li>Beklenmeyen redirect zincirleri (301 \u2192 301 \u2192 301\u2026)<\/li>\n<\/ul>\n<p>SEO kayb\u0131n\u0131n habercisi olabilir. Log okuma konusunda kendinizi geli\u015ftirmek istiyorsan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/hosting-sunucu-loglarini-okumayi-ogrenin-apache-ve-nginx-ile-4xx-5xx-hatalarini-teshis-rehberi\/\">Apache ve Nginx loglar\u0131yla 4xx\u20135xx hatalar\u0131n\u0131 te\u015fhis rehberimiz<\/a> ve <a href=\"https:\/\/www.dchost.com\/blog\/sunucu-loglariyla-core-web-vitals-iyilestirme-firsatlari\/\">sunucu loglar\u0131yla Core Web Vitals iyile\u015ftirme f\u0131rsatlar\u0131n\u0131 anlatt\u0131\u011f\u0131m\u0131z yaz\u0131m\u0131z<\/a> iyi bir ba\u015flang\u0131\u00e7 noktas\u0131d\u0131r.<\/p>\n<h2><span id=\"DCHost_Musteri_Senaryolarindan_Ogrendiklerimiz\">DCHost M\u00fc\u015fteri Senaryolar\u0131ndan \u00d6\u011frendiklerimiz<\/span><\/h2>\n<h3><span id=\"1_KOBI_e-ticaret_sitesinde_HTTPS_gecisi_ve_sepet_donusum_orani\">1. KOB\u0130 e-ticaret sitesinde HTTPS ge\u00e7i\u015fi ve sepet d\u00f6n\u00fc\u015f\u00fcm oran\u0131<\/span><\/h3>\n<p>Bir KOB\u0130 m\u00fc\u015fterimizin e-ticaret sitesinde HTTP \u2192 HTTPS ge\u00e7i\u015fini planlarken ilk yapt\u0131\u011f\u0131m\u0131z \u015fey, sepet ve \u00f6deme sayfalar\u0131n\u0131 ayr\u0131 bir \u00f6ncelik listesine almakt\u0131. \u00d6nce staging ortam\u0131nda SSL\u2019i kurduk, t\u00fcm \u00f6deme entegrasyon URL\u2019lerini (banka, 3D Secure, sanal POS callback adresleri) HTTPS\u2019e \u00e7ektik ve mixed content testlerini tamamlad\u0131k.<\/p>\n<p>Canl\u0131 ge\u00e7i\u015fi hafta i\u00e7i gece trafi\u011finin en d\u00fc\u015f\u00fck oldu\u011fu zaman diliminde yapt\u0131k ve Search Console\u2019da HTTPS m\u00fclk\u00fcn\u00fc ayn\u0131 g\u00fcn ekledik. \u0130lk hafta ufak dalgalanmalar olsa da 2\u20133 hafta i\u00e7inde organik trafik eski seviyesini yakalad\u0131; buna kar\u015f\u0131l\u0131k taray\u0131c\u0131 \u201cG\u00fcvenli de\u011fil\u201d uyar\u0131lar\u0131 ortadan kalkt\u0131\u011f\u0131 i\u00e7in sepet tamamlama oran\u0131nda g\u00f6zle g\u00f6r\u00fcl\u00fcr bir art\u0131\u015f oldu.<\/p>\n<h3><span id=\"2_Kurumsal_B2B_sitede_HSTS_ve_preload_stratejisi\">2. Kurumsal B2B sitede HSTS ve preload stratejisi<\/span><\/h3>\n<p>Bir ba\u015fka m\u00fc\u015fteri senaryosunda, global B2B bir \u015firkete ait kurumsal sitede HTTPS y\u0131llard\u0131r aktifti ancak HSTS kullan\u0131lm\u0131yordu. \u00d6nce t\u00fcm subdomain\u2019leri taray\u0131p HTTPS uyumlulu\u011funu kontrol ettik, sadece eski bir staging subdomain\u2019inde HTTP ba\u011f\u0131ml\u0131l\u0131\u011f\u0131 oldu\u011funu g\u00f6rd\u00fck. Bu alt alan\u0131 kapatt\u0131ktan sonra \u00f6nce 1 g\u00fcnl\u00fck <code>max-age<\/code> ile HSTS\u2019i devreye ald\u0131k.<\/p>\n<p>Herhangi bir sorun g\u00f6zlemlemeyince s\u00fcreyi 1 y\u0131la \u00e7\u0131kard\u0131k, ard\u0131ndan preload ba\u015fvurusu yapt\u0131k. Sonu\u00e7ta hem g\u00fcvenlik puanlar\u0131 (SSLLabs gibi testlerde) y\u00fckseldi, hem de kurumsal g\u00fcven alg\u0131s\u0131 a\u00e7\u0131s\u0131ndan IT ekibi i\u00e7 denetimlerde daha rahat ilerleyebildi.<\/p>\n<h2><span id=\"Sonuc_ve_DCHost_ile_Guvenli_HTTPS_Mimarisi\">Sonu\u00e7 ve DCHost ile G\u00fcvenli HTTPS Mimarisi<\/span><\/h2>\n<p>HTTP\u2019den HTTPS\u2019ye ge\u00e7i\u015f, do\u011fru planland\u0131\u011f\u0131nda hem g\u00fcvenlik hem SEO taraf\u0131nda kazan\u00e7l\u0131 \u00e7\u0131kaca\u011f\u0131n\u0131z bir yat\u0131r\u0131md\u0131r. Yanl\u0131\u015f kurguland\u0131\u011f\u0131nda ise canonical karma\u015fas\u0131, hatal\u0131 301 zincirleri, mixed content ve agresif HSTS kullan\u0131m\u0131 y\u00fcz\u00fcnden hem s\u0131ralama hem d\u00f6n\u00fc\u015f\u00fcm kayb\u0131 ya\u015faman\u0131z m\u00fcmk\u00fcn. Bu rehberde DCHost ekibi olarak sahada en s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz hatalar\u0131 ve bunlara kar\u015f\u0131 pratik \u00e7\u00f6z\u00fcmleri \u00f6zetledik.<\/p>\n<p>\u00d6zetle; \u00f6nce mimariyi ve canonical domaininizi netle\u015ftirin, sonra SSL kurulumunu temizce yap\u0131n, ard\u0131ndan 301 y\u00f6nlendirme ve canonical etiketlerini tutarl\u0131 hale getirin. HSTS ve preload hamlelerini ise ancak ge\u00e7i\u015f tamamen stabil olduktan sonra devreye al\u0131n. Sunucu loglar\u0131n\u0131, Search Console raporlar\u0131n\u0131 ve kullan\u0131c\u0131 geri bildirimlerini ilk haftalarda yak\u0131ndan izlemeyi unutmay\u0131n.<\/p>\n<p>E\u011fer HTTPS ge\u00e7i\u015finizi payla\u015f\u0131ml\u0131 hosting, y\u00f6netilen VPS, dedicated sunucu veya colocation altyap\u0131n\u0131z \u00fczerinde DCHost ile planlamak isterseniz; SSL tedarikinden otomasyonuna, HSTS ve HTTP g\u00fcvenlik ba\u015fl\u0131klar\u0131n\u0131n do\u011fru ayarlanmas\u0131na kadar t\u00fcm ad\u0131mlar\u0131 beraber tasarlayabiliriz. Altyap\u0131 taraf\u0131n\u0131 bize b\u0131rak\u0131p i\u00e7erik ve i\u015finize odaklanmak istiyorsan\u0131z, DCHost ekibiyle ileti\u015fime ge\u00e7meniz yeterli.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 HTTPS&#8217;e Ge\u00e7i\u015f Neden Sadece G\u00fcvenlik De\u011fil, Stratejik Bir SEO Karar\u0131?2 Ge\u00e7i\u015f \u00d6ncesi Haz\u0131rl\u0131k: Envanter, Mimari ve Planlama2.1 1. Mevcut URL ve alan ad\u0131 mimarinizi netle\u015ftirin2.2 2. SEO risk analizi yap\u0131n2.3 3. Do\u011fru SSL sertifikas\u0131n\u0131 se\u00e7in3 SSL Kurulumu ve Test: Sunucu Taraf\u0131nda Yap\u0131lmas\u0131 Gerekenler3.1 1. DNS ve hosting taraf\u0131 \u00f6nkontroller3.2 2. Sunucuya SSL sertifikas\u0131 kurma3.3 [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":4591,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-4590","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\/4590","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=4590"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/4590\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/4591"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=4590"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=4590"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=4590"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}