{"id":796,"date":"2017-12-20T08:00:36","date_gmt":"2017-12-19T23:00:36","guid":{"rendered":"https:\/\/websavii.com\/?p=796"},"modified":"2017-11-09T12:30:19","modified_gmt":"2017-11-09T03:30:19","slug":"google-mobile-seo","status":"publish","type":"post","link":"https:\/\/websavii.com\/google-mobile-seo\/","title":{"rendered":"Google Mobile SEO: 4 Basic Optimisations for 2017"},"content":{"rendered":"

Mobile smartphones are revolutionising society. Nowadays, wherever you go, you always see people are browsing, looking for interesting items or reading an article through their smartphones. Today, it is a medium of constant communication for their loved ones and the most used tool in search of answers for extensive information through the internet. According to the data below, mobile smartphones surpassed the usage of the Personal Computer (PC), and it\u2019s becoming an essential tool in reaching your potential online customers, readers, and buyers.<\/span>\r\n\r\n\r\n\"mobile-stats-vs-desktop-users-global-550x405\"\r\n\r\n<\/b>\r\n<\/p>\r\n\r\n

4 reasons why your website needs to have a mobile optimised page<\/h4>\r\n \r\n
    \r\n \t
  1. Difficulty in viewing a desktop version on a mobile version device. <\/span><\/li>\r\n \t
  2. Fonts and text are too small for your eye.<\/span><\/li>\r\n \t
  3. Zoom and pinch frustration are likely to abandon the site.<\/span><\/li>\r\n \t
  4. You\u2019re losing tons of potential readers and customers online.<\/span><\/li>\r\n<\/ol>\r\n \r\n<\/b><\/span>\r\n

    Mobile SEO Configuration Introduction<\/h2>\r\n \r\n

    There are a few things you need to bear in mind before configuring mobile for SEO. The first thing you need to do is to make sure that it shows up on the different mobile search engines. You should get similar results to what you\u2019re searching for in Google desktop search to Google mobile search results. Then, the second thing is you need to correctly configure your site so that it will run on multiple devices.<\/span><\/p>\r\n \r\n

    4 Basic Mobile SEO Configurations<\/h3>\r\n

    1. Responsive Web Design<\/h4>\r\n

    This is the preferable method to implement for your mobile website. The responsive web design (RWD) is very simple; the server sends the same HTML code to all devices, and the CSS is used to alter the process to fit and adjust on every device. \u00a0It\u2019s easier to link and share your content with just a single URL. \u00a0The Google algorithms or Googlebot should be able to detect the RWD setup and crawl every page including CSS, Javascript, and images.<\/span>\r\n\r\n\r\nTag this code after your website header (<head>) code<\/span>\r\n\r\n\r\n<meta name=”viewport” content=”width=device-width, initial-scale=1.0″><\/span>\r\n\r\n\r\n\"responsive-website-design\"<\/p>\r\n

    Via Web Media Maker<\/span><\/p>\r\nTo learn more about RWD set-up, Pete LePage discusses it further <\/span>here<\/span><\/a>.<\/span>\r\n\r\n \r\n

    2.\u00a0Dynamic Serving<\/h4>\r\n

    \r\nDynamic serving serves two different HTML and CSS codes with the same URL to fit or adjust depending on the user-agent page request on each device. A server hint sends a request that Googlebot for mobile phones is seeking to crawl and to discover the mobile content through an implementation of \u201c<\/span>Vary HTTP header<\/b>\u201d code.<\/span>\r\n\r\n\r\n\"vary-http-code\"\r\n\r\n<\/b><\/p>\r\n\r\n

    Detecting User-agents Setup<\/h5>\r\n

    \r\n\r\n\r\nThere are times that the Googlebot detects a desktop user-agent as a mobile user-agent or vice-versa. It\u2019s a common mismatch where Googlebot treated tablet devices as smartphones without any intention. This is why you need to add a specific mobile \u201c<\/span>user-agent string<\/b>\u201d in your header. <\/span>\r\n\r\n\"user-agent\"<\/p>\r\n

    Via Webmaster Central<\/span><\/p>\r\n\r\nHere\u2019s a huge list of specific <\/span>user-agent strings<\/span><\/a>.<\/span>\r\n\r\n\r\n\"dynamic-serving\"\r\n\r\n \r\n

    3. Separate URLs<\/b><\/h4>\r\n \r\n

    This configuration has an equally different URL serving for desktop, mobile optimised URL or even for tablets. Google algorithms do not favor any usage of URL formats as long as they are all accessible by Googlebot user-agent. These are the most common configuration for pages like www.yourdomain.com \u00a0for desktop and m.yourdomain.com for mobile. The hint signal serves as \u201c<\/span>Annotations<\/b>\u201d to Googlebot which would indicate that the website is using a separate URL type of mobile optimise page configuration. <\/span>\r\n\r\n\r\n\"annotations\"<\/p>\r\n

    Via Google Developer<\/span><\/p>\r\n\r\n\r\n<\/b>\r\n

    4. Tablet and Other Devices<\/h4>\r\n

    \r\n\r\n\r\nGoogle does not have any specific hint signals for tablet optimised websites. But, Google recommends separating tablet-dedicated URLs and use of rel=\u201dcanonical tags on each page equivalent to desktop URLs. Google also recommends to include <link rel=”alternate” media=”handheld”> tags for feature phones. <\/span>\r\n\r\n\r\nIf you\u2019re using WordPress CMS, you can easily download <\/span>handheld plugins<\/span><\/a>.<\/span>\r\n\r\n\r\n<\/b><\/p>\r\n\r\n

    4 Common Mistakes for Beginners to Avoid<\/h3>\r\n \r\n
      \r\n \t
    1. Neglecting your mobile customers<\/span><\/li>\r\n \t
    2. Creating different domains for mobile<\/span><\/li>\r\n \t
    3. Sticking to old-school website development<\/span><\/li>\r\n \t
    4. Unplayable videos or broken images <\/span><\/li>\r\n<\/ol>\r\n \r\n

      Website Content will load faster using AMP<\/h2>\r\n\"google-amp\"\r\n

      Via resultfirst.com<\/span><\/p>\r\n

      Accelerated mobile pages (AMP) can dramatically improve the performance and speed of the site content. It allows the user to instantly read interesting content without any additional hindrance like pop-up screens, pop-up scripts and ads that would cause the content to load slowly. <\/span>\r\n\r\n\r\nGoogle tends to provide good keyword rankings when you apply AMP on your website content. On the contrary, implementing AMP is only good for most sites that have lots of published article blog posts and news content. If you have an existing mobile optimised page but do not have a huge frequency of published content, there\u2019s no need for you to change to an AMP entirely.<\/span>\r\n\r\n\r\nAMP is equal to a normal HTML code format but there are a few additional changes on the HTML elements for AMP implementation e.g. <img> to <amp-img>. \u00a0It can work on both Mobile optimise pages and non-optimise mobile pages. To learn more, visit <\/span>AMP project<\/span><\/a> for the HTML recommended formats. <\/span>\r\n\r\n\r\n<\/p>\r\n\r\n

      Recommendations<\/h2>\r\n

      \r\n\r\nWe recommend testing each of your website\u2019s mobile compatibility using <\/span>Mobile-Friendly Test<\/span><\/a> and <\/span>PageSpeed Insights<\/span><\/a> (mobile and desktop version). Simply follow the recommended instructions provided to your website\u2019s results to improve performance and speed. We also recommend that you read our <\/span>onpage SEO<\/span><\/a> strategy for proper onsite optimisation setup. <\/span>\r\n\r\n\r\nTo start with, if you\u2019re having difficulties on choosing what mobile strategy your website needs, just fill out the form and we will let you know.<\/span>\r\n\r\n\r\n<\/p>\r\n

      <\/div>
      \r\n\r\n\r\n\r\n\r\n
      \r\n