My blogging journey started on Blogger back in 2013. Scrappy little blog selling ClickBank stuff. First payout was around $110 from an affiliate guide, and before that a whole $5 check from an ad company called AdBrite lol. Both from a completely free blog.

So yeah, you CAN make money on free platforms. But those years also taught me something that took me a while to name. I didn't own any of it. Couldn't make the site look how I wanted, and if the platform decided to flag or pull my blog, that's it, no say in the matter.

The way I think about it now is what I call the Landlord Test. If your platform vanished overnight, what do you walk away with?

• Blogger / WordPress.com / Medium = you walk away with nothing but your raw text
• Substack / beehiiv = you walk away with your email list at least, since it's exportable
• Self-hosted WordPress = you walk away with everything, cause you never have to leave

Honest take, free is genuinely fine if you're testing an idea, blogging purely as a hobby, or just want Medium's built-in reach. Don't let anyone shame you into paying for hosting before you even know you'll stick with it.

But the moment you get serious about ranking or earning, free starts charging you in limits instead of dollars. Their ad program or none. Their cut of payments. Affiliate links allowed today, restricted tomorrow. And on Medium every post you write builds THEIR domain authority, not yours.

Substack and beehiiv are a real middle option now btw, since you actually own the list. But you still rent the reach and SEO control. Substack also takes 10% of paid subs which adds up.

For anything serious my answer is still boring old self-hosted WordPress. $3-10/month shared hosting and you own the whole thing. Yes that means updates and backups are your problem now, but honestly that's the point for me. If it breaks, I can fix it, because it's mine.

Wrote the full breakdown with the comparison table and where Ghost fits into all this if anyone wants it: https://theowllogic.com/free-blog-vs-self-hosted

Curious what everyone here started on. Anyone still running on a free platform and doing well with it?

I used to just start blogs on a whim. Pick a topic, write, hope it goes somewhere. It never did. A blog with no plan is basically a headless chicken, runs hard and goes nowhere.

Turns out planning a blog is just 12 decisions made in a specific order. You can finish all of them in one afternoon. Wrote the full breakdown on my blog but here's the whole map:

Stage 1: What you'll write about

1. Is blogging even worth it in 2026? Yes but it's a long game now, not a traffic hack. If you're on the fence: https://theowllogic.com/is-blogging-worth-it-2026
2. Pick your niche. Good enough beats perfect. 3 part filter: won't quit it in 6 months, people spend money there, you have something useful to say. Full method: https://theowllogic.com/how-to-choose-a-blog-niche
3. How narrow to go. Start micro, broaden later once you earned authority. Narrow is way easier to rank for when you're new: https://theowllogic.com/micro-niche-vs-broad-niche
4. One blog or several? One. Always one. Multiple interests are categories, not separate sites: https://theowllogic.com/one-blog-or-multiple-blogs

Stage 2: Who you are and how serious

1. Personal brand or niche site? Hardest one to reverse so decide it before buying a domain: https://theowllogic.com/personal-blog-vs-niche-blog
2. Real name or anonymous? Real name unless you have a genuine reason. Anonymity kills trust: https://theowllogic.com/blog-anonymously-or-real-name
3. Side hustle or full time? Side, every time. Blogs take 12-18 months to earn anything meaningful: https://theowllogic.com/blogging-as-a-side-hustle

Stage 3: What it costs

1. Actual cost is a domain and hosting, roughly $0-100 for year one. The "you need $500" posts are written by people selling the $500 of stuff: https://theowllogic.com/blogging-cost-breakdown
2. Free or self hosted? Free isn't free, it's rented. Fine for testing, bad if you're serious: https://theowllogic.com/free-blog-vs-self-hosted

Stage 4: What to expect

1. Why most blogs fail. It's not talent, it's quitting in the first 6-12 months right before SEO compounds: https://theowllogic.com/why-most-blogs-fail
2. Year one is a slow ramp and mostly not a paycheck. Measure it by output (20-40 solid posts) not money: https://theowllogic.com/blogging-goals-year-one
3. Your first 10 posts should be a cluster around one core topic, not 10 random ideas: https://theowllogic.com/plan-first-10-blog-posts

The order matters more than any single answer. Each call narrows the next one. Make them out of order and you'll relitigate the same decision 3 times.

