Protecting Your Work: Tracking Content Use for Plagiarism and Citation

This guest blog is written by Brooke Weinbaum, Head of Marketing at Copyleaks, a partner in the Silverchair Universe program. 

Writing content of any kind requires a lot of work, from research and learning to writing and editing. Whether you’re a marketer or a researcher, preparing original content benefits not only your readership but also you, as it offers useful insight that only you can provide. This is where as a writer it is crucial to be sure your content is protected and not at risk of being used in another publication.

After spending so much time creating new content—writing, editing, graphics, promotion, social media—once your content is live, it is out there for all eyes to read and see. This is great—it’s able to reach new audiences and even go viral in your industry space. But the downside of high views is that more people exposed to your content are able to use it without consent or proper citation.

Living in a copy-and-paste era makes it easy for anyone’s words to appear just about anywhere without the original author’s knowledge. With billions of pages of content already out there and millions of new pages going live every day, how can someone keep track of all of their written content?

Additionally, for researchers (or anyone in the academic world creating original content), it’s important to check your work both before you submit it as well as after to make sure you are likewise citing work correctly. After all of the researching, writing, and citations that are put into a piece of research, it’s important to check that the content includes proper references. Many times when people are accused of plagiarism, it’s simply because they left out a citation they meant to include.

Copyleaks was designed to address exactly these dilemmas. When you scan your work with the Copyleaks duplicate content detector, you’re able to see all the similar text within your document and double check that each citation has been noted.

Once the work has been published, you then need to make sure no one else is inappropriately reusing your work. Scanning your work routinely allows you to see where else it has been used. This enables you to to find out if you have been given credit for your work and if the proper links to your site or specific publication are present. If it has been used without credit, writing to the owner of the website will typically get you the credit that is deserved. In cases of plagiarism and copyright infringement, the Copyleaks checker provides concrete supporting evidence as you determine the next steps.

Both giving and receiving credit for unique content ensures that your content is protected and that your research remains in-line with citation best practices. In this way, Copyleaks helps ensure your content is always protected.

Contact universe@silverchair.com to learn more about integrating Copyleaks with your content on the Silverchair Platform. 

1993 1999 2000s 2010 2017 calendar facebook instagram landscape linkedin news pen stats trophy twitter zapnito

This site uses cookies. By continuing to use our website, you are agreeing to our privacy policy
https://www.silverchair.com/news/protecting-your-work/
www.silverchair.com
crawl=CC-MAIN-2019-22
82291
application/http; msgtype=response
sha1:XBKJSTC455Y2LFCLIYU6WT3S67MQF446
<urn:uuid:087b7d85-cd7a-4031-9685-b0a4f1c363ff>
2019-05-25T04:19:47Z
104.198.190.59
text/html
sha1:RCZC3TNVKYIMYEEWKU3LW66ZADXVN6SJ
<urn:uuid:f33b0dfd-56f0-47fc-b524-1d902e6e91bf>
https://www.silverchair.com/news/protecting-your-work/
response
<urn:uuid:85616200-5668-4579-9ef7-716a0d5818aa>
isPartOf: CC-MAIN-2019-22
publisher: Common Crawl
description: Wide crawl of the web for May 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-171-192-21.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/