Permanently Closed Marketplace Sales Thread

[Peter Ngo]

Hi Scrapebox team,

I noticed recently that GOogle index check doesn't work anymore, it returns all URLs as Yes, do you have any solutions to that now?

 

[blinggam]

Hi Scrapebox team,

I noticed recently that GOogle index check doesn't work anymore, it returns all URLs as Yes, do you have any solutions to that now?

@loopline @Sweetfunny

Can confirm, Google index checking is 100% broken, all URLs display as "Indexed" even if they aren't indexed.

Does Scrapebox use the "info:" command? If so, then we likely know why it's broken.
https://www.seroundtable.com/google-info-command-change-24718.html

I did some testing and it seems that the "info:" command still technically works for checking indexing, but if a page/domain isn't indexed, it shows a blank page instead of "no results". I'm guessing Scrapebox used the "no results" text as a footprint to determine indexing. If so, hopefully you'll be able to change it to somehow understanding that no results were found, without the text being present.

 

[softtouch2009]

Hi Scrapebox team,

I noticed recently that GOogle index check doesn't work anymore, it returns all URLs as Yes, do you have any solutions to that now?

@loopline @Sweetfunny

Can confirm, Google index checking is 100% broken, all URLs display as "Indexed" even if they aren't indexed.

Does Scrapebox use the "info:" command? If so, then we likely know why it's broken.
https://www.seroundtable.com/google-info-command-change-24718.html

The issue was already fixed and will be available in the next update.

 

[blinggam]

The issue was already fixed and will be available in the next update.

Cool, that's good to know. Hopefully the update is sooner than later. Thanks for the information.

 

[Peter Ngo]

The issue was already fixed and will be available in the next update.

Thanks for your fast response, please do let me know when the update is live. I just updated this morning and the indexing problem is still not solved, i guess there must be another update to tackle this issue.

 

[loopline]

Cool, that's good to know. Hopefully the update is sooner than later. Thanks for the information.

Thanks for your fast response, please do let me know when the update is live. I just updated this morning and the indexing problem is still not solved, i guess there must be another update to tackle this issue.

Its live already as of a while ago.

 

[blinggam]

Seems the update fixed it for me!! Thanks!!

 

[blinggam]

@loopline

Getting a ton of "ERROR" on Indexing check, when using private, Google passed proxies.
I re-tested proxies, only choose Google passed ones, and still getting ERROR on all checks now.

I checked 700 links, the last 100 were ERROR. Now, 100% of all links I checked (even ones that worked before) are all showing ERROR now.

Why is this happening?

Update: Disabled proxies and checked 2 links only, and they worked. But the proxies are 100% Google search passed using SB proxy-testing... and only kept Google passed ones.

Update #2: Tested proxies using GSA Google search check, got all ones that passed, added to SB... still 100% ERROR on all links.

Information about my setup:
100 private proxies
50 threads on indexing check (too high now? used this for many years)

One reason I could possibly think for this, is that Google now limits the amount of "site:" searches any IP can do to ~3 searches before you get a captcha. If Scrapebox is not using "site:" search, it may be that the proxies are encountering captchas far more often than before. I haven't used "info:" command enough to know how many searches before a captcha is triggered, but it could be the same thing. Just depends on how SB is now doing index checks.

If it is indeed a captcha issue and there is no other way to check indexing, one potential way could be to add 2captcha as a service, which can solve Recaptcha v2... and have SB solve the Google captchas before index checking resumes. This could potentially cost a lot of money for an indexing check... Again, depends on what is actually causing the error.

 

[blinggam]

Here is a snippet of the index check error log:

11/6/2017 8:52:00 PM: HTTP: 503 Service Unavailable, SOCKET: , URL: http://www.google.com/search?hl=en&source=hp&q=info%3URL REMOVED FOR PRIVACY
11/6/2017 8:52:01 PM: HTTP: 503 Service Unavailable, SOCKET: , URL: http://www.google.com/search?hl=en&source=hp&q=info%3URL REMOVED FOR PRIVACY
11/6/2017 8:52:01 PM: HTTP: 503 Service Unavailable, SOCKET: , URL: http://www.google.com/search?hl=en&source=hp&q=info%3URL REMOVED FOR PRIVACY
11/6/2017 8:52:02 PM: HTTP: 503 Service Unavailable, SOCKET: , URL: http://www.google.com/search?hl=en&source=hp&q=info%3URL REMOVED FOR PRIVACY

 

[Zandra]

I'm not sure if this is the place but a request would be for Link Extractor to be able to re-run all the URLs delivering "Error" and make it possible to filter out 404 errors. Now I run a batch, export as Excel document, delete 404 errors and completed, copy the rest, paste it into Scrapebox harvestor, open Link Extractor, import the URLs from harvestor, run.

That's a lot of steps considering there are a lot of errors every run.

 

[seo-sem]

