Mobile friendly (old, probably outdated)

Warning: This page is pretty old and was imported from another website. Take any content here with a grain of salt.

I’ve been asked about the mobile-friendly tag in search and noticed two common mistakes that I wanted to share. Both of these result in the Mobile-Friendly Test showing that a page isn’t mobile-friendly, but the PageSpeed Insights tool showing that it’s ok:

  1. Too much blocked by robots.txt. Googlebot needs to be able to recognize the mobile-friendliness through crawling. If a JavaScript file that does a redirect is blocked, if a CSS file that’s necessary for the mobile version of the page is blocked, or if you use separate URLs and block those, then Googlebot won’t be able to see your mobile site. The Mobile-Friendly Test will hint at this, the Fetch and Render tool in Webmaster Tools will give you details. The PageSpeed Insights tool doesn’t use the robots.txt, so it may look normal there. Don’t disallow crawling of your site’s CSS or JS files!

  2. Cloaking to Googlebot. Cloaking has been in our Webmaster Guidelines for a long time, it causes all kinds of problems. Some sites try to recognize Googlebot by looking for “Googlebot” in the user-agent, and will then serve it a “Googlebot-version” of the page (which is often the desktop page). If Googlebot-smartphone crawls and sees the desktop page, the page won’t be seen as being mobile-friendly. Fetch and Render in Webmaster Tools can help you recognize this. The PageSpeed Insights tool doesn’t use the Googlebot user-agent. Don’t cloak!

Links for more information:

Original at https://plus.google.com/+JohnMueller/posts/B8gTgQjmrRM (archive.org)

Warning: This page is pretty old and was imported from another website. Take any content here with a grain of salt.

Comments / questions

There's currently no commenting functionality here. If you'd like to comment, please use Twitter and @me there. Thanks!

Tweet about this - and/or - search for latest comments / top comments

Related pages