quotingI hear you. The SEO benefits that once were are basically non-existent now.
nevent1q…8gmq
And for smaller sites the benefits are negligible so it really does come down to personal preference.
However, I've been developing sites for 20 years now and there are factual technical benefits to using www when working with large sites.
For example, if you have multiple subdomains, it helps with cookie management. Using www allows you to separate cookies from other subdomains.
When using a naked domain, cookies set for the naked domain are automatically sent to all subdomains. This can create issues with cookie management, particularly in terms of security, privacy, and performance.
So if one subdomain is compromised, an attacker could compromise your entire site when using a naked domain. Also there can be potential privacy issues if cookies with sensitive information meant for the naked domain are accessible to all the subdomains.
There is also a performance boost since you are not sending unnecessary cookies with every request.
In addition, using "www" allows you to create a CNAME record pointing to another domain which is particularly useful for load balancing and redundancy. For example, you can have (www.example.com) point to a CDN, while (example.com) directly points to your server.
Another example is that Netlify recomments www because they don;t support CNAME flattening like cloudflare does.
etc. etc.
vinney on Nostr: these are extremely good points. I was a little hasty elsewhere in the thread. i ...
these are extremely good points. I was a little hasty elsewhere in the thread. i stand by the point that “SEO” is a poor reason to care about www subdomain, but cookies and some DNS niceties are valid points!