How to Promote Blog Posts With No Audience Yet
If your new blog is getting no traffic, the most likely explanation is neither that your writing is bad nor that you need to wait longer — it's that nobody has put the post in front of a human yet. Ahrefs re-ran its ranking-age study on a million URLs and found that only 1.74% of newly published pages reach Google's top 10 within a year. So the practical answer to "how do I promote blog posts with no audience" is: build a per-post seeding plan — three to six hand-picked placements, chosen for the post rather than for your convenience, with a comment you write yourself — and treat it as a step in the publishing workflow rather than something you get around to.
That reframing matters more than any single tactic, because it changes what publishing means. Hitting publish isn't the finish line; it's the halfway mark. Marko Saric of Plausible Analytics put it about as plainly as it can be put: "The promotional work only starts after the blog post has been published."
The arithmetic that makes seeding non-optional
Start with the numbers, because the standard advice — write good stuff, be patient, SEO takes six months — was calibrated for a web that no longer exists.
That 1.74% figure has an inverse worth sitting with: 98.26% of the URLs Ahrefs sampled did not reach the top 10 within a year. And it's getting harder. The 2017 version of the same study found 5.7% — more than three times the current rate. Meanwhile the pages already sitting up there are entrenched: 72.9% of top-10 pages are more than three years old, and the average #1-ranking page is now five years old, up from two. You aren't competing against pages. You're competing against pages with a five-year head start.
Zoom out and it's bleaker still. Ahrefs' study of roughly 14 billion pages found that 96.55% get zero traffic from Google, with another 1.94% getting between one and ten visits a month — and Ahrefs notes its index skews toward the higher-quality end of the web, which makes that figure generous rather than harsh.
Then there's the prize itself, which has shrunk. SparkToro's analysis of Similarweb clickstream data found that in January–April 2026, 68.01% of US Google searches ended without a click, up from 60.45% in 2024. Pew Research Center's study of 900 US adults in March 2025 shows the mechanism up close: users clicked a traditional search result on 8% of visits to a results page with an AI summary, versus 15% without.
Stack those together and the picture is stark but clarifying: even in the good scenario where your post eventually ranks, the wait is long and the payoff smaller than the advice assumes. Waiting is not a strategy — it's the absence of one. (We've covered what a blog is still worth when most searches end without a click separately.)
Here's the part that turns all this from discouraging into actionable. Ahrefs names three causes of zero traffic: no search demand, no backlinks, and a mismatch with search intent. Two of those three are fixed by distribution, not by writing better. On backlinks specifically the numbers are brutal — among pages with no referring domains at all, roughly 1 in 6,671 gets more than 1,000 monthly visits. Seeding is how a new blog gets its first referring domain at all.
Bad, or just young? Run the diagnostic before the tactics
Before you place anything, answer the question that's actually keeping you up: is this post underperforming because it's bad, or because it's new?
There's no official Google sandbox. Google's John Mueller: "it's possible that in certain situations, some pages show up well quickly, while others take longer. There's no fixed rule or timeline there." So ignore the folklore about a fixed three-to-nine-month penalty box and use the distribution data instead.
The most diagnostic number in the Ahrefs study is this one: of the pages that did reach the top 10, 40.82% got there within one month. Fast ranking is not rare among winners — it's the modal outcome. Which means "it's just too young" is a strong defence at six weeks and a weak one at six months.
Here's the ladder I'd use:
- Not indexed after several weeks. A discovery problem, not a quality one. Check crawl paths, sitemap and internal links before you rewrite a word.
- Indexed, zero impressions for the target keyword at 8–12 weeks. Likely demand or intent — Ahrefs' causes one and three. Nobody is searching this, or the people searching it want something structurally different.
- Impressions rising, clicks flat. Now normal rather than a failure. Ahrefs' own data showed the correlation between impressions and clicks flip from +0.425 in late 2024 to −0.352 in early 2025, and across roughly 300,000 keywords, the presence of an AI Overview correlated with a 34.5% lower click-through rate. Read Search Console the old way and you'll rewrite posts that are working.
- Still nothing at six-plus months. Given that 40.82% figure, the "too young" explanation has largely expired.
The honest shortcut sits underneath all four: a seeding round is the only quality test that returns a result before the SEO clock does. Put the post in front of 200 real humans in a relevant community and you learn in an afternoon what search would take four months to tell you. If nobody engages, that's your answer, and it was cheap.
The alternative — publishing more and hoping — has a well-documented failure mode. A solo founder writing as IFS Space published 47 posts over roughly 120 hours of work and got about 45 Search Console impressions a month across all of them. Their own diagnosis is the line worth pinning above your desk: "Volume is a hiding place. I published 47 times instead of figuring out why the first 5 didn't work." Their further reading — that mediocre posts diluted their domain signals — is a personal inference rather than something Google has stated. But the impressions count isn't an inference, and it cost 120 hours. If you're weighing cadence against depth, our take on how often a small blog should actually publish covers where the frequency curve flattens.
The seeding plan, as a step in the workflow
The reason seeding gets skipped is that it lives nowhere. Drafting has a slot in your week; placement doesn't. So give it one — a fixed sequence that runs every time, in this order.
1. Publish, then confirm indexation before you syndicate. If you plan to cross-post to dev.to or Hashnode, let the canonical original get crawled first. Google no longer recommends cross-domain canonicals for syndicated content, and syndicated copies have been indexed ahead of originals. A few days of patience protects the version you own.
2. Send it to ten people by name, before any public placement. In founder accounts of landing the first ten customers, the pattern is almost never broadcast. Proxycurl's Steven Goh: "Cold email outreach got our first 10 paying customers," with SEO only dominating much later. Tally's Marie Martens DM'd Product Hunt users who had upvoted similar tools. The sequence is consistently outreach first, search later.
3. Place it in three to six hand-chosen communities, matched to the post. Not your defaults — the post's. When Plausible published "Why you should stop using Google Analytics on your website," their list was Twitter, Mastodon, Indie Hackers, Lobsters, Hacker News and r/degoogle. Six placements, each full of people who plausibly care about that specific argument.
4. Read each venue's rules first. Step zero, not a footnote — the next section covers why.
5. Write the accompanying comment yourself. Every word of it. That's the difference between a placement that works and an account that gets burned.
6. Set up keyword alerts so future placements come to you. F5Bot monitors Reddit, Hacker News and Lobsters for your keywords on a free tier and alerts within minutes; it has run since 2017 and delivers around 430,000 alerts a day. The best placement is often a reply to somebody else's question rather than a submission of your own.
Notice what this sequence assumes: hours available for placement. Most founders don't have them, because research, drafting and fact-checking already ate the week. That's the real argument for automating the half of the workflow that can be automated. Magic Share is built for exactly that split — the agent researches, drafts and verifies every cited link, then waits for your approval, so the scarce human hours go into the half a machine genuinely cannot do.
Does one seeded post actually move anything? Plausible's numbers are the best-documented case for this audience. Before that post, the site had 27,300 unique visitors in about 15 months. In the week after: more than 48,000 unique visitors and 166 new trial signups, more than the previous four months combined. Over the following 135 days, their traffic-source table reads: Hacker News 43.6K, Twitter 10K (from 674 followers), Facebook 6.4K at an 87% bounce rate, Google Search 6.3K but the highest-quality at 3+ minutes average visit duration, Indie Hackers 4.8K, Hacker Newsletter 2.6K, Reddit 2.2K, Dev.to 2.2K. MRR went from $415 in early April to $2,750 by the end of July, with zero paid ads.
Read that table closely and it says something the headline number doesn't: the seeded channels delivered the volume, search delivered the quality. You need both — but only one is available to you in month three.
The placement rules nobody tells you until you break them
Communities aren't distribution channels; they're rooms with house rules, and the rules are published. Reading them takes ten minutes and saves an account.
Hacker News. Blog posts are explicitly not eligible for Show HN: "Show HN is for something you've made that other people can play with… Off topic: blog posts, sign-up pages, newsletters, lists, and other reading material. Those can't be tried out, so can't be Show HNs." Submit it as a normal story. The self-promotion guideline is a ratio, not a ban — "It's ok to post your own stuff part of the time, but the primary use of the site should be for curiosity" — and asking friends to upvote is out: "Don't solicit upvotes, comments, or submissions."
The mechanics are worth knowing before you're disappointed. One community analysis of HN's ranking behaviour reports that a new story starts at 1 point and needs roughly four more to break into the Top 30, from an estimated 30 or so views in the new queue — about a 13% conversion. Median story score is 1–2 points; most stories go nowhere. If yours does, there are two sanctioned second chances. Moderator dang has said that if a good submission got no attention, "please tell us at hn@ycombinator.com!… It's fine if it's your own article, but we like it better when it's just something you ran across and recognized as good" — rescued stories go into a pool that moderators re-drop onto the lower front page. The other is a repost, which HN permits a small number of times within roughly a year. What you may not do is delete and repost: "Deletion is for things that shouldn't have been submitted in the first place."
Lobsters. Invitation-only, and self-promotion "should be less than a quarter of one's stories and comments." The rule that catches new blogs specifically: users are treated as new for their first 70 days, and during that window they can't submit links to domains the site hasn't seen before. Your brand-new domain isn't submittable on day one, however good the post is.
Reddit. A July 2026 audit of 49 subreddits founders commonly pitch in found that 39% ban self-promotion outright, 22% allow it only under a 9-to-1 ratio, 37% handle it case by case, and exactly one — r/SideProject — openly welcomes it. r/Entrepreneur (5.2M members) bans promotion despite its reputation as a founder hangout; r/marketing runs a zero-tolerance permanent-ban policy; r/SaaS permits occasional mentions at most once every 60 days, with disclosure. None of that is hostile to you — it's what keeps those rooms worth posting in.
dev.to and Hashnode. Legitimate channels — Plausible pulled 2.2K visitors from Dev.to — with the ordering caveat above. Original first, syndicate after.
X. Posts containing off-platform links are widely reported to see reduced reach, with figures circulating in the 50–90% range and link-in-the-first-reply as the common workaround. Treat those numbers as reported rather than measured — no primary measurement is public — but the pattern costs nothing to adopt. Plausible's 10K visitors came from 674 followers, so a small account isn't disqualifying.
Newsletters. Hacker Newsletter is a hand-curated weekly digest of HN with more than 60,000 subscribers, running since 2010 — a second bite at that audience even if your submission never surfaced. It sent Plausible 2.6K visitors.
One more legitimate door: HN runs recurring "share your personal website" threads, and they're real placement rather than spam — the January 2026 edition drew 950 points and 2,386 comments. Google's own SEO starter guide points the same way, naming word of mouth, community engagement and newsletters as ways to get people to your site — while warning that "you can overdo promoting your site and actually harm it."
What "good" looks like when you read the signal back
Seeding produces a number. The trick is knowing what number to expect, so you can tell a decent result from a disappointing one instead of measuring everything against a fantasy.
Two first-hand accounts bracket the range. A completely new site with zero prior traffic hit #17 on the HN front page with 68 points and saw roughly 3,500–4,000 visitors from the front page during about an hour of exposure, and around 8,000 uniques over four days. At the other end, a site with two posts sitting at positions 4 and 5 recorded roughly 43,000 unique visitors in 20 hours. So: mid-front-page is low thousands, top-five is tens of thousands.
Now convert that into things you keep. At the web-wide average email opt-in rate of 2.1% of visitors — drawn from Omnisend's analysis of over 1.24 billion popup displays, so ecommerce-skewed and rough — a 4,000-visitor spike "should" yield around 80 subscribers, and well-optimised capture at 3–8% would double or triple that. For trials, Plausible's week is the reality check: 48,000 visitors produced 166 trials, a 0.35% rate.
When a seeding round sends a spike your way, the harder question is which post actually produced the signups, and blog attribution on low-traffic sites explains how to tell when the numbers are small.
That's the honest framing of what a spike buys. Not sustained traffic — the spike dies within 48 hours, every time. What it buys is referring domains, subscribers and evidence. Given the 1-in-6,671 odds for pages with no backlinks, the referring domains alone justify the afternoon.
To judge the post rather than the placement, use engagement benchmarks. Contentsquare's Digital Experience Benchmark, published March 2026 from 99 billion sessions across roughly 6,500 sites, puts scroll rate at 50.5% on desktop and 45.2% on mobile. Land well below that with a warm, well-matched audience and you have a content signal, not a distribution one. Animalz's framework is the right lens: engaged sessions of 60+ seconds and scrolls to 90% depth are the leading indicators; conversions and revenue are the lagging ones. Or as they put it: "Better one lead in your inbox than a hundred pageviews."
Seeding is also how you get cited
There's a second return on community placement that barely existed three years ago, and for a blog with no rankings it may be the more durable one.
Treat that return as real but volatile, and don't build the plan on any one platform's citation habits. In late 2025, Semrush's study of AI-search citations (data refreshed in October 2025) found Reddit was the single most-cited domain on Perplexity, second on SearchGPT at 13% of responses, and third on Google AI Mode at 9%, and that 80% of the cited Reddit posts had fewer than 20 upvotes. Within a year that picture had moved. Ahrefs' October 2026 analysis of US ChatGPT answers found that ChatGPT's Reddit citations dropped 88% between March and September 2026: in March about 1 in every 5 answers cited Reddit, and by late September about 1 in 43. Wikipedia fell over the same period too.
The detail that should change your behaviour is where those citations went. Per Ahrefs, they moved to "research bodies, regulators, brands and hands-on testers, while explainer and aggregator sites fell." So seed a post where the people who need it actually gather, because that's where readers and links come from, and expect any AI citations to follow the original work on your own page rather than the thread you posted it in. A specific, genuinely useful answer in a quiet Q&A thread still helps the person who asked. Just don't count on it as your route into ChatGPT.
Is that traffic worth anything? Small but unusually valuable. Ahrefs found that over 30 days to mid-June 2025, AI search accounted for 0.5% of its visitors but 12.1% of its signups — roughly a 23× conversion multiple. Their own Ryan Law adds the caveat: "These CTRs are probably the highest they'll ever be as the novelty of this format wears off." Directionally useful, not a forecast.
You can now partly measure this. Google Search Console gained a dedicated generative-AI performance report on June 3, 2026, covering AI Overviews, AI Mode and generative AI in Discover — but it reports impressions, pages, countries, devices and dates, not clicks or CTR, and is rolling out to a subset of sites. So AI visibility is becoming measurable as impressions, which is precisely the metric that has decoupled from clicks. If citations are the goal, the on-page patterns that earn AI citations matter as much as where you place the link.
The honesty constraint — and why it works in your favour
If an AI assistant is anywhere in your writing process, this is the section that decides whether your seeding plan survives contact with these communities.
The venues have hardened. Hacker News added an explicit guideline: "Don't post generated text or AI-edited text. HN is for conversation between humans." In the thread announcing it, moderator dang drew the distinction carefully: "We aren't asking people to not use AI. (We use it ourselves.) What we're asking is not to post AI-generated comments to Hacker News" — adding that the rule partly exists "to protect users who don't realize how much damage they're doing to their reception here when they think 'I'll just run this through ChatGPT to fix my grammar and spelling.'" On Reddit, an analysis of 307,543 subreddits crawled in November 2024 found only 1.2% had any AI rule at all — though that had doubled in sixteen months, and among the largest 1% of subreddits adoption went from 8.4% to 17.1%. Of the AI rules studied, 55.23% were outright bans and 17.95% disclosure requirements; Reddit's own policy requires disclosure of primarily-AI content.
So the operating rule is simple, and it's a line rather than a compromise: the draft can be agent-assisted and human-approved; the comment you post must be written by you. Nothing in HN's guidelines bans linking to an article that had machine help — the guideline governs text posted to HN. What it bans is pasting a model's output into a conversation between people. That distinction is easy to respect and expensive to violate.
There's a broader reason to hold the line. Graphite's analysis of a Common Crawl sample found that AI-generated articles crossed human-written ones in November 2024 and have hovered near half of new articles since, reaching 51.7% by May 2025 — while concluding that those articles "largely do not appear in Google and ChatGPT." Half the new web is machine-made and mostly invisible. Being on the visible side comes down to whether a human checked it, whether the citations resolve, and whether anyone would place it in a community they care about. That last test doubles as an editorial filter: if you wouldn't post it under your own name, with your own comment explaining why it's useful, it probably isn't ready to publish either.
What to measure instead of traffic
Traffic is the wrong scoreboard for a blog this young, because it will read close to zero for months regardless of what you're doing right.
Rand Fishkin's alternative is to replace traffic KPIs with correlation dashboards — branded search volume, social engagement, share of voice, audience growth — and to invest in earning influence without requiring a visit. Seth Godin's June 2026 note on independent blogs lands in the same place from another direction: treat traffic as unpredictable, build direct subscriber relationships, serve niche audiences rather than depending on centralised platforms.
For a blog in month three, compress all of that into one target: the first 100 readers you can name. Email subscribers, repeat visitors you recognise from a Discord, the three people who replied. It's a smaller number than a traffic chart and a far better one, because it's the only asset here that no algorithm change can revoke.
Which brings the workflow full circle. Publishing is two jobs — making the post and placing it — and only one can be handed to software. Magic Share is built for that split: research, drafting, link verification on every cited URL and schema checks run on your cadence, drafts wait for your approval, and nothing publishes on its own. The free plan includes three posts, no card required. Take the hours that gives back and spend them where they compound — in the rooms where your first hundred readers already are.
FAQ
How long should I wait before deciding a blog post has failed? Use indexation and impressions rather than the calendar. Not indexed after a few weeks is a discovery problem. Indexed with no impressions for its target keyword at 8–12 weeks points to demand or intent. Beyond six months the "too young" explanation is weak: of pages that ever reach Google's top 10, 40.82% got there within one month. And a seeding round will tell you in an afternoon what search takes months to say.
Is it against the rules to post my own blog posts on Hacker News or Reddit? Not inherently, but the limits are specific and published. HN allows self-submissions "part of the time" while asking that curiosity be your primary use of the site, and forbids soliciting upvotes; blog posts are not eligible for Show HN. On Reddit, a 2026 audit of 49 founder-facing subreddits found 39% ban self-promotion outright and 22% allow it only under a 9-to-1 ratio, so read each subreddit's rules page before submitting.
Can I share an AI-assisted blog post in these communities? Linking to an article that had machine assistance isn't what HN's guideline prohibits — the guideline covers text posted to HN itself: "Don't post generated text or AI-edited text." So write your submission comment yourself, in your own words. On Reddit, disclose when content is primarily AI-generated and check the subreddit's own AI rule; 55.23% of the AI rules studied in one large crawl were outright bans.
How much traffic does a Hacker News front-page hit actually send? Two first-hand accounts give a realistic range: a brand-new site at position #17 with 68 points saw roughly 3,500–4,000 visitors from the front page and about 8,000 uniques over four days, while a site holding positions 4 and 5 simultaneously recorded around 43,000 uniques in 20 hours. At an average 2.1% opt-in rate, a 4,000-visitor spike converts to roughly 80 subscribers.
What if my post gets no traction on Hacker News? There are two sanctioned second chances. You can email hn@ycombinator.com about a submission you think deserved attention — moderators keep a pool of rescued stories they re-drop onto the lower front page — and HN permits a small number of reposts within roughly a year. What isn't allowed is deleting and reposting.