Table of Contents
How I Use Claude to Run a One-Person AI Blog (The Real Story, Not the Highlight Reel)
I have an M.Sc. in Agronomy. Not computer science, not marketing, not journalism — agronomy. Soil, crops, seasons. If you’d told 2018-me that six years later I’d be running an AI tools blog for a US audience, publishing SEO-optimized comparison articles, and getting cited by AI chatbots, I’d have asked what an “AI chatbot” even was.
This is the story of how I got here, and more specifically, how Claude became the tool that actually made it possible — not as a gimmick, but as something closer to a working partner.
The Part Nobody Puts in Their Bio
Before techdg.in, there were a lot of dead ends. A Blogger site in 2018 that went nowhere. A move to Google Sites. A WordPress news site in 2019–2020 that I eventually let fade out. Somewhere along the way I bought more than 20 domains, most of which never turned into anything real. I even built saralkheti.com, an agriculture advisory site in Hindi — my agronomy background finally meeting my content instincts — but it didn’t have the traction to justify keeping it alive, and I recently decided not to renew it.
I say all this because the version of this story where I “found my niche and everything clicked” isn’t honest. What actually happened is I kept hitting walls — no coding skills, no budget for paid tools, no team — until I found a workflow that didn’t require any of those things to be solved first.
Where Claude Actually Enters the Picture
I don’t use Claude as a novelty. I use it as the engine room of techdg.in’s entire content operation, and the workflow looks roughly like this:
1. Finding the angle. I don’t start with “what should I write about” in the abstract. I bring Claude real signals — trending AI stories, Google Search Console data, keyword gaps against competitors — and we figure out together which angle is actually worth writing, versus which one just looks tempting because it’s trending today.
That distinction turned out to matter more than I expected. Early on, I was publishing a lot of news-format posts chasing whatever AI story was blowing up that week. The traffic looked good on paper — high impressions — but almost nobody clicked through. Google’s AI Overviews were answering the question before anyone reached my site. I only understood this because Claude and I sat down with the actual Search Console numbers and traced it: news posts, high impressions, near-zero clicks; a comparison post I’d written on Codex vs ChatGPT, lower impressions, real sustained clicks. That one analysis quietly rewrote my entire content strategy.
2. Writing the actual article. Once we’ve picked an angle, Claude writes the full, publish-ready package — not a rough draft I have to rebuild, but something structured enough to paste straight into Gutenberg: the article, SEO metadata, an FAQ block formatted for Rank Math, and JSON-LD schema I drop into a Custom HTML block. I don’t touch code. I don’t need to.
3. The visual and video layer. Because I don’t have design skills either, Claude also handles the featured image (generated, not stock-photo generic), a script for my faceless YouTube Shorts channel, and a shorter repurposed version for X. One article becomes four pieces of content without me learning a single new skill.
4. The unglamorous SEO plumbing. Affiliate disclosure pages, cookie consent setup, author bio schema, fixing render-blocking scripts slowing down my site — none of this is exciting to write about, but all of it is the difference between a blog that ranks and one that quietly sits on page 4 forever. Claude has walked me through every piece of it, in plain language, because “plain language” is the only language I can act on.
The Honest Part: What Changed for Me
The biggest shift wasn’t speed, even though speed matters when you’re a team of one. It was that I stopped guessing.
Before, every decision — what to write, whether a headline was good, whether my site was technically healthy — was a shot in the dark based on gut feeling. Now, most of those decisions are grounded in something: actual GSC data, an actual keyword gap, an actual competitor comparison. Claude didn’t just help me write faster. It gave me a way to reason about a business I genuinely didn’t have the background for.
I also stopped chasing every shiny platform. After a Meta account suspension that never got resolved despite appeals, I made a deliberate call: invest in things I actually own — the website, the YouTube channel, an eventual email list — instead of building on rented land I don’t control. That’s not a Claude decision, but it’s the kind of clear-headed call that’s a lot easier to make when the rest of your operation isn’t held together by guesswork.
Where Things Stand Now
techdg.in is my one focused property now, built around five content clusters: AI tool comparisons, WordPress AI plugin tutorials, AI for SEO, basic SEO/WordPress guides from my own hard-won experience, and troubleshooting posts. Every piece fits into that system instead of being a one-off bet.
There’s a small but real signal I check now that I never used to: “AI Assistant” traffic in my analytics — clicks arriving from AI chatbots that cited techdg.in as a source. It’s not huge yet. But it’s growing, and it tells me the evergreen, well-structured, schema-backed approach isn’t just good for classic Google rankings — it’s also how you get found in whatever search looks like next.
None of this makes me a developer or a designer. I’m still the agronomy graduate who didn’t know what a chatbot was in 2018. What changed is that I found a way to run a real content business without needing to become someone else first.
That’s the actual story. Not “AI changed everything overnight” — just a slow, occasionally frustrating build, with a tool that finally matched how I actually work.
If you’re building something similar solo — no coding background, no big team, just persistence — I write about the real, unglamorous parts of that process on techdg.in. Not just the wins.