Saturday 1 September 2012

What is Content Duplication and Content Syndication?


Duplicate content is when you have large blocks of text that are identical between several different URLs. This can happen when you offer a printer-friendly page allowing your visitors to print a specific page without the extra advertisements and navigation. In this case, the main page and the printer-friendly version are considered duplicate content.
Even a mobile-friendly website in addition to your other website can be considered duplicate content. If you have a number of short pages on your website, you may have duplicate content. A travel website might also have duplicate content when describing the various amenities offered at different hotels in different cities. If you write articles that are syndicated, you’ll have duplicate content for each site where the content is syndicated.

Content syndication is a method by which writings find their way around the ether of the Internet. Specifically, one article that a person writes could appear, with the writer's permission, on many websites. The key word there is permission, which the writer is supposed to give before a website reprints his or her article. In many cases today, because it is so easy to cut and paste electronically, articles appear in syndication without the requisite author permission.
A content syndication agreement usually involves some form of compensation to the original author. This can be as little as acknowledging the author's name. It could include the author's name and website address. The agreement might even include monetary compensation.

A content syndication agreement can be for one article or for many. It can also be an ongoing agreement under which the author or authors agree to provide periodical writings that the website(s) will then publish on a daily or otherwise regular basis. With the explosion of web publishing tools in the past few years, it has become easier and easier for people to publish their writings on the web. Be they articles or reports or blogs or travelogues, these writings are prime candidates for content syndication to certain interested parties.

Syndicating your content is a tricky game. On the one hand, getting more exposure for you, your brand, or your company is a good thing. On the other hand, having another site outrank you for your own content is not a good thing. In this post, I’ll take a look at some of the pros and cons and offer some tips about how you can make syndication work for you.

Let’s get the easy stuff out of the way. Content syndication is different from web-scraping: content syndication is when you allow your content to be placed on another site. In some cases, the site will approach you asking to use your work; in other cases, you will approach them. In either case, both parties consent to the action. However, from a search engine perspective, it’s almost identical to web scraping because the engines see the same content in two places and have to look for signals that tell them who is the source or owner.
If you are thinking about content syndication, there are few things you do and don’t want to do. The first thing is you don’t want to give permission for someone to take all of your new content; instead, you want to give them access to a limited number of pieces. Try to come up with an arrangement that works for everyone like no more than 2 posts a month, or only posts from some select categories. If you have multiple syndication partners, this can be tricky.
If you can only get one link, go for the deep link to the original post. It may seem counter-intuitive but it’s key if you want the search engines to credit you properly. I have seen some people try and use the rel canonical tag, but I’m less than convinced that it’s fool proof when crossing domains. IMHO it’s not worth the dice roll. If you can negotiate they only re-publish a snippet/section and not the entire post, that can also work to you advantage, because it means they have to link back to the original post.

There are some instances when you want to let someone republish your post in its entirety and aren’t concerned about the link back to your post. For example, maybe you have an issue/rant/viewpoint that you want to get in front of a larger audience where it can do more good/damage. In that case, damn the search engines, full speed syndication ahead. Sometimes you know what type of post publishers like to syndicate, and you can create those posts with a few well-placed links to your projects, client’s projects, or friend’s projects. In the end you’ll end up with a higher powered link in exchange for giving up ownership of the content in the eyes of a search engine. Working on an ORM project? Get a pieced picked up with the client name in the post, point a few targeted anchor text links, and viola! One more SERP position will be under your control.

So what are the takeaways from this post:

§  Never let anyone republish 100% of your content
§  Try to get a link back to your main site and individual post in every article
§  Give permission to syndicate only a snippet of the post
§  Sometimes getting visibility is more important than getting credit
§  Sometimes getting a link from a higher powered site is more important than getting credit
§  Syndicated content can be powerful tool for ORM projects


0 comments:

Post a Comment