SmartphoneNot long ago Google announced its upcoming mobile-friendly algorithm change, but the search engine is making efforts to help webmasters prepare as well as possible. Google has been offering a steady stream of information helping webmasters avoid common mistakes while converting websites to mobile-friendly designs.

After answering questions over Twitter, Google also decided to directly ask webmasters what they were confused about and what problems they were encountering. Then, Google compiled the most common mistakes and shared them in a simple and easy to explore list.

According to Google, the most commonly mentioned mobile mistakes are:

  • Blocked JavaScript, CSS and image files: In order for Googlebot to see your site as a real user would, always allow access to these files in your site’s robots.txt.
  • Unplayable content: This consists of certain types of videos, or other content, that are not playable on mobile devices, such as license-constrained media or media that requires Flash.
  • Faulty redirects: If you have separate mobile URLs, you must redirect mobile users on each desktop URL to the appropriate mobile URL.
  • Mobile-only 404s: Some sites serve content to desktop users accessing a URL but show an error page to mobile users. Instead, redirect mobile users to an equivalent mobile page to avoid 404s.
  • App download interstitials: This is when websites block the view of pages with a prompt to download the site’s native app. Instead, use a small HTML banner at the top of the page.
  • Irrelevant cross-links: This is when users are linked to desktop-optimized pages from the mobile version of the site, and vice versa. Check your links to make sure that they point to the correct equivalent page.
  • Slow mobile pages: In order to avoid user frustration, ensure your mobile pages load quickly. You can check your page speed with Google PageSpeed Insights.

You can learn more from the complete guide here.

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply