{"id":3971,"date":"2026-01-02T15:14:50","date_gmt":"2026-01-02T12:14:50","guid":{"rendered":"https:\/\/www.dchost.com\/blog\/blog-magaza-ve-landing-page-icin-subdomain-mi-klasor-mu-seo-hosting-ve-cdn-karar-rehberi\/"},"modified":"2026-01-02T15:14:50","modified_gmt":"2026-01-02T12:14:50","slug":"blog-magaza-ve-landing-page-icin-subdomain-mi-klasor-mu-seo-hosting-ve-cdn-karar-rehberi","status":"publish","type":"post","link":"https:\/\/www.dchost.com\/blog\/blog-magaza-ve-landing-page-icin-subdomain-mi-klasor-mu-seo-hosting-ve-cdn-karar-rehberi\/","title":{"rendered":"Blog, Ma\u011faza ve Landing Page \u0130\u00e7in Subdomain mi Klas\u00f6r m\u00fc? SEO, Hosting ve CDN Karar Rehberi"},"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=\"#Neyi_Nereye_Koydugunuz_Neden_Bu_Kadar_Onemli\"><span class=\"toc_number toc_depth_1\">1<\/span> Neyi Nereye Koydu\u011funuz Neden Bu Kadar \u00d6nemli?<\/a><\/li><li><a href=\"#Subdomain_ve_Klasorun_Teknik_Farklari\"><span class=\"toc_number toc_depth_1\">2<\/span> Subdomain ve Klas\u00f6r\u00fcn Teknik Farklar\u0131<\/a><ul><li><a href=\"#DNS_SSL_ve_Barindirma_Ayrimi\"><span class=\"toc_number toc_depth_2\">2.1<\/span> DNS, SSL ve Bar\u0131nd\u0131rma Ayr\u0131m\u0131<\/a><\/li><li><a href=\"#Cerezler_Oturumlar_ve_Login_Paylasimi\"><span class=\"toc_number toc_depth_2\">2.2<\/span> \u00c7erezler, Oturumlar ve Login Payla\u015f\u0131m\u0131<\/a><\/li><li><a href=\"#Loglama_Guvenlik_ve_Izleme\"><span class=\"toc_number toc_depth_2\">2.3<\/span> Loglama, G\u00fcvenlik ve \u0130zleme<\/a><\/li><\/ul><\/li><li><a href=\"#SEO_Perspektifinden_Subdomain_mi_Klasor_mu\"><span class=\"toc_number toc_depth_1\">3<\/span> SEO Perspektifinden Subdomain mi Klas\u00f6r m\u00fc?<\/a><ul><li><a href=\"#Otorite_Backlink_ve_Domain_Gucu\"><span class=\"toc_number toc_depth_2\">3.1<\/span> Otorite, Backlink ve Domain G\u00fcc\u00fc<\/a><\/li><li><a href=\"#Blog_Icin_Kural_Degil_Ama_Guclu_Bir_Tavsiye\"><span class=\"toc_number toc_depth_2\">3.2<\/span> Blog \u0130\u00e7in: Kural De\u011fil Ama G\u00fc\u00e7l\u00fc Bir Tavsiye<\/a><\/li><li><a href=\"#Magaza_Eticaret_Icin_Mimari_Tercihler\"><span class=\"toc_number toc_depth_2\">3.3<\/span> Ma\u011faza (E\u2011ticaret) \u0130\u00e7in Mimari Tercihler<\/a><\/li><li><a href=\"#Landing_Page_ve_Kampanya_Sayfalari\"><span class=\"toc_number toc_depth_2\">3.4<\/span> Landing Page ve Kampanya Sayfalar\u0131<\/a><\/li><li><a href=\"#Uluslararasi_SEO_Dil_Surumleri_ve_Hreflang\"><span class=\"toc_number toc_depth_2\">3.5<\/span> Uluslararas\u0131 SEO, Dil S\u00fcr\u00fcmleri ve Hreflang<\/a><\/li><\/ul><\/li><li><a href=\"#Hosting_Mimarisi_ve_Yonetim_Acisindan_Etkiler\"><span class=\"toc_number toc_depth_1\">4<\/span> Hosting Mimarisi ve Y\u00f6netim A\u00e7\u0131s\u0131ndan Etkiler<\/a><ul><li><a href=\"#Paylasimli_Hosting_Basit_Projeler_Icin_Klasor_Avantaji\"><span class=\"toc_number toc_depth_2\">4.1<\/span> Payla\u015f\u0131ml\u0131 Hosting: Basit Projeler \u0130\u00e7in Klas\u00f6r Avantaj\u0131<\/a><\/li><li><a href=\"#VPS_ve_Dedicated_Sunucular_Ayri_Uygulamalar_Ayri_Subdomainler\"><span class=\"toc_number toc_depth_2\">4.2<\/span> VPS ve Dedicated Sunucular: Ayr\u0131 Uygulamalar, Ayr\u0131 Subdomain\u2019ler<\/a><\/li><li><a href=\"#Colocation_ve_Karmasik_Altyapilar\"><span class=\"toc_number toc_depth_2\">4.3<\/span> Colocation ve Karma\u015f\u0131k Altyap\u0131lar<\/a><\/li><\/ul><\/li><li><a href=\"#CDN_Medya_ve_Performans_Boyutu\"><span class=\"toc_number toc_depth_1\">5<\/span> CDN, Medya ve Performans Boyutu<\/a><ul><li><a href=\"#Statik_Dosyalar_Icin_Ayri_Subdomain_Kullanmak\"><span class=\"toc_number toc_depth_2\">5.1<\/span> Statik Dosyalar \u0130\u00e7in Ayr\u0131 Subdomain Kullanmak<\/a><\/li><li><a href=\"#CDN_Cografi_Yayilim_ve_Cok_Bolgeli_Mimari\"><span class=\"toc_number toc_depth_2\">5.2<\/span> CDN, Co\u011frafi Yay\u0131l\u0131m ve \u00c7ok B\u00f6lgeli Mimari<\/a><\/li><li><a href=\"#Core_Web_Vitals_ve_URL_Mimarisi\"><span class=\"toc_number toc_depth_2\">5.3<\/span> Core Web Vitals ve URL Mimarisi<\/a><\/li><\/ul><\/li><li><a href=\"#Farkli_Senaryolar_Icin_Karar_Modelleri\"><span class=\"toc_number toc_depth_1\">6<\/span> Farkl\u0131 Senaryolar \u0130\u00e7in Karar Modelleri<\/a><ul><li><a href=\"#1_Kucuk_Isletme_Kurumsal_Site_Blog\"><span class=\"toc_number toc_depth_2\">6.1<\/span> 1) K\u00fc\u00e7\u00fck \u0130\u015fletme: Kurumsal Site + Blog<\/a><\/li><li><a href=\"#2_Buyuyen_ETicaret_Kurumsal_Site_Buyuk_Magaza\"><span class=\"toc_number toc_depth_2\">6.2<\/span> 2) B\u00fcy\u00fcyen E\u2011Ticaret: Kurumsal Site + B\u00fcy\u00fck Ma\u011faza<\/a><\/li><li><a href=\"#3_SaaS_Urunu_Uygulama_Marketing_Site_Blog_Landing_Page\"><span class=\"toc_number toc_depth_2\">6.3<\/span> 3) SaaS \u00dcr\u00fcn\u00fc: Uygulama + Marketing Site + Blog + Landing Page<\/a><\/li><li><a href=\"#4_Cok_Dilli_Kurumsal_Site_Blog_Bolgesel_Landing_Pageler\"><span class=\"toc_number toc_depth_2\">6.4<\/span> 4) \u00c7ok Dilli Kurumsal Site + Blog + B\u00f6lgesel Landing Page\u2019ler<\/a><\/li><\/ul><\/li><li><a href=\"#Uygulanabilir_Kontrol_Listesi_ve_Ozet\"><span class=\"toc_number toc_depth_1\">7<\/span> Uygulanabilir Kontrol Listesi ve \u00d6zet<\/a><ul><li><a href=\"#Klasor_Alt_Dizin_Tercihini_Guclendiren_Sorular\"><span class=\"toc_number toc_depth_2\">7.1<\/span> Klas\u00f6r (Alt Dizin) Tercihini G\u00fc\u00e7lendiren Sorular<\/a><\/li><li><a href=\"#Subdomain_Tercihini_Guclendiren_Sorular\"><span class=\"toc_number toc_depth_2\">7.2<\/span> Subdomain Tercihini G\u00fc\u00e7lendiren Sorular<\/a><\/li><li><a href=\"#Son_Soz_ve_DCHost_Tarafinda_Nasil_Ilerleyebilirsiniz\"><span class=\"toc_number toc_depth_2\">7.3<\/span> Son S\u00f6z ve DCHost Taraf\u0131nda Nas\u0131l \u0130lerleyebilirsiniz?<\/a><\/li><\/ul><\/li><\/ul><\/div>\n<h2><span id=\"Neyi_Nereye_Koydugunuz_Neden_Bu_Kadar_Onemli\">Neyi Nereye Koydu\u011funuz Neden Bu Kadar \u00d6nemli?<\/span><\/h2>\n<p>Blogunuzu, ma\u011fazan\u0131z\u0131 veya kampanya landing page\u2019lerinizi nereye konumland\u0131raca\u011f\u0131n\u0131z \u00e7o\u011fu zaman tasar\u0131m toplant\u0131lar\u0131nda son dakikaya kalan bir karar oluyor: <strong>blog.site.com<\/strong> mu, yoksa <strong>site.com\/blog\/<\/strong> m\u00fc? Ma\u011faza i\u00e7in <strong>shop.site.com<\/strong> mu, <strong>site.com\/magaza\/<\/strong> m\u0131? Pazarlama ekibi \u00e7o\u011funlukla marka tutarl\u0131l\u0131\u011f\u0131na, ajans teknik ekibi URL d\u00fczenine, SEO taraf\u0131 ise otoriteye odaklan\u0131yor. Altyap\u0131 taraf\u0131nda biz ise DCHost ekibi olarak bunun sadece bir URL kozmeti\u011fi de\u011fil, <strong>DNS, SSL, CDN, cache, g\u00fcvenlik ve izleme<\/strong> boyutlar\u0131 olan bir mimari karar\u0131 oldu\u011funu g\u00f6r\u00fcyoruz.<\/p>\n<p>Bu yaz\u0131da; blog, ma\u011faza ve landing page \u00f6zelinde <strong>subdomain (alt alan ad\u0131)<\/strong> ile <strong>klas\u00f6r (alt dizin)<\/strong> tercihini; SEO etkileri, hosting y\u00f6netimi, CDN ve performans mimarisi \u00fczerinden detayl\u0131 \u015fekilde ele alaca\u011f\u0131z. Zaten yay\u0131nda bir siteniz varsa, yanl\u0131\u015f kararla SEO kayb\u0131 ya\u015famamak i\u00e7in y\u00f6nlendirme ve ge\u00e7i\u015f stratejilerine de de\u011finece\u011fiz. Daha \u00f6nce ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/subdomain-mi-alt-dizin-mi-blog-magaza-ve-dil-surumleri-icin-seo-ve-hosting-karsilastirmasi\/\">subdomain vs alt dizin kar\u015f\u0131la\u015ft\u0131rmas\u0131<\/a> yaz\u0131m\u0131z\u0131 geni\u015fleten, daha mimari odakl\u0131 bir rehber olarak d\u00fc\u015f\u00fcnebilirsiniz.<\/p>\n<p>Hedefimiz; \u201cherkes subdomain kullan\u0131yor\u201d ya da \u201cSEO i\u00e7in her \u015feyi klas\u00f6re al\u0131n\u201d gibi ezbere c\u00fcmleler yerine, <strong>farkl\u0131 senaryolara g\u00f6re uygulanabilir karar modelleri<\/strong> vermek. B\u00f6ylece ister <a href=\"https:\/\/www.dchost.com\/tr\/web-hosting\">payla\u015f\u0131ml\u0131 hosting<\/a>, ister <a href=\"https:\/\/www.dchost.com\/tr\/vps\">VPS<\/a>, <a href=\"https:\/\/www.dchost.com\/tr\/fiziksel-sunucu\">dedicated sunucu<\/a> veya colocation kullans\u0131n, DCHost \u00fczerinde bar\u0131nd\u0131rd\u0131\u011f\u0131n\u0131z projelerde tutarl\u0131 ve \u00f6l\u00e7eklenebilir bir yap\u0131 kurabilirsiniz.<\/p>\n<h2><span id=\"Subdomain_ve_Klasorun_Teknik_Farklari\">Subdomain ve Klas\u00f6r\u00fcn Teknik Farklar\u0131<\/span><\/h2>\n<p>\u00d6nce kavramlar\u0131 netle\u015ftirelim. \u00d6rnek bir alan ad\u0131m\u0131z olsun: <strong>site.com<\/strong>.<\/p>\n<ul>\n<li><strong>Klas\u00f6r (alt dizin):<\/strong> <code>site.com\/blog\/<\/code>, <code>site.com\/magaza\/<\/code>, <code>site.com\/kampanya\/indirim\/<\/code><\/li>\n<li><strong>Subdomain (alt alan ad\u0131):<\/strong> <code>blog.site.com<\/code>, <code>shop.site.com<\/code>, <code>kampanya.site.com<\/code><\/li>\n<\/ul>\n<p>G\u00f6z\u00fcn\u00fcze benzer g\u00f6r\u00fcnebilir ama altyap\u0131da ciddi farklar yarat\u0131rlar.<\/p>\n<h3><span id=\"DNS_SSL_ve_Barindirma_Ayrimi\">DNS, SSL ve Bar\u0131nd\u0131rma Ayr\u0131m\u0131<\/span><\/h3>\n<p>Klas\u00f6rler, domain ile ayn\u0131 DNS kayd\u0131n\u0131 ve genellikle ayn\u0131 web sunucusunu payla\u015f\u0131r. Yani <strong>site.com<\/strong> ve <strong>site.com\/blog\/<\/strong> ayn\u0131 IP\u2019ye gider. Bu, payla\u015f\u0131ml\u0131 hosting veya basit bir VPS \u00fczerinde y\u00f6netimi kolayla\u015ft\u0131r\u0131r.<\/p>\n<p>Subdomain\u2019de ise her alt alan i\u00e7in ayr\u0131 <strong>DNS kayd\u0131<\/strong> tan\u0131mlars\u0131n\u0131z:<\/p>\n<ul>\n<li><code>A site.com \u2192 203.0.113.10<\/code><\/li>\n<li><code>A blog.site.com \u2192 203.0.113.10<\/code> (ayn\u0131 sunucu) ya da<\/li>\n<li><code>A shop.site.com \u2192 203.0.113.20<\/code> (farkl\u0131 sunucu)<\/li>\n<\/ul>\n<p>Bu esneklik sayesinde blog, ma\u011faza ve ana sitenizi <strong>tamamen farkl\u0131 sunucularda<\/strong> bar\u0131nd\u0131rabilirsiniz. DCHost \u00fczerinde bir projeyi payla\u015f\u0131ml\u0131 hosting\u2019te, di\u011ferini ayr\u0131 bir VPS\u2019te veya dedicated sunucuda ko\u015fturmak istedi\u011finizde subdomain mimarisi \u00e7ok i\u015fe yarar.<\/p>\n<p>SSL taraf\u0131nda da durum benzer. <strong>Wildcard SSL<\/strong> (\u00f6rne\u011fin <code>*.site.com<\/code>) ile \u00e7ok say\u0131da subdomain\u2019i tek sertifikayla kapsayabilirsiniz. Bir yandan da <a href=\"https:\/\/www.dchost.com\/blog\/lets-encrypt-ile-ucretsiz-ssl-sertifikasi-kurulumu-cpanel-ve-directadminde-otomatik-yenileme-rehberi\/\">Let\u2019s Encrypt otomatik SSL<\/a> s\u00fcre\u00e7leri devreye girer. Klas\u00f6r yap\u0131s\u0131nda ise tek bir sertifika t\u00fcm dizinleri kapsar; y\u00f6netim daha basittir ama altyap\u0131sal ayr\u0131\u015ft\u0131rma yapman\u0131z zorla\u015f\u0131r.<\/p>\n<h3><span id=\"Cerezler_Oturumlar_ve_Login_Paylasimi\">\u00c7erezler, Oturumlar ve Login Payla\u015f\u0131m\u0131<\/span><\/h3>\n<p>Taray\u0131c\u0131 \u00e7erezleri (cookies), hangi alan ad\u0131nda set edildi\u011finize g\u00f6re \u00e7al\u0131\u015f\u0131r. \u00d6rne\u011fin:<\/p>\n<ul>\n<li><code>Domain=site.com<\/code> \u00e7erezi \u2192 <strong>site.com<\/strong> ve t\u00fcm alt alanlarda (blog.site.com, shop.site.com\u2026) ge\u00e7erli olabilir.<\/li>\n<li><code>Domain=blog.site.com<\/code> \u00e7erezi \u2192 sadece blog subdomain\u2019inde ge\u00e7erlidir.<\/li>\n<\/ul>\n<p>Bu neye etki eder?<\/p>\n<ul>\n<li>Tek oturum ile hem ana site hem ma\u011fazada login kalmak istiyorsan\u0131z; \u00e7erez domain\u2019ini ve mimariyi buna g\u00f6re tasarlamal\u0131s\u0131n\u0131z.<\/li>\n<li>G\u00fcvenlik gere\u011fi, admin paneli i\u00e7in ayr\u0131 subdomain kullan\u0131p \u00e7erezleri sadece orada ge\u00e7erli k\u0131labilirsiniz.<\/li>\n<\/ul>\n<p>Tek uygulamal\u0131 klas\u00f6r yap\u0131s\u0131nda (\u00f6rne\u011fin tek WordPress veya Laravel kurulumunda <code>\/blog<\/code>, <code>\/magaza<\/code> gibi) oturum payla\u015f\u0131m\u0131 do\u011fas\u0131 gere\u011fi daha basittir. Mikroservis veya farkl\u0131 teknoloji stack\u2019leri kullan\u0131yorsan\u0131z, subdomain taraf\u0131 y\u00f6netilebilirli\u011fi art\u0131r\u0131r.<\/p>\n<h3><span id=\"Loglama_Guvenlik_ve_Izleme\">Loglama, G\u00fcvenlik ve \u0130zleme<\/span><\/h3>\n<p>Subdomain tercih etti\u011finizde:<\/p>\n<ul>\n<li>Her alt alan ad\u0131n\u0131 ayr\u0131 sanal host olarak konumland\u0131rabilir, <strong>ayr\u0131 access\/error log<\/strong> tutabilirsiniz.<\/li>\n<li>WAF kurallar\u0131, rate limiting, IP k\u0131s\u0131tlamas\u0131 gibi g\u00fcvenlik politikalar\u0131n\u0131 alt alan baz\u0131nda ay\u0131rabilirsiniz.<\/li>\n<li>Uptime izleme, performans \u00f6l\u00e7\u00fcm\u00fc ve alarm kurallar\u0131n\u0131 her subdomain i\u00e7in ayr\u0131 ayr\u0131 yap\u0131land\u0131rabilirsiniz.<\/li>\n<\/ul>\n<p>Klas\u00f6r yap\u0131s\u0131nda da benzer gran\u00fclerlik m\u00fcmk\u00fcn; ancak genelde tek uygulama ve tek log ak\u0131\u015f\u0131 oldu\u011fu i\u00e7in sorun tespiti biraz daha emek ister. Y\u00fcksek trafikli yap\u0131larda, <a href=\"https:\/\/www.dchost.com\/blog\/vps-log-yonetimi-nasil-rayina-oturur-grafana-loki-promtail-ile-merkezi-loglama-tutma-sureleri-ve-alarm-kurallari\/\">merkezi loglama ve izleme<\/a> senaryolar\u0131nda subdomain segmentasyonu hayli i\u015fe yarar.<\/p>\n<h2><span id=\"SEO_Perspektifinden_Subdomain_mi_Klasor_mu\">SEO Perspektifinden Subdomain mi Klas\u00f6r m\u00fc?<\/span><\/h2>\n<p>Teknik taraf\u0131 bir kenara koyup SEO a\u00e7\u0131s\u0131ndan bakal\u0131m. Klasik \u00f6zet \u015f\u00f6yle anlat\u0131l\u0131r: \u201cGoogle subdomain\u2019i ayr\u0131 site gibi g\u00f6r\u00fcr, klas\u00f6r ise ana domainin par\u00e7as\u0131d\u0131r.\u201d Bu ifade hem do\u011fru hem eksik.<\/p>\n<h3><span id=\"Otorite_Backlink_ve_Domain_Gucu\">Otorite, Backlink ve Domain G\u00fcc\u00fc<\/span><\/h3>\n<p>SEO\u2019da kritik metriklerden biri, domain\u2019in genel otoritesidir (farkl\u0131 ara\u00e7larda farkl\u0131 isimlerle \u00f6l\u00e7\u00fcl\u00fcr). Genel kabul g\u00f6ren yakla\u015f\u0131m \u015fudur:<\/p>\n<ul>\n<li><strong>Klas\u00f6r:<\/strong> <code>site.com\/blog\/<\/code> \u00fczerinde \u00fcretti\u011finiz i\u00e7erik, backlink\u2019ler ve trafik; <strong>site.com\u2019un genel otoritesine<\/strong> daha do\u011fal ve h\u0131zl\u0131 katk\u0131 sa\u011flar.<\/li>\n<li><strong>Subdomain:<\/strong> <code>blog.site.com<\/code> daha ba\u011f\u0131ms\u0131z bir site gibi yorumlan\u0131r; otoritesini ayr\u0131 ayr\u0131 in\u015fa etmeniz gerekir, ancak yine de ana domainle ba\u011f g\u00fc\u00e7l\u00fc ise tamamen kopuk de\u011fildir.<\/li>\n<\/ul>\n<p>E\u011fer hedefiniz; markan\u0131z\u0131 tek domain alt\u0131nda g\u00fc\u00e7lendirmek ve blog\/icerik pazarlamas\u0131 ile ana domaini beslemekse, \u00e7o\u011fu senaryoda <strong>blog i\u00e7in klas\u00f6r<\/strong> (\u00f6rne\u011fin <code>site.com\/blog\/<\/code>) daha avantajl\u0131d\u0131r.<\/p>\n<h3><span id=\"Blog_Icin_Kural_Degil_Ama_Guclu_Bir_Tavsiye\">Blog \u0130\u00e7in: Kural De\u011fil Ama G\u00fc\u00e7l\u00fc Bir Tavsiye<\/span><\/h3>\n<p>Pratikte g\u00f6rd\u00fc\u011f\u00fcm\u00fcz \u015fu: Blog, dok\u00fcmantasyon, yard\u0131m merkezi gibi <strong>i\u00e7erik zenginli\u011fi<\/strong> sa\u011flayan kanallar\u0131 alt dizinde (klas\u00f6r) konumland\u0131ran siteler, uzun vadede ana domain otorisini beslemede daha net bir avantaj yakal\u0131yor. Yine de baz\u0131 durumlarda subdomain daha mant\u0131kl\u0131 olabilir:<\/p>\n<ul>\n<li>Blog tamamen farkl\u0131 bir teknoloji stack\u2019i ile \u00e7al\u0131\u015f\u0131yor (\u00f6rne\u011fin Ghost veya statik site), ana site bamba\u015fka bir framework \u00fczerinde.<\/li>\n<li>Blog ekibi ayr\u0131 bir altyap\u0131, deploy s\u00fcreci ve g\u00fcvenlik politikas\u0131 kullanmak istiyor.<\/li>\n<li>Farkl\u0131 diller i\u00e7in blog\u2019u co\u011frafi subdomain\u2019lere b\u00f6lmek istiyorsunuz (\u00f6r. <code>blog-en.site.com<\/code>).<\/li>\n<\/ul>\n<p>E\u011fer bu tip mimari ihtiya\u00e7lar yoksa, \u201cblogu klas\u00f6rde tutmak\u201d genellikle daha sade ve SEO a\u00e7\u0131s\u0131ndan daha verimli bir yoldur. Bu noktada; URL yap\u0131s\u0131 de\u011fi\u015fikli\u011fi yapacaksan\u0131z, <a href=\"https:\/\/www.dchost.com\/blog\/seo-kaybi-olmadan-url-yapisini-degistirmek-htaccess-ve-nginx-301-yonlendirme-rehberi\/\">SEO kayb\u0131 olmadan 301 y\u00f6nlendirme yapma rehberimize<\/a> mutlaka g\u00f6z atman\u0131z\u0131 \u00f6neririz.<\/p>\n<h3><span id=\"Magaza_Eticaret_Icin_Mimari_Tercihler\">Ma\u011faza (E\u2011ticaret) \u0130\u00e7in Mimari Tercihler<\/span><\/h3>\n<p>Ma\u011faza taraf\u0131 biraz daha kritik, \u00e7\u00fcnk\u00fc:<\/p>\n<ul>\n<li>Performans bask\u0131s\u0131 daha y\u00fcksektir (\u00fcr\u00fcn listeleme, filtre, sepet, \u00f6deme).<\/li>\n<li>G\u00fcvenlik, PCI-DSS uyumu, \u00f6deme sayfalar\u0131 gibi ek gereksinimler vard\u0131r.<\/li>\n<li>\u00d6zel bir altyap\u0131 ve \u00f6l\u00e7eklenebilirlik ihtiyac\u0131 do\u011far.<\/li>\n<\/ul>\n<p>Senaryolar:<\/p>\n<ol>\n<li><strong>K\u00fc\u00e7\u00fck\/orta \u00f6l\u00e7ekli ma\u011faza + kurumsal site:<\/strong> Ana domain WordPress kurumsal site, ma\u011faza WooCommerce veya basit bir e-ticaret eklentisi ise <code>site.com\/magaza\/<\/code> veya <code>site.com\/shop\/<\/code> klas\u00f6r yap\u0131s\u0131 genellikle idealdir. SEO a\u00e7\u0131s\u0131ndan t\u00fcm otorite tek domain \u00fczerinde toplan\u0131r.<\/li>\n<li><strong>B\u00fcy\u00fck katalog, y\u00fcksek trafik:<\/strong> Ma\u011faza motoru (Magento, \u00f6zel yaz\u0131l\u0131m vb.) i\u00e7in ayr\u0131 bir altyap\u0131, veritaban\u0131 replikasyonu, cache katman\u0131 kurgulamak istiyorsan\u0131z <strong>shop.site.com<\/strong> gibi ayr\u0131 bir subdomain\u2019e ta\u015f\u0131mak operasyonel olarak i\u015fleri kolayla\u015ft\u0131rabilir. Burada SEO kayb\u0131 ya\u015famamak i\u00e7in 301 ve i\u00e7erik stratejisi hayati \u00f6nem ta\u015f\u0131r.<\/li>\n<\/ol>\n<p>\u00d6zetle: \u201cMa\u011faza kesinlikle subdomain olmal\u0131\u201d ya da \u201cmutlaka klas\u00f6r olmal\u0131\u201d diye evrensel bir kural yok. Tercih; b\u00fcy\u00fckl\u00fck, teknoloji seti ve g\u00fcvenlik\/reg\u00fclasyon ihtiya\u00e7lar\u0131na g\u00f6re de\u011fi\u015fmelidir.<\/p>\n<h3><span id=\"Landing_Page_ve_Kampanya_Sayfalari\">Landing Page ve Kampanya Sayfalar\u0131<\/span><\/h3>\n<p>Landing page\u2019ler (\u00f6zellikle reklam ve k\u0131sa s\u00fcreli kampanyalar i\u00e7in) \u00e7o\u011fu zaman h\u0131zl\u0131 kurulup h\u0131zl\u0131 kapanan yap\u0131lard\u0131r. Burada iki ana se\u00e7enek \u00e7\u0131kar:<\/p>\n<ul>\n<li><strong>Klas\u00f6r:<\/strong> <code>site.com\/kampanya\/yeni-urun\/<\/code><\/li>\n<li><strong>Subdomain:<\/strong> <code>yeni-urun.site.com<\/code><\/li>\n<\/ul>\n<p>SEO a\u011f\u0131rl\u0131kl\u0131, uzun vadeli bir sayfa ise genelde klas\u00f6r kullanmak daha mant\u0131kl\u0131d\u0131r. Ama pazarlama ekibi farkl\u0131 bir tasar\u0131m sistemi, farkl\u0131 bir Javascript framework\u2019\u00fc ve A\/B test altyap\u0131s\u0131 kurmak istiyorsa, landing page\u2019leri <strong>ayr\u0131 bir subdomain<\/strong> alt\u0131nda toparlamak (\u00f6rn. <code>campaign.site.com<\/code>) daha y\u00f6netilebilir hale gelebilir.<\/p>\n<h3><span id=\"Uluslararasi_SEO_Dil_Surumleri_ve_Hreflang\">Uluslararas\u0131 SEO, Dil S\u00fcr\u00fcmleri ve Hreflang<\/span><\/h3>\n<p>Farkl\u0131 diller ve \u00fclkeler i\u00e7in \u00e7ok say\u0131da blog, ma\u011faza ve landing page y\u00f6netiyorsan\u0131z, konu daha da karma\u015f\u0131kla\u015f\u0131r. ccTLD (\u00fclke uzant\u0131s\u0131), subdomain ve alt dizin kombinasyonlar\u0131n\u0131 do\u011fru kurgulamak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/hreflangi-dogru-kurmanin-sirlari-cctld-alt-dizin-alt-alan-ve-x-default-ile-uluslararasi-seoyu-rayina-oturt\/\">hreflang\u2019i do\u011fru kurma rehberimize<\/a> mutlaka g\u00f6z at\u0131n. Orada; ccTLD, alt dizin ve alt alan se\u00e7eneklerinin uluslararas\u0131 SEO\u2019ya etkilerini detayland\u0131rd\u0131k.<\/p>\n<h2><span id=\"Hosting_Mimarisi_ve_Yonetim_Acisindan_Etkiler\">Hosting Mimarisi ve Y\u00f6netim A\u00e7\u0131s\u0131ndan Etkiler<\/span><\/h2>\n<p>SEO taraf\u0131n\u0131 bir kenara b\u0131rak\u0131p, i\u015fin operasyonel boyutuna bakal\u0131m. DCHost taraf\u0131nda g\u00fcnl\u00fck olarak g\u00f6rd\u00fc\u011f\u00fcm\u00fcz en yayg\u0131n karar noktas\u0131 \u015fu: \u201cT\u00fcm siteyi tek hosting hesab\u0131nda m\u0131 toplayal\u0131m, yoksa blog, ma\u011faza ve kampanyalar\u0131 farkl\u0131 sunuculara m\u0131 da\u011f\u0131tal\u0131m?\u201d<\/p>\n<h3><span id=\"Paylasimli_Hosting_Basit_Projeler_Icin_Klasor_Avantaji\">Payla\u015f\u0131ml\u0131 Hosting: Basit Projeler \u0130\u00e7in Klas\u00f6r Avantaj\u0131<\/span><\/h3>\n<p>K\u00fc\u00e7\u00fck i\u015fletmeler, ki\u015fisel bloglar ve basit katalog siteleri i\u00e7in <strong>payla\u015f\u0131ml\u0131 hosting<\/strong> halen olduk\u00e7a mant\u0131kl\u0131. Bu senaryoda:<\/p>\n<ul>\n<li>Tek bir cPanel\/DirectAdmin hesab\u0131n\u0131z vard\u0131r.<\/li>\n<li>Root SSH eri\u015fimi genelde yoktur.<\/li>\n<li>Tek uygulama (\u00f6rne\u011fin WordPress) ile hem kurumsal siteyi, hem blogu, hem ma\u011fazay\u0131 y\u00fcr\u00fctmek istersiniz.<\/li>\n<\/ul>\n<p>Bu durumda ayr\u0131 ayr\u0131 subdomain + ayr\u0131 uygulama kurmak, y\u00f6netim y\u00fck\u00fcn\u00fc art\u0131r\u0131r. Klas\u00f6r yap\u0131s\u0131 (\u00f6rn. <code>\/blog<\/code>, <code>\/magaza<\/code>) hem maliyet hem operasyon a\u00e7\u0131s\u0131ndan daha hafif olur. Payla\u015f\u0131ml\u0131 hosting\u2019te kaynaklar\u0131 do\u011fru kullanmak i\u00e7in <a href=\"https:\/\/www.dchost.com\/blog\/cpanelde-kaynak-limitleri-cpu-io-ep-ram-ve-resource-limit-reached-hatasi\/\">cPanel kaynak limitleri<\/a> ve <a href=\"https:\/\/www.dchost.com\/blog\/paylasimli-hostingde-resource-limit-reached-hatasini-onlemek\/\">Resource Limit Reached hatas\u0131n\u0131 \u00f6nleme<\/a> yaz\u0131lar\u0131m\u0131z\u0131 da inceleyebilirsiniz.<\/p>\n<h3><span id=\"VPS_ve_Dedicated_Sunucular_Ayri_Uygulamalar_Ayri_Subdomainler\">VPS ve Dedicated Sunucular: Ayr\u0131 Uygulamalar, Ayr\u0131 Subdomain\u2019ler<\/span><\/h3>\n<p>Projeler b\u00fcy\u00fcd\u00fck\u00e7e; blog, ma\u011faza ve uygulama panellerini <strong>farkl\u0131 servisler<\/strong> haline getirmek \u00e7o\u011fu zaman zorunlu hale gelir. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Blog: WordPress (PHP, MySQL)<\/li>\n<li>Ma\u011faza: Laravel + Vue.js tabanl\u0131 \u00f6zel uygulama<\/li>\n<li>Landing page: statik HTML + Tailwind + k\u00fc\u00e7\u00fck bir Node.js API<\/li>\n<\/ul>\n<p>Bu yap\u0131y\u0131 tek domain alt\u0131nda tek sunucuda zorlamak yerine, her bile\u015feni ayr\u0131 bir VPS veya dedicated sunucuya da\u011f\u0131t\u0131p <strong>subdomain ile y\u00f6nlendirmek<\/strong> \u00e7ok daha sa\u011fl\u0131kl\u0131d\u0131r. B\u00f6ylece:<\/p>\n<ul>\n<li>CPU\/RAM disk kotalar\u0131n\u0131 her servis i\u00e7in ayr\u0131 ayr\u0131 planlars\u0131n\u0131z.<\/li>\n<li>Bak\u0131m ve deploy s\u00fcre\u00e7lerinde (\u00f6rne\u011fin blog g\u00fcncellemesi) ma\u011fazay\u0131 etkilemezsiniz.<\/li>\n<li>G\u00fcvenlik a\u00e7\u0131\u011f\u0131 veya DDoS sald\u0131r\u0131s\u0131 bir servisi hedef ald\u0131\u011f\u0131nda di\u011ferleri etkilenmez.<\/li>\n<\/ul>\n<p>B\u00fcy\u00fck ajans veya \u00e7ok siteli yap\u0131larda bu konuyu daha geni\u015f ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/ajanslar-ve-freelancerlar-icin-hosting-mimarisi-20-wordpress-sitesini-tek-altyapida-guvenle-yonetmek\/\">ajanslar i\u00e7in hosting mimarisi rehberinde<\/a> de, subdomain + \u00e7oklu sunucu yakla\u015f\u0131m\u0131n\u0131n pratik avantajlar\u0131n\u0131 bulabilirsiniz.<\/p>\n<h3><span id=\"Colocation_ve_Karmasik_Altyapilar\">Colocation ve Karma\u015f\u0131k Altyap\u0131lar<\/span><\/h3>\n<p>Kendi fiziksel sunucular\u0131n\u0131 veri merkezinde bar\u0131nd\u0131ran (colocation) veya karma\u015f\u0131k cluster mimarileri kullanan yap\u0131larda subdomain, <strong>servis s\u0131n\u0131rlar\u0131n\u0131<\/strong> tan\u0131mlamak i\u00e7in adeta bir harita i\u015flevi g\u00f6r\u00fcr:<\/p>\n<ul>\n<li><code>api.site.com<\/code> \u2192 API k\u00fcmesi<\/li>\n<li><code>shop.site.com<\/code> \u2192 e-ticaret front-end<\/li>\n<li><code>cdn.site.com<\/code> \u2192 statik dosya\/medya sunucular\u0131<\/li>\n<li><code>panel.site.com<\/code> \u2192 y\u00f6netim paneli<\/li>\n<\/ul>\n<p>Bu sayede; a\u011f topolojisi, firewall kurallar\u0131, load balancer konfig\u00fcrasyonlar\u0131 ve log\/izleme sistemleri de bu alt alan adlar\u0131 \u00fczerinden net bir \u015fekilde tan\u0131mlan\u0131r. DCHost\u2019ta colocation veya y\u00fcksek eri\u015filebilirlik senaryolar\u0131 kurgularken, subdomain hiyerar\u015fisini bu g\u00f6zle tasarlamay\u0131 \u00f6neriyoruz.<\/p>\n<h2><span id=\"CDN_Medya_ve_Performans_Boyutu\">CDN, Medya ve Performans Boyutu<\/span><\/h2>\n<p>Blog, ma\u011faza ve landing page\u2019lerin performans\u0131n\u0131 konu\u015furken; CDN (Content Delivery Network), statik dosyalar ve g\u00f6rsel optimizasyonu g\u00f6z ard\u0131 etmek m\u00fcmk\u00fcn de\u011fil. \u00d6zellikle <strong>Core Web Vitals<\/strong> metriklerini iyile\u015ftirmek istiyorsan\u0131z, alt alan adlar\u0131 burada stratejik bir rol oynuyor.<\/p>\n<h3><span id=\"Statik_Dosyalar_Icin_Ayri_Subdomain_Kullanmak\">Statik Dosyalar \u0130\u00e7in Ayr\u0131 Subdomain Kullanmak<\/span><\/h3>\n<p>Geleneksel yakla\u015f\u0131m, statik i\u00e7erikleri (g\u00f6rseller, CSS, JS) <strong>cdn.site.com<\/strong> gibi ayr\u0131 bir subdomain \u00fczerinden servis etmektir. Bunun baz\u0131 avantajlar\u0131:<\/p>\n<ul>\n<li>Taray\u0131c\u0131ya \u201cbu alan sadece statik i\u00e7erik\u201d sinyali verilir; \u00e7erez y\u00fck\u00fc azal\u0131r.<\/li>\n<li>CDN\u2019ler genelde alt alan \u00fczerinden konumland\u0131r\u0131ld\u0131\u011f\u0131 i\u00e7in konfig\u00fcrasyon basitle\u015fir.<\/li>\n<li>Statik dosyalar\u0131 farkl\u0131 bir sunucu veya object storage \u00fczerinde tutup ana sunucunun y\u00fck\u00fcn\u00fc azaltabilirsiniz.<\/li>\n<\/ul>\n<p>\u00d6zellikle g\u00f6rsel a\u011f\u0131rl\u0131kl\u0131 sitelerde bu konuyu <a href=\"https:\/\/www.dchost.com\/blog\/gorsel-seo-ve-hosting-altyapisi-webp-avif-cdn-alt-alan-adlari-ve-gorsel-site-haritasi\/\">g\u00f6rsel SEO ve CDN alt alan adlar\u0131<\/a> yaz\u0131m\u0131zda detayland\u0131rd\u0131k. Burada; WebP\/AVIF d\u00f6n\u00fc\u015f\u00fcm\u00fc, g\u00f6rsel site haritalar\u0131 ve alt alan stratejisinin arama motoru trafi\u011fine do\u011frudan etkilerini bulabilirsiniz.<\/p>\n<h3><span id=\"CDN_Cografi_Yayilim_ve_Cok_Bolgeli_Mimari\">CDN, Co\u011frafi Yay\u0131l\u0131m ve \u00c7ok B\u00f6lgeli Mimari<\/span><\/h3>\n<p>Kullan\u0131c\u0131lar\u0131n\u0131z farkl\u0131 \u00fclkelerden geliyorsa, sadece tek sunucu \u00fczerinde durmak yerine <strong>CDN + \u00e7ok b\u00f6lgeli DNS<\/strong> stratejilerini d\u00fc\u015f\u00fcnmek gerekir. Statik i\u00e7erikleri subdomain \u00fczerinden CDN\u2019e vermek; hem yap\u0131land\u0131rmay\u0131 sadele\u015ftirir, hem de ileride \u00e7ok b\u00f6lgeli mimariye ge\u00e7mek istedi\u011finizde i\u015finizi kolayla\u015ft\u0131r\u0131r.<\/p>\n<p>Bu konuda iki yaz\u0131m\u0131z do\u011frudan i\u015finize yarayacakt\u0131r:<\/p>\n<ul>\n<li><a href=\"https:\/\/www.dchost.com\/blog\/cdn-nedir-ne-zaman-gerekir-trafik-ve-lokasyona-gore-karar-rehberi\/\">CDN nedir, ne zaman gerekir?<\/a> \u2013 CDN\u2019e ger\u00e7ekten ihtiyac\u0131n\u0131z olup olmad\u0131\u011f\u0131n\u0131 anlamak i\u00e7in karar rehberi.<\/li>\n<li><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> \u2013 Farkl\u0131 b\u00f6lgelerdeki kullan\u0131c\u0131lar\u0131 en yak\u0131n sunucuya y\u00f6nlendirme stratejileri.<\/li>\n<\/ul>\n<p>Blog, ma\u011faza ve landing page\u2019lerinizi farkl\u0131 subdomain\u2019lere da\u011f\u0131t\u0131yor olman\u0131z, CDN kurgusunu da esnekle\u015ftirir. \u00d6rne\u011fin sadece <code>cdn.site.com<\/code> ve <code>img.site.com<\/code> i\u00e7in CDN a\u00e7\u0131p, dinamik uygulamalar\u0131 do\u011frudan origin sunucudan servis edebilirsiniz.<\/p>\n<h3><span id=\"Core_Web_Vitals_ve_URL_Mimarisi\">Core Web Vitals ve URL Mimarisi<\/span><\/h3>\n<p>Google\u2019\u0131n Core Web Vitals metrikleri (TTFB, LCP, CLS vb.) art\u0131k s\u0131ralama fakt\u00f6rleri aras\u0131nda. URL mimariniz, bu metrikleri do\u011frudan etkilemez; ama altyap\u0131 tasar\u0131m\u0131n\u0131z\u0131 etkiledi\u011fi i\u00e7in dolayl\u0131 yoldan b\u00fcy\u00fck rol oynar. \u00d6rne\u011fin:<\/p>\n<ul>\n<li>Blogu alt dizinde tutup tek g\u00fc\u00e7l\u00fc VPS\u2019te ko\u015fturmak, TTFB\u2019yi d\u00fc\u015f\u00fcrmenize yard\u0131mc\u0131 olabilir.<\/li>\n<li>Ma\u011fazay\u0131 ayr\u0131 subdomain\u2019de ayr\u0131 bir optimizasyon seti ile \u00e7al\u0131\u015ft\u0131rmak, checkout performans\u0131n\u0131 iyile\u015ftirebilir.<\/li>\n<li>G\u00f6rselleri CDN alt alan\u0131na ta\u015f\u0131yarak LCP\u2019yi anlaml\u0131 \u00f6l\u00e7\u00fcde d\u00fc\u015f\u00fcrebilirsiniz.<\/li>\n<\/ul>\n<p>Bu konular\u0131 daha teknik seviyede ele ald\u0131\u011f\u0131m\u0131z <a href=\"https:\/\/www.dchost.com\/blog\/core-web-vitals-ve-hosting-altyapisi-ttfb-lcp-ve-clsyi-sunucu-tarafinda-iyilestirme-rehberi\/\">Core Web Vitals ve hosting altyap\u0131s\u0131 rehberini<\/a> de okuman\u0131z\u0131 \u00f6neririm.<\/p>\n<h2><span id=\"Farkli_Senaryolar_Icin_Karar_Modelleri\">Farkl\u0131 Senaryolar \u0130\u00e7in Karar Modelleri<\/span><\/h2>\n<p>Teoriyi bir kenara b\u0131rak\u0131p, pratik senaryolar \u00fczerinden ilerleyelim. A\u015fa\u011f\u0131daki \u00f6rnekler; DCHost\u2019ta s\u0131k kar\u015f\u0131la\u015ft\u0131\u011f\u0131m\u0131z durumlar\u0131n sadele\u015ftirilmi\u015f \u00f6zetleri.<\/p>\n<h3><span id=\"1_Kucuk_Isletme_Kurumsal_Site_Blog\">1) K\u00fc\u00e7\u00fck \u0130\u015fletme: Kurumsal Site + Blog<\/span><\/h3>\n<p><strong>Durum:<\/strong> Tek dilde web sitesi, referanslar, hizmetler ve d\u00fczenli i\u00e7erik \u00fcreten bir blog. Trafik orta d\u00fczey, tek ekibiniz var.<\/p>\n<ul>\n<li><strong>\u00d6neri:<\/strong> Kurumsal site ve blogu tek WordPress kurulumu alt\u0131nda <code>site.com\/blog\/<\/code> olarak kullan\u0131n.<\/li>\n<li><strong>Hosting:<\/strong> G\u00fc\u00e7l\u00fc bir payla\u015f\u0131ml\u0131 hosting plan\u0131 veya k\u00fc\u00e7\u00fck\/orta kaynakl\u0131 bir VPS yeterli olur.<\/li>\n<li><strong>SEO:<\/strong> T\u00fcm i\u00e7erik otoriteyi <strong>site.com<\/strong> \u00fczerinde toplar.<\/li>\n<\/ul>\n<p>Burada subdomain a\u00e7mak genellikle gereksiz karma\u015f\u0131kl\u0131k yarat\u0131r. Sadece staging veya test ortam\u0131 i\u00e7in <code>staging.site.com<\/code> gibi subdomain\u2019ler kullanmak mant\u0131kl\u0131d\u0131r.<\/p>\n<h3><span id=\"2_Buyuyen_ETicaret_Kurumsal_Site_Buyuk_Magaza\">2) B\u00fcy\u00fcyen E\u2011Ticaret: Kurumsal Site + B\u00fcy\u00fck Ma\u011faza<\/span><\/h3>\n<p><strong>Durum:<\/strong> Markan\u0131z g\u00fc\u00e7lenmi\u015f, \u00fcr\u00fcn gam\u0131 b\u00fcy\u00fcm\u00fc\u015f, ma\u011faza yaz\u0131l\u0131m\u0131 ayr\u0131 bir ekip taraf\u0131ndan geli\u015ftiriliyor. Y\u00fcksek say\u0131da \u00fcr\u00fcn, filtreleme, kampanya ve yo\u011fun kampanya d\u00f6nemleri var.<\/p>\n<ul>\n<li><strong>\u00d6neri (ba\u015flang\u0131\u00e7):<\/strong> Ma\u011fazay\u0131 <code>site.com\/magaza\/<\/code> alt\u0131nda ba\u015flatmak; SEO otoritesi i\u00e7in avantajl\u0131d\u0131r.<\/li>\n<li><strong>\u00d6neri (\u00f6l\u00e7eklenme a\u015famas\u0131):<\/strong> Trafik ve kaynak ihtiyac\u0131 ciddi \u015fekilde artmaya ba\u015flad\u0131\u011f\u0131nda, ma\u011fazay\u0131 <code>shop.site.com<\/code> gibi ayr\u0131 bir subdomain\u2019e ta\u015f\u0131y\u0131p; kendi VPS veya dedicated sunucusuna almak mant\u0131kl\u0131 hale gelir.<\/li>\n<li><strong>Dikkat:<\/strong> Ge\u00e7i\u015fte 301 y\u00f6nlendirme, canonical etiketleri ve site haritalar\u0131n\u0131 titizlikle g\u00fcncellemek gerekir.<\/li>\n<\/ul>\n<p>Burada; PCI-DSS gibi reg\u00fclasyon, log saklama politikalar\u0131 ve performans hedeflerine g\u00f6re <a href=\"https:\/\/www.dchost.com\/blog\/pci-dss-uyumlu-e-ticaret-hosting-rehberi\/\">PCI-DSS uyumlu e-ticaret hosting rehberinde<\/a> anlatt\u0131\u011f\u0131m\u0131z ilkeleri de devreye almak gerekir.<\/p>\n<h3><span id=\"3_SaaS_Urunu_Uygulama_Marketing_Site_Blog_Landing_Page\">3) SaaS \u00dcr\u00fcn\u00fc: Uygulama + Marketing Site + Blog + Landing Page<\/span><\/h3>\n<p><strong>Durum:<\/strong> Ana \u00fcr\u00fcn\u00fcn\u00fcz SaaS; React\/SPA + API altyap\u0131s\u0131 \u00fczerinde \u00e7al\u0131\u015f\u0131yor. Bunun yan\u0131nda pazarlama sitesi, blog ve \u00e7ok say\u0131da kampanya landing page\u2019iniz var.<\/p>\n<p>Bu tarz yap\u0131larda, s\u0131k g\u00f6rd\u00fc\u011f\u00fcm\u00fcz ba\u015far\u0131l\u0131 mimari \u015f\u00f6yle:<\/p>\n<ul>\n<li><code>site.com<\/code> \u2192 Marketing site (WordPress veya statik site)<\/li>\n<li><code>app.site.com<\/code> \u2192 Uygulama<\/li>\n<li><code>blog.site.com<\/code> veya <code>site.com\/blog\/<\/code> \u2192 Blog (karar\u0131 SEO stratejinize g\u00f6re verin)<\/li>\n<li><code>go.site.com<\/code> veya <code>campaign.site.com<\/code> \u2192 Landing page ve izleme\/redirect altyap\u0131s\u0131<\/li>\n<\/ul>\n<p>Burada kritik nokta, <strong>oturum ve g\u00fcvenlik s\u0131n\u0131rlar\u0131n\u0131<\/strong> net \u00e7izmektir. Uygulama taraf\u0131nda authentication \u00e7erezlerini sadece <code>app.site.com<\/code> alan\u0131nda ge\u00e7erli tutmak, marketing ve kampanya taraf\u0131n\u0131 tamamen izole etmek genellikle en iyi uygulamad\u0131r.<\/p>\n<h3><span id=\"4_Cok_Dilli_Kurumsal_Site_Blog_Bolgesel_Landing_Pageler\">4) \u00c7ok Dilli Kurumsal Site + Blog + B\u00f6lgesel Landing Page\u2019ler<\/span><\/h3>\n<p><strong>Durum:<\/strong> Birden fazla dilde i\u00e7erik, b\u00f6lgesel kampanyalar ve her \u00fclke i\u00e7in ayr\u0131 landing page\u2019leriniz var.<\/p>\n<ul>\n<li>Dil s\u00fcr\u00fcmlerini alt dizinlerle y\u00f6netmek: <code>site.com\/tr\/<\/code>, <code>site.com\/en\/<\/code>, <code>site.com\/de\/<\/code><\/li>\n<li>Bloglar\u0131 dil dizinleri alt\u0131nda konumland\u0131rmak: <code>site.com\/en\/blog\/<\/code>, <code>site.com\/de\/blog\/<\/code><\/li>\n<li>B\u00f6lgesel landing page\u2019leri ilgili dil dizini i\u00e7inde tutmak: <code>site.com\/tr\/kampanyalar\/<\/code><\/li>\n<\/ul>\n<p>Bu yakla\u015f\u0131m; hreflang, canonical ve site haritas\u0131 y\u00f6netimini sadele\u015ftirir. E\u011fer her \u00fclke i\u00e7in ayr\u0131 ekip, ayr\u0131 altyap\u0131 veya yerel reg\u00fclasyon gereksinimleri varsa; o zaman \u00fclke bazl\u0131 subdomain veya ccTLD stratejisine ge\u00e7mek de\u011ferlendirilebilir.<\/p>\n<h2><span id=\"Uygulanabilir_Kontrol_Listesi_ve_Ozet\">Uygulanabilir Kontrol Listesi ve \u00d6zet<\/span><\/h2>\n<p>Karar\u0131 verirken elinizde net bir checklist olsun istiyorsan\u0131z, a\u015fa\u011f\u0131daki sorular\u0131 tek tek yan\u0131tlay\u0131n. \u00c7o\u011funa \u201cevet\u201d diyorsan\u0131z, o madde sizi subdomain veya klas\u00f6r y\u00f6n\u00fcne iter.<\/p>\n<h3><span id=\"Klasor_Alt_Dizin_Tercihini_Guclendiren_Sorular\">Klas\u00f6r (Alt Dizin) Tercihini G\u00fc\u00e7lendiren Sorular<\/span><\/h3>\n<ul>\n<li>Blog\/ma\u011faza\/landing page\u2019lerinizin <strong>hepsi ayn\u0131 ekip<\/strong> taraf\u0131ndan m\u0131 y\u00f6netiliyor?<\/li>\n<li>Hepsi <strong>ayn\u0131 teknoloji<\/strong> \u00fczerinde mi (\u00f6rne\u011fin tek WordPress, tek Laravel monolit)?<\/li>\n<li>SEO a\u00e7\u0131s\u0131ndan <strong>t\u00fcm otoriteyi tek domain \u00fczerinde<\/strong> toplamak kritik mi?<\/li>\n<li>Payla\u015f\u0131ml\u0131 hosting gibi <strong>basit ve ekonomik<\/strong> bir mimari kullanmak istiyor musunuz?<\/li>\n<li>Uygulamalar aras\u0131nda kompleks oturum payla\u015f\u0131mlar\u0131 veya mikroservis mimarisi yok mu?<\/li>\n<\/ul>\n<p>Bu sorular\u0131n \u00e7o\u011funa \u201cevet\u201d diyorsan\u0131z; blog, ma\u011faza ve landing page\u2019leri <strong>alt dizin<\/strong> olarak konumland\u0131rmak (\u00f6rne\u011fin <code>site.com\/blog\/<\/code>, <code>site.com\/magaza\/<\/code>, <code>site.com\/kampanya\/<\/code>) genellikle daha sa\u011fl\u0131kl\u0131 olacakt\u0131r.<\/p>\n<h3><span id=\"Subdomain_Tercihini_Guclendiren_Sorular\">Subdomain Tercihini G\u00fc\u00e7lendiren Sorular<\/span><\/h3>\n<ul>\n<li>Blog, ma\u011faza ve uygulamalar\u0131n\u0131z <strong>farkl\u0131 teknolojiler<\/strong> veya framework\u2019ler mi kullan\u0131yor?<\/li>\n<li>Her birini farkl\u0131 VPS, dedicated veya colocation altyap\u0131s\u0131nda <strong>ayr\u0131 ayr\u0131 \u00f6l\u00e7eklendirmek<\/strong> istiyor musunuz?<\/li>\n<li>Her alt alan i\u00e7in <strong>farkl\u0131 g\u00fcvenlik politikalar\u0131<\/strong> (WAF kurallar\u0131, IP k\u0131s\u0131tlamas\u0131, mTLS, vs.) m\u0131 gerekli?<\/li>\n<li>G\u00f6rsellere, statik i\u00e7eriklere veya API\u2019lere \u00f6zel <strong>CDN ve cache politikalar\u0131<\/strong> tan\u0131mlamak istiyor musunuz?<\/li>\n<li>Tak\u0131mlar\u0131n\u0131z ve deploy s\u00fcre\u00e7leriniz birbirinden ba\u011f\u0131ms\u0131z m\u0131 (\u00f6rne\u011fin \u00fcr\u00fcn ekibi, marketing ekibi, altyap\u0131 ekibi ayr\u0131)?<\/li>\n<\/ul>\n<p>Bu sorular\u0131n \u00e7o\u011funa \u201cevet\u201d diyorsan\u0131z; blog, ma\u011faza ve landing page\u2019ler i\u00e7in <strong>subdomain tabanl\u0131 bir hiyerar\u015fi<\/strong> (\u00f6rne\u011fin <code>blog.site.com<\/code>, <code>shop.site.com<\/code>, <code>campaign.site.com<\/code>) mimari olarak daha s\u00fcrd\u00fcr\u00fclebilir olacakt\u0131r.<\/p>\n<h3><span id=\"Son_Soz_ve_DCHost_Tarafinda_Nasil_Ilerleyebilirsiniz\">Son S\u00f6z ve DCHost Taraf\u0131nda Nas\u0131l \u0130lerleyebilirsiniz?<\/span><\/h3>\n<p>Subdomain mi klas\u00f6r m\u00fc sorusunun tek bir do\u011fru cevab\u0131 yok; do\u011fru olan, <strong>i\u015f hedefleriniz, ekip yap\u0131n\u0131z ve teknik altyap\u0131n\u0131zla uyumlu karar<\/strong>. K\u00fc\u00e7\u00fck bir blog i\u00e7in alt dizin yeterli olurken, b\u00fcy\u00fcyen bir SaaS i\u00e7in subdomain\u2019lerle ayr\u0131lm\u0131\u015f \u00e7ok katmanl\u0131 bir mimari \u015fart hale gelebilir.<\/p>\n<p>DCHost olarak; basit kurumsal sitelerden, y\u00fcksek trafikli e\u2011ticaret ve SaaS projelerine kadar geni\u015f bir yelpazede <strong>payla\u015f\u0131ml\u0131 hosting, VPS, dedicated ve colocation<\/strong> altyap\u0131lar\u0131 sunuyoruz. Yeni bir proje planl\u0131yor ya da mevcut yap\u0131n\u0131z\u0131 subdomain\/klas\u00f6r ekseninde yeniden tasarlamay\u0131 d\u00fc\u015f\u00fcn\u00fcyorsan\u0131z, mimari tasar\u0131m a\u015famas\u0131nda birka\u00e7 saatlik do\u011fru planlaman\u0131n size aylarca s\u00fcrecek sorunlar\u0131 \u00f6nleyebilece\u011fini rahatl\u0131kla s\u00f6yleyebilirim.<\/p>\n<p>\u0130sterseniz mevcut URL yap\u0131n\u0131z\u0131, SEO risklerini, hosting ve CDN konfig\u00fcrasyonunuzu birlikte g\u00f6zden ge\u00e7irip; blog, ma\u011faza ve landing page\u2019leriniz i\u00e7in en dengeli mimariyi netle\u015ftirebiliriz. B\u00f6ylece hem arama motoru g\u00f6r\u00fcn\u00fcrl\u00fc\u011f\u00fcn\u00fcz\u00fc, hem de altyap\u0131 esnekli\u011finizi uzun vadeli bir plana oturtmu\u015f olursunuz.<\/p>\n<\/div>","protected":false},"excerpt":{"rendered":"<p>\u0130&ccedil;indekiler1 Neyi Nereye Koydu\u011funuz Neden Bu Kadar \u00d6nemli?2 Subdomain ve Klas\u00f6r\u00fcn Teknik Farklar\u01312.1 DNS, SSL ve Bar\u0131nd\u0131rma Ayr\u0131m\u01312.2 \u00c7erezler, Oturumlar ve Login Payla\u015f\u0131m\u01312.3 Loglama, G\u00fcvenlik ve \u0130zleme3 SEO Perspektifinden Subdomain mi Klas\u00f6r m\u00fc?3.1 Otorite, Backlink ve Domain G\u00fcc\u00fc3.2 Blog \u0130\u00e7in: Kural De\u011fil Ama G\u00fc\u00e7l\u00fc Bir Tavsiye3.3 Ma\u011faza (E\u2011ticaret) \u0130\u00e7in Mimari Tercihler3.4 Landing Page ve Kampanya [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":3972,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[26],"tags":[],"class_list":["post-3971","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\/3971","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=3971"}],"version-history":[{"count":0,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/posts\/3971\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media\/3972"}],"wp:attachment":[{"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/media?parent=3971"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/categories?post=3971"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.dchost.com\/blog\/wp-json\/wp\/v2\/tags?post=3971"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}