Understanding Mobile First Indexing

Understanding Mobile First Indexing

Mobile first indexing

Last year Google announced the rollout of their Mobile First Indexing initiative, or MFI for short. Although it was long anticipated and a hot topic in the SEO community, a year later it is still a subject shrouded in mystery to the average site owner. We’ll break it down for you and take the mystery out.

What is Mobile First Indexing?

In a nutshell, MFI is Google’s response to the ever-increasing number of mobile users. As you may know, in 2016 the number of web visits by mobile device users worldwide surpassed the number of those on laptops and desktops.

Until now, Google typically indexed the desktop version of sites, and based page rank on those. However, when content on the mobile version of the site varied from that of the desktop, mobile users suffered. What they found on the site was not what they saw in the search results.

One factor which fueled this problem was the fact that, despite all the evidence to the contrary, many site owners and even developers think of mobile usage as secondary. Many sites do not offer the same content to mobile users, often out of a well-meaning but erroneous attempt to simplify the mobile user experience. Additionally, media such as video or animation used on a site’s desktop version is often incompatible with mobile devices. To make matters worse, many site owners and developers felt for various reasons that mobile was unimportant, or less important than their “real” site.

So Google decided to start indexing and ranking any mobile version of pages it finds, in preference to the desktop version. Read that sentence again, it’s the simple answer behind all the confusion and misconceptions.

Subway commuters using mobile devices

Mobile device users have taken the lead, and they’re showing no sign of slowing down. In fact, they’re gaining momentum. Recent studies show that not only are there more mobile device users these days, but that average mobile device users are spending more and more time on the internet.

How Will I Know When Mobile First Indexing is Enabled for My Site?

You will receive a notification via the Google Search console:

Notification

Image source: Google

How Will Mobile First Indexing Affect My Site?

This is the question everyone is asking these days. Unfortunately, there is no simple answer. Don’t take that to mean the answer is unknown, just that the answer may be a little complicated. It mostly depends on the current condition of your site.

In general, the advice of the day is, “Don’t panic!” Google understands the impact something like this could have, so they are bringing it in slowly and carefully. Google states that, “We evaluate each site individually on its readiness for mobile-first indexing based on the best practices and transition the site when the site is ready.” Breathe, sit back, and we’ll walk you through it.

First off, Google will only index mobile versions of pages when they deem they are mobile-friendly. Until then, they will index the desktop version. Below is an example of a site which is not optimized for mobile, compared to one that is optimized.

For more information on mobile-friendly design, see this article by Google.

Google also provides this handy tool to quickly test how a page scores for mobile-friendliness:  Mobile-Friendly Test

The main determining factor in assessing MFI’s impact on a given site is your strategy for desktop vs mobile sites. Coming out on top with MFI comes down to these three things: Quality of content, user experience and performance. Sounds familiar, right? It should, it’s really the same old game. The only difference is that Google will now be indexing and ranking any mobile version of your pages in preference to the desktop version.

What that means is that if you are delivering exactly the same content in a way that is just as easy to use on any device, with similar load speeds on all devices, nothing will likely change for you. Pat yourself on the back and go watch a movie!

If, however, you are serving different or less content to your mobile visitors, or the interface is clumsy, your rankings will likely suffer to some degree. Likewise if you are sending your mobile visitors the same gigantic images you send to desktop users with giant peripheral monitors.

Remember not to panic. Google uses hundreds of complex “signals,” each with a set of “sub-signals,” to determine page rank. Google has stated repeatedly that this will not cause your page rank to come crashing down overnight. As they state in this Google Webmaster’s Blog entry:

“Sites that are not in this initial wave don’t need to panic. Mobile-first indexing is about how we gather content, not about how content is ranked. Content gathered by mobile-first indexing has no ranking advantage over mobile content that’s not yet gathered this way or desktop content. Moreover, if you only have desktop content, you will continue to be represented in our index.”

However, that doesn’t mean we can ignore this important change. If your site needs help, the sooner you do something about it the better.

Strategies for Delivering Content to Desktop and Mobile Devices

The internet was born in an age when users accessed it on machines that weighed over twenty pounds and were cabled to the wall. Users were stuck at desks in mazes of cubicles, websites were chiseled in stone, and all was dark.

More than two decades of this led to the concept of websites as we have known them, and it’s a difficult paradigm to break from. However, the rapid advancement of mobile devices, along with the users themselves, requires us all to re-think and adapt our concepts of websites, visitors, and how they interact.

