GSA optimizing - help needed.

bossaura

Hey GSA users.

So far I've been playing around with gsa for some days, and have been struggeling to maintain a stable vpm over 100.

I've ordered a vps from cheapseovps, with 3 gb ram, and 2 cores, which im running GSA ser, GSA captcha breaker and nothing else on.

Im using GSA Captcha breaker as main, and deathbycaptcher as second captcher solving service. 

Im using 30 semi dedicated proxies(buyproxies.org) for GSA, and running with 250 threads.

Beside that I have a premium list. (serlists.com) (RED list)

My settings are like this:

Project settings:

GSA Options:

With this im running around 25 vpm, and I want to optimize for around 100 vpm.

Any hints for what I can change?

Thank you for your readings.

ron

1. Don't disable banned proxies. Every private or public proxy will get line noise. One by one each proxy will get shut down and your LPM will suffer. It is temporary (as in seconds). Never check this if you are using private proxies.

2. I would not check "Automatically decrease threads..."....Unless you are having serious server issues because the server is outdated or weak.

3. In project data settings, always, always check "Try to always place an URL with an anchor text..." You are missing out on a lot of links.

4. Uncheck Web2.0 (you need SEREngines to make that platform work, so you will get almost zero links), bookmarks (almost impossible to make links because of captcha, and there are very few anyway), Pingback, Indexer, and Exploit (because in my opinion these are complete total garbage links), and consider checking directory.

5. The above comment #4 is about linkbuilding efficiency (getting rid of web2.0 and bookmarks) so that SER can focus on more productive platforms - so more links. And I also threw in the comment about Pingback, Exploit and Indexer, as they have little to zero SEO value.

6. I would consider splitting this project into two. You want to post again and again to the junk platforms like comments, guestbook forum, etc. You are not allowing yourself the chance to do so with this configuration, and that is costing you LPM.

Ron