x

Google indexing disaster

Hi,

Just I have looked at Google search console, and seen that most (33) of pages of my website (www.pearlew.com) can't be indexed because they have two blocked ressources:

 https://www.pearlew.com > /ajax/api/JsonRPC/Commerce/?Commerce[Checkout::getMiniCart

 > https://www.pearlew.com > /ajax/api/JsonRPC/CustomerAccounts/?CustomerAccounts[CustomerAccounts::getAccountDetails]

I can't do anything about these settings, I think it's a problem of Weebly engineering. I hope a solution will be found quickly, then I have lost any of my positions in Google pages.

I have sent an email to french help support.........

What do you think of that?

Thanks a lot for your replies

Eric

5,162 Views
Message 1 of 44
Report
43 REPLIES 43
Square

We deliberately block files in those folders because they are backend scripting resources. All of the pages of your site and the content you add should be indexed, though, unless you chose to block a specific page on the Pages tab. It shouldn't have any impact on the indexing of these pages.

5,028 Views
Message 2 of 44
Report

Hi Adam,

Thank you for your reply.

Just I have reported what Search Console explains me, about settings hindering robots exploration.

I add that I don't understand why such lignes of code, talking of "customers_accounts", or "minicart", describe my pages out of my e-shop....

Best regards

Eric

5,013 Views
Message 2 of 44
Report

163 Pages blocked from index due to this: /ajax/api/JsonRPC/CustomerAccounts/?CustomerAccounts[CustomerAccounts::getAccountDetails]

Who placed that script?

since ajax itself is blocked by robots, anything under its root is blocked. SInce I have /ajax/api/JsonRPC/CustomerAccounts/?CustomerAccounts[CustomerAccounts::getAccountDetails] showing up on many of my pages, naturally they have been blocked because /ajax/ is blocked. 

again, Who placed that script?

4,999 Views
Message 2 of 44
Report
Square

Blocking a subdirectory does not block the parent directory; it would only block further subdirectories. None of the files in that directory are files you would want indexed as they are all scripting resources used by a site.

4,996 Views
Message 2 of 44
Report

Hi,

I have the same problem ( www.smservice.ch ) and it has an impact on google ranking. So it would be nice if you can fix it or give us advice how we can do it.

Thanks for your time and all the best.

4,973 Views
Message 2 of 44
Report

 /ajax/api/JsonRPC/CustomerAccounts/?CustomerAccounts[CustomerAccounts::getAccountDetails]
 
These pages use this blocked resource. If Googlebot can't access important resources on your page, the page might be indexed incorrectly
 
 
Same here what is up...google does not index pages that have blocked resources!
 
4,922 Views
Message 2 of 44
Report

How do we edit the robot.txt file so we can remove the two blocked subdirectories in robot.txt file,ie:
User-agent: *
Disallow: /ajax/
Disallow: /apps/
As this is causing major indexing issues with our site.
This requires URGENT action by the weebly administrators.
From being SERP 2 for major keyword search, we have dropped of the face of the earth impacting business. And google search console has shown us the root cause of the problem of blocked resourse

4,901 Views
Message 2 of 44
Report
Square

Blocking access to those two directories will have zero impact on the indexing and ranking of the rest of your site. Everything in those directories are scripting and backend resources, and not content you would want indexed.

4,886 Views
Message 2 of 44
Report

These ARE impacting Weebly site's search rankings. If we were with WP this would be a 2-second fix/change to allow. If we are unable to do it, can you please log in and change it your end? If you cannot, we have to move to WP. Please advise.

4,870 Views
Message 2 of 44
Report

We are FAR from the only one with this problem:

https://community.weebly.com/t5/SEO/Google-indexing-disaster/td-p/106741

4,131 Views
Message 2 of 44
Report
Square

Unless you are trying to actually rank these scripting resources themselves, it's not going to have any effect on your site.

4,124 Views
Message 2 of 44
Report

OMG so have I. Have had my website since 2000 and have always been  in the top 3 organically, but after I converted to weebly I have been devastated in the rankings. What is being done to fix this?

4,110 Views
Message 2 of 44
Report
Square

Did your URLs change after moving your site, @TBears2000, and if so did you set up any 301 redirects?

4,107 Views
Message 2 of 44
Report

I have exactly the same problem. My "pages indexed" just went from about 45 to 11. The issue according to Google's Search Console appears to be my robots.txt file blocking ajax. Our organic search traffic has dropped off dramatically.

What's going on at Weebly?

Our website is: hairstyles.kimcatalano.com

imageimage

4,051 Views
Message 8 of 44
Report

This script HAS A MAJOR factor on rankings and indexing.

Just had a coversation with a former programmer and seo expert. This is not going to work for Google at all.

Bad resource for SEO and indexing. 

Sorry weebly but needs to be corrected ASAP!

4,047 Views
Message 8 of 44
Report

These pages use this blocked resource. If Googlebot can't access important resources on your page, the page might be indexed incorrectly
4,046 Views
Message 8 of 44
Report
Square

I don't think backend scripts that are purely procedural are going to have any impact on the SEO of your site and content. These scripts are minimized javascript, which is basically gibberish from an SEO perspective.  Also, these scripts contain the same content so if they were not blocked then every single Weebly-built site out there would have some identical content in the eyes of Google.

4,041 Views
Message 8 of 44
Report

You definitely seem to be responding at cross purposes to the people giving you feedback.

These errors ARE showing up in our pages. These are not scripts that we have put in place, they are automatically generated. These ARE being seen and notated as errors with Google. Errors are supposed to negatively effect page placement.

You respond with what you -assume- to be true about what SHOULD be happening with Google. However you've shown no citation or proof that this is the case, and don't seem to have any position that guarantees this.

This is a problem that needs a fix between your backend and googles search indexing tools. There is nothing that we can do about it if you do not solve it other than begin looking for other hosts that don't have this problem.
3,898 Views
Message 8 of 44
Report

I'm having the same problem

so are you telling me that this is a problem caused by weebly and you are not fixing it???

15 pages have been blocked because contain blocked resources and so almost my website has lost indexing in google.

(ajax/api/JsonRPC/CustomerAccounts/?CustomerAccounts[CustomerAccounts::getAccountDetails])


THIS IS A HUGE PROBLEM

how can i solve it??

3,795 Views
Message 8 of 44
Report
Square

Guys, these are not files you would want indexed because 1.) All they are is code, and 2.) it's the same code included with any site. Ignoring that the code is of no indexing value, it would actually do more harm then good if millions of sites suddenly had a whole bunch of identical pages on them.

As far as the impact of blocking pages, blocking one page does not affect the ranking or indexing of an unblocked page. Let me give you an example. I did some Google searches for "cowboy hats lubbock" and "cowboy boots lubbock". This site was the top result for boots and second result for hats:

https://www.bootcity.com

Now take a look at their robots.txt file:

http://www.bootcity.com/robots.txt

They're blocking whole bunch of pages. Are those pages indexed? No, but it had no bearing at all on the rest of their site. Google throws warnings at your because they don't know what your intent is, and depending on how or what you used to build your site, you might actually want something indexed which is being shown as blocked.

Any CMS or site creation tool out there will block backend resources; WordPress does this, Shopify does this, etc.  I can definitely understand that it can come off as alarming when you see that, but I want you to know that there's nothing really wrong here and you don't need to worry.

3,653 Views
Message 8 of 44
Report