Whether you manufacture semiconductors, sell ice cream, or offer junk-hauling services, your customers are looking for you on both desktop and mobile. It is imperative to have a strategy that can deliver quality content with good user experience on any device your customers may use.
Image of man using laptop and phone

Statistics show that 70% of high school graduates and over 90% of college graduates in the U.S. own a smart phone. Despite the rise in popularity of smart phones, ownership and usage of desktop and laptop computers has remained steady for a decade at roughly 75%. Demographically, laptop and desktop ownership rises with education and income.

Currently, the three top strategies for achieving this are responsive design, dynamic serving (aka dynamic rendering), and separate URLs. From the Google Developers Guide:

Responsive web design: Serves the same HTML code on the same URL regardless of the users’ device (desktop, tablet, mobile, non-visual browser), but can render the display differently (i.e., “respond”) based on the screen size. Responsive design is Google’s recommended design pattern.

Image source: Google

Dynamic serving: Uses the same URL regardless of device, but generates a different version of HTML for different device types based on what the server knows about the user’s browser.

Image depicting dynamic serving

Image source: Google

Separate URLs: Serves different code to each device, and on separate URLs. This configuration tries to detect the users’ device, then redirects to the appropriate page using HTTP redirects along with the Vary HTTP header.

Image depicting separate URLs

Image source: Google

So what does all that boil down to?

As Google states here and elsewhere, “Sites that make use of responsive web design and correctly implement dynamic serving (that include all of the desktop content and markup) generally don’t have to do anything.”

Note that nobody is saying you have absolutely nothing to worry about, every article on the subject throws in that “generally” clause. That’s simply because the sheer number of possible scenarios is beyond imagination, so somebody out there might need to worry.

For more information, see this article on Google Search.

Common Misconceptions

A quick look through the forums reveals a flood of panicked questions regarding Mobile First Indexing. While we can’t cover them all, here are a few of the big ones we noticed.

Are there two indexes now, one for mobile and one for desktop?

No. Google is selecting pages that are mobile-friendly in preference to any other versions, and indexing those in their single index. If you doubt our word, Danny Sullivan (@searchliason) of Google stated most emphatically in this amusing tweet that there is only one index.

He also offers us a useful analogy: “Think of it like a library that can have one copy of every book. Initially, it was all print books. As ebooks became popular, it starts to replace the print versions with ebooks. Still one library, mix of both types but over time, it’ll be mostly ebooks.”

Does Mobile First Indexing mean that mobile-friendly sites get ranked above all others?

No. Google is only changing what they index, not how pages are ranked. If a mobile friendly version of your page is available, Google will index that, otherwise they will index the desktop version. Google will then rank your page according to whichever version they indexed.

My site uses separate URLs for desktop and mobile, like example.com and m.example.com. Will Mobile First Indexing cause all visitors to get the mobile URLs?

No. Google will index the mobile version, and show content snippets from that. The URLs will still be correct for the device.

Conclusion

The best approach to surviving Mobile First Indexing is to focus on quality of content, user experience and performance. Make sure your site is just as accessible to users on smartphones and small tablets as it is to desktop and large-tablet users. Give them all the same content presented in the same order. Make sure the site is easy to use on all device sizes, and optimize page load times for all.

 

 

Get a plan in place

Our Approach Is Different

  • We listen
  • Work together
  • Measure success

We know how you feel, so let’s talk


iCita plan step one 1
Schedule a call
Step 2 of a plan
Create a plan
Step 3 of the plan
Move forward

Want to know more about us?

15 + 8 =

Copyright © 2022 iCita LLC. All rights reserved.
Sitemap

Twitter leading the charge with new Progressive Web App

Twitter leading the charge with new Progressive Web App

In later 2018, Twitter made a bold move. Twitter replaced it much neglected Windows native app with a progressive web app version. They are not the first app to leverage progressive web apps in the Windows store, but they are one of the first to have a public announcement.

Twitter announced last May at Google I/O it was launching Twitter Lite, a Progressive Web App (PWA) version of the twitter client. The new interface is faster, uses less data, and already powers some Twitter apps.

At the conference they also shared some statistics from their initial trials:

  • 65% increase in pages per session
  • 75% increase in Tweets sent
  • 20% decrease in bounce rate

These increased engagements numbers are not unusual. When you make an intentional effort to deliver a better user experience your customers they respond by giving you more attention.

>> Read more in this similar post.

The Growth of Progressive Web Applications – PWA

The Growth of Progressive Web Applications – PWA

Progressive Web App – What?

