DEV Organization Accounts: Tips for Reposting Blog Content

As many of you may already know, we at DEV provide a feature that allows you to create organizations, invite people to join the organization and post articles within the organization. For example, if you look down the left side of my profile, you can see that I’m part of several organizations, including the DEV team:

There are many benefits to creating an organization, many of which are listed on our organization’s information and FAQ page – I recommend checking out that resource for a high-level view.

Below, we’ll zoom in on a number of organizations’ common use on DEV: Repost content from an organization’s blog to DEV And we’ll talk about best practices to keep in mind when doing so.

Repost an organization’s blog content to DEV

There are a lot of organizations out there with developer-focused blogs that have really interesting content. We strongly encourage people from these organizations to join DEV, form an organization, and share their blog content with the community.

We provide tools that make it easy to import and share posts from an existing blog (as long as RSS is set up) and that makes it safe to do so without losing SEO (ie DEV version) of the original post . Do not want surpassed the original version in search rankings). Let’s talk about each!

Importing posts via RSS

In particular, there is a feature called “Publishing from RSS” that allows you to easily import content to a DEV that exists elsewhere on the web so that it can be re-shared with the community.

This feature is found in Settings (/Settings/Extensions) and gives you the ability to input an RSS feed URL to import any articles you’ve added to RSS. So, if your organization has a blog and you all have RSS set up for it, you can continue to create articles on your blog first and then import them to DEV; That way you only need to write the article in one place, but you can easily import and post it to DEV without doing the weird copy/paste dance.

That said, note that this feature was created with more individuals in mind than organizations, so the flow is a bit tricky for organizations (note: this request is intended to make it easier). If you are planning to use this method as an organization, you will want to follow these steps:

  1. For this to work, make sure you have administrative privileges for your organization.
  2. Here in your settings under “Publishing RSS to DEV Community ” enter the URL of your blog’s RSS feed and click “Submit Feed Settings”.
  3. After submitting the URL go to your User Dashboard. From here, click to edit each post in your organization one by one, and use the drop-down menu (top of the post) to set them all to be posted under your organization, selecting each draft Be sure to save.
  4. Go back to your user dashboard and use the drop-down menu at the top right of the page to change from “Personal” to your organization.
  5. Go to the list of posts and click the three-dot menu next to each title, then use the author drop-down menu to attribute the correct author in your organization for each post.
  6. You can then read the posts you want to publish. You can also publish on behalf of your team members if you wish.

Org Two Quick Tips for Sharing Blog Content! First, we recommend that you don’t post all your articles at once, but instead gradually remove a few per week – this will help with your visibility. We also strongly recommend against posting articles that are purely promotional… As always, if your articles do not conform to our Content Policy listed in our Terms, we may remove your post. and/or suspend your account.

Another thing to keep in mind, when reposting via RSS, you have the option to mark the RSS source as authentic URL by default. You will definitely want to do so if you expect to keep your SEO ranking high for the original source when reposting content. More on that below…

Importance of specifying a canonical URL

Often, organizations that repost content are concerned about:
a) their original post is becoming less searchable in search engines
b) their website is becoming less searchable in search engines because the new location in which their content is published (eg DEV) may reach the first place where the article was published (eg org blog) .

Luckily Purposefully, we built DEV with contributors in mind and gave authors the ability to easily tell search engines where a reposted article originally came from by inputting a canonical URL. As long as authors specify an authenticated URL, they shouldn’t need to worry about being penalized for reposting content. search engine crawler should View Through HTML When specifying a canonical URL on a post and re-paying attention to the posted article actually boosts the ranking of the original article.

How to Specify a Canonical URL

First, if you’re reposting via RSS, as mentioned earlier, you have to check a box next to “Mark RSS source as canonical URL by default” upon import. – If it’s important to you and your organization, be sure to do so!

That said, it is possible to specify a canonical URL on individual posts you share as well.

There are two different methods available depending on which editor version you are on. Check to see which editor version you are using from /Settings/Customization.

if using Rich + markdown And to repost an article, you’ll need to click the gear icon at the bottom of the page next to “Save draft.” You will then see an input for “Canonical URL” where you can share the URL for the original location of the post. This will tell search engine crawlers that the post first appeared at the URL you set.

if using Basic markdown and reposting an article, you need to add canonical_url: X To specify where the post first appeared, in the body of your post, like so:

title: ""
published: false
enter fullscreen mode

exit fullscreen mode


We hope this helps take some of the work and fear that comes with reposting content on DEV. If you are an organization looking to share your articles with our community, we hope you do!

If you have any questions or feedback, don’t hesitate to hit us up here!

Leave a Comment