CYBERSEO Error (fixed) | CyberSEO Pro | Support Forum

Uninstalling the plugin and reinstalling with a fresh install from download of pro did not work.  Now I am trying uninstalling all feeds and uploading them one by one again manually instead of with old .dat file.  It appears to be the case that the settings have something to do with this.  If you feeds get all messed up in the timer incrementation, it crashes the program.  Then the program remembers this state, and it is not possible to remove the settings until you remove the saved feeds.  It's a hell of a lot of work but I am going to try and see if it works.  I really don't want to spend the money on Pro here and then have to spend even more over at WPeMatico.  I will update once I have done so.

I think it bears looking at the solution offered in the other plugin before we jump to conclusions.  Something different is going on that is a ton faster and is very stable.  On another note, I installed a fresh instance of CyberSEO Lite on a brand new site and it is whipping along at light speed with no issues.  So I can confirm that this is a matter of slowdown due to database size and the number of posts.  So there is a tradeoff here.  The excellence of your features in the Pro package versus limiting the power of SEO through sheer numbers of posts and evergreening content.  In order to achieve the weight necessary to move the needle so to speak, one has to have a volume of content.

The function to assign a lifetime to the posts is most likely the workaround that you thought of and I am sure that if I kept everything to about a week of posts it would function perfectly but I would be getting a ton of 505 errors from Google AdSense and eventually get kicked out.  Too much post rotation is a major red flag.

You might be able to get away with about 90 days of rotation and not trigger the Google Apocalypse on your site.

The journey that I have been on so far has been quite a nightmare.  I started out on shared hosting with a site running CyberSEO Lite and WP to Twitter.  I did some excellent backlinking and was cooking along with over 30K unique visitors a month, page RPM of 26 USD and CPC of around 5 USD.  Then I hit the 1GB database limit on shared hosting and the site died. I had no way to get the database to work without removing tons of entries in the wp-postmeta and wp-posts tables which just ruined the site and I had to start over but I did so on a VPS server to avoid the database size limit issue.  I managed to get everything back up but the bots lost me in the IP changeover even with an htaccess redirect and I had to start over again at about 100 visitors a day.  The site worked pretty well off and on and I was able to get the number of posts back up to around 120K and started to pull some search traffic again and then it started really freaking out.  I spent a ton of money on server and database specialists to analyze what could be done with the server to make it more efficient and I upgraded to the largest VPS package (6 cores, 12GB RAM, 240 GB SSD) but nothing helped.  It ate that disk the way a kid eats candy, voracious.  Needless to say stuff just started changing out of the blue, the security holes in the website due to the lag problem on post-insertion and closing out the tables caused me to get hacked no matter what I did and I got pretty messed up so I had to can that instance too.  Now I am on my third instance and it's basically dead in the water as well.  The failed calls are in the cache and it does not have enough juice to move beyond them and run the plugin at the same time with more than one RSS feed.  If I go over one feed the entire site crashes.   Tons of anguish and now two months later and no hope of recovering the success I once had.  Shared hosting flexes power to the user that needs it the most and so I was able to get away with sucking whatever power was necessary to continually beat the ceiling and I was none the wiser until I hit the DB limit. BOOM.  Death spiral.  This is with several server and database specialists on payroll trying to figure it out.

The test instance that I just set up confirms that what you said about lag and post-insertion as well as some other things like timer incrementation in your two timers on the dashboard, which when they get screwed up by the lag cause all sorts of nasty shit to happen.

But look, I am not knocking your plugin.  It is by far the most feature-rich and amazing Autoblog plugin out there until you hit about 20 K posts.  I put on about 1200 posts a day so that happens in about ten days.  So basically I would have to set the post-life to two weeks tops.  Way too soon to escape the Google hammer I am afraid.  My prototype will only exist for about thirty days on a shared server or on the cloud where I Would be spending about 1K a month on bandwidth for sure to keep an archive site that would influence the bots and suck search traffic.

At the end of the day you don't need much.  You need the ability to pull from at least 50 RSS feeds in your niche keywords and post about 1200 to 2400 posts to your blog and Twitter daily being careful not to trip Twitter's API.  Then you need the ability to archive above 150K article snippets with a fairly good sized excerpt (around 400 words) with a nice looking "Read More" link.  You need internal linking on specific niche keywords that lead to all your category archive posts.  Finally you need to have the ability to evergreen your old content to keep the bots happy with the age of the posts.  Externally you need to have a strong and well thought out backlinking strategy but that can be done effectively in about 30 days.  The Achilles heel is the lag from the database on anything other than unlimited resources.  That is why I am so impressed with WPeMatico RSS Feed Fetcher.  The features are not as Cadillac but the performance is Hot Rod, literally kick ass.  I installed it on the site I imported the posts (127K) from my second instance (this current iteration - not the dev or brand new instance) and it churned right along as if nothing was different from a brand spanking new site like the dev/test instance is now)

However it has issues.  The tags do not get picked up by WP to Twitter and get converted to hashtags.  Some hook is not functioning properly there.  So that literally cuts your impressions on Twitter to less than a third.  Not tenable.  I am not sure if the Pro version of the plugin functions any better but he has a no refund policy so its a steep 280 bucks to find out!  Ha ha!  I am tempted to bite the bullet because of the performance.  I did the same with your plugin due to the features but hit the snag of performance lag and site degradation/hacking/vulnerability.

So I was thinking that if the performance of WPeMatico could marry the Kick Ass Features of CyberSEO PRO and have a kid, that would be money.  Big money.  But alas it most likely never will be.

I will continue to update you if I continue this journey.  Right now I am just kinda watching the dev/test instance to really flesh out my theories on performance and when and where things go bat shit crazy. 

Final update:

Our LIVE site is running WPeMatico and cranking out a steady 10 posts every 15 minutes with less than 25% load on CPU while the DEV site is maxed out CPU of 6 cores and posts only 6-8 posts an hour.

WPeMatico however does not create posts where the tags are picked up by Social Media Broadcast plugins.  I have a ticket in with them about this.  So I have decided to go with WPeMatico for now until something can be done about the lag issue with CyberSEO Pro.  I really hope you can fix it.  I would come back in a heartbeat!

For now I am going to talk with them a bit and then probably bite the bullet on an upgrade with them for at least the extended excerpt function.