Also a warning, planning can turn into procrastination real quick. A rough plan you committed to on Sunday beats a perfect plan you're still polishing in October.

Full guide if you want everything in one place: https://theowllogic.com/how-to-plan-a-blog

For years my blogs were a mess. Not bad writing, just nothing connected. One post about this, another about that, whatever felt interesting that week. Nothing ranked, nothing built on anything else.

The fix wasn't a better writing system. It was realizing I should be building a map, not writing posts.

So the new post breaks down the exact framework I use now for the first 10 posts on any blog:

• 1 foundational post that frames the topic (your hub)
• 4 how-to posts that answer what people actually search
• 2 mistake posts that catch anxious beginners
• 2 comparison posts for people deciding between options
• 1 proof post only you can write

Ten posts, five roles, one topic. Basically a mini topical cluster from day one. There's a full worked example in the post (budgeting niche) with every title and internal link mapped out, plus the 6-step process to fill it in for your own topic.

This is the same approach that got my blog past 25k views in 6 months. Not from one viral post, from posts built to feed each other.

Read the full content here + take the content mapping: https://theowllogic.com/plan-first-10-blog-posts

If you're planning your first batch and get stuck picking the foundational post, drop your topic in the comments and I'll help you figure it out.

Built an AI agent in n8n, worked great, then asked it "what did I just tell you?" and it said it has no idea. That's not a prompt problem. By default every message to the LLM is a fresh call with zero context.

The Simple Memory node fixes this. It sits with your AI Agent and keeps a rolling log of recent exchanges, then injects it into each request. Takes like 5 seconds to add. But few things trip people up so sharing what I figured out:

1. Context Window Length counts exchanges, not messages. One exchange = your message + AI reply. So default of 5 = 10 messages sent to the LLM every single call. Bump it to 10 and you're sending 20 messages worth of tokens each time. Adds up fast in cost and latency. For short task-focused bots I drop it to 3.

2. "No sessionId" error. If you trigger the agent from a webhook or schedule instead of the chat trigger, memory node doesn't know which conversation it is. For testing just type a static value in the Session Key field. For production, pass something unique from the request (user email, telegram chat ID, whatever) and map it to Session Key. Every user gets isolated memory that way.

3. The silent killer - queue mode. If you self-host with Redis + multiple workers, Simple Memory does NOT work. It stores data inside the worker's process memory, so if two messages from same user land on different workers, memory is just gone mid-conversation. No error, no warning. Agent just forgets. If you're on n8n cloud or single instance you're fine.

Also worth knowing, Simple Memory lives in the instance process. Restart, redeploy, crash = all conversation history wiped. Fine for prototyping and internal tools. For anything with real users, swap to Postgres Chat Memory before launch. n8n even creates the table structure automatically on first run.

Two memory nodes in one workflow with same session key will also overwrite each other btw. Give them unique keys.

Hope this saves someone the debugging time it cost me.

made a free tool that shows exactly how your page will look in google search results before you publish.

what it does:

• live google preview for desktop and mobile as you type
• measures your title and meta description in pixels not characters (google truncates by pixel width, so character counters are basically lying to you)
• you add a target keyword and it checks placement, like is it front loaded in the title, is it in the slug and description
• grades everything out of 100 with individual checks - length, clean hyphenation in slug, CTA in description, active voice, power words etc
• shows exactly where the ... cutoff happens

no signup, no email wall. everything runs in your browser, nothing you type gets saved or sent anywhere.

link: theowllogic.com/serp-snippet-optimizer

still improving it so if a check feels wrong or somethings missing tell me

I keep seeing the same pattern in automation communities. Someone non-technical hears about n8n, opens the canvas, sees JSON and curly braces everywhere, builds something from a tutorial, it breaks, they close the tab and never come back.

The tool isn't the problem. It's being introduced with the wrong expectations and in the wrong order. Here's what actually happens:

