I'm a friendly, non-dev, cisgender guy from NC who enjoys playing music/making noise, hiking, eating veggies, and hanging out with my best friend/wife + our 3 kitties + 1 greyhound.
I'm interested if anybody looking at this thread is using the Publishing from RSS feature to import their posts from a blog elsewhere?
When I think of answering the question How do you cross-post articles from your blog to DEV?, this is probably the first thing that comes to mind. 🙂
The second thing that DEV also offers is the ability for authors to specify a canonical URL in their posts which helps Google (and other search engines) understand where an article came from first. This is good for your SEO if you're looking to grow traffic on your own private blog.
NOTE: If you use the Publishing from RSS feature mentioned above, the canonical URL, should be automatically added to your post.
And let's see... are there any other cool reposting tips I can give ya?
One thing that DEV ask folks not to do is to post short "lead in" articles with a sentence or two that then say "Read more here..." and link to a page elsewhere. There's not hard stance against these posts, but they'll not be heavily promoted and the community generally seems to be put off by posts that tease content elsewhere.
And if anyone is curious how to add the Canonical URL here, just add canonical_url: <link_to_original_post> to the header (same place where you have the title) of your Markdown. :-)
You will know that it worked if you see this under the title of your post:
I'm a friendly, non-dev, cisgender guy from NC who enjoys playing music/making noise, hiking, eating veggies, and hanging out with my best friend/wife + our 3 kitties + 1 greyhound.
Awesome addition, thanks for that added clarity, Ruan!
And another note on that... if you're using the Rich + Markdown editor version (which you can select from here), then the UX for inputting a Canonical URL is just slightly different. Just click the little gear icon at the bottom of the page beside Publish/Save Draft and you'll find the place to input your canonical.
Frontend developer who is passionate about building ideas and projects in open source communities. Interested in learning, sharing, and collaborating with people.
I'm a friendly, non-dev, cisgender guy from NC who enjoys playing music/making noise, hiking, eating veggies, and hanging out with my best friend/wife + our 3 kitties + 1 greyhound.
Vikas Rai is a college student studying at Maharaja Agrasen Institute of Technology, currently pursuing B.Tech (Graduation) in Electrical Engineering.Web development enthusiast & Next.js Lover.
Will this affect my orignal post link. Like SEO problem or not appearing in Google Search. If I use the RSS feature to import articles from my blog to dev.to .
I'm a friendly, non-dev, cisgender guy from NC who enjoys playing music/making noise, hiking, eating veggies, and hanging out with my best friend/wife + our 3 kitties + 1 greyhound.
There are a lot of factors that might affect your SEO and it's too difficult for me to say 100% that reposting to DEV via the RSS feature won't affect your SEO.
However, if you want to apply the canonical URL to all posts when importing them via RSS, make sure to check the box that says "Mark the RSS source as canonical URL by default" when setting things up:
Also, if you'd like to read more in depth about this subject, check out this post on forem.dev.
Vikas Rai is a college student studying at Maharaja Agrasen Institute of Technology, currently pursuing B.Tech (Graduation) in Electrical Engineering.Web development enthusiast & Next.js Lover.
I'm interested if anybody looking at this thread is using the Publishing from RSS feature to import their posts from a blog elsewhere?
When I think of answering the question How do you cross-post articles from your blog to DEV?, this is probably the first thing that comes to mind. 🙂
The second thing that DEV also offers is the ability for authors to specify a canonical URL in their posts which helps Google (and other search engines) understand where an article came from first. This is good for your SEO if you're looking to grow traffic on your own private blog.
NOTE: If you use the Publishing from RSS feature mentioned above, the canonical URL, should be automatically added to your post.
And let's see... are there any other cool reposting tips I can give ya?
One thing that DEV ask folks not to do is to post short "lead in" articles with a sentence or two that then say "Read more here..." and link to a page elsewhere. There's not hard stance against these posts, but they'll not be heavily promoted and the community generally seems to be put off by posts that tease content elsewhere.
I’ll definitely have a look at it, thanks!
And if anyone is curious how to add the Canonical URL here, just add
canonical_url: <link_to_original_post>
to the header (same place where you have the title) of your Markdown. :-)You will know that it worked if you see this under the title of your post:
confirmed, works! example
Awesome addition, thanks for that added clarity, Ruan!
And another note on that... if you're using the
Rich + Markdown
editor version (which you can select from here), then the UX for inputting a Canonical URL is just slightly different. Just click the little gear icon at the bottom of the page beside Publish/Save Draft and you'll find the place to input your canonical.This worked perfectly, thanks.
Awesome! Really great to hear that. 🙌
Will this affect my orignal post link. Like SEO problem or not appearing in Google Search. If I use the RSS feature to import articles from my blog to dev.to .
There are a lot of factors that might affect your SEO and it's too difficult for me to say 100% that reposting to DEV via the RSS feature won't affect your SEO.
However, if you want to apply the canonical URL to all posts when importing them via RSS, make sure to check the box that says "Mark the RSS source as canonical URL by default" when setting things up:
Also, if you'd like to read more in depth about this subject, check out this post on forem.dev.
Thank you so much for the reply. Now I have understand completely.