{"id":38814,"date":"2026-02-08T12:40:55","date_gmt":"2026-02-08T09:40:55","guid":{"rendered":"https:\/\/fatihsoysal.com\/blog\/?p=38814"},"modified":"2026-02-08T12:40:55","modified_gmt":"2026-02-08T09:40:55","slug":"wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber","status":"publish","type":"post","link":"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/","title":{"rendered":"www’den Non-www’ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber"},"content":{"rendered":"

<\/p>\n

www’den Non-www’ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber<\/h2>\n

Web sitenizi yay\u0131nlarken, alan ad\u0131n\u0131z\u0131n “www” \u00f6n eki ile mi yoksa onsuz mu eri\u015filebilir olaca\u011f\u0131 karar\u0131, teknik bir tercih olmaktan \u00f6te, sitenizin arama motorlar\u0131ndaki performans\u0131 ve kullan\u0131c\u0131 deneyimi a\u00e7\u0131s\u0131ndan kritik bir \u00f6neme sahiptir. \u00d6rne\u011fin, www.example.com<\/code> ve example.com<\/code> teknik olarak iki farkl\u0131 URL olarak kabul edilir. Bu durum, arama motorlar\u0131 i\u00e7in “yinelenen i\u00e7erik” (duplicate content) sorununa yol a\u00e7abilir ve sitenizin SEO s\u0131ralamas\u0131n\u0131 olumsuz etkileyebilir. Bu nedenle, web sitenizin tek bir tercih edilen URL \u00fczerinden eri\u015filebilir olmas\u0131n\u0131 sa\u011flamak amac\u0131yla birinden di\u011ferine y\u00f6nlendirme yapmak elzemdir.<\/p>\n

Bu kapsaml\u0131 rehberde, Ubuntu 14.04 i\u015fletim sistemi \u00fczerinde \u00e7al\u0131\u015fan Apache web sunucusunu kullanarak www.example.com<\/code> adresinden example.com<\/code> adresine (yani “www” \u00f6n ekinden “non-www” \u00f6n ekine) nas\u0131l y\u00f6nlendirme yapaca\u011f\u0131n\u0131z\u0131 ad\u0131m ad\u0131m a\u00e7\u0131klayaca\u011f\u0131z. Farkl\u0131 senaryolar\u0131, \u00f6zellikle de HTTPS (SSL\/TLS) kullan\u0131m\u0131n\u0131 da ele alarak, en do\u011fru ve SEO dostu y\u00f6nlendirme y\u00f6ntemlerini sunaca\u011f\u0131z.<\/p>\n

Neden Y\u00f6nlendirme Yapmal\u0131y\u0131z?<\/h3>\n

Alan ad\u0131n\u0131z\u0131n “www” \u00f6n eki ile mi yoksa onsuz mu kullan\u0131laca\u011f\u0131na karar vermek, sadece estetik bir tercih de\u011fildir; web sitenizin teknik altyap\u0131s\u0131 ve performans\u0131 \u00fczerinde do\u011frudan etkileri vard\u0131r. \u0130\u015fte bu y\u00f6nlendirmeyi yapman\u0131n ba\u015fl\u0131ca nedenleri:<\/p>\n

SEO (Arama Motoru Optimizasyonu)<\/h4>\n

Arama motorlar\u0131, www.example.com<\/code> ve example.com<\/code> adreslerini ayr\u0131 ve ba\u011f\u0131ms\u0131z web siteleri olarak alg\u0131lar. E\u011fer her iki adrese de ayn\u0131 i\u00e7erikle eri\u015filebiliyorsa, bu durum “yinelenen i\u00e7erik” sorununa yol a\u00e7ar. Yinelenen i\u00e7erik, arama motorlar\u0131n\u0131n hangi versiyonun orijinal veya tercih edilen versiyon oldu\u011funa karar vermesini zorla\u015ft\u0131r\u0131r. Bu da sitenizin arama motoru s\u0131ralamalar\u0131n\u0131 d\u00fc\u015f\u00fcrebilir, \u00e7\u00fcnk\u00fc arama motorlar\u0131 i\u00e7eri\u011finizin de\u011ferini iki farkl\u0131 URL aras\u0131nda payla\u015ft\u0131rabilir. 301 kal\u0131c\u0131 y\u00f6nlendirmesi kullanarak, arama motorlar\u0131na tercih edilen versiyonu a\u00e7\u0131k\u00e7a belirtir ve t\u00fcm “link g\u00fcc\u00fc”n\u00fcn (link equity) tek bir URL’de toplanmas\u0131n\u0131 sa\u011flars\u0131n\u0131z. Bu, sitenizin SEO performans\u0131n\u0131 \u00f6nemli \u00f6l\u00e7\u00fcde art\u0131r\u0131r.<\/p>\n

Kullan\u0131c\u0131 Deneyimi<\/h4>\n

Kullan\u0131c\u0131lar genellikle bir web sitesinin adresini taray\u0131c\u0131lar\u0131na yazarken “www” \u00f6n ekini atlama e\u011filimindedir. E\u011fer siteniz bu \u00f6n ek olmadan eri\u015filebilir de\u011filse veya yanl\u0131\u015f bir yere y\u00f6nlendiriliyorsa, bu durum kullan\u0131c\u0131lar i\u00e7in kafa kar\u0131\u015ft\u0131r\u0131c\u0131 ve sinir bozucu olabilir. Tek bir, tutarl\u0131 bir URL’ye y\u00f6nlendirme yapmak, kullan\u0131c\u0131lar\u0131n sitenize daha kolay ve sorunsuz bir \u015fekilde eri\u015fmesini sa\u011flar, bu da genel kullan\u0131c\u0131 deneyimini iyile\u015ftirir.<\/p>\n

Canonicalization (Kanonikle\u015ftirme)<\/h4>\n

Canonicalization, web sitenizin i\u00e7eri\u011finin tek, tercih edilen bir URL \u00fczerinden eri\u015filebilir olmas\u0131n\u0131 sa\u011flama s\u00fcrecidir. Bu, hem arama motorlar\u0131 hem de kullan\u0131c\u0131lar i\u00e7in tutarl\u0131l\u0131k sa\u011flar. Y\u00f6nlendirme yaparak, sitenizin kanonik versiyonunu belirtir ve arama motorlar\u0131n\u0131n sitenizi do\u011fru bir \u015fekilde dizine eklemesine yard\u0131mc\u0131 olursunuz.<\/p>\n

Analiz ve Raporlama<\/h4>\n

Web sitesi trafi\u011fini analiz ederken, t\u00fcm verilerin tek bir URL alt\u0131nda toplanmas\u0131, daha do\u011fru ve anlaml\u0131 raporlar alman\u0131z\u0131 sa\u011flar. E\u011fer trafik hem “www” hem de “non-www” versiyonlar\u0131na da\u011f\u0131lm\u0131\u015fsa, analiz ara\u00e7lar\u0131n\u0131zda (\u00f6rne\u011fin Google Analytics) verilerinizi birle\u015ftirmek ve yorumlamak zorla\u015fabilir. Y\u00f6nlendirme, bu verileri tek bir havuzda toplar ve analiz s\u00fcre\u00e7lerini basitle\u015ftirir.<\/p>\n

\u00d6n Gereksinimler<\/h3>\n

Bu rehberdeki ad\u0131mlar\u0131 takip edebilmek i\u00e7in a\u015fa\u011f\u0131daki \u00f6n gereksinimlere sahip olman\u0131z gerekmektedir:<\/p>\n

* Ubuntu 14.04 Sunucusu:<\/strong> Apache web sunucusunun kurulu oldu\u011fu bir Ubuntu 14.04 sunucusuna eri\u015fiminiz olmal\u0131.
\n* Apache Web Sunucusu:<\/strong> Apache’nin sunucunuzda kurulu ve \u00e7al\u0131\u015f\u0131r durumda olmas\u0131 gerekmektedir.
\n* mod_rewrite<\/code> Mod\u00fcl\u00fc:<\/strong> Apache’nin URL yeniden yazma (rewrite) mod\u00fcl\u00fcn\u00fcn etkinle\u015ftirilmi\u015f olmas\u0131 gerekmektedir. Bu mod\u00fcl, y\u00f6nlendirme kurallar\u0131n\u0131 uygulamak i\u00e7in kritik \u00f6neme sahiptir.
\n* SSH Eri\u015fimi:<\/strong> Sunucunuza SSH \u00fczerinden ba\u011flanabilmeniz gerekmektedir.
\n* Temel Linux Komut Sat\u0131r\u0131 Bilgisi:<\/strong> Dosya sisteminde gezinme, dosya olu\u015fturma\/d\u00fczenleme gibi temel komutlara a\u015fina olman\u0131z faydal\u0131d\u0131r.
\n* Metin D\u00fczenleyici:<\/strong> nano<\/code> veya vim<\/code> gibi bir komut sat\u0131r\u0131 metin d\u00fczenleyicisi kullanabilmeniz.
\n* Root veya Sudo Yetkileri:<\/strong> Yap\u0131land\u0131rma dosyalar\u0131n\u0131 de\u011fi\u015ftirmek i\u00e7in y\u00f6netici (root) veya sudo<\/code> yetkilerine sahip bir kullan\u0131c\u0131 olman\u0131z gerekmektedir.
\n* Alan Ad\u0131:<\/strong> Y\u00f6nlendirme yapaca\u011f\u0131n\u0131z alan ad\u0131n\u0131n DNS kay\u0131tlar\u0131n\u0131n hem www.example.com<\/code> hem de example.com<\/code> i\u00e7in sunucunuzun IP adresine do\u011fru \u015fekilde i\u015faret etti\u011finden emin olun.<\/p>\n

Apache Yap\u0131land\u0131rmas\u0131n\u0131 Anlamak<\/h3>\n

Ubuntu \u00fczerindeki Apache, yap\u0131land\u0131rma dosyalar\u0131n\u0131 belirli bir hiyerar\u015fi ve dizin yap\u0131s\u0131 i\u00e7inde tutar. Bu yap\u0131y\u0131 anlamak, y\u00f6nlendirme kurallar\u0131n\u0131 do\u011fru yere yerle\u015ftirmek i\u00e7in hayati \u00f6nem ta\u015f\u0131r.<\/p>\n

* \/etc\/apache2\/<\/code>:<\/strong> Apache’nin ana yap\u0131land\u0131rma dizinidir.
\n* \/etc\/apache2\/apache2.conf<\/code>:<\/strong> Apache’nin ana yap\u0131land\u0131rma dosyas\u0131d\u0131r. Genellikle global ayarlar ve di\u011fer yap\u0131land\u0131rma dosyalar\u0131n\u0131 dahil etme (include) i\u015flemleri burada yap\u0131l\u0131r.
\n* \/etc\/apache2\/ports.conf<\/code>:<\/strong> Apache’nin hangi portlar\u0131 dinleyece\u011fini (genellikle 80 ve 443) tan\u0131mlar.
\n* \/etc\/apache2\/mods-available\/<\/code> ve \/etc\/apache2\/mods-enabled\/<\/code>:<\/strong> Apache mod\u00fcllerinin (\u00f6rne\u011fin mod_rewrite<\/code>) yap\u0131land\u0131rma dosyalar\u0131n\u0131 ve etkinle\u015ftirme ba\u011flant\u0131lar\u0131n\u0131 i\u00e7erir.
\n* \/etc\/apache2\/sites-available\/<\/code> ve \/etc\/apache2\/sites-enabled\/<\/code>:<\/strong> Bu dizinler, her bir web sitesi (Virtual Host) i\u00e7in ayr\u0131 yap\u0131land\u0131rma dosyalar\u0131n\u0131 bar\u0131nd\u0131r\u0131r. sites-available<\/code> i\u00e7inde bulunan bir dosya, a2ensite<\/code> komutuyla sites-enabled<\/code> i\u00e7ine bir sembolik ba\u011f (symlink) olu\u015fturularak etkinle\u015ftirilir.
\n* .htaccess<\/code> Dosyalar\u0131:<\/strong> Da\u011f\u0131t\u0131lm\u0131\u015f yap\u0131land\u0131rma dosyalar\u0131d\u0131r. Genellikle web sitesinin k\u00f6k dizininde veya alt dizinlerinde bulunur ve belirli dizinler i\u00e7in Apache davran\u0131\u015f\u0131n\u0131 ge\u00e7ersiz k\u0131lmaya yarar. Performans a\u00e7\u0131s\u0131ndan Virtual Host yap\u0131land\u0131rmas\u0131na g\u00f6re daha yava\u015f olabilirler.<\/p>\n

Y\u00f6ntem 1: .htaccess<\/code> Dosyas\u0131 Kullanarak Y\u00f6nlendirme<\/h3>\n

.htaccess<\/code> dosyalar\u0131, \u00f6zellikle payla\u015f\u0131ml\u0131 hosting ortamlar\u0131nda veya h\u0131zl\u0131, dizin bazl\u0131 de\u011fi\u015fiklikler yapmak istedi\u011finizde kullan\u0131\u015fl\u0131d\u0131r. Ancak, her istekte Apache’nin bu dosyalar\u0131 okumas\u0131 gerekti\u011fi i\u00e7in performans \u00fczerinde hafif bir etkisi olabilir.<\/p>\n

Ad\u0131m 1: mod_rewrite<\/code> Mod\u00fcl\u00fcn\u00fc Etkinle\u015ftirme<\/h4>\n

Y\u00f6nlendirme kurallar\u0131n\u0131 .htaccess<\/code> dosyas\u0131 i\u00e7inde kullanabilmek i\u00e7in \u00f6ncelikle Apache’nin mod_rewrite<\/code> mod\u00fcl\u00fcn\u00fc etkinle\u015ftirmemiz gerekir.<\/p>\n

sudo a2enmod rewrite<\/code><\/pre>\n
Bu komut, mod_rewrite<\/code> mod\u00fcl\u00fcn\u00fc etkinle\u015ftirir. Ard\u0131ndan, Apache sunucusunu yeniden ba\u015flatarak de\u011fi\u015fikliklerin etkili olmas\u0131n\u0131 sa\u011flay\u0131n:<\/p>\n
sudo service apache2 restart<\/code><\/pre>\n
Ad\u0131m 2: AllowOverride All<\/code> Ayar\u0131n\u0131 Yap\u0131land\u0131rma<\/h4>\n
Apache’nin .htaccess<\/code> dosyalar\u0131ndaki y\u00f6nergeleri i\u015flemesi i\u00e7in, ilgili web sitesinin VirtualHost<\/code> yap\u0131land\u0131rmas\u0131nda veya ana Apache yap\u0131land\u0131rmas\u0131nda AllowOverride All<\/code> y\u00f6nergesinin ayarlanm\u0131\u015f olmas\u0131 gerekir. Bu ayar genellikle \/etc\/apache2\/sites-available\/your_domain.com.conf<\/code> dosyas\u0131nda bulunur.<\/p>\n
1.  Web sitenizin Virtual Host yap\u0131land\u0131rma dosyas\u0131n\u0131 a\u00e7\u0131n:<\/p>\n
sudo nano \/etc\/apache2\/sites-available\/your_domain.com.conf<\/code><\/pre>\n
    (Burada your_domain.com.conf<\/code> yerine kendi alan ad\u0131n\u0131z\u0131n yap\u0131land\u0131rma dosyas\u0131n\u0131n ad\u0131n\u0131 yazmal\u0131s\u0131n\u0131z.)<\/p>\n
2.  Dosya i\u00e7inde, DocumentRoot<\/code>‘unuzu (\u00f6rne\u011fin \/var\/www\/html\/your_domain.com\/public_html<\/code>) g\u00f6steren <\/code> blo\u011funu bulun. Bu blok genellikle \u015f\u00f6yle g\u00f6r\u00fcn\u00fcr:<\/p>\n
\n        Options Indexes FollowSymLinks MultiViews\n        AllowOverride None\n        Require all granted\n    <\/Directory><\/code><\/pre>\n
3.  AllowOverride None<\/code> sat\u0131r\u0131n\u0131 AllowOverride All<\/code> olarak de\u011fi\u015ftirin:<\/p>\n
\n        Options Indexes FollowSymLinks MultiViews\n        AllowOverride All\n        Require all granted\n    <\/Directory><\/code><\/pre>\n
4.  Dosyay\u0131 kaydedin (CTRL+O, Enter) ve kapat\u0131n (CTRL+X).<\/p>\n
5.  Apache yap\u0131land\u0131rmas\u0131nda bir hata olup olmad\u0131\u011f\u0131n\u0131 kontrol edin ve ard\u0131ndan Apache’yi yeniden ba\u015flat\u0131n:<\/p>\n
sudo apache2ctl configtest\n    sudo service apache2 restart<\/code><\/pre>\n
Ad\u0131m 3: .htaccess<\/code> Dosyas\u0131n\u0131 Olu\u015fturma veya D\u00fczenleme<\/h4>\n
\u015eimdi, web sitenizin k\u00f6k dizininde bir .htaccess<\/code> dosyas\u0131 olu\u015fturabilir veya mevcut olan\u0131 d\u00fczenleyebilirsiniz.<\/p>\n
1.  Web sitenizin DocumentRoot<\/code> dizinine gidin (\u00f6rne\u011fin \/var\/www\/html\/your_domain.com\/public_html<\/code>):<\/p>\n
cd \/var\/www\/html\/your_domain.com\/public_html<\/code><\/pre>\n
2.  .htaccess<\/code> dosyas\u0131n\u0131 a\u00e7\u0131n veya olu\u015fturun:<\/p>\n
sudo nano .htaccess<\/code><\/pre>\n
3.  A\u015fa\u011f\u0131daki y\u00f6nlendirme kurallar\u0131n\u0131 dosyaya ekleyin:<\/p>\n
RewriteEngine On\n    RewriteCond %{HTTP_HOST} ^www\\.your_domain\\.com [NC]\n    RewriteRule ^(.*)$ http:\/\/your_domain\\.com\/$1 [L,R=301]<\/code><\/pre>\n
    A\u00e7\u0131klama:<\/strong>
\n    *   RewriteEngine On<\/code>: URL yeniden yazma motorunu etkinle\u015ftirir.
\n    *   RewriteCond %{HTTP_HOST} ^www\\.your_domain\\.com [NC]<\/code>: Bu bir ko\u015fuldur. Gelen iste\u011fin Host<\/code> ba\u015fl\u0131\u011f\u0131n\u0131n www.your_domain.com<\/code> ile ba\u015flay\u0131p ba\u015flamad\u0131\u011f\u0131n\u0131 kontrol eder. [NC]<\/code> bayra\u011f\u0131 b\u00fcy\u00fck\/k\u00fc\u00e7\u00fck harf duyars\u0131zl\u0131\u011f\u0131n\u0131 sa\u011flar. \\.<\/code> ise noktay\u0131 \u00f6zel karakter olarak de\u011fil, ger\u00e7ek nokta olarak e\u015fle\u015ftirmek i\u00e7indir.
\n       RewriteRule ^(.<\/em>)$ http:\/\/your_domain\\.com\/$1 [L,R=301]<\/code>: Bu kural, ko\u015ful do\u011fru oldu\u011funda uygulan\u0131r.
\n           ^(.<\/em>)$<\/code>: Gelen URL’nin yol k\u0131sm\u0131n\u0131 (domain sonras\u0131) yakalar. (.*)<\/code> ile yakalanan k\u0131s\u0131m $1<\/code> ile temsil edilir.
\n        *   http:\/\/your_domain.com\/$1<\/code>: Yakalanan yolu ($1<\/code>) http:\/\/your_domain.com\/<\/code> adresinin sonuna ekleyerek y\u00f6nlendirme yapar.
\n        *   [L]<\/code>: “Last” (Son) bayra\u011f\u0131, bu kural uyguland\u0131ktan sonra ba\u015fka hi\u00e7bir RewriteRule<\/code>‘un i\u015flenmemesini sa\u011flar.
\n        *   [R=301]<\/code>: “Redirect” (Y\u00f6nlendirme) bayra\u011f\u0131d\u0131r ve taray\u0131c\u0131ya kal\u0131c\u0131 bir y\u00f6nlendirme (HTTP 301 kodu) g\u00f6ndermesini s\u00f6yler. Bu, SEO a\u00e7\u0131s\u0131ndan \u00e7ok \u00f6nemlidir.<\/p>\n
4.  Dosyay\u0131 kaydedin ve kapat\u0131n. Bu y\u00f6ntem i\u00e7in Apache’yi yeniden ba\u015flatman\u0131za gerek yoktur, \u00e7\u00fcnk\u00fc .htaccess<\/code> de\u011fi\u015fiklikleri an\u0131nda uygulan\u0131r (e\u011fer AllowOverride All<\/code> do\u011fru yap\u0131land\u0131r\u0131lm\u0131\u015fsa).<\/p>\n
\u00d6nemli:<\/strong> your_domain.com<\/code> yerine kendi alan ad\u0131n\u0131z\u0131 yazmay\u0131 unutmay\u0131n.<\/p>\n
Y\u00f6ntem 2: Virtual Host Yap\u0131land\u0131rmas\u0131 Kullanarak Y\u00f6nlendirme<\/h3>\n
Virtual Host yap\u0131land\u0131rmas\u0131, \u00f6zellikle \u00f6zel sunucularda veya y\u00fcksek trafikli sitelerde tercih edilen y\u00f6ntemdir. Performans a\u00e7\u0131s\u0131ndan .htaccess<\/code>‘e g\u00f6re daha avantajl\u0131d\u0131r \u00e7\u00fcnk\u00fc Apache, yap\u0131land\u0131rma dosyalar\u0131n\u0131 yaln\u0131zca ba\u015flang\u0131\u00e7ta bir kez y\u00fckler ve her istekte tekrar okumaz.<\/p>\n
Bu y\u00f6ntemde iki farkl\u0131 yakla\u015f\u0131m izlenebilir:<\/p>\n
*   A) Tek Virtual Host i\u00e7inde Rewrite Kurallar\u0131:<\/strong> www<\/code> ve non-www<\/code> i\u00e7in tek bir Virtual Host tan\u0131mlay\u0131p i\u00e7inde y\u00f6nlendirme kurallar\u0131 kullanmak.
\n*   B) Ayr\u0131 Virtual Hostlar ile Y\u00f6nlendirme (\u00d6nerilen):<\/strong> www<\/code> \u00f6n eki i\u00e7in sadece y\u00f6nlendirme yapan ayr\u0131 bir Virtual Host tan\u0131mlamak ve as\u0131l i\u00e7eri\u011fi sunan non-www<\/code> Virtual Host’u ayr\u0131 tutmak. Bu yakla\u015f\u0131m daha temiz ve y\u00f6netimi kolayd\u0131r.<\/p>\n
Biz burada B) Ayr\u0131 Virtual Hostlar ile Y\u00f6nlendirme<\/strong> yakla\u015f\u0131m\u0131n\u0131 kullanaca\u011f\u0131z.<\/p>\n
Ad\u0131m 1: mod_rewrite<\/code> Mod\u00fcl\u00fcn\u00fc Etkinle\u015ftirme (Gerekliyse)<\/h4>\n
E\u011fer Virtual Host i\u00e7inde RewriteEngine<\/code> kullanacaksan\u0131z, mod_rewrite<\/code> mod\u00fcl\u00fcn\u00fcn etkin oldu\u011fundan emin olun (Y\u00f6ntem 1’deki ad\u0131mlar\u0131n ayn\u0131s\u0131d\u0131r):<\/p>\n
sudo a2enmod rewrite\nsudo service apache2 restart<\/code><\/pre>\n
Ad\u0131m 2: non-www<\/code> Virtual Host Yap\u0131land\u0131rmas\u0131n\u0131 Olu\u015fturma\/D\u00fczenleme<\/h4>\n
Bu Virtual Host, sitenizin ana i\u00e7eri\u011fini example.com<\/code> \u00fczerinden sunacakt\u0131r.<\/p>\n
1.  Web sitenizin mevcut yap\u0131land\u0131rma dosyas\u0131n\u0131 a\u00e7\u0131n (veya yeni bir tane olu\u015fturun):<\/p>\n
sudo nano \/etc\/apache2\/sites-available\/your_domain.com.conf<\/code><\/pre>\n
2.  Dosyan\u0131n i\u00e7eri\u011fini a\u015fa\u011f\u0131daki gibi d\u00fczenleyin. ServerName<\/code> olarak non-www<\/code> alan ad\u0131n\u0131z\u0131 ve DocumentRoot<\/code> olarak web sitenizin ana dizinini belirtti\u011finizden emin olun.<\/p>\n
\n        ServerName your_domain.com\n        DocumentRoot \/var\/www\/html\/your_domain.com\/public_html\n\n        \n            Options Indexes FollowSymLinks MultiViews\n            AllowOverride None # .htaccess kullanm\u0131yorsan\u0131z None olarak b\u0131rak\u0131n\n            Require all granted\n        <\/Directory>\n\n        ErrorLog ${APACHE_LOG_DIR}\/error.log\n        CustomLog ${APACHE_LOG_DIR}\/access.log combined\n    <\/VirtualHost><\/code><\/pre>\n
3.  Dosyay\u0131 kaydedin ve kapat\u0131n.<\/p>\n
Ad\u0131m 3: www<\/code> Y\u00f6nlendirme Virtual Host’unu Olu\u015fturma<\/h4>\n
\u015eimdi, www.your_domain.com<\/code> adresinden gelen t\u00fcm istekleri your_domain.com<\/code> adresine y\u00f6nlendirecek ayr\u0131 bir Virtual Host olu\u015fturaca\u011f\u0131z.<\/p>\n
1.  Yeni bir yap\u0131land\u0131rma dosyas\u0131 olu\u015fturun:<\/p>\n
sudo nano \/etc\/apache2\/sites-available\/www.your_domain.com.conf<\/code><\/pre>\n
2.  A\u015fa\u011f\u0131daki i\u00e7eri\u011fi dosyaya ekleyin. Burada Redirect<\/code> y\u00f6nergesini kullan\u0131yoruz, bu daha basit ve do\u011frudan bir y\u00f6nlendirme y\u00f6ntemidir:<\/p>\n
\n        ServerName www.your_domain.com\n        Redirect 301 \/ http:\/\/your_domain.com\/\n        # Alternatif olarak RewriteEngine kullanmak isterseniz:\n        # RewriteEngine On\n        # RewriteRule ^(.*)$ http:\/\/your_domain.com\/$1 [L,R=301]\n\n        ErrorLog ${APACHE_LOG_DIR}\/error.log\n        CustomLog ${APACHE_LOG_DIR}\/access.log combined\n    <\/VirtualHost><\/code><\/pre>\n
    A\u00e7\u0131klama:<\/strong>