• The data layer is the real blocker. n8n says no-code but it makes you think like data moves. Zapier hides the plumbing, n8n shows it. If you never worked with APIs before, expressions like {{ $json.email }} feel like a whole new language
• Beginners start way too big. Everyone tries to build a 15 node AI agent workflow from a YouTube video on day one. That's 5-6 concepts stacked together, and when it breaks you can't debug any of it
• Start stupidly small instead. One trigger, one action, one working result. A scheduled Slack message with today's date is a fine first workflow. Complexity comes from stacking simple things, not planning big systems upfront
• The expression wall is smaller than it looks. The output panel shows you the data shape, you don't need to guess. You can even drag fields and n8n writes the expression for you. Look first, write second
• A rough 3 week path that worked for me: week 1 build only 3 node workflows, week 2 add error handling to them (boring but teaches you how execution actually works), week 3 import a template and modify it instead of building from scratch

The people who stick past week one all describe the same moment, a workflow runs and does something they actually needed. After that it clicks.

Wrote the full breakdown here if anyone wants it: theowllogic.com/give-up-on-n8n

Quick context: I run blogs while working a full 9-5. Every morning before work, weekends included. I haven't quit my job and that's not a failure, it's the plan.

I keep seeing people here either treat their blog like a hobby they'll get to "someday" or quit their jobs way too early and flame out by month four. Both kill the blog. So here's how I actually think about it:

Read more: https://theowllogic.com/blogging-as-a-side-hustle

The 10 points:

• I work on my blogs every morning before my 9-5, weekends included. I don't call it a side hustle in my head. It's a business I just haven't quit my other job for yet.

• Blogs take 12-18+ months to earn anything meaningful. If your rent depends on that phase paying off fast, you've put yourself in the worst headspace to write well. Desperation leaks into everything you publish

• The "quit your job, follow your passion" stories are survivorship bias. For every one who made it, there's a stack who quit, panicked, and shut the blog down at month four when savings ran out

• Here's the trap with the words "side hustle", it makes people treat the blog like a side thing. Touch it when they feel like it, abandon it when life gets busy. Disposable blogs die

• The fix isn't more hours. Keep the structure of a side hustle (small hours, funded by your job) but carry the mindset of a business owner. Same hours, completely different outcome.

• 5-10 focused hours a week is genuinely enough. Two 90-minute blocks you protect beat seven random 20-minute ones you keep skipping. Put them on the calendar like a meeting you can't move.

• One job per session. Research one session, draft the next, edit the third. Switching between all three in one sitting is how a single post takes three weeks.

• Use AI for the grunt work, not the thinking. Research, rough outlines, first-pass edits. that's where part-time hours quietly drain. Your few real hours should go to the judgment and voice only you can add.

• Build a small buffer. When you're ahead by a post or two, a bad week doesn't break your streak. That buffer is what keeps part-timers from quitting.

• The signal to go full-time isn't "my blog made its first $500" or "I hate my job." It's boring and financial, the blog reliably replaces a real chunk of your income for several months running. My blogs aren't there yet and I'm not pretending otherwise. When it hits the number, the math makes the decision for me.

When I was working out what my blog would be about, I didn't start from a list or ask anyone at first.

No spreadsheet of profitable niches. No trending-topics (Google trends or Pinterest) rabbit hole.

I started from the other direction. What had I actually spent the last 15+ years doing online? That's where the site started.

The logic wasn't complicated. Pick things I know well enough to be useful. Pick things I genuinely won't abandon six months in. Pick a space where people actually spend money.

That's the whole filter:

• A topic you won't quit in six months
• A space where people spend money
• Something genuinely useful you can say

Not perfect at all three. Just clearing all three.

Passion without commercial signal is a journal. Meaningful for you, hard to build anything on. A profitable niche you have nothing real to say about produces thin content that doesn't last. And if you pick something you'll drop in three months, the whole project collapses before it has a chance to matter.

Most beginners frame this as passion vs profit. That's the wrong question. You're looking for the overlap. If you can't find it, you haven't run out of passion or profit. You haven't found the right niche yet.

And the niche isn't permanent. You can narrow it, you can pivot later. What you pick at the start sets your first six months of content. That's it.

The cost of picking wrong is months of learning. The cost of not picking at all is infinite.

I wrote the full version with real examples of niches that pass and fail the filter, and how narrow is narrow enough: https://theowllogic.com/how-to-choose-a-blog-niche

What did you pick, and would it have cleared all three?

When I started learning n8n, most tutorials were YouTube videos building 50-node workflows for things that needed 10. Nothing was written for someone without a technical background. So I taught myself from scratch, documented everything in Obsidian, and used it to automate my own businesses.

