iHateReading — software development blogs

iHateReading is a software development learning platform that breaks programming topics into step-by-step threads, roadmaps, templates, and curated developer resources. The homepage lists practical tutorials for React, Next.js, Node.js, JavaScript, TypeScript, AI tooling, and product engineering. Each thread is a short, structured walkthrough you can skim, bookmark, and reuse while building. Use iHateReading when you need a concrete implementation path rather than a long essay: how to add auth, ship a SaaS starter, submit a product to directories, follow a frontend or backend roadmap, or scan GitHub trending repositories. Start from the article index at /blog, or the machine-readable list at /articles.json. Continue to Explore for curated blogs, the Magazine for a monthly developer digest, Roadmaps for skill paths, Store for website templates, Jobs for developer roles, and SaaS Directories for launch lists. Machine-readable index: https://ihatereading.in/llms.txt. Latest articles JSON: https://ihatereading.in/articles.json. RSS: https://ihatereading.in/rss.xml (also /feed.xml). Topics: https://ihatereading.in/topics (e.g. /topics/react). Search: https://ihatereading.in/search?q={query}. Blog sitemap: https://ihatereading.in/sitemap-blogs.xml. Sitemap index: https://ihatereading.in/sitemap_index.xml. About: https://ihatereading.in/about.

Machine-readable index: https://ihatereading.in/llms.txt. XML sitemap: https://ihatereading.in/sitemap.xml. Agent instructions: https://ihatereading.in/agent-instructions.md.

Show previous threadShow next thread

How to Get Free Traffic to Your Website in 2026: The Complete Free-to-Paid Growth Playbook

ree SaaS directories to submit for free 2026, Reddit marketing for startups without ads, Hacker News Show HN launch guide, Dev.to article distribution for developers, content scheduling tools for X LinkedIn Instagram, free-to-paid website traffic strategy, indie hacker distribution channels

Sep 10, 2026
min

Copy HTML

Copy Markdown

How to Get Free Traffic to Your Website in 2026: The Complete Free-to-Paid Growth Playbook cover image
Most founders treat traffic as a budget problem. It isn't.
It's a distribution problem, and distribution is the one part of building a product that costs nothing but time and consistency. A large share of indie hackers who fail don't fail on product — they fail on distribution, spending the overwhelming majority of their time on features and almost none on getting in front of people. This is the playbook we actually run to get free traffic to a website: every free channel that works in 2026, the exact tools that turn a single piece of content into a dozen posts across platforms, and the point where it genuinely makes sense to spend a few dollars to accelerate what's already working.
This is a long one — budget about 25 minutes. It's built to be a reference you come back to section by section, not a listicle you skim once and forget.
For starters, read these Reddit posts

Free traffic vs. paid traffic: the framework

Free traffic is any visitor who reaches your site without you paying per click or per impression — search engines, social shares, community links, directory listings, referrals. Paid traffic is anything you buy directly: ads, sponsored placements, boosted posts. The two aren't rivals. The strongest growth systems in 2026 use free channels to build the compounding base — content, community trust, backlinks — and paid spend to accelerate specific channels once you already know they convert. Paid ads scale fast but stop the instant the budget runs out; free traffic keeps compounding as long as the content, brand, and relationships behind it keep working.
The mistake most early-stage builders make is jumping straight to paid spend before they've proven a single free channel actually works. If a channel doesn't convert for free, paying to push more volume through it usually just burns money faster. Free-first, paid-to-accelerate is the order that holds up in practice.
Here's the process we'll walk through, in order:
  • Foundation — the content and product surface everything else points back to
  • Free distribution — directories, communities, and social platforms where you show up without paying
  • Automation — the tools that let one piece of content become ten posts without ten hours of manual work
  • The free-to-paid transition — where and when a few dollars actually buys leverage instead of just noise
One more thing before the channel-by-channel breakdown: pick two or three channels from this list and go deep for a real stretch of time — a common and painful mistake is trying to be everywhere at once, which produces noise instead of growth. Depth on two channels beats a shallow presence on eight.

Step 1: Build the foundation before you distribute anything

Every distribution channel below points traffic somewhere. That somewhere needs to already exist and already be good, or the traffic bounces and the distribution effort is wasted. Two things need to be in place first:
  • A piece of content or a product page worth linking to. If you're publishing a blog to drive traffic, make it genuinely useful — see our AEO guide for technical founders for how to structure content so it gets picked up by both search engines and AI answer engines, which is where a growing share of discovery traffic originates in 2026.
  • A clear idea worth building distribution around. If you're still validating what to build, work backward from demand first — our piece on finding your next SaaS idea covers that groundwork.
