April 17, 2026
Subdirectory smackdown
How to Host a Blog on a Subdirectory Instead of a Subdomain
How-to puts your blog under your main site; commenters say they did it in the ’90s
TLDR: A guide shows how to put your blog under your main site using Cloudflare to boost search visibility. Commenters flame it as ancient, obvious, and basically documentation, while others quietly appreciate a straightforward how-to—sparking a clash between old-school pride and practical step-by-step help.
A new guide shows how to park your blog at example.com/blog instead of blog.example.com using Cloudflare Workers—promising better SEO (search engine optimization) and a smoother experience. The author swears moving a blog into a subfolder boosted traffic without new posts, and offers a step-by-step. That’s the article. The comments? Oh, they were on fire.
Readers rolled in with big “we were there first” energy. One wag said the headline should add “with Cloudflare Workers,” arguing this is basic web stuff dressed up as news. Another flexed: “I was doing this 30 actual years ago,” dunking on the idea that this belongs anywhere near a news feed. A third called it “basically product docs,” not a breakthrough. Someone even dropped a link to an earlier thread, implying this ground has been trodden, reshod, and trodden again.
Still, the tutorial’s pitch—keep the blog under your main site so your whole domain shares reputation—hit a nerve. The drama split the room between veterans who see it as yesterday’s bread and pragmatists who just want a clear recipe, even if the oven’s named Cloudflare. In short: old-school pride vs. modern tooling and an eternal internet truth—what’s “obvious” to some is gold to others.
Key Points
- •The guide explains how to host a blog at example.com/blog using Cloudflare Workers rather than a subdomain.
- •It argues subdirectories can improve SEO by consolidating domain authority, citing an external ButterCMS article and personal experience.
- •The example setup uses a Next.js blog on Vercel and a static main site on Render, but steps apply to other providers.
- •All configuration is performed in Cloudflare (Dashboard/Workers), with no changes required at Vercel or Render.
- •Step 1 covers Cloudflare SSL/TLS (set to Full) and DNS record additions (e.g., CNAME to provider service URL).