tumblr scraping went bad

[abcva]

so basicly I harvested kws then scraped tumblr urls and then gone through them with vanity checker or whatever is name of scrapebox plugin. results 352 urls - 352 errors. mostly error 500/403, 'completed', timeout.
What is problem? I am using scrapebox with 380 proxies I scraped with scrapebox

 

[SOCOM]

Public proxies go to shit after a while. That may be the case. I only use private proxies and it seems to work fine.

 

[loopline]

so basicly I harvested kws then scraped tumblr urls and then gone through them with vanity checker or whatever is name of scrapebox plugin. results 352 urls - 352 errors. mostly error 500/403, 'completed', timeout.
What is problem? I am using scrapebox with 380 proxies I scraped with scrapebox

As noted above the first thing to do is use private proxies. 500 is a server error and 403 is a forbidden error.

You might wind up with a 403 from Tumblr but its more likely a proxy issue and its unlikely tumblr would give a 500 so again probably the proxy.

I think tumblr also changed their formatting, if you haven't updated it yourself, you can always do so. I know in the next version of the vanity addon they will update it, but Scrapebox built the vanity addon so users can customize it. So you can always just check it yourself.

But if you want to edit the defintion this works:

[Available1]
resultcode=404
mustcontain= <h1 class="error-message-title" data-localization="heading">
                    There's nothing here.
                </h1>
mustnotcontain=

 

[mindmaster]

Check my guide on how to streamline your tumblr scrape and availability check: http://www.blackhatworld.com/seo/th...blogs-10-times-faster-than-anyone-else.834896