\n    *   ServerName www.your_domain.com<\/code>: Bu Virtual Host’un www.your_domain.com<\/code> i\u00e7in ge\u00e7erli oldu\u011funu belirtir.
\n    *   Redirect 301 \/ http:\/\/your_domain.com\/<\/code>: Bu y\u00f6nerge, www.your_domain.com<\/code> adresine gelen t\u00fcm istekleri ( \/<\/code> ile belirtilen k\u00f6k dizin ve alt\u0131ndaki t\u00fcm yollar) kal\u0131c\u0131 olarak (301<\/code>) http:\/\/your_domain.com\/<\/code> adresine y\u00f6nlendirir.<\/p>\n
3.  Dosyay\u0131 kaydedin ve kapat\u0131n.<\/p>\n
Ad\u0131m 4: Yeni Virtual Host’u Etkinle\u015ftirme ve Apache’yi Yeniden Ba\u015flatma<\/h4>\n
1.  Yeni olu\u015fturdu\u011funuz www<\/code> y\u00f6nlendirme Virtual Host’unu etkinle\u015ftirin:<\/p>\n
sudo a2ensite www.your_domain.com.conf<\/code><\/pre>\n
2.  Apache yap\u0131land\u0131rmas\u0131nda bir hata olup olmad\u0131\u011f\u0131n\u0131 kontrol edin:<\/p>\n
sudo apache2ctl configtest<\/code><\/pre>\n
    E\u011fer Syntax OK<\/code> \u00e7\u0131kt\u0131s\u0131n\u0131 al\u0131rsan\u0131z, her \u015fey yolundad\u0131r.<\/p>\n
