DEV.to vs Hashnode vs Medium for Backlinks in 2026: Real Data, Honest Take

If you’ve ever been told to “just publish on DEV.to, Hashnode, and Medium for free backlinks,” you’ve been given half-right advice. Two of those platforms actually pass meaningful SEO value in 2026. One of them — the most famous one — quietly nofollows your link before it even leaves the editor. This guide is the honest comparison of all three, with real numbers, the catch nobody mentions, and a clear verdict by use case.

For context: all three sit on the broader category of cloud backlinks — real, indexed pages hosted on high-authority cloud platforms. But within that category they behave very differently.

TL;DR — Quick verdict table

Platform	DR (root)	Indexing speed	External link by default	Best for
DEV.to	90	Hours	dofollow	SEO backlinks + AI search citations
Hashnode	83	Same day	dofollow	SEO backlinks (with API at scale)
Medium	96	Hours	nofollow	Brand reach — not SEO link equity

Short version: DEV.to and Hashnode are real backlink surfaces. Medium is a brand surface that gives you nofollow links. If your goal is SEO authority transfer, Medium isn’t competing — it just looks like it is from the outside.

DEV.to — the honest pick for 2026

Root domain authority: DR 90 (Ahrefs).

How DEV.to handles external links: Posts can include any number of external links in the body, and they are rendered as standard <a href> tags — dofollow by default. Embedded media, code blocks and rich Markdown all work, so your post can carry both a meaningful backlink and the kind of content depth that survives moderation.

Indexing behavior: Google crawls dev.to extremely aggressively because the platform updates constantly. In our own dataset across 1,000+ Forgendo-published DEV.to posts, the median time to Google-indexed status is under 4 hours, with roughly 92% of posts indexed within 48 hours.

AI search citations: This is where DEV.to has quietly become a top-tier platform in 2026. Perplexity, ChatGPT search and Google AI Overviews cite DEV.to posts at unusually high rates for technical, SaaS and developer-adjacent queries. Many marketing teams now publish on DEV.to primarily to get cited by AI, not to get a backlink — the backlink is the bonus.

API access: DEV.to has a clean, free, well-documented API. You can programmatically publish posts, edit them later, and read your own articles. Rate limits are reasonable. This is the platform you most easily automate at scale.

The catch: Moderation is real. Posts that read as obvious SEO doorways — thin content, multiple anchor variations of the same external link, no actual value to a developer reader — do get unpublished. The win condition: write something a developer would genuinely upvote, then embed your link once or twice in context.

Best for: SaaS founders, technical writers, agency operators publishing developer-adjacent content, anyone optimizing for the Perplexity / ChatGPT citation surface.

Hashnode — the underrated runner-up

Root domain authority: DR 83 (Ahrefs) on the apex hashnode.dev, with per-user subdomains carrying the parent’s authority.

How Hashnode handles external links: Dofollow by default, full Markdown support, syntax highlighting, embedded video, custom domains available on paid plans. The link equity behavior is identical to a normal blog post on a high-DR host.

Indexing behavior: Slightly slower than DEV.to but reliable — same-day indexing for the majority of posts, well under 7 days for the rest. Our Forgendo data shows ~85% of Hashnode posts indexed within 72 hours.

AI search citations: Strong for developer and SaaS queries, second only to DEV.to in our citation tracking. Particularly good for “how to” technical content that Perplexity tends to cite directly.

API access: Hashnode exposes a GraphQL API for publishing — but it requires the Hashnode Pro plan ($5/month at the time of writing) to publish via API. Manual publishing through the web UI is free. This is a small recurring cost if you want to automate.

The catch: The community is smaller and the platform skews developer-tooling more than DEV.to does. Generic marketing or pure SEO content lands flatter here. Lean into the technical or product angle if you want the post to age well.

Best for: Programmatic publishing at scale (especially if you already pay for Pro), product-led SaaS content, developer documentation that needs SEO surface.

Medium — the uncomfortable truth

This is the section most “best platforms for backlinks” articles skip. Pay attention.

Root domain authority: DR 96 (Ahrefs) — the highest of the three. On paper, this looks like the strongest backlink surface.

How Medium handles external links: Here’s the catch. Medium adds rel="nofollow" to external links by default. You can publish a beautiful, well-read article with a link to your money site — and that link will pass exactly zero PageRank equity. Medium has done this for years; it’s well-documented in their help center, but the SEO tutorial industry rarely mentions it.

You can read a Medium link the same way you read any link. You can click it. But Google’s link-equity flow treats it as “the publisher does not vouch for this destination.” That is the literal opposite of what an SEO backlink is supposed to do.

Indexing behavior: Excellent — Medium posts index within hours.

AI search citations: Medium gets cited by AI search, but less than DEV.to in technical verticals. For mainstream and lifestyle topics it can be strong.

API access: Medium’s official publishing API has been deprecated and partially restricted for years. Programmatic publishing is unreliable at best. This is the worst of the three for automation.

The catch: The nofollow issue is the main one, but there’s also distribution: Medium’s algorithm has shifted heavily toward paywalled content inside the platform. Unpaywalled posts get less organic reach than they used to.

Best for: Brand exposure, thought leadership in mainstream verticals, building a personal-writing audience. Not for SEO backlinks. Not for link equity transfer.

