Quick answer: Hashnode is a developer blogging platform that publishes each writer under a personal domain, with a strong technical community and the support for cross-posting. As with dev.to, the canonical URL keeps the original as the indexed source.

The cross-post rule

  • Publish the original on the company blog.
  • Cross-post the same content to Hashnode.
  • Set the canonical to the original.

The dev.to cross-post explains the same principle for the other platform.

The steps

  1. Publish on the company blog first. The original is the source.
  2. Allow the index to settle. A short delay before the cross-post.
  3. Create the Hashnode post. Use the markdown editor.
  4. Set the canonical URL. In the post settings, the canonical points to the original.
  5. Add the tags and the cover. The tags reach the developer readers.
  6. Publish. The post is attributed to the original.

Where the canonical lives

In the Hashnode editor, the post settings include the canonical URL field; the cross-post points to the company blog. The exact field name is the canonical URL setting, and the value is the full URL of the original post.

What to cross-post

The three surfaces

The same content is published on:

  • The company blog, the original.
  • dev.to, the cross-post.
  • Hashnode, the cross-post.

The canonical always points to the company blog.

The Hashnode specifics

  • The personal blog builds the writer's profile.
  • The tags and the feed surface the post.
  • The community comments are the engagement.
  • The OG image is the cover.

The cadence

The batch content produces the long-form piece, and the cross-posting is the last step:

  1. The original blog.
  2. The dev.to cross-post.
  3. The Hashnode cross-post.
  4. The slides for the talk if relevant.

What to avoid

  • The cross-post without the canonical.
  • The post before the original.
  • The different content across the three platforms; the rule is the same content.
  • The over-promotion in the technical post.

Frequently asked questions

Is Hashnode the same as dev.to? Both are developer platforms; the cross-post mechanics differ, but the canonical rule is the same. Can the same post be on both? Yes, with the canonical set to the original on each. Which original is indexed? The company blog, the owned property. Do the cross-posts send traffic? The platform audiences and the links can; the main benefit is the reach.

Publish the original, cross-post with the canonical set, and let the developer platforms widen the reach.

Related guide: the social media scheduling guide.