Prosperative Public Forum

copyscape api

0 Members and 1 Guest are viewing this topic.

copyscape api
« on: October 19, 2011, 07:24:07 PM »
With Article Builder, can a copyscape api be used inside wordpress to check for dup content?  Also, I'm thinking of buying it but am concerned that it's just churning out snippets of the same paragraphs on the Internet.  However, copyscape can detect even at the sentence level?  What is the safe percentage for google to not ding a page for dup content?

Offline Jonathan Leger

  • *****
  • 8863
  • Here's to your success!
    • View Profile
    • Jonathan Leger's Blog
Re: copyscape api
« Reply #1 on: October 19, 2011, 07:33:41 PM »
This post is worth reading in regards to your questions:

jlforums.com/article-builder/new!-inject-content-functionality/msg39982/#msg39982

Re: copyscape api
« Reply #2 on: October 20, 2011, 03:58:10 AM »
Just put my first "Article Builder" article on my blog a couple of days ago after running it through Copyscape first. No problem at Copyscape as 100% unique. This was added to my site that has only unique content on it, so I was a bit aprehensive about adding this new article.

The article has been indexed at Google, so ran it through Copyscape again and it did not recognise it, maybe a bit early!

Only problem I can possibly foresee is that as this content in "Article Builder" gets used more and more often, will this then make my articles I add to my sites, to be no longer unique.

Maybe I am using this content in the wrong manner. Should we simply add this content to feeder sites and the such and not on sites we are protecting as unique, especially with Google Panda etc.

Re: copyscape api
« Reply #3 on: October 20, 2011, 04:15:36 AM »
Just put my first "Article Builder" article on my blog a couple of days ago after running it through Copyscape first. No problem at Copyscape as 100% unique. This was added to my site that has only unique content on it, so I was a bit aprehensive about adding this new article.

The article has been indexed at Google, so ran it through Copyscape again and it did not recognise it, maybe a bit early!

Only problem I can possibly foresee is that as this content in "Article Builder" gets used more and more often, will this then make my articles I add to my sites, to be no longer unique.

Maybe I am using this content in the wrong manner. Should we simply add this content to feeder sites and the such and not on sites we are protecting as unique, especially with Google Panda etc.


it depends on how google views your site. I believe your site would get the credit if it was first published their. On the other hand, if a more reputable site publishes the same article, your indexed pages might get pushed further down.

A good trick is to immediately do some bookmark on such content after publishing

Offline Meg

  • *****
  • 7587
  • Freedup to do what you really want
    • View Profile
    • Keep The Fire Lit!
Re: copyscape api
« Reply #4 on: October 20, 2011, 04:32:59 AM »


A good trick is to immediately do some bookmark on such content after publishing

What do you mean by "bookmark" please?

Re: copyscape api
« Reply #5 on: October 20, 2011, 09:55:01 AM »
I think he means social bookmarking sites.  That way Google can detect the date/time stamp of the posted page article.  Is that what you mean?

Re: copyscape api
« Reply #6 on: October 20, 2011, 08:42:17 PM »
I think he means social bookmarking sites.  That way Google can detect the date/time stamp of the posted page article.  Is that what you mean?


yes indeed! I always use Google bookmarks first. Another good trick is also to inject some lsi relevant keywords into the article to make it more powerful.

Offline Meg

  • *****
  • 7587
  • Freedup to do what you really want
    • View Profile
    • Keep The Fire Lit!
Re: copyscape api
« Reply #7 on: October 20, 2011, 11:54:13 PM »
I think he means social bookmarking sites.  That way Google can detect the date/time stamp of the posted page article.  Is that what you mean?


yes indeed! I always use Google bookmarks first. Another good trick is also to inject some lsi relevant keywords into the article to make it more powerful.

Thanks