How to Start a Blog That Actually Earns Traffic

Key takeaways

Put your blog on a subdirectory of your main domain (yoursite.com/blog), not a subdomain, so it inherits your site's existing authority instead of starting from zero.
Write your first post as the answer to a question your exact reader is already typing into Google or ChatGPT — not an introduction to yourself or your company.
Plan your first 10-15 posts as a connected cluster before you publish post one, or you'll end up with orphaned pages that nothing links to and nothing ranks.

Pick the platform based on who maintains it in six months

Most "how to start a blog" advice treats platform choice as the hard part. It isn't. WordPress, Ghost, and a static site generator like Astro or Next.js will all rank fine — Google's crawler doesn't care what generated your HTML. What it does care about is whether the page loads fast, has a clean URL, and isn't buried three clicks deep.

The real decision is who's going to publish to it after the novelty wears off. If that's a non-technical founder, a hosted CMS (WordPress.com, Ghost(Pro), Webflow) beats a self-hosted static site every time, because "add a blog post" shouldn't require a pull request. If you're a solo technical founder who'll write in Markdown anyway, a static generator gives you faster pages and fewer plugin-security headaches — WordPress sites are a disproportionate target for exploits precisely because plugins are so easy to install and so rarely updated, a point the Cybersecurity and Infrastructure Security Agency has flagged repeatedly in advisories about outdated CMS software.

One decision here is not reversible without pain: domain placement.

yoursite.com/blog — shares your root domain's backlink profile and domain history from day one.
blog.yoursite.com — some crawlers and analytics tools treat it as a semi-distinct property, which can dilute the authority transfer between your blog and your product pages.

Google has said subdomains versus subdirectories don't inherently affect rankings, but in practice, most SaaS teams we've watched migrate from a subdomain to a subdirectory see a bump in organic traffic within a few months — because internal linking and topical relevance finally flow in one direction instead of being split across two "sites."

Decide what the blog is for before you write anything

A blog without a job description turns into a graveyard of three posts from 2024 and nothing since. Before you touch a CMS, answer one question: is this blog for organic search traffic, for building an audience you own, or for getting cited by AI tools when someone asks a question in your category? Those goals point to different post types.

Search traffic rewards specific, answerable posts tied to real query volume — "how to export Stripe invoices to Xero," not "thoughts on billing."
Audience-building rewards a recognizable voice and a consistent publishing rhythm people can plan around.
AI citation (GEO) rewards clear, self-contained definitions and answers near the top of the page — the exact paragraph structure this article opens with.

Most indie hackers try to do all three at once with the first post and end up with something too vague for any of them. Pick one as primary. You can layer the others in later once you have ten posts and can see what's actually getting clicks.

Structure your first posts as a cluster, not a list

The single biggest mistake we see when a founder starts a blog solo: publishing whatever topic seems interesting that week, with no plan for how the posts connect. Six months later there are 12 posts, none of them linking to each other, and Google Search Console shows most of them getting zero impressions because nothing on the site signals they're related or important.

Instead, pick one broad topic your product solves and map it like this before writing:

One pillar post — the beginner's overview of the whole topic, comprehensive enough to be the obvious link target for everything else.
Four to eight cluster posts — narrow, specific answers to sub-questions, each linking back to the pillar and to each other where relevant.
One comparison or decision post — "X vs Y" or "when to use X" — because these convert better than either individual topic post and often earn backlinks from people writing about the same comparison.

If you're not sure what a strong pillar post looks like structurally, this guide to writing a beginner's guide that ranks long term walks through the format that tends to hold its ranking for years instead of months.

Write the first post to answer, not to introduce

Skip the "welcome to my blog" post. It has no search demand — nobody types "welcome to my blog" into Google — and it wastes the one slot where you have the most motivation to write well. Your first published post should target a question with actual demand, answer it in the first two sentences, and then go deeper.

This structure also happens to be what AI answer engines look for when deciding what to quote. Tools like ChatGPT's browsing mode and Perplexity tend to pull the sentence that most directly and completely answers the implied question, usually from near the top of the page, not from a well-argued conclusion three screens down. Writing your key claim first isn't just good UX — it's the exact shape that gets lifted into an AI-generated answer with your source attached.

If you plan to lean on AI drafting tools to get through the backlog faster (most solo founders end up doing this within the first month), build a verification step into your process before you publish, not after. Wrong dates, invented statistics, and misattributed quotes are the most common failure mode we see in AI-assisted drafts, and they're the fastest way to get a post quietly excluded from citation once an AI engine or a sharp reader catches one factual error. This process for fact-checking AI-generated posts quickly is worth setting up before you publish post three, not after someone emails you a correction.

Build for posts that still work in three years

A blog that only produces content tied to news cycles or version-specific screenshots needs constant rewriting just to stay accurate — and most solo founders don't have the bandwidth to rewrite twelve old posts every quarter. The fix is writing a meaningful share of your early posts as evergreen: content anchored to a problem that doesn't change, even if the tools mentioned do.

Compare two post types:

"5 Best AI Writing Tools in 2024" — dead within a year, needs a full rewrite or it visibly ages.
"How to Evaluate an AI Writing Tool Before You Buy" — the criteria stay useful regardless of which tools exist.

Writing genuinely evergreen content up front means fewer emergency rewrites later, and it compounds — a post that's still accurate and still ranking after 18 months is worth far more than three posts that each got a burst of traffic and died.

Even evergreen posts drift, though — pricing changes, product screenshots go stale, a linked tool gets acquired and renamed. Set a recurring quarterly check rather than waiting for traffic to visibly drop before you notice. A workflow for refreshing older posts is far cheaper than writing replacements from scratch, and it signals freshness to both Google's crawler and AI tools that weight recency when choosing what to cite.

Set realistic expectations for when it starts working

Google itself states that new sites and new pages typically take weeks to months to get crawled, indexed, and begin appearing in search results — there's no fast lane, according to Google's own Search Central documentation. A blog with five posts and no backlinks isn't going to outrank an established competitor's fifth post in month one, no matter how well it's written.

What actually moves the timeline:

Internal links from your homepage or nav to at least your pillar post — pages with zero internal links are far slower to get crawled at all.
One or two backlinks from relevant sites, even small ones — this remains one of the strongest trust signals available.
Consistent publishing — not because "the algorithm rewards frequency" (it doesn't directly), but because each new post is another chance to rank, another internal link target, and another data point showing the site is maintained rather than abandoned.

Plan for three to six months before you can honestly evaluate whether the strategy is working. Anything judged before that is judging noise, not signal.

Frequently Asked Questions

Q: Do I need a custom domain to start a blog, or can I use a free subdomain from the platform?

You can technically start on a free subdomain (like yourname.wordpress.com), but you should move to your own domain before investing real time in content — free subdomains can't be migrated without losing SEO history, and most platforms limit customization and monetization until you upgrade.

Q: How often should I publish when starting a blog?

Consistency matters more than frequency — one well-researched post every two weeks that answers a real question beats four thin posts a week. What matters for search and for AI citation is that the archive keeps growing and older posts get occasional updates, not that you hit a specific weekly quota.

Q: Should I write blog posts myself or use AI to draft them?

Either works, but AI drafts need a fact-check pass before publishing since factual errors — wrong dates, invented statistics, misattributed claims — are the most common failure and the fastest way to lose trust with both readers and AI answer engines that might otherwise cite the post.

Q: What's the fastest way to get my first blog post noticed?

Link to it from somewhere with existing traffic — your homepage nav, an existing product page, or a relevant online community — and target a specific question with real search demand rather than a broad topic, since narrow questions face far less competition for a brand-new domain.