3.  De\u011fi\u015fikliklerin etkili olmas\u0131 i\u00e7in Apache’yi yeniden ba\u015flat\u0131n:<\/p>\n
sudo service apache2 restart<\/code><\/pre>\n
Art\u0131k www.your_domain.com<\/code> adresine yap\u0131lan t\u00fcm HTTP istekleri, http:\/\/your_domain.com<\/code> adresine kal\u0131c\u0131 olarak y\u00f6nlendirilmelidir.<\/p>\n
HTTPS (SSL\/TLS) ile Y\u00f6nlendirme<\/h3>\n
G\u00fcn\u00fcm\u00fczde web sitelerinin b\u00fcy\u00fck \u00e7o\u011funlu\u011fu g\u00fcvenlik nedeniyle HTTPS kullanmaktad\u0131r. E\u011fer sitenizde SSL\/TLS sertifikas\u0131 kuruluysa, y\u00f6nlendirme stratejiniz biraz daha karma\u015f\u0131k hale gelir. Genellikle en iyi uygulama, t\u00fcm HTTP isteklerini HTTPS’ye y\u00f6nlendirmek ve ard\u0131ndan www<\/code>‘den non-www<\/code>‘ye y\u00f6nlendirmeyi HTTPS \u00fczerinde yapmakt\u0131r.<\/p>\n
A\u015fa\u011f\u0131da, hem HTTP’den HTTPS’ye hem de www<\/code>‘den non-www<\/code>‘ye y\u00f6nlendirmeyi kapsayan iki ana senaryoyu ele alaca\u011f\u0131z.<\/p>\n
Senaryo 1: Virtual Host Yap\u0131land\u0131rmas\u0131 ile HTTP’den HTTPS’ye ve www’den Non-www’ye Y\u00f6nlendirme<\/h4>\n
Bu y\u00f6ntem, en sa\u011flam ve performansl\u0131 yakla\u015f\u0131md\u0131r. \u0130ki ana Virtual Host’a ihtiyac\u0131n\u0131z olacak: biri port 80 (HTTP) i\u00e7in, di\u011feri port 443 (HTTPS) i\u00e7in.<\/p>\n
1.  HTTP (Port 80) Virtual Host Yap\u0131land\u0131rmas\u0131:<\/strong>
\n    Bu Virtual Host, www<\/code> veya non-www<\/code> fark etmeksizin t\u00fcm HTTP isteklerini do\u011frudan https:\/\/your_domain.com<\/code> adresine y\u00f6nlendirecektir.<\/p>\n
sudo nano \/etc\/apache2\/sites-available\/your_domain.com-le-ssl.conf # veya benzer bir isim<\/code><\/pre>\n
    (Genellikle Let’s Encrypt gibi ara\u00e7lar bu dosyay\u0131 otomatik olu\u015fturur, ancak manuel de d\u00fczenleyebilirsiniz.)<\/p>\n
    HTTP Virtual Host’unuzu a\u015fa\u011f\u0131daki gibi yap\u0131land\u0131r\u0131n:<\/p>\n
