About bonus tip - you can start very easily at hashnode; add there custom domain & maintain those two blogs very easily. I keep on publishing on dev.to first; but I immediately import the new post to hashnode, and set canonical URL to the hashnode one.
dev.to seems to have bigger community, but hashnode isn't far behind. Being on two both platforms has a side effect of different post getting promoted by one or the other platform.
I am a Frontend Engineer with a passion for building pixel-perfect web applications, with great user interface and user experience, and also teaching others what I learn
I am interested in Web3, WebGL
Hello Marcin
So dev.to has the original article, while you republish on Hashnode, for indexing and SEO purposes
But the bots crawl and recognize the article on dev.to as the original article
Am i right?
I am a Frontend Engineer with a passion for building pixel-perfect web applications, with great user interface and user experience, and also teaching others what I learn
I am interested in Web3, WebGL
Thanks for the tip @marcinwosinek !
I started using hashnode after reading your comment. I imported all my articles there, and now I have a question for you (as I am still new at this): should I set the canonical url to dev.to on my imported articles, or is it safe to change the canonical url of old articles in dev.to to point to the new article imported on hashnode ? Do you have an advice ? (I am talking only about the old/imported articles. For the new ones, I will set the canonical URL to hashnode).
Hello @derlin! I don't know if moving the articles around hurts your SEO. I was conservative myself, and after migrating my blog I only imported stuff and set the canonical ULR to original dev.to location.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
About bonus tip - you can start very easily at hashnode; add there custom domain & maintain those two blogs very easily. I keep on publishing on dev.to first; but I immediately import the new post to hashnode, and set canonical URL to the hashnode one.
dev.to seems to have bigger community, but hashnode isn't far behind. Being on two both platforms has a side effect of different post getting promoted by one or the other platform.
If you want to join:
hashnode.com/@marcin-wosinek/joinme
Hello Marcin
So dev.to has the original article, while you republish on Hashnode, for indexing and SEO purposes
But the bots crawl and recognize the article on dev.to as the original article
Am i right?
Sorry, I was mixing 2 things in my comment.
How my articles are available online:
How it's easiest to achieve it:
The dev.to before hashnode is just workaround about tooling the two platforms ofert. My focus is on hashnode - or rather, my own domain.
Thanks Marcin that was helpful
Thanks for the tip @marcinwosinek !
I started using hashnode after reading your comment. I imported all my articles there, and now I have a question for you (as I am still new at this): should I set the canonical url to dev.to on my imported articles, or is it safe to change the canonical url of old articles in dev.to to point to the new article imported on hashnode ? Do you have an advice ? (I am talking only about the old/imported articles. For the new ones, I will set the canonical URL to hashnode).
Hello @derlin! I don't know if moving the articles around hurts your SEO. I was conservative myself, and after migrating my blog I only imported stuff and set the canonical ULR to original dev.to location.