Re-posting your blog articles across the web sounds like a good idea in theory. Not only does it give you increased exposure, you can also link back to your original post, giving your blog an extra boost when it comes to search engine results (for more on how links help your search engine optimisation, or SEO, read this). But there are a few things to watch out for when re-posting, as it can actually harm your SEO if not done right.
The main issue when it comes to re-posting your content is that while search engines will reward you for links, they will not look so kindly on what they deem to be “duplicate content.” To get a clearer idea of what duplicate content is, we asked Joe Hanna, resident SEO expert at propertyadguru.com publisher Classified Ad Ventures.
“The rule of thumb generally is that is if one page is 80 percent the same as another (regardless of whether it is within the same domain or not) then you run the risk of duplicate content issues,” Hanna explains. He also points to Google’s own definition of duplicate content, which defines it as “substantive blocks of content within or across domains that either completely match other content or are appreciably similar.”
“When search engines uncover two or more pages that looks pretty much identical, they may not be able to clearly identify the originating source,” Hanna says. “In such circumstances one of two things could happen. Firstly, the search engine may penalise all web pages (and reduce all their ability to rank), or the search engine may only pick one source (which may not actually be the originating source).”
To avoid these issues, the best thing to do if you choose to re-post your articles is to re-work them as much as possible. You can still use the same information, but try re-writing the headline and adding a new introductory paragraph that directs your audience back to the original post. To be extra safe, you could also try posting just part of your original article, then adding in a link inviting people to read the rest back at your own blog.
Related posts:
Loading ...