Hey,I've updated to 2.0.0.92 but still google index is showing YES.Any other way to check indexed in scrapebox?

 

[loopline]

@loopline

Getting a ton of "ERROR" on Indexing check, when using private, Google passed proxies.
I re-tested proxies, only choose Google passed ones, and still getting ERROR on all checks now.

I checked 700 links, the last 100 were ERROR. Now, 100% of all links I checked (even ones that worked before) are all showing ERROR now.

Why is this happening?

Update: Disabled proxies and checked 2 links only, and they worked. But the proxies are 100% Google search passed using SB proxy-testing... and only kept Google passed ones.

Update #2: Tested proxies using GSA Google search check, got all ones that passed, added to SB... still 100% ERROR on all links.

Information about my setup:
100 private proxies
50 threads on indexing check (too high now? used this for many years)

One reason I could possibly think for this, is that Google now limits the amount of "site:" searches any IP can do to ~3 searches before you get a captcha. If Scrapebox is not using "site:" search, it may be that the proxies are encountering captchas far more often than before. I haven't used "info:" command enough to know how many searches before a captcha is triggered, but it could be the same thing. Just depends on how SB is now doing index checks.

If it is indeed a captcha issue and there is no other way to check indexing, one potential way could be to add 2captcha as a service, which can solve Recaptcha v2... and have SB solve the Google captchas before index checking resumes. This could potentially cost a lot of money for an indexing check... Again, depends on what is actually causing the error.

Scrapebox uses the info: operator.

Also not complaining at you, but if you look at the urls string in your error log you posted, you can see the string, including the info: operator. So that may be beneficial to you in the future.

As for now, just build a custom test for the info: operator.

Hey,I've updated to 2.0.0.92 but still google index is showing YES.Any other way to check indexed in scrapebox?

Ive seen this in some cases, I already mailed support about it. Im sure they will sort it.

 

[blinggam]

Scrapebox uses the info: operator.

Also not complaining at you, but if you look at the urls string in your error log you posted, you can see the string, including the info: operator. So that may be beneficial to you in the future.

As for now, just build a custom test for the info: operator.

Ive seen this in some cases, I already mailed support about it. Im sure they will sort it.

Right, I saw that after I posted -- but couldn't edit my first post.

Do you think this is caused by a change Google made to prevent people from checking indexing?
Why is it happening now when Index check has worked fine with these proxies/settings for many many years?

 

[blinggam]

Update - I did a custom proxy test as you said and it does seem to be working now. I'll wait until I start getting ERROR again and see what I can do about different proxies etc..

 

[seo-sem]

Ive seen this in some cases, I already mailed support about it. Im sure they will sort it.

I updated to newest version today and can confirm the issue is fixed.Thank you.

 

[loopline]

Right, I saw that after I posted -- but couldn't edit my first post.

Do you think this is caused by a change Google made to prevent people from checking indexing?
Why is it happening now when Index check has worked fine with these proxies/settings for many many years?

No I don't think its google trying to prevent index checking. I mean maybe they updated it so it would break any old tool that doesn't get updated, but google changes all sorts of things all the time. I think its just a case of they got around to changing the code of how this works because they thought the new code was better in some way for their users or their purposes and it inadvertently broke the index checking.

Same thing has happened for the entire 7 years Scrapebox has been around, stuff occasionally breaks because things get updated and then scrapebox will just update to compensate. Its the great thing about a tool that actually gets updated.

Update - I did a custom proxy test as you said and it does seem to be working now. I'll wait until I start getting ERROR again and see what I can do about different proxies etc..

Sounds good.

I updated to newest version today and can confirm the issue is fixed.Thank you.

Excellent, glad its working for you.

 

[aF1zhu]

Great Tool, i'm ready purchase it (Y)

 

[blinggam]

Locking the Indexer to 1 thread is/was a horrible idea, not sure why you would do that. I've tried adjusting the settings, doesn't work. Set "min. threads" in the Indexer, doesn't work. It's locked to 1 thread, which is totally unrealistic when checking more than... 10(?) links? I've been using 15 threads on 2.0.0.92 and it's been working fine. Please unlock this setting... Had to roll back to the previous version.

 

[softtouch2009]

Locking the Indexer to 1 thread is/was a horrible idea, not sure why you would do that. I've tried adjusting the settings, doesn't work. Set "min. threads" in the Indexer, doesn't work. It's locked to 1 thread, which is totally unrealistic when checking more than... 10(?) links? I've been using 15 threads on 2.0.0.92 and it's been working fine. Please unlock this setting... Had to roll back to the previous version.

Did you set a delay on the indexer page, or have the number of threads set to 1 in the settings?

 

[blinggam]

Did you set a delay on the indexer page, or have the number of threads set to 1 in the settings?

The delay is on default "1". Didn't change any settings after updating.

The settings page is on 15 threads same as 2.0.0.92. But no matter what it's locked to 1 thread.