\n        ServerName your_domain.com\n        ServerAlias www.your_domain.com\n\n        # T\u00fcm HTTP isteklerini HTTPS non-www adresine y\u00f6nlendir\n        Redirect 301 \/ https:\/\/your_domain.com\/\n\n        ErrorLog ${APACHE_LOG_DIR}\/error.log\n        CustomLog ${APACHE_LOG_DIR}\/access.log combined\n    <\/VirtualHost><\/code><\/pre>\n
    Bu yap\u0131land\u0131rma, http:\/\/your_domain.com<\/code> ve http:\/\/www.your_domain.com<\/code> adreslerinden gelen t\u00fcm istekleri https:\/\/your_domain.com<\/code> adresine y\u00f6nlendirecektir.<\/p>\n
2.  HTTPS (Port 443) Virtual Host Yap\u0131land\u0131rmas\u0131:<\/strong>
\n    Bu Virtual Host, sitenizin ana i\u00e7eri\u011fini https:\/\/your_domain.com<\/code> \u00fczerinden sunacak ve https:\/\/www.your_domain.com<\/code> adresinden gelen istekleri https:\/\/your_domain.com<\/code> adresine y\u00f6nlendirecektir.<\/p>\n
    HTTPS Virtual Host dosyan\u0131z\u0131 a\u00e7\u0131n:<\/p>\n
