How to Promote a Tech Blog: Communities, Tutorial SEO and Syndication Done Right
To promote a tech blog, write posts that solve a specific technical problem, share them in developer communities on those communities' terms, cross-post to dev.to or Medium with a canonical link back to your site, and use your GitHub projects and docs as entry points. Developers are allergic to marketing, so the promotion that works looks a lot like being useful in public. Here is how to do each part without getting flagged or ignored.
What makes tech blog promotion different
Technical readers search for exact error messages, compare approaches, and share posts that saved them an afternoon. They also downvote anything that smells like an ad. That shapes the strategy: the content itself has to carry most of the promotion, and every community you post in has its own written rules. Read them before you post, not after your account gets flagged.
Write posts that are worth sharing
The tech posts that travel share a few traits:
- One concrete problem per post. "Fixing
ECONNRESETin Node 22 behind an nginx proxy" beats "Networking tips." - Reproducible code. Minimal examples that run, with versions stated. Link a repo or gist when the example is longer than a screen.
- Honest trade-offs. When not to use your approach, and what you measured (with your setup described) rather than claimed.
- A clear "who wrote this." Google's guidance on creating helpful content asks whether it is self-evident who authored the content and whether it shows first-hand expertise. A short author note with your GitHub profile does both.
Formats that tend to get shared: deep dives into how something works internally, post-mortems of real bugs, benchmarks with full methodology, and "I built X, here is what I learned" write-ups.
Hacker News: share occasionally, never ask for votes
The Hacker News guidelines allow posting your own work "part of the time," but the site is not meant to be a promotion channel. A few rules matter most for bloggers:
- Use the post's original title unless it is misleading or linkbait; don't editorialize.
- Don't ask anyone to upvote, comment or submit your post. HN treats this as manipulation.
- Show HN is for things people can try, not articles. The Show HN rules list blog posts among off-topic submissions, so submit your post as a regular story.
If a post does get traction, show up in the comments, answer questions and accept corrections gracefully. That discussion is often worth more than the traffic spike.
Lobsters and Reddit: participate first
Lobsters registers new users by invitation, and its guidelines say self-promotion should be less than a quarter of your stories and comments. The site explicitly discourages using it as a write-only tool for driving traffic to your work.
Reddit's sitewide rules ask users to follow each community's rules, participate authentically in communities where they have a personal interest, and not spam. Programming subreddits often add their own limits on self-posted links. A practical approach:
- Pick two or three subreddits that match your stack.
- Spend a few weeks answering questions there without linking anything.
- When you share your own post, add a comment explaining the context and what readers will learn.
- Keep your own links a small share of your activity.
Cross-post to dev.to, Hashnode and Medium with a canonical link
Developer platforms come with built-in audiences. Cross-posting lets you reach them while keeping your own site as the original. The tool for that is the canonical URL, which tells search engines which version you consider the main one.
| Platform | How to point back to your post |
|---|---|
| dev.to (Forem) | Set canonical_url in the post's front matter or via the API. The Forem API docs describe it as the field to use if the post was originally published elsewhere. |
| Medium | Use the Import a story tool, which Medium says adds a canonical link to the original, or set the canonical manually in the story settings. |
| Hashnode and others | Look for an "originally published at" or canonical URL field in the post settings, then check the page source of the published copy. |
Two caveats. First, Google calls rel="canonical" a strong signal, not a command, and says it decides which pages are duplicates based on content similarity (see Consolidate duplicate URLs). A copy on a large platform can still show up in search. Second, wait until Google has indexed your original before you cross-post, and always check the published copy's source for the canonical tag. Our content syndication guide covers timing and partner sites in more detail.
SEO for tutorials: errors, versions and freshness
Technical search is unusually literal. People paste errors, API names and version numbers into the search box. Use that:
- Put the exact error string in the text (in a
codeelement and in a heading if it is the main topic). - State versions in the intro: framework, runtime, OS. Readers decide in seconds whether your fix applies to them.
- Update when versions change. Add a note with the date and what changed, instead of silently editing.
- Link to official docs for every API you use. It helps readers and shows you checked the source.
- Build a series around one tool or stack and link the parts together, so readers and crawlers find the whole set.
For niche-blog SEO basics like topic clusters and internal links, see our SEO guide for niche blogs.
Use GitHub and documentation as channels
If you write about your own code, the repository is often the best-targeted promotion you have. Developers who find your project are exactly the readers who care about how it works.
- Link relevant posts from the README ("Why we chose SQLite," "Benchmarks").
- Link from issues and discussions when a post answers a recurring question, instead of repeating the explanation.
- Write the post you wish existed when you got stuck on a library, and offer it as an example to the project's docs or community page if they accept contributions.
- Put your blog URL in your GitHub profile; people who like your code check it.
Newsletters, aggregators and podcasts
Many language and framework ecosystems have curated weekly newsletters that accept link suggestions. Find the ones for your stack, read a few issues to see what they include, and submit only your strongest, most relevant posts. The same goes for community podcasts that invite guests: a well-researched post is often the best pitch for an episode.
Start your own newsletter too, even a small one. An RSS feed plus an email digest of your posts keeps readers who arrived from a one-time spike.
Collaborate with other tech bloggers
Pair up with writers working on adjacent stacks: a joint benchmark, a "two ways to solve this" post, a guest tutorial, or a shared series. Each brings their own readers and the result is usually better than either could write alone. Our blogger collaboration guide has outreach templates. Keep collaborations about content: Google's spam policies list excessive link exchanges among link schemes.
If you want regular mentions on related sites without managing outreach, the Satelo exchange places labeled partner articles in a circle among sites of a similar level and topic, with links marked rel="sponsored". It is a public beta with a small network, so use it as an extra channel, not the main one. If you work with AI agents, you can also drive Satelo through its MCP server from your editor or agent of choice.
Mistakes that quietly kill tech blog promotion
- Posting the same link everywhere on day one. Communities notice cross-posted announcements; tailor the context to each one or skip it.
- Cross-posting before your original is indexed. The copy on a big platform may be found first.
- Stale code with no date. A tutorial that breaks on the current version costs you trust with every reader who tries it.
- Asking friends to upvote. HN forbids it, and vote rings get noticed on most sites.
- Hiding who you are. Anonymous tech advice is harder to trust; an author note with real projects helps readers judge your experience.
A weekly routine that fits around coding
| When | Task | Time |
|---|---|---|
| Monday | Note one problem you solved last week as a post idea | 10 min |
| Midweek | Answer two questions in your chosen communities, no links | 20 min |
| Publish day | Publish, check it is indexable, link it from the README or related posts | 30 min |
| A few days later | Cross-post with a canonical URL; share in one community where it fits | 20 min |
| Monthly | Review Search Console queries; update posts for new versions | 45 min |
Times are illustrative; adjust them to your own pace.
What to do next
Pick one recent problem you solved, write it up with exact errors and versions, and run it through the routine above. If you plan to approach other blogs for collaborations, check how your site looks from their side first: you can see your tech blog's Quality Score, built mostly from open data, with the evidence behind each number, in about 30 seconds.
FAQ
How do I get readers for my tech blog?
Write posts that solve one specific technical problem with reproducible code, share them occasionally in communities like Hacker News, Lobsters or relevant subreddits within their rules, cross-post with canonical links, and link posts from your GitHub projects.
Can I post my own blog on Hacker News?
Yes, occasionally. The HN guidelines allow posting your own work part of the time, ask you to keep the original title and forbid asking for upvotes. Blog posts are not allowed as Show HN; submit them as regular stories.
Should I cross-post to dev.to or Medium?
It can reach new readers. Set a canonical URL pointing to your original post (dev.to supports a canonical_url field; Medium's import tool adds one) and wait until your original is indexed. Canonical is a strong signal, not a guarantee.
Does cross-posting hurt SEO?
Duplicate copies can compete with your original in search. A correct canonical link reduces that risk but Google may still choose another version, so publish on your own site first and check the canonical tag on every copy.
What should a tech blog write about?
Problems you have actually solved: exact errors, migrations, performance investigations, post-mortems and honest comparisons with the setup and versions stated.
Is Reddit good for promoting a tech blog?
It can be, within each subreddit's rules. Reddit asks users to participate authentically and not spam, so answer questions first and keep your own links a small part of your activity.
Read next
Check your site's Quality Score
Free, no sign-up: a 0–100 score from mostly open data. Then add your site to Satelo and get partner articles from sites of your level.
Enter a domain like example.com
Add my site