PR checking AFTER checking if GSA can post to the site?
I tried the PR filter for a few days but switched it off again as it cut my LPM down by more than 50%.
When I looked in the logs, I often saw that a site was loaded, then the PR was checked and if considered good, GSA tried finding a form to post/sign up. More often than not, though, it realized that it couldn't detect the engine and moved on.
In other words, there was a lot of time wasted checking PR. I use fast private proxies for posting and rather slow (but working) public ones for checking PR.
It would be great if SER could load a site, check if it can detect the engine and if there was one detected (one that's been selected under "where to submit"), then check for the PR.
When I looked in the logs, I often saw that a site was loaded, then the PR was checked and if considered good, GSA tried finding a form to post/sign up. More often than not, though, it realized that it couldn't detect the engine and moved on.
In other words, there was a lot of time wasted checking PR. I use fast private proxies for posting and rather slow (but working) public ones for checking PR.
It would be great if SER could load a site, check if it can detect the engine and if there was one detected (one that's been selected under "where to submit"), then check for the PR.
Comments
Wouldn't it be faster for SER to check if it can post to a site (engine detection) and then check for PR?
21:46:26: [+] 00468/16029 matches engine Wordpress Article - http://singlemindedwomen.com/editors/
21:46:26: [+] 00468/16029 PR-3 OK - http://singlemindedwomen.com/editors/
21:46:26: [+] 00468/16029 new URL - http://singlemindedwomen.com/wp-login.php?action=register
21:46:26: [-] 00468/16029 required variable "login" was not used in form.
21:47:24: [+] 00514/16029 matches engine Article Directory Pro - http://articledirectorypro.com/
21:47:24: [+] 00514/16029 PR-1 OK - http://articledirectorypro.com/
21:47:24: [-] 00514/16029 unable to find suitable URL
21:47:30: [+] 00517/16029 matches engine Wordpress Article - http://thompsonteam.ca/blog.html
21:47:30: [+] 00517/16029 PR-2 OK - http://thompsonteam.ca/blog.html
21:47:30: [+] 00517/16029 new URL - http://thompsonteam.ca/wp-login.php?action=register
21:47:30: [-] 00517/16029 wrong engine detected - http://thompsonteam.ca/wp-login.php?action=register
And in the last case, "wrong engine detected"...GSA detects the engine first, checks the PR but then suddenly it's a wrong engine? (the url still looks like WP to me).
That's what I meant in the original request, to do the PR checking after these secondary checks (first it checks for the engine and then it seems to check for a form or something - sorry, I'm not a coder so my understanding is limited
"wrong engine detected" simply means something like it's that platform but still has some things that would make a further submission useless like a "this site is invite only" message.
But I can not optimize this much further. The "new url" or "no form found" already belongs to the submission process. It's hard to tell when to do the PR check here before or after it as the finding of a new URL could even result in a submission (e.g. Fast Indexer engine or fake referer one).