Once something exists that's worth pointing people to, everything below is about getting in front of the people who'd actually want it.

Step 2: Free SaaS directories — the lowest-effort, highest-leverage first move

Directory submissions are the closest thing to free money in early-stage marketing: a one-time form fill that keeps sending trickle traffic and, more importantly, a backlink, for years. A focused campaign across free directories with real domain authority beats a spray-and-pray blast across every directory you can find — the quality of the directory matters more than the raw count.
We maintain a running list of 393 SaaS directories, filterable by free vs. paid and sorted by domain rank, at ihatereading.in/saas-directories. Start with the free listings with the highest domain rank — Google Business Profile, Trustpilot, G2, Crunchbase, Product Hunt, and Hacker News are all free listings that carry real SEO weight. We also wrote up the reasoning behind the full directory list if you want the backstory on why we built it and how to prioritize which ones to submit to first.
Two directory listings deserve special mention because they double as active distribution channels, not just static form submissions:
  • Hacker News — a listing here is also a live community with its own submission mechanics, covered in detail below.
  • Dev Community (Dev.to) — same story: it's both a directory entry and an active publishing platform for technical content.
How to actually do this without losing a weekend: manually filling out 50+ directory forms is genuinely one of the most tedious tasks in early marketing — each has its own form, its own review timeline, and sometimes a fee that only appears after you've filled out the whole thing. If you have any scraping or automation skills, this is a strong candidate for an AI agent to handle: form-filling, screenshot verification, and status tracking are all things a scraping pipeline can do far faster than a human clicking through 50 tabs. We've written about the swarm-of-agents approach to content and SEO ops if you want to see what that looks like in practice.

Step 3: Reddit — the highest-trust, highest-risk channel

Reddit sends real, high-intent traffic, and it's one of the only major platforms where a genuinely good product can go from zero to thousands of visitors off a single well-received post. It's also the platform most founders get wrong, because the instinct to post a link and leave is exactly what gets accounts banned or, worse, shadowbanned without any notice at all.

The 90/10 rule

Reddit's own guidance, echoed across every serious Reddit marketing resource, is the 90/10 rule: roughly 90% of your activity should be genuine, non-promotional participation, and no more than 10% should reference your own product. That ratio is evaluated across your account's overall history, not per individual post, which means the real work starts weeks before you ever mention what you built. Individual subreddit moderators enforce their own, often stricter, versions of this ratio on top of the site-wide guideline — what's tolerated in r/SaaS can get you instantly banned in r/programming, so read each subreddit's sidebar rules before posting anything.
Practical steps:
  • Find your subreddits first. For a developer tool, that's places like r/SaaS, r/startups, r/webdev, r/programming, or niche subs matching your exact category. Search reddit.com directly for communities your ICP already hangs out in.
  • Spend two to three weeks just participating — answering questions, upvoting, commenting — before posting anything about your own product.
  • When you do post, lead with the problem, not the pitch. "I built X because Y kept happening to me" reads very differently from "Check out my new tool."
  • Always disclose your affiliation. Reddit users are unusually good at spotting undisclosed marketing, and getting caught hiding it costs you the whole subreddit's trust at once.
  • Never use multiple accounts to upvote your own posts, and don't buy upvotes or karma. This is worth stating plainly: paid upvote and karma services exist and are cheap, but they violate Reddit's content policy, they're increasingly detectable, and a caught account gets permanently banned along with every post it ever made — the opposite of what you're trying to build. The legitimate paid option on Reddit is Reddit's own advertising platform, which runs promoted posts transparently rather than faking organic ones — see the paid section below for how that fits in.
