innosoft
Elite Member
- Nov 25, 2008
- 1,661
- 643
Thanks a lot for your kind words!
Permanently Closed Marketplace Sales Thread
- Thread starter innosoft
- Start date
- Status
Thanks a lot for your kind words!
Hello, I'm trying to buy the pro lifetime on the site and it keeps showing a popup of 30% off, but the BlackFriday coupon code does not work as it says!
please send me the correct coupon code
thank you!
iguanna
innosoft
Elite Member
- Nov 25, 2008
- 1,661
- 643
purely depends on proxy. you might need 40-50 dedicated proxies for that.
innosoft
Elite Member
- Nov 25, 2008
- 1,661
- 643
i have sent you coupon code.
innosoft
Elite Member
- Nov 25, 2008
- 1,661
- 643
We are working on update. Within 24 hours you will have a update. it will be then fixed
innosoft
Elite Member
- Nov 25, 2008
- 1,661
- 643
Update V1.0.7.7.0 Released!
This Major/Critical Update for Ezee Rank Tracker. We have fixed few bugs and implemented several enhancements.
Change Log:
1. Updated Google Parser Algorithm
2. Updated Bing Parser Algorithm
3. Updated Datetime Issue.
4. Fixed IP Problem Issue.
5. Fixed CSV Export Bug.
This Major/Critical Update for Ezee Rank Tracker. We have fixed few bugs and implemented several enhancements.
Change Log:
1. Updated Google Parser Algorithm
2. Updated Bing Parser Algorithm
3. Updated Datetime Issue.
4. Fixed IP Problem Issue.
5. Fixed CSV Export Bug.
IMTopgun
Power Member
- Sep 5, 2011
- 737
- 229
Thanks for the recent update, works great! As long as you continue to fix bugs that occasionally crop up you will continue to have a valuable tool. Because you fix issues quickly I bought your other two software programs although I haven't tested them yet. Hope they work just as good as EzeeRankTracker!
innosoft
Elite Member
- Nov 25, 2008
- 1,661
- 643
innosoft
Elite Member
- Nov 25, 2008
- 1,661
- 643
Critical Update V1.0.7.7.2 Released!
Please Update your Software ASAP.
Change Log:
1. Fixed Famous "Parsing Results" Issue
2. Fixed Memory Leak Issue.
3. Fixed bugs in Bing and Yahoo Parser
4. Updated Google Parser Algorithm
5. Updated Internal Threading Algorithm
6. Improved Efficiency and Stability.
Please Update your Software ASAP.
Change Log:
1. Fixed Famous "Parsing Results" Issue
2. Fixed Memory Leak Issue.
3. Fixed bugs in Bing and Yahoo Parser
4. Updated Google Parser Algorithm
5. Updated Internal Threading Algorithm
6. Improved Efficiency and Stability.
waitier
Power Member
- Sep 5, 2013
- 738
- 208
The initial review was made in a very sarcastic tone, which I think it's not very suitable for either of us. Now I am going to construct it in such a way that will be a constructive criticism.
I'm going to skip some of the initial roadblocks and minor UI/UX that isn't what this software is built for.
What I have faced is an issue that's very unique and most people will not face because the first thing people thought of when bumping into it is "you need proxies" "you need to change the settings" and the canned response we all know when dealing with IP blocking. But what happened was that the software itself got blocked by google, instead of my IP being blocked.
I have tested it with the same 1000 position keyword in my own browsers, with and without incognito, and I can still search normally. I have since contacted support, and there it was, the support gave me the textbook answer of "this is the setting in order to avoid your IP being blocked", and nothing else. I wrote so many lines, and they gave me a one liner reply, very unsatisfactory. And we are all busy people, me, you, your support team, and a one liner canned reply means this will never get solved till a long long time. I have yet to utilize it to it's full potential, while waiting for a better answer.
If the software developer is open minded and willing to improve his program based on user's suggestion, then
Here's what I will suggest:
Find a fix to the software regarding my issue. (believe it or not, you might actually reduce the cost of getting more proxies if it didn't expose itself as a bot)
A better trained support team. (one liner and no "we'll look into it ASAP" attitude is what makes people get angry and nets you negative reviews)
A captcha option (i heard this will come in v2. i'm surprised this isn't in there sooner as this is the first thing anyone dealing with scraping will use. but, it ties back to my initial issue, if it ain't IP issue, then it shouldn't need captcha in the first place. if you fixed that, then you don't need captcha.)
A auto stop when hit captcha (i'm very curious why it didn't stop automatically when it was faced with captcha verification, yet it doesn't have captcha option, so it continued to perform search despite knowing it's blocked)
A better error reporting to user and to you (telling us "ip problem" means alot of things, telling "ip blocked:captcha verification" means one thing. We know what happened, and you also need to know what happened, and it's easier to solve when we know what exactly went wrong)
Method to prevent being blocked (i think we need a better implementation of human emulation.
1. setting a timer to perform at a fixed interval is IMO not how a human behaves. this works better for example: first-keyword (search 100 - 10 seconds, search 200 - 15 seconds) pause for 30 seconds before firing the next-keyword. i think that in between pause is missing in this current version.
2. what i do is also click into results, go back to search, go back and forth the serps randomly when i want to find for something not in page 1.
3. sometimes, i also type in search not related to any of the kw that i entered before.
4. and, i don't always go all the way down to page 10, if i want to, i will resume the search after another kw to go page 10.
5. different URL (to maintain the accuracy, sure, you need to perform using the exact match query string, but that is a footprint in itself. once in a while, use a different URL unrelated to the project)
6. leave zero footprint (well, i guess there's a need to elaborate on this. your bot was detected by google, so i think you need to clear up your internal browser, maybe even cookies, i don't really know what internal engine you use, but leave zero footprint.)
That's all from me at the moment, I'm sure I had more in my mind, but I can only churn out so many. I see a huge potential going forward, and i hope i hadn't waste any of our time, me writing this, and you reading this.
I'm going to skip some of the initial roadblocks and minor UI/UX that isn't what this software is built for.
What I have faced is an issue that's very unique and most people will not face because the first thing people thought of when bumping into it is "you need proxies" "you need to change the settings" and the canned response we all know when dealing with IP blocking. But what happened was that the software itself got blocked by google, instead of my IP being blocked.
I have tested it with the same 1000 position keyword in my own browsers, with and without incognito, and I can still search normally. I have since contacted support, and there it was, the support gave me the textbook answer of "this is the setting in order to avoid your IP being blocked", and nothing else. I wrote so many lines, and they gave me a one liner reply, very unsatisfactory. And we are all busy people, me, you, your support team, and a one liner canned reply means this will never get solved till a long long time. I have yet to utilize it to it's full potential, while waiting for a better answer.
If the software developer is open minded and willing to improve his program based on user's suggestion, then
Here's what I will suggest:
Find a fix to the software regarding my issue. (believe it or not, you might actually reduce the cost of getting more proxies if it didn't expose itself as a bot)
A better trained support team. (one liner and no "we'll look into it ASAP" attitude is what makes people get angry and nets you negative reviews)
A captcha option (i heard this will come in v2. i'm surprised this isn't in there sooner as this is the first thing anyone dealing with scraping will use. but, it ties back to my initial issue, if it ain't IP issue, then it shouldn't need captcha in the first place. if you fixed that, then you don't need captcha.)
A auto stop when hit captcha (i'm very curious why it didn't stop automatically when it was faced with captcha verification, yet it doesn't have captcha option, so it continued to perform search despite knowing it's blocked)
A better error reporting to user and to you (telling us "ip problem" means alot of things, telling "ip blocked:captcha verification" means one thing. We know what happened, and you also need to know what happened, and it's easier to solve when we know what exactly went wrong)
Method to prevent being blocked (i think we need a better implementation of human emulation.
1. setting a timer to perform at a fixed interval is IMO not how a human behaves. this works better for example: first-keyword (search 100 - 10 seconds, search 200 - 15 seconds) pause for 30 seconds before firing the next-keyword. i think that in between pause is missing in this current version.
2. what i do is also click into results, go back to search, go back and forth the serps randomly when i want to find for something not in page 1.
3. sometimes, i also type in search not related to any of the kw that i entered before.
4. and, i don't always go all the way down to page 10, if i want to, i will resume the search after another kw to go page 10.
5. different URL (to maintain the accuracy, sure, you need to perform using the exact match query string, but that is a footprint in itself. once in a while, use a different URL unrelated to the project)
6. leave zero footprint (well, i guess there's a need to elaborate on this. your bot was detected by google, so i think you need to clear up your internal browser, maybe even cookies, i don't really know what internal engine you use, but leave zero footprint.)
That's all from me at the moment, I'm sure I had more in my mind, but I can only churn out so many. I see a huge potential going forward, and i hope i hadn't waste any of our time, me writing this, and you reading this.
innosoft
Elite Member
- Nov 25, 2008
- 1,661
- 643
IP Blocking is very common if your ISP is spammed. I dont know how to write a long story on this
This is very common thing that every IM'er knows. There are several users who use Proxies and it does works great for them.
We have an awesome training team. they are doing really good job. I will see what is missing and do needful.
When it comes to suggestions, half of it is already being worked on V2. I dont have any ETA on that as of now as we planned to release it by start of this year but got delayed.. I can try to sneak some if it in current version.
waitier
Power Member
- Sep 5, 2013
- 738
- 208
Yep, we all know that ip blocking is very common. I myself have faced the issue when doing it on my own browser. When someone on the other end of my country is using the same ip as me searching for things frantically, i face the ip ban on the first search. But I am not talking about any of those.
I'm talking about not leaving footprints and not revealing the bot as bot. Now, i have mentioned to you about 2 types of ban. IP ban, and bot ban (inbuilt browser ban). I'm facing a bot ban, not IP ban. If you can solve the bot ban issue, then per ip can go way farther than the current few searches. Again, I know what it means to face a IP ban, on a dynamic or static IP. In my office, sometimes I overdid it on my PC, and my colleagues are curious why they face the ban on their PC. That's IP ban. Now, what I'm talking about is bot ban. Instead of trying to find out the problem, you [still] insisted you are not wrong.
At least a "we'll look into this matter and give you a feedback in 1 days time" or something along the lines is what nets you positive review and recommendation. It goes a long way.
Update: While browsing normally, this is what happened. http://prntscr.com/9vrz93 all i did was using site:site.com and after a few searches it got blocked, it's a common thing while scraping. Then i fired a incognito and there's no block.
I'm talking about not leaving footprints and not revealing the bot as bot. Now, i have mentioned to you about 2 types of ban. IP ban, and bot ban (inbuilt browser ban). I'm facing a bot ban, not IP ban. If you can solve the bot ban issue, then per ip can go way farther than the current few searches. Again, I know what it means to face a IP ban, on a dynamic or static IP. In my office, sometimes I overdid it on my PC, and my colleagues are curious why they face the ban on their PC. That's IP ban. Now, what I'm talking about is bot ban. Instead of trying to find out the problem, you [still] insisted you are not wrong.
At least a "we'll look into this matter and give you a feedback in 1 days time" or something along the lines is what nets you positive review and recommendation. It goes a long way.
Update: While browsing normally, this is what happened. http://prntscr.com/9vrz93 all i did was using site:site.com and after a few searches it got blocked, it's a common thing while scraping. Then i fired a incognito and there's no block.
Last edited:
- Status