sudo nano \/etc\/apache2\/sites-available\/your_domain.com-ssl.conf # veya benzer bir isim<\/code><\/pre>\n
    \u0130\u00e7eri\u011fini a\u015fa\u011f\u0131daki gibi d\u00fczenleyin (SSL sertifika yollar\u0131n\u0131 kendi sertifika dosyalar\u0131n\u0131zla de\u011fi\u015ftirmeyi unutmay\u0131n):<\/p>\n
\n    \n        ServerName your_domain.com\n        ServerAlias www.your_domain.com # www alias'\u0131 burada da olmal\u0131\n\n        DocumentRoot \/var\/www\/html\/your_domain.com\/public_html\n\n        # SSL Ayarlar\u0131\n        SSLEngine on\n        SSLCertificateFile \/etc\/letsencrypt\/live\/your_domain.com\/fullchain.pem\n        SSLCertificateKeyFile \/etc\/letsencrypt\/live\/your_domain.com\/privkey.pem\n        # Di\u011fer SSL ayarlar\u0131 (SSLCipherSuite, SSLProtocol vb.)\n\n        \n            Options Indexes FollowSymLinks MultiViews\n            AllowOverride All # E\u011fer .htaccess kullan\u0131yorsan\u0131z\n            Require all granted\n        <\/Directory>\n\n        # www'den non-www'ye y\u00f6nlendirme (HTTPS \u00fczerinde)\n        RewriteEngine On\n        RewriteCond %{HTTP_HOST} ^www\\.your_domain\\.com [NC]\n        RewriteRule ^(.*)$ https:\/\/your_domain\\.com\/$1 [L,R=301]\n\n        ErrorLog ${APACHE_LOG_DIR}\/error.log\n        CustomLog ${APACHE_LOG_DIR}\/access.log combined\n    <\/VirtualHost>\n    <\/IfModule><\/code><\/pre>\n
    A\u00e7\u0131klama:<\/strong>
\n    *   ServerName your_domain.com<\/code>: Ana domain.
\n    *   ServerAlias www.your_domain.com<\/code>: www<\/code> \u00f6n ekli domainin de bu Virtual Host taraf\u0131ndan i\u015flenmesini sa\u011flar.
\n    *   RewriteEngine On<\/code>, RewriteCond<\/code>, RewriteRule<\/code>: Bu kurallar, https:\/\/www.your_domain.com<\/code> adresine gelen istekleri https:\/\/your_domain.com<\/code> adresine y\u00f6nlendirir.<\/p>\n
3.  Dosyalar\u0131 kaydedin ve kapat\u0131n.<\/p>\n
4.  Apache yap\u0131land\u0131rmas\u0131n\u0131 kontrol edin ve yeniden ba\u015flat\u0131n:<\/p>\n
sudo apache2ctl configtest\n    sudo service apache2 restart<\/code><\/pre>\n
Bu yap\u0131land\u0131rma ile, kullan\u0131c\u0131lar http:\/\/your_domain.com<\/code>, http:\/\/www.your_domain.com<\/code> veya https:\/\/www.your_domain.com<\/code> adreslerinden hangisini girerlerse girsinler, nihayetinde https:\/\/your_domain.com<\/code> adresine y\u00f6nlendirileceklerdir.<\/p>\n
Senaryo 2: .htaccess<\/code> Dosyas\u0131 ile HTTP’den HTTPS’ye ve www’den Non-www’ye Y\u00f6nlendirme<\/h4>\n
Bu y\u00f6ntem, Virtual Host yap\u0131land\u0131rmas\u0131na eri\u015fiminizin olmad\u0131\u011f\u0131 payla\u015f\u0131ml\u0131 hosting ortamlar\u0131nda veya h\u0131zl\u0131 bir \u00e7\u00f6z\u00fcm arad\u0131\u011f\u0131n\u0131zda kullan\u0131labilir. Ancak, .htaccess<\/code> dosyalar\u0131n\u0131n i\u015flenmesi i\u00e7in ilgili Virtual Host’larda AllowOverride All<\/code> ayar\u0131n\u0131n hem port 80 hem de port 443 i\u00e7in etkinle\u015ftirildi\u011finden emin olman\u0131z gerekir.<\/p>\n
1.  Web sitenizin DocumentRoot<\/code> dizinine gidin:<\/p>\n
cd \/var\/www\/html\/your_domain.com\/public_html<\/code><\/pre>\n
2.  .htaccess<\/code> dosyas\u0131n\u0131 a\u00e7\u0131n veya olu\u015fturun:<\/p>\n
sudo nano .htaccess<\/code><\/pre>\n
3.  A\u015fa\u011f\u0131daki y\u00f6nlendirme kurallar\u0131n\u0131 dosyaya ekleyin:<\/p>\n
RewriteEngine On\n\n    # HTTP'den HTTPS'ye y\u00f6nlendirme (\u00f6nce bu kural \u00e7al\u0131\u015f\u0131r)\n    RewriteCond %{HTTPS} off\n    RewriteRule ^(.*)$ https:\/\/%{HTTP_HOST}%{REQUEST_URI} [L,R=301]\n\n    # www'den non-www'ye y\u00f6nlendirme (HTTPS sonras\u0131)\n    RewriteCond %{HTTP_HOST} ^www\\.your_domain\\.com [NC]\n    RewriteRule ^(.*)$ https:\/\/your_domain\\.com\/$1 [L,R=301]<\/code><\/pre>\n
    A\u00e7\u0131klama:<\/strong>
