dev-to-hashnode

When the user wants to publish on Dev.to, Hashnode, or other developer blogging platforms. Trigger phrases include "Dev.to," "Hashnode," "developer blog," "cross-posting," "technical blogging," "canonical URL," or "developer content platform."

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "dev-to-hashnode" with this command: npx skills add jonathimer/devmarketing-skills/jonathimer-devmarketing-skills-dev-to-hashnode

Dev.to & Hashnode Publishing

Developer blogging platforms offer built-in audiences of hundreds of thousands of developers. This skill covers cross-posting strategy, platform-specific optimization, and building followers on Dev.to and Hashnode.


Before You Start

  1. Read .agents/developer-audience-context.md if it exists
  2. Decide your canonical URL strategy (important for SEO)
  3. Create accounts on both platforms to reserve your username
  4. Understand: These platforms reward consistency and engagement

Platform Comparison

Dev.to vs Hashnode

FeatureDev.toHashnode
Monthly visitors~10M+~3M+
Custom domainNo (subdomain only)Yes (free)
Canonical URL supportYesYes
SEO benefitsHigh domain authorityYour domain gets SEO
MonetizationNo nativeSponsors, newsletter
NewsletterNoBuilt-in
Series supportYesYes
Code highlightingExcellentExcellent
Community featuresStrong (reactions, comments)Growing
AudienceBroader, more beginnersMore senior, focused

When to Use Each

Use Dev.to whenUse Hashnode when
Maximum reach is priorityBuilding your own brand
Targeting beginners/mid-levelWant custom domain SEO
Community engagement mattersBuilding email list
Quick validation of contentLong-term content strategy
Don't have your own blogSupplementing your main blog

Cross-Posting Strategy

The Canonical URL Decision

StrategyProsCons
Original on your blogSEO to your domain, full controlPlatforms may rank lower
Original on Dev.toMaximum initial reachNo SEO to your domain
Original on Hashnode (custom domain)SEO + platform reachSmaller initial audience

Best Practice: Your Blog + Cross-Post

  1. Publish on your blog first — This is canonical
  2. Wait 1-2 days — Let Google index your original
  3. Cross-post to Dev.to — Set canonical URL to your blog
  4. Cross-post to Hashnode — Set canonical URL to your blog

Setting Canonical URLs

Dev.to (in frontmatter):

---
title: Your Title
canonical_url: https://yourblog.com/your-post
---

Hashnode (in editor):

  • Click "Article settings" gear icon
  • Paste original URL in "Canonical URL" field

Dev.to Optimization

Frontmatter Structure

---
title: "Specific, Keyword-Rich Title (Not Clickbait)"
published: true
description: "One compelling sentence that shows up in previews and SEO"
tags: javascript, webdev, tutorial, beginners
cover_image: https://your-cdn.com/image.png
canonical_url: https://yourblog.com/original-post
series: "Building a CLI from Scratch"
---

Tag Strategy

TagFollowersUse for
#javascript200K+JS content
#webdev150K+General web development
#beginners120K+Accessible content
#tutorial100K+Step-by-step guides
#react80K+React specific
#programming80K+General programming
#python70K+Python content
#devops50K+DevOps, CI/CD
#opensource40K+OSS projects
#productivity40K+Dev tools, workflows

Rules:

  • Maximum 4 tags per post
  • First tag is primary (appears in URL)
  • Check tag follower count before using

What Performs on Dev.to

Content typePerformanceNotes
Beginner tutorialsHighLargest audience segment
Listicles ("10 tools...")HighEasy to consume
Career adviceHighAspirational content
Hot takesMedium-highControversial drives engagement
Deep technicalMediumNiche but engaged audience
Project showcasesMediumBest with story behind it
News/updatesLowCompetes with official sources

Dev.to Engagement Features

FeatureHow to use
ReactionsHeart, unicorn, saved, fire — different meanings
CommentsReply to every comment for algorithm boost
SeriesGroup related posts, drives binge reading
DiscussionTag #discuss for opinion/question posts
ListingsPost jobs, events, products

Hashnode Optimization

Article Settings

SettingRecommendation
SubtitleUse for SEO keywords
Cover image1600x840 optimal size
SEO titleCan differ from article title
SEO description155 characters max
Canonical URLYour original if cross-posting
Enable table of contentsYes for long posts
Disable commentsNo — engagement helps

Tag Strategy

Hashnode tags work differently:

  • Tags are linked to global topics
  • Some tags have dedicated feeds
  • Fewer tags, more focused

Popular Hashnode tags:

  • javascript, web-development, react
  • devops, cloud, aws
  • beginners, tutorial
  • opensource, programming

What Performs on Hashnode

Content typePerformanceNotes
In-depth tutorialsHighAudience expects depth
Architecture postsHighMore senior audience
DevOps/cloud contentHighStrong niche presence
Career storiesMedium-highPersonal narratives work
Quick tipsMediumLess than on Dev.to
ListiclesMediumLess effective here

Hashnode-Specific Features

