New google mobile-algorithm

Permalink 1 user found helpful
Google is changing his search algorithm on 21. April. Not mobile friendly sites will experience a loss in search rank. If you try to run this test from google on your c5 website, it will fail, altough you got a mobile friendly site:https://www.google.com/webmasters/tools/mobile-friendly/....
This is a huge problem!

The problem is the c5 generated robots.txt file. There is a disallow for the /themes folder. If you got your css files in there, the algorithm fails! So remove this in your robots.txt file:
(Disallow: /application/themes).

Can anyone tell me how to adress this issue on github? Cannot find the file where the robots.txt is generated. Thank you

micrdy
View Replies:
mesuva replied on at Permalink Reply
mesuva
I'm pretty sure 5.6.3.3 will update the robots.txt file on upgrade (nice work hissy), but if you just want to quickly update the robots.txt file you can manually edit it on your server.

Just replace it with the latest version from github:
https://raw.githubusercontent.com/concrete5/concrete5/master/web/rob...

I've done this on quite a few sites already and it solves the issue of Google not being able to access the resources it needs to evaluate it to be 'mobile friendly'.
micrdy replied on at Permalink Reply
micrdy
Yeah I have done this already. In 5.7 there is no robots.txt file on github. Is it generated elsewhere?
mesuva replied on at Permalink Reply
mesuva
https://raw.githubusercontent.com/concrete5/concrete5-5.7.0/develop/web/robots.txt
micrdy replied on at Permalink Reply
micrdy
Hell! Did not saw this yesterday. Thanks man
Chrouglas replied on at Permalink Reply
I tried this on a 5.6.3.2 site and ran the test... still got the dreaded 'your S#it don't fly' from google. I even tried uploading a blank robots.txt and that didn't resolve the issue. Any ideas? Could it be a caching thing? Do i need to reindex with google?
micrdy replied on at Permalink Reply
micrdy
Is google still complaining about your robots.txt?
It´s most likely not a caching problem.