Simple answer, it depends on what you are trying to accomplish. If you are trying to attract people to your website, x-posting to dev.to works out well because in many cases they promote your content. If you are trying to score SEO, I suggest not to because you are putting duplicate content out there. Which Google's algorithm pretty much is designed to compare overall site rankings and will put dev.to in the key words you are trying to score for in place of your blog.
The best of both worlds is to place unique content for each with dev.to being more focused towards the development audience, linking back to a blog post you are trying to promote.
The SEO part is not an issue if you define canonical_url in the frontmatter part of your dev.to post, this will tell Google that the real URL of your post is the one defined there.
Simple answer, it depends on what you are trying to accomplish. If you are trying to attract people to your website, x-posting to dev.to works out well because in many cases they promote your content. If you are trying to score SEO, I suggest not to because you are putting duplicate content out there. Which Google's algorithm pretty much is designed to compare overall site rankings and will put dev.to in the key words you are trying to score for in place of your blog.
The best of both worlds is to place unique content for each with dev.to being more focused towards the development audience, linking back to a blog post you are trying to promote.
Hope that helps.
Ah, that makes sense. Also, the SEO part is something I overlooked.
Thank you for your comment!
The SEO part is not an issue if you define
canonical_urlin the frontmatter part of your dev.to post, this will tell Google that the real URL of your post is the one defined there.Check support.google.com/webmasters/answ...
Yes! Add a canonical url!