\n    *   \u0130lk RewriteCond<\/code> ve RewriteRule<\/code> \u00e7ifti, gelen iste\u011fin HTTPS olmad\u0131\u011f\u0131n\u0131 (%{HTTPS} off<\/code>) kontrol eder ve e\u011fer HTTP ise, iste\u011fi ayn\u0131 domain ve yolla HTTPS’ye y\u00f6nlendirir. %{HTTP_HOST}<\/code> ve %{REQUEST_URI}<\/code> de\u011fi\u015fkenleri, orijinal domain ve yolu korur.
\n    *   \u0130kinci RewriteCond<\/code> ve RewriteRule<\/code> \u00e7ifti, iste\u011fin www.your_domain.com<\/code> adresinden geldi\u011fini kontrol eder (bu art\u0131k HTTPS \u00fczerinden gelen bir istek olabilir) ve https:\/\/your_domain.com<\/code> adresine y\u00f6nlendirir.<\/p>\n
4.  Dosyay\u0131 kaydedin ve kapat\u0131n.<\/p>\n
5.  Bu .htaccess<\/code> kurallar\u0131n\u0131n \u00e7al\u0131\u015fabilmesi i\u00e7in, hem HTTP (port 80) hem de HTTPS (port 443) Virtual Host’lar\u0131n\u0131zda AllowOverride All<\/code> y\u00f6nergesinin ilgili DocumentRoot<\/code> dizini i\u00e7in ayarland\u0131\u011f\u0131ndan emin olun. Gerekirse Apache’yi yeniden ba\u015flat\u0131n.<\/p>\n
Bu .htaccess<\/code> kurallar\u0131, t\u00fcm y\u00f6nlendirme mant\u0131\u011f\u0131n\u0131 tek bir yerde toplar.<\/p>\n
Y\u00f6nlendirmelerinizi Test Etme<\/h3>\n
Y\u00f6nlendirme kurallar\u0131n\u0131 uygulad\u0131ktan sonra, her \u015feyin beklendi\u011fi gibi \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olmak i\u00e7in kapsaml\u0131 testler yapman\u0131z \u00e7ok \u00f6nemlidir.<\/p>\n
1.  Taray\u0131c\u0131 Testi:<\/strong>
\n    *   Taray\u0131c\u0131n\u0131z\u0131n \u00f6nbelle\u011fini temizleyin.
\n    *   A\u015fa\u011f\u0131daki URL’leri deneyin ve her birinin nihayetinde https:\/\/your_domain.com<\/code> (veya sadece http:\/\/your_domain.com<\/code> e\u011fer SSL kullanm\u0131yorsan\u0131z) adresine y\u00f6nlendirildi\u011finden emin olun:
\n        *   http:\/\/your_domain.com<\/code>
\n        *   http:\/\/www.your_domain.com<\/code>
\n        *   https:\/\/www.your_domain.com<\/code> (e\u011fer SSL kullan\u0131yorsan\u0131z)<\/p>\n
2.  curl<\/code> Komutu ile Test:<\/strong>
\n    curl<\/code> komutu, HTTP ba\u015fl\u0131klar\u0131n\u0131 kontrol etmek i\u00e7in harika bir ara\u00e7t\u0131r. \u00d6zellikle 301 Moved Permanently<\/code> durum kodunu g\u00f6rmeniz \u00f6nemlidir.<\/p>\n
    *   www<\/code> \u00f6n ekli HTTP iste\u011fi i\u00e7in:<\/p>\n
curl -I http:\/\/www.your_domain.com<\/code><\/pre>\n
        \u00c7\u0131kt\u0131da HTTP\/1.1 301 Moved Permanently<\/code> veya HTTP\/1.1 302 Found<\/code> (e\u011fer ge\u00e7ici y\u00f6nlendirme yapt\u0131ysan\u0131z ki yapmamal\u0131s\u0131n\u0131z) ve Location: http:\/\/your_domain.com\/<\/code> (veya https:\/\/your_domain.com\/<\/code> e\u011fer HTTPS’ye de y\u00f6nlendiriyorsan\u0131z) g\u00f6rmelisiniz.<\/p>\n
    *   non-www<\/code> \u00f6n ekli HTTP iste\u011fi i\u00e7in:<\/p>\n
curl -I http:\/\/your_domain.com<\/code><\/pre>\n
        E\u011fer sadece www<\/code>‘den non-www<\/code>‘ye y\u00f6nlendiriyorsan\u0131z HTTP\/1.1 200 OK<\/code> g\u00f6rmelisiniz. E\u011fer HTTP’den HTTPS’ye de y\u00f6nlendiriyorsan\u0131z, 301 Moved Permanently<\/code> ve Location: https:\/\/your_domain.com\/<\/code> g\u00f6rmelisiniz.<\/p>\n
    *   www<\/code> \u00f6n ekli HTTPS iste\u011fi i\u00e7in (e\u011fer SSL kullan\u0131yorsan\u0131z):<\/p>\n
curl -I https:\/\/www.your_domain.com<\/code><\/pre>\n
        301 Moved Permanently<\/code> ve Location: https:\/\/your_domain.com\/<\/code> g\u00f6rmelisiniz.<\/p>\n
    *   non-www<\/code> \u00f6n ekli HTTPS iste\u011fi i\u00e7in (e\u011fer SSL kullan\u0131yorsan\u0131z):<\/p>\n
curl -I https:\/\/your_domain.com<\/code><\/pre>\n
        HTTP\/1.1 200 OK<\/code> g\u00f6rmelisiniz.<\/p>\n
