what is problem with this? [scrapebox]

[koreanbrokie]

i cant scrape normally. i can only scrape google 10 results..

 

[tazarbm]

google blocks your IP, you need to use proxies (and preferably private proxies, too as they last longer and they're safer then free proxies)

 

[koreanbrokie]

google blocks your IP, you need to use proxies (and preferably private proxies, too as they last longer and they're safer then free proxies)

i got same result with residential proxies asocks.com provides.
so i thought it could be caused by other problems.

maybe i should just change proxy comp

 

[tazarbm]

i got same result with residential proxies asocks.com provides.
so i thought it could be caused by other problems.

maybe i should just change proxy comp

i'm not an expert on proxies so I don't know what the problem could be. When I used SB last year I used proxies from MyPrivateProxies.com and as long as you specify on the checkout page that you'll be using them for SB they will work flawlessly.

If you have $11-12 to waste buy 5 proxies off MPP and see if they work and then you'll know if it's the proxies

Or, wait for someone else to share their opinion, maybe they know what the problem is...

 

[Steptoe]

Google have slightly changed the html of their results pages, which unfortunately has broken Scrapebox's parser. I'm sure they'll update soon, but in the meantime you can you can go to Settings > Harvester Engine Configuration > click on Google (SSL) > update the text in 'Just before the url' to

<div><a href="

> change Display Name to something else > click Add as New Engine. Then use this new engine for scraping instead of the usual Google engine.

 

[koreanbrokie]

ㅅ

Google have slightly changed the html of their results pages, which unfortunately has broken Scrapebox's parser. I'm sure they'll update soon, but in the meantime you can you can go to Settings > Harvester Engine Configuration > click on Google (SSL) > update the text in 'Just before the url' to

<div><a href="

> change Display Name to something else > click Add as New Engine. Then use this new engine for scraping instead of the usual Google engine.

thanks for great help

 

[kenobeen]

Google have slightly changed the html of their results pages, which unfortunately has broken Scrapebox's parser. I'm sure they'll update soon, but in the meantime you can you can go to Settings > Harvester Engine Configuration > click on Google (SSL) > update the text in 'Just before the url' to

<div><a href="

> change Display Name to something else > click Add as New Engine. Then use this new engine for scraping instead of the usual Google engine.

bro it still says when i test the engine "no links retrieved". Do you have an alternative solution ?

Best

 

[SERPhustler]

Use some good proxies and you'll be good!

 

[Steptoe]

bro it still says when i test the engine "no links retrieved". Do you have an alternative solution ?

Best

You're right, Google have updated their SERPs output yet again. These are the values I'm using now:

Just before the url:

<a jsname="UWckNb" href="

Marker for "Next page":

aria-label="See more"

I'm sure Scrapebox will update the default engines in due course.

 

[kenobeen]

You're right, Google have updated their SERPs output yet again. These are the values I'm using now:

Just before the url:

<a jsname="UWckNb" href="

Marker for "Next page":

aria-label="See more"

I'm sure Scrapebox will update the default engines in due course.

@loopline boos check it out.

 

[loopline]

Yes, here is a copy and paste of the mail from support

"
Google has made some changes to their code, and in order to compenste you will need a new version of scrapebox as well as the new engine files we released.



First please update to at least Version 2.1.0.38 beta 6 of Scrapebox.



Depending on what version of Scrapebox you are currently using, you may need to go thru the update process multiple times to get the choice of beta 6.



Here is a video explaining the new update process:

Second please go to settings >> harvester engine configuration >> import >> download default engines



Then it should work.







We are also currently in the process of rebuilding addons and plugins that use google, so if there is any addon or plugin using google that does not work, please update that. If there is no update out just yet, check back and update when there is."

 

[Steee]

I think you already use the same proxy again and again that's why Google blocked your proxy. Change your proxy to Private sock5 proxy. Shared proxy won't work for you only dedicated proxy can run scrapebox.

 

[koala_lumpbua]

Thanks a lot @Steptoe and @loopline! Had the same issue and thought the problem was how I configured ScrapingBee proxies but now it works after adjusting the harvester engine config / adding a new custom engine.

 

[ecarder]

Yes, here is a copy and paste of the mail from support

"
Google has made some changes to their code, and in order to compenste you will need a new version of scrapebox as well as the new engine files we released.



First please update to at least Version 2.1.0.38 beta 6 of Scrapebox.



Depending on what version of Scrapebox you are currently using, you may need to go thru the update process multiple times to get the choice of beta 6.



Here is a video explaining the new update process:

Second please go to settings >> harvester engine configuration >> import >> download default engines



Then it should work.







We are also currently in the process of rebuilding addons and plugins that use google, so if there is any addon or plugin using google that does not work, please update that. If there is no update out just yet, check back and update when there is."

This worked for me. I was having the same problem with Google. Thanks!