FeatureHow to use
NewsletterEnable to collect subscribers
SeriesGreat for tutorials, courses
Custom CSSStyle your blog uniquely
WidgetsAdd GitHub, newsletter CTAs
SponsorsHashnode has sponsor program
AnalyticsBuilt-in, more detailed than Dev.to

Content Formatting

Structure That Works

# Title

[Compelling hook — why should they care?]

## Table of Contents (for long posts)
- [Section 1](#section-1)
- [Section 2](#section-2)

## The Problem

[What pain point are you solving?]

## The Solution

[Your approach, with code examples]

### Code Example

```language
// Well-commented code
const example = "explained";

Step-by-Step

  1. Step one — Explanation
  2. Step two — Explanation
  3. Step three — Explanation

Common Pitfalls

[What to watch out for]

Conclusion

[Summary + CTA]


If you found this helpful, follow me for more content about [topic].


### Formatting Best Practices

| Element | Guideline |
|---------|-----------|
| **Headers** | Use H2 for sections, H3 for subsections |
| **Code blocks** | Always specify language for syntax highlighting |
| **Images** | Use descriptive alt text, compress for speed |
| **Links** | Descriptive text, not "click here" |
| **Length** | 1000-2500 words performs best |
| **Paragraphs** | Keep short, 2-3 sentences max |
| **Lists** | Use liberally for scannability |

---

## Building Followers

### Consistency Strategy

| Frequency | Result |
|-----------|--------|
| 4+ posts/month | Rapid follower growth |
| 2-3 posts/month | Steady growth |
| 1 post/month | Slow but sustainable |
| Sporadic | Minimal follower retention |

### Engagement Tactics

| Tactic | Why it works |
|--------|--------------|
| Reply to every comment | Algorithm boost + relationship building |
| Comment on others' posts | Visibility + community |
| Follow relevant authors | Often reciprocated |
| Share on social media | Drives external traffic |
| Link between your posts | Keeps readers on your content |
| Create series | Encourages following for updates |

### Bio and Profile Optimization

**Dev.to profile**:
- Clear profile photo
- Bio with what you write about
- Link to your main site
- List your expertise areas

**Hashnode profile**:
- Custom domain setup
- Newsletter enabled
- Social links populated
- Blog name and tagline set

---

## Platform-Specific Do's and Don'ts

### Do's

1. **Do** set canonical URLs to protect your SEO
2. **Do** use platform-specific formatting (embeds, etc.)
3. **Do** engage with comments within 24 hours
4. **Do** cross-post to both platforms
5. **Do** use series for related content
6. **Do** optimize cover images for each platform
7. **Do** include a CTA at the end

### Don'ts

1. **Don't** post identical content without canonical URLs
2. **Don't** ignore comments
3. **Don't** use only self-promotional content
4. **Don't** neglect tags — they're discovery mechanisms
5. **Don't** forget mobile readability
6. **Don't** publish unfinished drafts
7. **Don't** keyword stuff your content

---

## Analytics and Iteration

### Dev.to Dashboard

| Metric | What it tells you |
|--------|-------------------|
| Views | Reach/impressions |
| Reactions | Engagement quality |
| Comments | Discussion value |
| Reading time | Content depth |
| Followers from post | Conversion rate |

### Hashnode Analytics

| Metric | What it tells you |
|--------|-------------------|
| Total views | Reach |
| Unique visitors | Audience size |
| Read ratio | Completion rate |
| Time on page | Engagement depth |
| Referrers | Traffic sources |
| Newsletter signups | List growth |

### What to Optimize

| Low metric | Try this |
|------------|----------|
| Low views | Better title, different tags |
| Low reactions | More engaging opening |
| Low comments | End with a question |
| High bounce | Better structure, hook |
| Low followers | Stronger CTA, series |

---

## Tools

| Tool | Use case |
|------|----------|
| **[Octolens](https://octolens.com)** | Monitor Dev.to and Hashnode for mentions of your topic, competitors, and trends. Find popular content to learn from. |
| **Hemingway Editor** | Improve readability |
| **Carbon** | Beautiful code screenshots |
| **Unsplash** | Free cover images |
| **Canva** | Custom cover image design |
| **Grammarly** | Catch errors before publishing |

---

## Content Calendar Template

| Week | Dev.to | Hashnode | Topic |
|------|--------|----------|-------|
| 1 | Publish | Cross-post (day 2) | Tutorial |
| 2 | Cross-post | Publish | Deep dive |
| 3 | Publish | Cross-post (day 2) | Listicle |
| 4 | Cross-post | Publish | Opinion/experience |

---

## Related Skills

- `developer-audience-context` — Know who you're writing for
- `hacker-news-strategy` — Drive traffic from HN to your posts
- `reddit-engagement` — Share posts in relevant subreddits
- `github-presence` — Link from READMEs to your content
- `x-devs` — Promote posts on Twitter/X

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

Coding

reddit-engagement

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

developer-seo

No summary provided by upstream source.

Repository SourceNeeds Review
Coding

linkedin-technical

No summary provided by upstream source.

Repository SourceNeeds Review