Yayg\u0131n Sorun Giderme<\/h3>\n
Y\u00f6nlendirmelerde kar\u015f\u0131la\u015fabilece\u011finiz baz\u0131 yayg\u0131n sorunlar ve \u00e7\u00f6z\u00fcmleri:<\/p>\n
*   mod_rewrite<\/code> Etkin De\u011fil:<\/strong> E\u011fer .htaccess<\/code> veya Virtual Host i\u00e7inde RewriteEngine<\/code> kullan\u0131yorsan\u0131z, sudo a2enmod rewrite<\/code> komutuyla mod\u00fcl\u00fcn etkinle\u015ftirildi\u011finden ve Apache’nin yeniden ba\u015flat\u0131ld\u0131\u011f\u0131ndan emin olun.
\n*   AllowOverride All<\/code> Ayar\u0131 Eksik:<\/strong> .htaccess<\/code> dosyalar\u0131 \u00e7al\u0131\u015fm\u0131yorsa, ilgili VirtualHost<\/code>‘un <\/code> blo\u011funda AllowOverride All<\/code> ayar\u0131n\u0131n yap\u0131ld\u0131\u011f\u0131ndan emin olun ve Apache’yi yeniden ba\u015flat\u0131n.
\n*   S\u00f6zdizimi Hatalar\u0131:<\/strong> Apache yap\u0131land\u0131rma dosyalar\u0131nda veya .htaccess<\/code> dosyas\u0131nda s\u00f6zdizimi hatalar\u0131 olabilir. sudo apache2ctl configtest<\/code> komutuyla hatalar\u0131 kontrol edin.
\n*   Yanl\u0131\u015f Alan Adlar\u0131:<\/strong> Y\u00f6nlendirme kurallar\u0131nda your_domain.com<\/code> yerine kendi alan ad\u0131n\u0131z\u0131 do\u011fru yazd\u0131\u011f\u0131n\u0131zdan emin olun. Noktalar\u0131 \\.<\/code> \u015feklinde ka\u00e7\u0131rd\u0131\u011f\u0131n\u0131zdan emin olun.
\n*   Taray\u0131c\u0131 \u00d6nbelle\u011fi:<\/strong> Taray\u0131c\u0131n\u0131z y\u00f6nlendirmeleri \u00f6nbelle\u011fe alm\u0131\u015f olabilir. Test ederken taray\u0131c\u0131 \u00f6nbelle\u011fini temizleyin veya gizli (incognito) mod kullan\u0131n.
\n*   Apache Yeniden Ba\u015flat\u0131lmad\u0131:<\/strong> Virtual Host yap\u0131land\u0131rma dosyalar\u0131nda yapt\u0131\u011f\u0131n\u0131z de\u011fi\u015fikliklerin etkili olmas\u0131 i\u00e7in Apache’yi her zaman yeniden ba\u015flatman\u0131z gerekir (sudo service apache2 restart<\/code>).
\n*   \u00c7ak\u0131\u015fan Kurallar:<\/strong> Birden fazla .htaccess<\/code> dosyas\u0131 veya farkl\u0131 Virtual Host’lar aras\u0131nda \u00e7ak\u0131\u015fan y\u00f6nlendirme kurallar\u0131 olabilir. En \u00fcst d\u00fczeydeki veya en spesifik kural\u0131n beklendi\u011fi gibi \u00e7al\u0131\u015ft\u0131\u011f\u0131ndan emin olun.
\n*   DNS Sorunlar\u0131:<\/strong> Alan ad\u0131n\u0131z\u0131n hem www<\/code> hem de non-www<\/code> versiyonlar\u0131 i\u00e7in DNS A kay\u0131tlar\u0131n\u0131n sunucunuzun IP adresine do\u011fru \u015fekilde i\u015faret etti\u011finden emin olun. Aksi takdirde, Apache iste\u011fi do\u011fru bir \u015fekilde alamayacakt\u0131r.<\/p>\n
En \u0130yi Uygulamalar ve Dikkat Edilmesi Gerekenler<\/h3>\n
*   Daima 301 Kal\u0131c\u0131 Y\u00f6nlendirme Kullan\u0131n:<\/strong> SEO a\u00e7\u0131s\u0131ndan 301 Moved Permanently<\/code> durum kodu, arama motorlar\u0131na sayfan\u0131n kal\u0131c\u0131 olarak ta\u015f\u0131nd\u0131\u011f\u0131n\u0131 bildirir ve t\u00fcm link g\u00fcc\u00fcn\u00fc yeni adrese aktar\u0131r. 302 Found<\/code> (ge\u00e7ici y\u00f6nlendirme) kullanmaktan ka\u00e7\u0131n\u0131n.
\n*   Virtual Host’u .htaccess<\/code>‘e Tercih Edin:<\/strong> M\u00fcmk\u00fcnse, y\u00f6nlendirme kurallar\u0131n\u0131 Virtual Host yap\u0131land\u0131rmas\u0131 i\u00e7inde tan\u0131mlay\u0131n. Bu, daha iyi performans, daha kolay y\u00f6netim ve daha iyi g\u00fcvenlik sa\u011flar.
\n*   HTTPS’yi En Ba\u015fa Koyun:<\/strong> E\u011fer SSL kullan\u0131yorsan\u0131z, t\u00fcm HTTP trafi\u011fini \u00f6nce HTTPS’ye y\u00f6nlendirin, ard\u0131ndan www<\/code>‘den non-www<\/code>‘ye y\u00f6nlendirmeyi HTTPS \u00fczerinde yap\u0131n. Bu, g\u00fcvenli\u011fin en \u00fcst d\u00fczeyde tutulmas\u0131n\u0131 sa\u011flar.
\n*   Kapsaml\u0131 Test Edin:<\/strong> Herhangi bir de\u011fi\u015fiklik yapt\u0131ktan sonra, t\u00fcm olas\u0131 senaryolar\u0131 (HTTP, HTTPS, www, non-www, alt sayfalar) test etti\u011finizden emin olun.
\n*   Yap\u0131land\u0131rma Dosyalar\u0131n\u0131 Yedekleyin:<\/strong> \u00d6nemli Apache yap\u0131land\u0131rma dosyalar\u0131n\u0131 de\u011fi\u015ftirmeden \u00f6nce daima yedeklerini al\u0131n.
\n*   Arama Motorlar\u0131n\u0131 Bilgilendirin:<\/strong> Y\u00f6nlendirmeleri yapt\u0131ktan sonra Google Search Console gibi ara\u00e7lar\u0131 kullanarak tercih etti\u011finiz domaini (\u00f6rne\u011fin example.com<\/code>) arama motorlar\u0131na bildirin.<\/p>\n
Sonu\u00e7<\/h3>\n
www<\/code> \u00f6n ekinden non-www<\/code> \u00f6n ekine y\u00f6nlendirme yapmak, web sitenizin SEO performans\u0131, kullan\u0131c\u0131 deneyimi ve genel teknik sa\u011fl\u0131\u011f\u0131 i\u00e7in kritik bir ad\u0131md\u0131r. Bu rehberde, Ubuntu 14.04 \u00fczerinde Apache kullanarak bu y\u00f6nlendirmeyi hem .htaccess<\/code> dosyalar\u0131yla hem de Virtual Host yap\u0131land\u0131rmas\u0131yla nas\u0131l yapaca\u011f\u0131n\u0131z\u0131 detayl\u0131 bir \u015fekilde \u00f6\u011frendiniz. Ayr\u0131ca, HTTPS’nin i\u015fin i\u00e7ine girdi\u011fi senaryolar\u0131 ve yayg\u0131n sorun giderme ipu\u00e7lar\u0131n\u0131 da ele ald\u0131k.<\/p>\n
Unutmay\u0131n ki her web sitesi kurulumu benzersiz olabilir, bu nedenle ad\u0131mlar\u0131 kendi \u00f6zel durumunuza g\u00f6re uyarlaman\u0131z ve her de\u011fi\u015fiklikten sonra dikkatlice test etmeniz \u00f6nemlidir. Do\u011fru yap\u0131land\u0131r\u0131lm\u0131\u015f bir y\u00f6nlendirme, sitenizin arama motorlar\u0131nda daha iyi s\u0131ralanmas\u0131na ve ziyaret\u00e7ileriniz i\u00e7in daha tutarl\u0131 bir deneyim sunmas\u0131na yard\u0131mc\u0131 olacakt\u0131r.<\/body><\/p>\n","protected":false},"excerpt":{"rendered":"www’den Non-www’ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber\nWeb sitenizi yay\u0131nlarken, alan ad\u0131n\u0131z\u0131n “www” \u00f6n eki ile mi","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"csco_page_header_type":"","csco_page_load_nextpost":"","csco_page_subscribe_form":"","csco_page_contact_form":"","footnotes":""},"categories":[1468],"tags":[],"class_list":{"0":"post-38814","1":"post","2":"type-post","3":"status-publish","4":"format-standard","6":"category-ubuntu","7":"cs-entry","8":"cs-video-wrap"},"yoast_head":"\nwww'den Non-www'ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/\" \/>\n<meta property=\"og:locale\" content=\"tr_TR\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"www'den Non-www'ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber\" \/>\n<meta property=\"og:description\" content=\"www'den Non-www'ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber Web sitenizi yay\u0131nlarken, alan ad\u0131n\u0131z\u0131n "www" \u00f6n eki ile mi\" \/>\n<meta property=\"og:url\" content=\"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/\" \/>\n<meta property=\"og:site_name\" content=\"Kodlar\u0131n Gizemli D\u00fcnyas\u0131\" \/>\n<meta property=\"article:published_time\" content=\"2026-02-08T09:40:55+00:00\" \/>\n<meta name=\"author\" content=\"Fatih Soysal\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Yazan:\" \/>\n\t<meta name=\"twitter:data1\" content=\"Fatih Soysal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Tahmini okuma s\u00fcresi\" \/>\n\t<meta name=\"twitter:data2\" content=\"20 dakika\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/\"},\"author\":{\"name\":\"Fatih Soysal\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"headline\":\"www’den Non-www’ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber\",\"datePublished\":\"2026-02-08T09:40:55+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/\"},\"wordCount\":3106,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"articleSection\":[\"Ubuntu\"],\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/#respond\"]}],\"copyrightYear\":\"2026\",\"copyrightHolder\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#organization\"}},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/\",\"name\":\"www'den Non-www'ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131\",\"isPartOf\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\"},\"datePublished\":\"2026-02-08T09:40:55+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/#breadcrumb\"},\"inLanguage\":\"tr\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Anasayfa\",\"item\":\"https:\/\/fatihsoysal.com\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"www’den Non-www’ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#website\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/\",\"name\":\"Fatihsoysal.com\",\"description\":\"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim\",\"publisher\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"tr\"},{\"@type\":[\"Person\",\"Organization\"],\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1\",\"name\":\"Fatih Soysal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"tr\",\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"contentUrl\":\"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png\",\"width\":512,\"height\":512,\"caption\":\"Fatih Soysal\"},\"logo\":{\"@id\":\"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/\"},\"description\":\"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.\",\"url\":\"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"www'den Non-www'ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/","og_locale":"tr_TR","og_type":"article","og_title":"www'den Non-www'ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber","og_description":"www'den Non-www'ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber Web sitenizi yay\u0131nlarken, alan ad\u0131n\u0131z\u0131n \"www\" \u00f6n eki ile mi","og_url":"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/","og_site_name":"Kodlar\u0131n Gizemli D\u00fcnyas\u0131","article_published_time":"2026-02-08T09:40:55+00:00","author":"Fatih Soysal","twitter_card":"summary_large_image","twitter_misc":{"Yazan:":"Fatih Soysal","Tahmini okuma s\u00fcresi":"20 dakika"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/#article","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/"},"author":{"name":"Fatih Soysal","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"headline":"www’den Non-www’ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber","datePublished":"2026-02-08T09:40:55+00:00","mainEntityOfPage":{"@id":"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/"},"wordCount":3106,"commentCount":0,"publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"articleSection":["Ubuntu"],"inLanguage":"tr","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/#respond"]}],"copyrightYear":"2026","copyrightHolder":{"@id":"https:\/\/fatihsoysal.com\/blog\/#organization"}},{"@type":"WebPage","@id":"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/","url":"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/","name":"www'den Non-www'ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber - Kodlar\u0131n Gizemli D\u00fcnyas\u0131","isPartOf":{"@id":"https:\/\/fatihsoysal.com\/blog\/#website"},"datePublished":"2026-02-08T09:40:55+00:00","breadcrumb":{"@id":"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/#breadcrumb"},"inLanguage":"tr","potentialAction":[{"@type":"ReadAction","target":["https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/fatihsoysal.com\/blog\/wwwden-non-wwwye-apache-ile-yonlendirme-ubuntu-14-04-uzerinde-kapsamli-rehber\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Anasayfa","item":"https:\/\/fatihsoysal.com\/blog\/"},{"@type":"ListItem","position":2,"name":"www’den Non-www’ye Apache ile Y\u00f6nlendirme: Ubuntu 14.04 \u00dczerinde Kapsaml\u0131 Rehber"}]},{"@type":"WebSite","@id":"https:\/\/fatihsoysal.com\/blog\/#website","url":"https:\/\/fatihsoysal.com\/blog\/","name":"Fatihsoysal.com","description":"Blog - Yaz\u0131l\u0131m D\u00fcnyas\u0131 Tecr\u00fcbelerim","publisher":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/fatihsoysal.com\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"tr"},{"@type":["Person","Organization"],"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/002a254750921dcfd568a99e48240dd1","name":"Fatih Soysal","image":{"@type":"ImageObject","inLanguage":"tr","@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/","url":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","contentUrl":"https:\/\/fatihsoysal.com\/blog\/wp-content\/uploads\/2024\/04\/cropped-replicate-prediction-3kgg1hgjn5rgp0cf0p5tr0jw7w-1.png","width":512,"height":512,"caption":"Fatih Soysal"},"logo":{"@id":"https:\/\/fatihsoysal.com\/blog\/#\/schema\/person\/image\/"},"description":"Kullan\u0131m ve kodlama m\u00fckemmeliyetini odak alan uygulamalar olu\u015fturma deneyimine sahip, profesyonel olarak 15+ y\u0131l \u00fczeri deneyime sahip bir yaz\u0131l\u0131m m\u00fchendisi.","url":"https:\/\/fatihsoysal.com\/blog\/author\/fatihsoysal\/"}]}},"yoast_meta":{"yoast_wpseo_title":"","yoast_wpseo_metadesc":"","yoast_wpseo_canonical":""},"amp_enabled":true,"_links":{"self":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/38814","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/comments?post=38814"}],"version-history":[{"count":1,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/38814\/revisions"}],"predecessor-version":[{"id":38815,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/posts\/38814\/revisions\/38815"}],"wp:attachment":[{"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/media?parent=38814"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/categories?post=38814"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fatihsoysal.com\/blog\/wp-json\/wp\/v2\/tags?post=38814"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}