Should I host my blog on a naked domain or a www subdomain for better SEO?
SEO-wise, it's a coin flip — just pick one and 301 redirect the other. Forgetting the redirect splits your backlinks and tanks your rankings.
From an SEO standpoint, it honestly makes absolutely zero difference whether you host your blog on a naked domain or a www subdomain. The only thing search engines actually care about is that you pick one version and permanently redirect the other to it so you don't accidentally split your traffic.
Does Google actually prefer one version over the other?
Search engine bots don't play favorites here. Whether you type in just your brand name dot com or throw those three Ws in front of it, Google treats both paths with the exact same level of respect. Back in the early days of the internet, that www prefix was basically required to tell servers exactly what kind of traffic was coming through. Today? It's really just a cosmetic choice. If you're running a sleek, modern setup — which you probably are if you're using VeloCMS instead of wrestling with clunky old WordPress databases — dropping the www gives your URLs a cleaner, punchier look. People are lazy typers anyway. They rarely bother tapping out those extra letters on their phones, so a naked domain often feels a lot more natural for personal blogs and newer brands.
What happens if I forget to redirect the version I didn't pick?
This is where things can go sideways fast. If somebody can reach your blog with the www and without it, search engines see that as two entirely separate websites fighting for the exact same keywords. It's a classic case of keyword cannibalization (and a massive headache to fix after the fact). You end up watering down your own ranking power because the algorithms can't figure out which page is the "real" one. Your backlinks get split down the middle, your page authority tanks, and you're left wondering why nobody is finding your articles. You have to force all roads to lead to the exact same destination.
How do I lock in my choice the right way?
Since you're building on VeloCMS — enjoying that blazing fast Next.js frontend and lightweight PocketBase backend — handling this routing is pretty straightforward. Here is your specific, actionable tip to keep your SEO perfectly intact: once you've decided between the naked domain or the www subdomain, immediately log into your DNS provider and set up a 301 permanent redirect from the discarded version to your primary one. Do not use a 302 temporary redirect under any circumstances! A 301 specifically tells Google's crawlers that the move is forever, passing all of your hard-earned link juice directly to the correct address. If you're hooking things up through a modern host like Vercel or Cloudflare to serve your site, they usually have a single toggle switch in their domain settings panel that handles this apex-to-www redirect automatically.
Why do some massive companies still cling to the www subdomain?
You've probably noticed that internet giants almost always use the www version, and there is a highly technical reason for that. When you run a massive corporate infrastructure, using a subdomain gives you a lot more flexibility to restrict cookies and manage heavy server loads across multiple regions. Naked domains force cookies down to every single subdomain attached to them, which can slow down things like static image delivery. But let's be real — unless you are serving millions of concurrent requests a second across a complex global network, you don't need to worry about that. A standard blog running on our Next.js architecture is already so heavily optimized and inexpensive to run that those legacy cookie concerns simply don't apply to your day-to-day operations.
At the end of the day, don't let this decision paralyze you. Go with whichever URL style looks best on your business cards and social media profiles. Just claim your favorite, set up that permanent 301 redirect right out of the gate, and get back to writing content that actually matters to your readers.