If we combine the best of the web and the best of mobile apps—it will be Progressive Web Apps or PWA. Progressive web apps are websites that look and feel like an app, load quicker, and are easier to develop. This means users can access all information and capabilities without downloading a mobile app.  It starts as a normal web page in a browser, and as a user explores the web page, they get the prompt if they would like to “Add to Home Screen”. Once the user gives the thumbs up to this prompt, VOILA! The PWA gets added to their home screen just like an app. Once open from the home screen, it can even hide the browser UI controls and appear as an app.

PWAs have managed to bridge the gap in the web between the web and mobile apps much more than a .bookmark would.  More than 40% of the users bounce from the websites that take more than three seconds to load. PWA is a solution for this “Web Speed Epidemic” faced by many companies. 

Why is this it important?

It is a myth that the users will happily download the app of every website they visit frequently. The Mobile App Report by Comscore shows that over 50% of America’s smart phone users download zero apps a month. Yes, that’s correct, gone are the days when the phone is full of apps and people-smart phone honeymoon phase is getting depleted. Additional, there is a drop of off 20% of users with each step it takes to step to download an app. Progressive Web Apps reduce the steps between discovery of an app and getting it on the home screen and thereby eliminates friction of getting an app installed. This provides a very fertile ground for businesses to pitch in their PWA.

PWA helps to improve conversions by increasing potential reach with low acquisition costs.  For example:

Increasing Reach: Comscore reports the reach of mobile web is 2.5 times more than that of mobile apps (while considering the top 1000 sites and apps). This is the reason why many corporate plans to abandon their website for an “app only” model has backfired. Now, if companies can start to provide a better experience to a wider audience, they could surely get a competitive edge over the others.

Higher Acquisition: Another serious concern faced by the mobile apps are their user discoverability compared to websites. The user acquisition cost of web will be 10 times cheaper than that of native apps. With more exposure and low friction for on-boarding, PWA is likely to acquire more users at very less expense.

Higher Conversion Rates: The end user experience increases greatly with PWA because it improves the number of successful conversions. Many apps report delivering an increase in the conversion rate of near 70% with lower acquisition cost.

Case Studies:

Trivago: An increase of over 150% for Trivago’s PWA for people who added it to their home screen. This increased engagement led to a 97% increase for hotel offer clickouts. Now, users who go offline (while they are browsing), can continue to access the site and of these users, 67% continue to browse even when they come back online.
>> More

Uber: The PWA Uber designed was directed to their 2G users. Their core app is so small is is only 50k gzipped and loads in 3 seconds on 2G networks.
>> More

Pinterest: Recently Pinterest rebuild their whole mobile site as a PWA. This increased core engagements by 60%, and an increase of 44% in user-generated ad revenue. Time spend on the site has increased by over 40%.
>> More

Forbes: The magazine recently developed a Progressive Web App to improve its mobile web user experience. The Progressive Web App increased load times and doubled engagement rates through the use of push notifications and an option to add the Progressive Web App to home screens.

  • 43% increase in sessions per user
  • 20% increase in impressions per page
  • 100% increase in engagement rates
  • 6x increase in the number of readers completing articles

>> More

Web Developers – How to test a new website before you launch it.

Web Developers – How to test a new website before you launch it.

1. Live URLs

Often, sites are built at a URL (uniform resource locator) that isn’t the website’s final destination. When a site goes live, the URLs are transferred from a staging area to production. All the URLs change at this time, and they need to be tested.

On small sites without any tools, you can navigate to each page to make sure they all work. On a site with fewer than 500 URLs, you can use Screaming Frog SEO Spider Tool for free to find bad URLs. For larger sites, there is a modest annual fee.

2. Sign up to Google Search Console

Google Search Console (previously Webmaster Tools) is an invaluable tool for all webmasters. This is where Google will communicate with you should anything go wrong (crawling errors, manual penalties, increase in 404 pages, malware detected, etc.)

Search Console is also where you can monitor your site’s performance, identify issues, submit content for crawling, remove content you don’t want indexed, view the search queries that brought visitors to your site, monitor backlinks.

You should also sign up to Bing Webmaster Tools.

3. Minify

This is a technique that combines and compresses website code into smaller chunks to speed up your site. You can read more about it at Google. Then, look at the website pre-launch to see if the site is using minify where it can.

4. 404 pages

When a 404 (“page not found”) error occurs, make sure you have a custom page to help your visitor find something else of use, even if it wasn’t what they were looking for. Do you have an HTML sitemap there? Does the 404 page include a site search?

5. Favicon

Favicons are those little iconic images that show up in the address bar and tabs of your browser. How does it help? It’s a small branding opportunity that lends credibility to your site. It’s nice to have one when you launch.

A part of the article posted on ClickZ here.