The honest takeaway: keep Medium in your distribution mix if you’re playing a long-form brand game. Drop it from your link-building strategy entirely.

Side-by-side comparison

Criterion	DEV.to	Hashnode	Medium
Root Domain Rating (Ahrefs)	90	83	96
External links	dofollow	dofollow	nofollow
Median time to indexed	< 4 hours	Same day	Hours
API access	Free, clean	Pro plan required ($5/mo)	Deprecated
AI search citation rate	High	Medium-high	Medium
Moderation strictness	Strict on doorways	Moderate	Light (paywall-driven)
Suited to programmatic publishing	Yes	Yes (paid)	No
Free tier exists	Yes	Yes (UI only)	Yes
SEO backlink value	High	High	None (nofollow)

For SEO backlinks specifically — which wins?

If your single goal is passing link equity to a target URL, the answer is clear:

1. DEV.to first. Highest indexing speed of the three, dofollow by default, free API for scale, and the most consistent crawl behavior.
2. Hashnode second. Slightly lower DR, same dofollow behavior, slightly slower indexing — but a strong second source for diversifying your link profile away from a single platform.
3. Medium does not count. The nofollow makes the comparison meaningless for this use case.

The right play is usually to publish on both DEV.to and Hashnode for the same target URL, with slightly differentiated content on each. You diversify the host footprint, double the indexing surface, and don’t put all your equity on one platform that could change its TOS tomorrow.

For AI search citations — which wins?

If your goal is getting cited by Perplexity, ChatGPT search and Google AI Overviews when someone asks a question in your niche, the order shifts slightly:

1. DEV.to remains first. The platform’s reputation as a credible developer source means AI search engines treat it as a high-trust citation target.
2. Hashnode close second. Particularly strong for “how to” and product-led queries.
3. Medium third, with caveats. Medium does get cited, but the citation rate drops outside mainstream consumer topics.

The key shift in 2026 is that AI search engines weigh where a piece of content lives heavily. A clear, technical post on DEV.to often outperforms the same post on a generic Medium account because the platform itself signals expertise.

What about Telegra.ph, Substack, LinkedIn Articles?

Quick notes on the three platforms that usually come up next in this conversation:

Telegra.ph: DR 88, instant publishing, no account required, dofollow links. Faster than all three above for raw publishing speed. Trade-off: very lightweight platform, no community, limited content depth. Useful as a complementary surface, not a primary one.

Substack: Excellent for newsletter-style content and audience building, but external links from posts are typically rendered with nofollow when posts are republished publicly. Best treated as a brand and audience tool, not a backlink tool.

LinkedIn Articles: High DR, but LinkedIn aggressively rewrites and tracks external links via redirects. The SEO value of links from LinkedIn Articles is debated and inconsistent. Useful for B2B distribution, not load-bearing for an SEO strategy.

How to publish across all three (without burning a weekend)

If you’ve decided DEV.to and Hashnode are worth using and you want to scale beyond one-off manual posts, you have three realistic paths:

1. Manual, one platform at a time. Write the post once, adapt it slightly for each platform, publish through each web UI. Around 25–40 minutes per platform per post once you have a workflow. Fine for 1–2 posts per month.

2. DIY with each platform’s API. DEV.to’s REST API and Hashnode’s GraphQL API are both well-documented. Engineering effort is around 8–15 hours to wire up a robust two-platform pipeline, plus periodic maintenance when APIs change.

3. Use Forgendo. Forgendo publishes a real generated article across DEV.to, Hashnode, and 9 other cloud platforms in roughly 30 seconds per backlink — same content adapted per surface, indexing tracked per provider, and credentials stored encrypted. The free tier publishes 3 backlinks with no card required, which is enough to verify that the indexing-rate numbers in this guide hold on your own domain before committing further.

FAQ

Are DEV.to backlinks dofollow?
Yes. External links in DEV.to post bodies render as standard dofollow anchor tags. This is consistent across the platform.

Why does Medium use nofollow?
Medium added nofollow to external links to discourage spam and link-buying schemes years ago, and never reversed the policy. This is documented in their help center but rarely mentioned in SEO tutorials that recommend Medium as a backlink source.

Does Hashnode need a paid plan?
Only for API publishing. Manual publishing through the web UI is free on all plans. The Pro plan is around $5/month and unlocks programmatic publishing plus custom domain hosting.

How fast do these platforms index?
Across the Forgendo dataset, DEV.to medians under 4 hours, Hashnode within the same day, and Medium typically within hours. All three sit in Google’s hot-crawl tier because of how much content they publish daily.

Will publishing on these platforms hurt my main site’s SEO?
No. Republishing the same content as a guest post on DEV.to, Hashnode, or any high-authority platform is editorially equivalent to a normal guest post. The risk only emerges if you publish thin, machine-spammed content at scale, which any platform’s moderation will catch eventually.

Should I use canonical tags when republishing?
If the content originally lives on your own site and you’re republishing on DEV.to or Hashnode, set the canonical URL back to your own version. Both platforms support this. It preserves your money site’s authority while still earning the backlink from the new surface.

---

Ready to forge your own? Forgendo publishes SEO-optimized articles across Cloudflare, Netlify, Azure and more — real, fast-loading blogs that carry your backlink and load in ~50ms. Start free with 3 links →