Passer au contenu
← Back to Blog Cross-Post Your Blog to Medium, Dev.to and Hashnode — Without Copy-Paste
PostClaw Team · · 5 min read
blog syndication seo guide

Cross-Post Your Blog to Medium, Dev.to and Hashnode — Without Copy-Paste

You wrote the post once. Publishing it to Medium, Dev.to, and Hashnode should not take longer than writing it did.

Yet the standard workflow for blog syndication in 2026 is still: open Medium, paste, fix the formatting Medium broke, open Dev.to, paste, re-upload the images, open Hashnode, paste, forget to set the canonical URL, and then wonder three weeks later why Google is ranking the Medium copy above your own site.

This guide covers how cross-posting a blog actually works, the SEO rules that keep syndication from backfiring, and the ways to automate the whole thing — from DIY scripts to one-click publishing.

Why syndicate at all

Dev.to, Hashnode, and Medium each have a built-in audience your blog doesn't. A post that gets 40 readers on a young domain can get 2,000 on Dev.to's front page. Syndication is the cheapest distribution you'll ever get for written content — the marginal cost is zero if the publishing is automated and the SEO is set up right.

The one SEO rule: canonical URLs

Google does not penalize syndicated content — it penalizes ambiguity about the original. Every serious platform has a field that says "the original lives here":

  • Dev.to: canonical_url in the post's front matter or settings.
  • Hashnode: "original article URL" (originalArticleURL in the API).
  • Medium: its import tool sets the canonical to the source automatically.
  • WordPress / Ghost / Blogger: canonical is usually your own site, or set via SEO plugin when the copy lives elsewhere.

Set it every time, on every copy, pointing at your own domain. Do that and syndication strengthens your site (links, readers, brand searches). Skip it and you're competing against your own content with a bigger domain than yours.

One more habit: publish on your own site first, let it get indexed, then syndicate. Even a day's head start helps Google lock in the right original.

Platform quirks worth knowing

Medium killed its write API. New integration tokens are no longer issued, so tools that "publish to Medium via API" either grandfathered old tokens or actually drive the import flow. The import tool remains the honest path — and it sets your canonical correctly.

Dev.to is the most automation-friendly. A clean REST API, markdown-native, front-matter support. If you script one platform yourself, script this one.

Hashnode wants GraphQL. Fully capable, more ceremony. Their API also lets you backdate and set canonicals, which matters for migrating an archive.

Images don't travel. Paste-based syndication breaks image hosting more than anything else. Automated publishing re-uploads or hotlinks correctly; manual paste leaves you with broken thumbnails on platform number three.

Your options, from DIY to one-click

1. Manual paste. Fine for one post a month on two platforms. The canonical field is the step everyone forgets.

2. A script + GitHub Actions. Push a markdown file, let CI call the Dev.to and Hashnode APIs with the canonical pointing home. Genuinely good if your blog is already a git repo. You'll maintain it forever, and Medium still isn't covered.

3. A headless CMS with webhooks. Strapi or similar firing a serverless function per publish. Same result as the script with more moving parts. Right when the blog is one part of a larger content system.

4. A publishing tool that treats blogs as first-class targets. This is the gap in the market: social schedulers mostly stop at social. PostClaw (our product — bias declared) publishes to 7 blog platforms — WordPress, Medium, Dev.to, Hashnode, Ghost, Blogger, and your own site via API — from the same composer that handles your 11 social accounts. Write once; the AI adapts the announcement posts for X, LinkedIn, and Threads while the article itself syndicates with canonicals intact. One publish, whole distribution chain done.

The full loop most people miss

Syndicating the article is half the job. Each platform copy also deserves its own announcement on social — and that's the part nobody has energy for by platform number four. The workflow that actually compounds:

  1. Publish on your own domain (canonical home).
  2. Syndicate to Dev.to, Hashnode, Medium with canonical URLs set.
  3. Announce on every social platform, adapted per platform — not eleven identical "New blog post 🔗" posts. (We wrote a whole guide on posting to all social media at once without the copy-paste.)
  4. Repeat weekly without it consuming a morning.

Steps 2–4 are exactly what we automated PostClaw to do — see how the publishing side works or the pricing if you're evaluating tools. But even if you never touch our product: set your canonicals. It is the difference between syndication being free reach and free self-sabotage.

Quick answers

Does cross-posting hurt SEO? Not with canonical URLs set. Without them, the biggest domain wins the ranking — and that usually isn't yours.

Can I still auto-publish to Medium? Not via new API tokens. Use Medium's import tool (which sets canonicals) or a tool that automates that flow.

Best platform for developers? Dev.to for reach and API simplicity; Hashnode if you want your own domain on the hosted blog. There's no reason not to do both — the whole point is that the second copy is free.