How to create your own author-centered knowledge graph

I'm not a fear salesman, really! But the thought to name this article as "how to defend abusive content removal requests" comes to me from the reading of the Google's updated report on "How Google Fights Piracy". The following sentence makes me conceiving suspicion:

...sites with high numbers of removal notices may appear lower in search results.

On the background of all known Negative SEO cases this can be the next thing, where a honest publisher will be punished for nothing.

There are enough known cases, where content scraping sites get better SERP places as the unique content providers. And there are enough abusive content removal requests - just read the Google's report. The best defense is a good offence. We construct our publishing identities network, which serves as our own author-oriented knowledge graph. Its purposes are, that

• always working removal requests at Google and DMCA takedowns,
• lack of effect in case of abusive third part removal requests,
• doubtless machine-readable relations between author's entity and author's creative work.

Our objective is a solid, structured and chained publisher identity, which will include the author, the publishing medium and the publication itself. Let's work!
Read full article »

October 26, 2014