@Kaine - Ah, I don't know how I forgot to mention keyword density to Sven. Its so basic, but I totally forgot :)
@Sven - Taken from the web. "The formula to calculate your keyword density on a web page for SEO purposes is ( X / Y ) ∗ 1…
@TheGypsy - Yes, I hope so too. Hopefully, things will run smoother with the new version since James will be here directly. I'm sure he'll create a new thread for that. We'll have to see ...
I spoke with James (SEREngines) creator to see what was going on with SERE V3.
He said, "Working through some changes on SERE3 (some things that Sven picked up), hopefully can shortly roll it out soon."
He also mentioned he would be coming…
@TheGypsy - For SEREngines, from what James (SERengines) developer told me in the past was that V2 was having issues with newer javascript sites due to an outdated browser which caused memory and CPU bloating. The new version &…
James from SERE told me, "Over the past 4 months we have been working on SEREngines v3 and it has just been integrated within GSA SER beside SEREngines v2 (while we migrate the engines to the new system). I found the issue and…
I wonder what he's been up to? I used to talk to him pretty often, but haven't seen him around in a while. From what I remember, I think he stopped using the automated tools and was doing more white hat stuff. Hope he is doing well.
Also, I tried y…
It seems there might be an issue with your headless install, "C:\Users\Admin\AppData\Roaming\GSA Search Engine Ranker\serengines\HeadlessM.dll"
I would try clicking the update button next to the SEREngines API key and choosing "force …
Hmm,
In SER go to options > advanced tab. Click the button that says "update" next to the SERengines API key and choose "force reinstall". Hopefully that helps.
If that doesn't help, you probably need to contact SERengines…
@prniches - That is really odd. Something similar happened to users back when there was a bad DDOS and it triggered some licensing issues. I'm assuming you're on the latest version 1.97?
I've sent you a PM.
So you have one project that is identifying URLS and then another dup remove project that is removing dups from that identified folder?
I can try to test on my end as well.
@Aleksandrius- Yes, I did create a KW tool a few years ago. (which I never released) I agree that the UI needs some improvement. I gave Sven some of my UI ideas for this KW tool a few months ago so I'm sure it will improve over time.
I was just cu…
It looks like James pushed an update the other day to fix a some sites.
As far as SEO goes, all I can say is that the Web 2.0's haven't had any negative effect on any of my sites. I'm not sure how much of a ranking benefit I've gotten from them, b…
@starpulse89 - Well, the identification should be very close to how SER identifies them but there might be some differences. It's really up to you if you want to import a raw list or not. Using the "deep matching" option in Pi might help a…
If you import a raw URL list, SER will need to identify each URL + register + post where if you import a .SL (site list) its already identified and SER will be able to register + post.
SER should work a bit faster with a .SL than a raw list.
I'm n…
@tennisfans- James asked what email you sent it from? Can you PM me the email? Also, he said he might request VPS login details to check your setup if you're running on a VPS.
@ksatul - It should be active and working and yes it should fill out profile and other pages to make it look more natural. It's best to shoot an email to them directly if you need assistance.
@Vmart - Ok, on my end the unrecognized URLS are going in the unrecognized folder that I set. That's why its important to have the "create a file for unrecognized URLS" checked. I would prefer if you send me the "unknown" URLs fr…
@VMart - Well, if the URLS are dead, they should not be in the recognized folder. You do have the option "create a file for unrecognized URLS" selected, right?
Dead links should be going in the folder you set there.
I'm testing on my end n…
@VMart - Are you using proxies while identifying?
Also, make sure you just select the SER engines in Pi and not the extended engines when identifying if you're using them with SER.
It's hard to say why a URL was identified without seeing a sample …