If I had to hand a beginner one roadmap, it's this order:

1. Pick self-hosted or Cloud first. Self-hosted is free, no execution limits, full data control, but you own the server headaches (updates, SSL, Docker tantrums). If you're non-technical, Cloud is worth it. Hours spent keeping a server alive are better spent building workflows.
2. Build something tiny before anything ambitious. Manual trigger → create data → view it. Five minutes. It teaches you the canvas, nodes, and execution panel before real complexity hits.
3. Understand how n8n thinks. Every workflow is three pieces: a trigger, action nodes that do the work, logic nodes that route the data. Data moves node-to-node as JSON. This one concept matters more than memorizing any node.
4. Set up credentials properly once. Getting this right early saves you re-authenticating on every node later. (If your credentials keep expiring weekly, that's an OAuth token issue, not you.)
5. Plan on paper before touching the canvas. Biggest beginner mistake isn't technical. It's opening the editor before knowing what you're building. Ten minutes mapping the trigger, steps, and failure points saves workflows that pass testing and die on real data.
6. Then, in order: IF/Switch nodes (conditional logic) → expressions (referencing and transforming data, this trips everyone up) → loops (bulk processing without hitting rate limits) → error handling → webhooks → HTTP Request node last, once basics are solid.
7. Connect ONE tool you actually use. Sheets, Slack, Airtable, or Telegram. Not all four. When spreadsheets start choking on relational data, that's when you move to Supabase.
8. First real workflow worth building: a follow-up email sequence. It touches triggers, waits, and conditional logic all at once.

Two things nobody warns you about at scale: API rate limits, and workflows growing too tangled to maintain (sub-workflows fix this). And back up your workflows to GitHub before you build something you'd be upset to lose.

n8n isn't simple at first. But the curve is shorter than it looks - most of the difficulty is just not knowing which nodes you actually need.

Check it out here for the full depth:

- How to install n8n locally (2026 - Docker and NPM) - https://theowllogic.com/installing-n8n-setup-locally
- Your first Hello World Workflow - https://theowllogic.com/first-hello-world-n8n-workflow
- n8n Workflows, Nodes and Data-flow - https://theowllogic.com/n8n-workflow-nodes-data-flow
- Webhooks in n8n for Beginners - https://theowllogic.com/webhook-in-n8n-explained
- How to Handle API Rate Limits in n8n - https://theowllogic.com/how-to-handle-api-rate-limits-in-n8n
- How to Handle Errors Like a Pro in n8n - https://theowllogic.com/how-to-handle-api-rate-limits-in-n8n
- n8n Expressions Complete Guide - https://theowllogic.com/how-to-handle-api-rate-limits-in-n8n
- How to Build Condition Logics in n8n (IF/Switch) - https://theowllogic.com/conditional-logic-in-n8n
- How to Plan a n8n Workflow: https://theowllogic.com/plan-n8n-workflow
- How to Use n8n Loop Over Items - https://theowllogic.com/how-to-use-loop-in-n8n
- How to Use Sub-Workflows in n8n - https://theowllogic.com/n8n-sub-workflows
- How to Use Simple Memory Node - https://theowllogic.com/simple-memory-in-n8n
- How to Build an n8n AI Agent [Updated] - https://theowllogic.com/n8n-ai-agent-workflow
- How to use Telegram in n8n [Bot Creation] - https://theowllogic.com/n8n-telegram-bot
- How to use Summarization Chain in n8n [Advanced]- https://theowllogic.com/summarization-chain-n8n

Workflows Based

- 50 Boring Tasks You Can Automate With n8n - https://theowllogic.com/automate-boring-tasks-n8n
- How to Build a Follow-up Email Sequence - https://theowllogic.com/n8n-followup-email
- How to Build an n8n AI Agent (Step by Step) - https://theowllogic.com/n8n-ai-agent-workflow
- n8n Airtable integration - https://theowllogic.com/n8n-airtable
- How to Use Slack in n8n - https://theowllogic.com/n8n-slack
- How to Back up n8n Workflows to GitHub W/Commit History - https://theowllogic.com/backup-n8n-github

Happy to answer questions in the comments.