+- ScrapeBox Forum (https://www.scrapeboxforum.com)
+-- Forum: ScrapeBox Main Discussion (https://www.scrapeboxforum.com/Forum-scrapebox-main-discussion)
+--- Forum: General ScrapeBox Talk (https://www.scrapeboxforum.com/Forum-general-scrapebox-talk)
+--- Thread: Google not work when use Custom footprint with inurl:blog (/Thread-google-not-work-when-use-custom-footprint-with-inurl-blog)
Google not work when use Custom footprint with inurl:blog - tomrev - 10-09-2011
When I harvest by custom footprint with *inurl:blog* and some keywords, the google harvesting process forever (I push abort button after several minutes because any result or bandwidth change and I tried many times).
But there are harvest URL result for harvesting with blank(in custom footprint textbox) custom footprint, Wordpress and others footprints.
All process use public proxy. Does Scrapebox have problem with the "inurl:blog" custom footprint?
Sorry for confused question.
Edit: Tested by disable proxy, inurl:blog custom footprint is worked. ?? Can I assumed that google could detected scrapebox or public proxy to disable some search function?
RE: Google not work when use Custom footprint with inurl:blog - etojoy - 10-09-2011
no idea, maybe you should play around with maximum connections.
I never use proxy to scrape, takes too long.
RE: Google not work when use Custom footprint with inurl:blog - s4nt0s - 10-10-2011
(10-09-2011, 08:53 AM)tomrev Wrote: When I harvest by custom footprint with *inurl:blog* and some keywords, the google harvesting process forever (I push abort button after several minutes because any result or bandwidth change and I tried many times).
But there are harvest URL result for harvesting with blank(in custom footprint textbox) custom footprint, Wordpress and others footprints.
All process use public proxy. Does Scrapebox have problem with the "inurl:blog" custom footprint?
Sorry for confused question.
Edit: Tested by disable proxy, inurl:blog custom footprint is worked. ?? Can I assumed that google could detected scrapebox or public proxy to disable some search function?
Well that just solved your problem right there. The issue is your free proxies. Get you a decent set of private proxies and the issue should be fixed.
