ScrapeBox Problem - Custom Footprint

J

jelderkin

Newbie

Nov 30, 2011

15

1

• Jan 18, 2012

• #1

Hey everyone

I have used SB in the past to scrape pligg bookmarking sites to create lists for Sick Submitter yet I started trying to scrape today using SB with the custom footprint

inurl:/register.php intextowered by Pligg (same as I used before)

Now I scrape a 1000 keywords and clicked harvest but when my results comes through maybe one or 2 will meet the custom footprint?????

Why is this happening

Also what are the best keywords to find bookmarking sites???

 

J

-Jericho-

Elite Member

Jan 10, 2010

2,831

1,739

• Jan 18, 2012

• #2

Have you tested it in Google? Test it there to make sure it's working first. Google has made some modifications to their boolean searches recently like the + symbol doesn't work as AND anymore last time I checked. Also have you tried using "" around the intext words?

 

J

jelderkin

Newbie

Nov 30, 2011

15

1

• Jan 18, 2012
• Thread Starter Thread Starter

• #3

Yes it works fine in Google but it is not pulling the results into SB well it is but none of them have /register.php in the url I don't see why its not working????

It was like 2 weeks ago so why the sudden stop also when I used sick submitters scraper just to see the difference using the same footprint it pulled fine of course I want to use SB due to pulling better results

 

J

jelderkin

Newbie

Nov 30, 2011

15

1

• Jan 18, 2012
• Thread Starter Thread Starter

• #4

I turned off use proxies and bang worked fine :S:S:S:S what is that all about????

 

bulletservice

Regular Member

Mar 1, 2008

319

342

• Jan 18, 2012

• #5

jelderkin said:

I turned off use proxies and bang worked fine :S:S:S:S what is that all about????

Click to expand...

May be your proxies are IP banned? Timeout?

 

J

jelderkin

Newbie

Nov 30, 2011

15

1

• Jan 18, 2012
• Thread Starter Thread Starter

• #6

I cannot get it to work with proxies ia anyone else having SB problems scraping using custom footprints???

 

kokoloko75

Elite Member

Jan 1, 2011

1,627

1,950

• Jan 18, 2012

• #7

This will not fix your problem but just I advise you to use double quotes, like :

Code:

inurl:"/register.php" intext:"Powered by Pligg"

Beny

 

huykun

Regular Member

Jan 16, 2011

224

97

• Jan 18, 2012

• #8

thats because a lot of pligg sites these days are changing their registration to avoid footprints.

Like this one forgalombolkivonas . com/fuck-spammers3.php

It's not register.php anymore! LOL

 

J

jelderkin

Newbie

Nov 30, 2011

15

1

• Jan 18, 2012
• Thread Starter Thread Starter

• #9

I will try it with double quotes from now on and it can't be IP blocked or they would fail the SB test, I am currently testing 9000 public proxies and will try again with a fresh list I have also sent a message to the SB team to see what they have to say.

I will give it a go scraping looking for different footprints but when I turned off proxies I found 4000 with /register.php but I will keep you all updated until I solve this problem

 

kokoloko75

Elite Member

Jan 1, 2011

1,627

1,950

• Jan 18, 2012

• #10

jelderkin said:

I will try it with double quotes from now on and it can't be IP blocked or they would fail the SB test, I am currently testing 9000 public proxies and will try again with a fresh list I have also sent a message to the SB team to see what they have to say.

I will give it a go scraping looking for different footprints but when I turned off proxies I found 4000 with /register.php but I will keep you all updated until I solve this problem

Click to expand...

Try (right now) with these fresh proxies :

Code:

61.6.213.121:8118
86.99.217.77:8118
92.96.62.202:8118
92.96.164.197:8118
92.96.203.69:8118
92.96.203.107:8118
92.96.203.162:8118
92.96.207.159:8118
92.96.208.61:8118
92.96.208.109:8118
92.96.211.33:8118
92.96.214.112:8118
92.96.246.213:8118
92.96.247.203:8118
92.96.251.128:8118
92.99.136.251:8118
92.99.250.131:8118
92.99.250.168:8118
92.99.251.86:8118
119.73.1.33:8118
119.73.3.123:8118
119.73.15.75:8118
119.73.45.213:8118
119.73.55.137:8118
119.73.55.176:8118
119.160.138.176:8118
119.160.146.42:8118
119.160.176.72:8118
119.160.176.107:8118
119.160.177.76:8118

Beny

 

monkid

Power Member

Jan 2, 2010

679

312

• Jan 21, 2012

• #11

I have the same problem here! It has been few days, the odd thing is the default wordpress is working, but when I try using cutom footprints, it's not working. So, I dont think it is problem with proxies. Any solution yet?