If you want to see what automated Reddit research looks like on the content side (not the posting side — finding what's already resonating), we covered our own Reddit trend-scraping pipeline — it's a good way to figure out which subreddits and topics are already primed for the angle you're bringing before you write a single post.

Step 4: X (Twitter) — build in public, daily

X remains one of the best places to build a founder audience in public. The strategy that consistently works for indie builders: post the process, not just the launch. Progress screenshots, small wins, the occasional failure, and genuine questions to your audience outperform polished announcement threads by a wide margin, because they read as a person building something rather than a brand broadcasting at people.
Basic cadence that works:
  • One build-in-public update per day (a screenshot, a metric, a decision you made and why)
  • One "lesson learned" or opinion thread per week
  • Reply to 5-10 relevant accounts in your space daily — replies are often a bigger growth lever than original posts for a new account, since they put you in front of an audience that's already engaged rather than waiting for your own following to notice you
Once you're posting daily, manually logging into X every time gets old fast, which is exactly where a scheduling tool earns its keep — covered in the automation section below.

Step 5: LinkedIn — underrated for B2B and technical founders

LinkedIn's organic reach for founder content has genuinely improved over the past couple of years, and it's a channel most indie hackers under-invest in because it feels less "cool" than X. For B2B SaaS, developer tools sold to teams, or anything with an enterprise angle, it's often the higher-intent audience — the people reading are frequently the ones with a budget and a buying decision to make, not just other builders scrolling for entertainment.
What performs on LinkedIn specifically:
  • Carousel-style breakdowns of a technical decision or architecture choice
  • "Here's what we learned building X" narrative posts with a specific, concrete lesson
  • Screenshots of real metrics or before/after results, with context on how you got there
Cross-post your X build-in-public content here too, but rewrite the framing — LinkedIn audiences respond better to a slightly more narrative, less shorthand style than X's clipped, in-the-moment tone.

Step 6: Instagram — visual proof and behind-the-scenes

Instagram is the least obvious channel for a developer tool, but it works surprisingly well for two specific content types: visual before/afters (a UI redesign, a dashboard glow-up) and behind-the-scenes founder content via Stories and Reels. If your product has any visual surface at all — a dashboard, a generated output, a design tool — this is worth the low effort of repurposing what you're already posting elsewhere. Don't build original Instagram-first content unless your product is inherently visual; repurpose your best X and LinkedIn posts as Reels or carousels instead, using the same content once you've already written it for another platform.

Step 7: Hacker News — the highest ceiling, the highest bar

A front-page Hacker News post is one of the biggest single traffic spikes available to a technical product — commonly 5,000 to 30,000 unique visitors in 24 hours for a front-page "Show HN," with a long tail of search traffic for months afterward because the discussion thread itself gets indexed and cited by search engines. It's also the community with the lowest tolerance for anything that smells like marketing, and the community that's best at spotting it instantly.
Rules that matter most:
We have a directory listing for Hacker News with more submission context if you want the quick-reference version alongside the rest of our directory database.

Step 8: Dev.to and the developer-publishing circuit

Dev.to, and platforms like it, are where a technical audience actually reads long-form content, and — critically — where you can republish content you've already written elsewhere without an SEO penalty, as long as you set it up correctly.
The canonical URL trick: when you publish your original article on your own domain first, then republish the same piece on Dev.to (or Medium, or Hashnode), set the article's canonical URL field to point back to your original. This tells Google the republished copy is a duplicate of your original rather than a competing version, so your own domain keeps the SEO credit while you still benefit from Dev.to's built-in audience. The same logic works in reverse too: treating your own domain as the canonical source and setting every republished copy's canonical tag to point back to it is what lets you leverage other platforms' audiences without losing ownership of your content. Publish and let the original get indexed first — Dev.to's canonical support is generally considered the most reliable among developer publishing platforms.
We built a small internal tool for this ourselves — a simple POST API that pushes a blog straight to Dev.to programmatically, which is worth a look if you're publishing often enough that manual copy-pasting has become the bottleneck. We also maintain a Dev Community directory listing with the specific submission details.
For the B2B and programming-adjacent angle specifically, tag your Dev.to posts and cross-post to relevant tags (#programming, #webdev, #showdev, #saas) so the platform's own discovery surfaces it to the right readers, not just your existing followers.

Step 9: Substack and Medium — content that compounds

Substack works two ways for a product: as a standalone newsletter that builds a direct-owned audience (the one channel that isn't subject to any platform's algorithm), and as a distribution surface where existing Substack writers in your niche might mention or link to your content if it's genuinely useful to their readers. Starting your own Substack newsletter is close to zero cost and turns every blog post into an email that reaches people directly, without depending on any algorithm's mood that day.
Medium is worth cross-posting to for the built-in reader base and, in practice, for the search visibility Medium's high domain authority carries — the same canonical URL approach from the Dev.to section applies here too. As an example of this in practice, we cross-posted our own SaaS directories research to Medium, which continues to pull in readers who never would have found the original iHateReading post directly. Medium is free to publish on and doesn't require an existing following to get initial reads, thanks to its topic-based internal distribution.

Step 10: Peerlist and Indie Hackers — the builder-native communities

Peerlist is worth treating as its own channel rather than just another directory. It combines a LinkedIn-style professional profile (pulling in your GitHub, Dribbble, and other work) with a weekly product launch board called Launchpad. Two things make it different from a typical launch platform: the launch window runs for a full week rather than one day, so timezone luck matters far less, and every launch is tied to your existing Peerlist profile, so credibility compounds across multiple launches instead of resetting to zero each time. Peerlist's audience skews heavily toward designers and developers specifically, which makes it a strong fit for a technical product or dev tool. It's also worth cross-checking our Product Hunt directory listing since the two platforms serve overlapping but distinct audiences and most founders should use both rather than choosing one.
Indie Hackers deserves a section of its own because it rewards a completely different pace than a one-day launch. Founders who commit to sustained community presence over several months — not a single launch event — tend to see meaningfully better conversion from Indie Hackers than from a single-day launch platform, because the platform's value comes from ongoing relationships and build-in-public threads rather than a one-time upvote spike. Post your build-in-public journey as a running thread, engage genuinely with other founders' posts, and treat it as a long game rather than a launch checkbox.

The automation layer: turning one post into ten

Posting consistently across Reddit, X, LinkedIn, and Instagram by hand is a full second job. This is where a small stack of scheduling tools pays for itself almost immediately, and there's a meaningful free tier available before you need to pay for anything.
ToolBest forFree tier
Postiz
All-in-one scheduling across X, LinkedIn, Instagram, Threads, Reddit, and more
Open-source, self-hostable for free (source on GitHub)
Hypefury
X-specific growth: thread scheduling, evergreen recycling of top posts, auto-repost across timezones
Free tier available, paid plans start around $19-29/mo
Taplio
LinkedIn-specific: AI-assisted drafting in your voice, scheduling, and engagement tracking
7-day free trial, paid plans start around $39/mo
Postiz is the one to start with if budget is genuinely zero — it's open-source and self-hostable, supports X, LinkedIn, Instagram, Threads, Reddit, Discord, and more from a single dashboard, and it has a hosted free tier too if self-hosting isn't your thing. It's the tool that lets you write one piece of content once and schedule adapted versions across every platform in this playbook without opening each app individually every day.
Hypefury and Taplio are worth the (small) paid upgrade once you're posting consistently enough that you can tell they're moving numbers — Hypefury's evergreen recycling in particular means your best-performing X posts keep circulating to new followers automatically, and Taplio's carousel generation is a fast way to turn a blog post directly into a LinkedIn-native format without redesigning anything by hand. Both tools also offer basic analytics that tell you which posts are actually working, which is the signal you need before deciding where to put paid spend.

Step 11: The free-to-paid transition — when a few dollars actually helps

None of the channels above require spending anything. But once you know a channel converts — you've posted on Reddit organically and it drove signups, or your Hacker News post landed and you can see where the traffic went — a small, targeted paid push accelerates what's already proven rather than gambling on what might work. A few places where modest spend genuinely helps:
  • Reddit's official ad platform for promoting a post that's already performing organically to a wider audience within the same subreddit's demographic — a legitimate paid extension of the same channel, distinct from any vote-manipulation service, and one that doesn't put your account at risk of a ban.
  • Paid tiers on the SaaS directories flagged in our directory list — many free directories offer a small paid upgrade (featured placement, faster approval) that's worth it once you've confirmed the directory itself sends real traffic. Some directories in the list also fall into the "free to submit, but only truly free after you complete the whole form" category, so read each listing carefully before assuming it's zero cost.
  • Paid plans on Hypefury and Taplio once manual scheduling is genuinely the bottleneck, not before — there's no reason to pay for automation on a posting cadence you haven't proven you can sustain manually first.
  • A small budget behind your best-performing organic post on LinkedIn or X, which most platforms let you boost directly to extend its reach to a wider, similar audience.
The rule of thumb: pay to amplify a channel you've already validated for free, not to skip the validation step entirely. Spending money is a legitimate, fast way to test whether a product has real pull once you have a baseline — it just shouldn't be the first thing you reach for.

Putting it together: a realistic weekly rhythm

Here's roughly how the free channels above stack into a week that doesn't eat every waking hour:
  • Monday — publish the week's main piece of content on your own domain. Submit it (or the product) to 2-3 relevant free SaaS directories.
  • Tuesday — Dev.to and Medium cross-posts with canonical tags pointing home. One genuine Reddit comment or contribution in a relevant subreddit (no promotion yet if you're still in the trust-building phase).
  • Wednesday — best day for a Hacker News submission if you have something genuinely show-worthy this week.
  • Thursday — LinkedIn carousel or narrative post breaking down something from the week's content. Peerlist Launchpad if you're launching something new, or an Indie Hackers build-in-public update if not.
  • Friday — Substack newsletter recapping the week, X thread summarizing the biggest lesson.
  • Daily, every day — one X build-in-public post, 5-10 replies to relevant accounts, scheduled through Postiz or Hypefury so it doesn't require logging in five separate times a day.
Give any single channel at least a month before judging it — most of the compounding channels here (SEO, directories, Hacker News, Indie Hackers) show their real value in the weeks and months after the post, not in the first 24 hours.

Common mistakes that quietly kill free traffic efforts

  • Posting the same generic copy everywhere. Each platform's audience reads differently — a Reddit post that sounds like a LinkedIn post reads as spam, and vice versa.
  • Promoting before participating. Every community-based channel above (Reddit, Hacker News, Peerlist, Indie Hackers) punishes accounts that show up only to post a link and disappear.
  • Skipping the canonical tag when cross-posting. Without it, you're handing your own domain's SEO credit to Dev.to or Medium for free instead of keeping it for yourself.
  • Buying fake engagement. Purchased upvotes, karma, or followers violate every platform's terms, are increasingly easy to detect, and the downside — a banned account and a torched reputation — is disproportionate to whatever short-term visibility bump they promise.
  • Trying to be everywhere at once. Spreading effort across five or six platforms from day one generates noise, not growth — two channels executed deeply beat six executed shallowly.
  • Giving up after one post. Most of the channels here have a long tail — real traffic often arrives months after the original post, through search, not in the first 24 hours.

FAQ

How long does it take to see results from free traffic channels? Directory listings and SEO-driven channels (Dev.to, Medium, your own blog) typically take weeks to months to show their full effect, since they depend on search indexing and compounding backlinks. Community channels like Reddit and Hacker News can spike immediately if a post lands, but the sustainable version of both depends on weeks of prior participation, not a single post.
Do I need to pay for anything to get started? No. Every channel in this playbook — directories, Reddit, X, LinkedIn, Instagram, Hacker News, Dev.to, Substack, Medium, Peerlist, Indie Hackers — has a genuinely free path. Postiz, the scheduling tool, is also free and open-source if you self-host it. Paid spend in this playbook is an accelerant for proven channels, never a requirement to start.
Is it safe to buy Reddit upvotes or karma to get past subreddit gates? No — this violates Reddit's content policy, risks a permanent ban on the account and everything it ever posted, and is increasingly detectable by both moderators and Reddit's own systems. Build karma the slow way, through genuine participation, or use Reddit's official ad platform if you want a paid option that doesn't put the account at risk.
Which channel should a solo developer start with? Dev.to and a free SaaS directory submission are the lowest-friction starting points — no community trust-building required, and both compound through SEO. Add Reddit and Hacker News once you have something genuinely show-worthy and have spent time participating first.

How to measure whether any of this is actually working

Distribution without measurement just feels like busywork after a few weeks, so track a small set of numbers from day one:
  • Referral source in your analytics. Know which channel each visitor came from — a UTM parameter on every link you post (?utm_source=reddit, ?utm_source=hn, ?utm_source=devto) takes thirty seconds to add and tells you which channels are actually converting versus which just feel productive.
  • Signups or conversions per channel, not just visits. A channel that sends 2,000 visitors and zero signups is worse than one that sends 200 visitors and twenty signups. Traffic volume alone is a vanity metric.
  • Time-to-payoff per channel. Directories and SEO-driven channels take weeks; Hacker News and Reddit can spike same-day. Don't compare them on the same weekly scorecard, or the slow-compounding channels will look like they're failing when they're actually just early.
  • Backlink count over time, if you have access to a tool like Ahrefs or even the free tier of Google Search Console — this is the number that tells you whether your directory and cross-posting effort is actually building domain authority, separate from any single week's traffic spike.
Revisit this monthly, not daily. Free-traffic channels are slow-compounding by nature, and judging Hacker News-style spike channels against SEO-style compounding channels on the same weekly report will make the compounding ones look like they're underperforming when they're actually just early.

Where to go from here

Free traffic isn't actually free — it costs consistency instead of a budget. Pick two or three channels from this list, run them for a full month before judging results, and layer in paid spend only once you can point to a specific channel that's already working. For more on the content and product side that all of this distribution is pointing back to, check our SaaS idea and monetization guide and the AEO guide for making sure the content itself is built to get found.
Want more breakdowns like this? Subscribe to the iHateReading newsletter or browse the Magazine for the monthly digest across frontend, backend, tools, and growth.

Subscribe

Our once a week newsletter on Programming, Jobs, AI, and Business