When I launched the revamped version of this blog nearly a year ago, my goal was simple: build a clean, lightweight home on the web to share code, tutorials, and thoughts on modern WordPress development, along with some writing for myself along the way.

One aspect of running a blog in the current web landscape has become increasingly clear, comment sections just aren’t what they used to be.

Today, I’m disabling comments across the blog, and here is why.

The LLM and Bot Dilemma

We are living in the full swing of LLMs, scrapers, and automated scripts. A massive portion of the requests hitting blog endpoints today isn’t even human – it’s automated robots crawling content, scraping text, or firing brute-force scripts.

When a notification pops up saying there’s a new pending comment, more often than not, it’s an automated bot or an AI-generated generic response designed purely to drop a backlink.

Cycles of Spam Moderation

Almost every single time I publish a new article, a fresh wave of spam comments follows. While some get caught automatically, I still find myself spending unnecessary time manually marking them as spam. It’s an administrative tax that adds zero value to writing code or sharing useful technical guides.

Content Ownership

Beyond the noise, there’s also a fundamental question of ownership. When someone writes a comment on someone else’s blog, who does that content actually belong to?

If you have a thoughtful response, a detailed code breakdown, or a deeper perspective on something I’ve written, the absolute best place for that piece of content is on your own website. Publish it on your own domain, retain full ownership of your writing, and send a ping my way.

BloatBuster: How I Disabled Them

Instead of just flipping a simple switch or piling on more single-purpose plugins, I ended up writing a dedicated tool to handle this cleanly.

I built BloatBuster – Performance & Asset Cleaner, a lightweight WordPress plugin that strips out site bloat, disables comments completely, and handles several core tweaks I regularly use across my WP builds. It keeps the site lean and execution faster. I’ve made the repository public on GitHub, and depending on where it goes, I might even publish it to the official WordPress plugin directory down the road.

Reaching Out

Disabling the comment box doesn’t mean closing the door to communication. If you have a question about a post, spotted an edge case in some code I shared, or just want to discuss WordPress engineering, you can easily reach out through any of the profile links down in the footer (GitHub, social channels, or community profiles).

Moving forward, I’m turning off the comment noise so I can focus on what actually matters: writing clean code, building fast tools, and publishing quality posts from time to time. Thanks for reading! 😉