- Use cases
- Customer Success
- LOG IN
- Start free trial
The webinar Smart SEO for smartphone browsers is a part of the SEO in Orbit series, and aired on May 29th, 2019. For this episode, Cindy Krum takes us through the differences between mobile and desktop SEO. Where do the differences come from, and what should you as an SEO do about them? We cover topics from Mobile-First Indexing to AMP, and everything in between.
SEO in Orbit is the first webinar series sending SEO into space. Throughout the series, we discussed the present and the future of technical SEO with some of the finest SEO specialists and sent their top tips into space on June 27th, 2019.
Watch the replay here:
Cindy Krum is the CEO and Founder of MobileMoxie, LLC, which provides mobile marketing consultancy as well as offering a custom suite of cutting-edge online mobile marketing and SEO tools. Cindy brings fresh and creative ideas to her clients, providing on-site training and workshops.
Cindy is an active member of the digital marketing & growth communities. She regularly speaks at national and international conferences and has been quoted by many respected publications including PC World, Internet Retailer, TechWorld, Direct Magazine and Search Marketing Standard. She is also the author of Mobile Marketing: Finding Your Customers No Matter Where They Are.
This episode was hosted by Rebecca Berbel, Content Manager at OnCrawl. Fascinated by NLP and machine models of language in particular, and by systems and how they work in general, Rebecca is never at a loss for technical SEO subjects to get excited about. She believes in evangelizing tech and using data to understand website performance on search engines.
Even though a lot of the principles of mobile and desktop SEO are the same, with the mobile-first index, mobile versions become the more important of the two for ranking metrics.
Mobile SEO focuses more on the look and feel of the search engine results page (SERP). Google has always stacked more things at the top of the SERP before the organic results in mobile, because everything that shows up in the right sidebar on desktop searches pushes your results down.
Even though Google limits the ads that appear in mobile search, the non-organic search features taking up a lot of space. This is not new, but it’s getting worse. It’s also something that more people are just now becoming aware of: despite ranking number 1, they show up half-way down the page.
Mobile-First is something that Google started talking about over two years ago. With this change, Google has started crawling and indexing the web as a mobile phone. They do continue to crawl desktop versions and desktop-only content, but they now prefer to crawl and index mobile-oriented or responsive content.
Shortly before this webinar aired, Google announced that, starting in July 2019, mobile-first indexing would be the standard for all new sites.
Accelerated Mobile Pages (AMP) is a special subset of HTML that follows rigid guidelines as to what can and can’t be included in a page.
Google prefers AMP and would love it if the web were AMP-only.
You can implement AMP in different ways:
There are observed difference between mobile and desktop SERPs.
Google states that they are trying to accomodate the searcher’s intent and the needs of the searcher.
Cindy believes that, while Google is focused on the user’s search experience, they use this as a means to coax webmasters into creating content that’s easier to crawl, index, repurpose, reuse, and borrow.
We see Google lifting content from web pages in SERP features like featured snippets and AMP stories, in which they take content and repurpose it for their own needs.
Justifying this with user intent sounds good. However, the things that Google is pushing us to do to rank well in mobile also make their job easier.
Some mobile searches show a fact, with no actual search results, requiring user to click to get to the results if their question isn’t answered by the fact.
Cindy also ties this in to gamification: Google has gamified SEO to a certain extent. We need to remember that the reality is that the house always wins: we’re playing in their playground. Things that help us rank also help Google monetize content in a growing variety of ways.
On mobiles, there’s a broader potential intent because people have their phones with them during more of the day.
Google is trying to figure out how to monetize these types of behaviors and needs–and they’re doing a great job. They’ve broadened the number of ways that they can make money, which is exceptionally prominent on mobile.
Many SEOs don’t look at this closely.
Some of the newer things that just came out of Google I/O are great examples.
[…] And so ultimately, what I’m really trying to say is because Google’s Googlebot actually runs two waves of indexing across web content, it’s possible some details might be missed.”
[Note: This is also evolving. Martin Splitt, in an August 2019 Google Webmaster Hangout, stated: “The two waves of indexing play less and less of a role. I wouldn’t say that two waves of indexing are dead, it’s definitely not. I expect eventually rendering crawling and indexing will come closer together.”]
Google has also launched an indexing API. It’s limited at the moment to things like jobs and live videos. However, Google always starts things like this out small, with a subset of types of content, before generalizing it.
The reason Google might provide an indexing API is to back up the untenable support that they’ve had for PWAs, which has been so hard to index.
Cindy believes that we’ll see a shift towards more PWAs and using the indexing API to make sure they’re taken into account.
Another new feature announced at Google I/O were TWAs, which stands for “Trusted Web Activities”, which Cindy expects will be soon be modified to “Trusted Web App”. These are windows that you can submit to Google Play (and, presumably, eventually to the App Store as well). They are essentially window apps, which as more secure and faster than traditional web views. This allows you to use your TWA to compete against native apps.
This is another example of how what was originally a website can be transformed to compete against native apps, not just in Google rankings, but can also show up in Google Play or in an app pack.
SEOs should stay aware of what’s happening in Google, even if you’re not doing it, or even if it’s not something that technical SEOs and SEOs on stages at conferences are talking about.
“There’s a world outside of our universe. Sometimes that stuff will creep in, and it’s usually being talked about in other groups–with developer groups or at other Google events. It’s just not creeped into the SEO mindset yet.”
Being aware of this sort of thing might let you know that the ground underneath might be shifting. For example, if you have an app that has a lot of web competitors but not a lot of app competitors, changes that allow web competitors to be present in the App Store affect you. You might have brand new competitors outranking you for keywords in the App Store that you never assumed could compete with you.
This can happen very quickly. The way Google talks about these new technologies suggest that their implementation is very fast: your website can become a PWA in a day or two; they demoed getting a TWA set up on stage in five minutes.
Mobile SEO is something you should always want to concentrate on.
You may have an increased need for mobile SEO in the following situations:
All markets have a need for SEO, but some markets’ needs are greater:
In entertainment, the mobile is the new everything: you use it to look for shows, music, podcasts… The phone has become the entertainment device, going beyond just replacing the old TV guide.
These platforms are examples of a place where voice search is increasingly prominent, for example to find media available through cable providers, Hulu or Netflix.
This is very similar to how cell phones our need to memorize phone numbers: we no longer know anyone’s phone number. The same is true of TV channels, for example: you no longer need to know the channel number of CNN to watch it. Google hosts all of this information that you no longer need to store in your brain.
Google says the official way to tell if you’ve been switched to mobile-first indexing is with the notification in Google Search Console, which doesn’t specify the date of the change. OnCrawl has seen that these notifications can be sent up to three weeks after the fact, based on log data of Googlebot visits.
Cindy notes that you can also use the URL inspection tool to see which bot was the last to crawl and index your pages.
[Note: Since late June 2019, Google Search Console also contains indicators of the primary crawler used on your site.]
You’ll find two new indicators in several reports:
1- Primary crawler used for specific reports 🎊
2- Chart annotation showing when your site was switched to mobile-first indexing 🎊
— Google Webmasters (@googlewmc) June 26, 2019
Google talks openly about mobile-first indexing and the smartphone bot being used as the primary crawler.
One thing they haven’t been as open about is the fact that the smartphone bot has been the primary crawler since about 2014; based on what we’ve been told, it just hasn’t been used as much for indexing.
Cindy’s worry is that websites that haven’t gotten the official notification yet might have less ability to rank in certain ways in both mobile and desktop search results. Usually, though, even these websites are already being crawled regularly by the smartphone bot.
If you’re being crawled by the smartphone bot but haven’t yet received the notification that you’ve been moved to mobile-first indexing, the most likely risk is that you have more difficulty getting your website into what Cindy calls “hosted inclusions” or rich results.
These include clusters of content on the SERPs:
Cindy’s experience leads her to believe that mobile-first indexing allows sites to obtain more featured snippets and more potential indexing of individual aspects of elements within a page. (This is what she has termed “fraggles” from “fragment” + “handle”.)
Fraggles are evidence that Google seems to index not only pages, but parts of pages. You can see the effects of this in features such as:
This is a much more sophisticated form of indexing, which Cindy believes is included as part of Google’s mobile-first indexing, as opposed to traditional indexing methods.
While you don’t need to have a mobile version of your site to move to mobile-first indexing, Google’s mobile bot might struggle with sites that are neither mobile nor responsive. This could, in turn, impact your rankings.
A mobile-friendly site should at least meet Google’s guidelines for mobile websites.
Many of these points are UX- or crawl-related. This includes things like:
In addition to Google’s guidelines, Cindy encourages people to embrace the infotainment use cases in order to address a mobile audience. Examples might include using the type of content throughout your site:
This idea is reinforced by how Google has been pushing podcasts. Previously, just the podcast title and description were available. Now, thanks to their live transcription feature, Google has text that can be indexed and used as fraggles. This has a lot of potential for use as audio answers, particularly on devices with speakers or that might be used to play podcasts, like phones.
This can provide more qualitative answers: most people would much rather hear podcast excerpts featuring a real voice with depth and emotion than listen to a robot voice read them text from a website.
If you have two different versions of your site for mobile and desktop, Google recommends that you make sure the following elements are coherent between the two versions:
There’s a lot of debate around whether or not it’s worthwhile to adopt AMP for your website. While Cindy sees both sides of the debate, she’s theoretically in favor of AMP: a faster web with stronger standards are positive points for her.
Additionally, if you’re playing the game to rank in Google, it’s worth noting that Google seems to prefer to rank things that it hosts, like AMP. If Google wants AMP, and we want to rank, we should consider doing AMP.
AMP is also expanding, It’s now a default aspect of many PWA talks in order to make PWAs even faster. It has also crept into email.
In general, AMP reflects a worthwhile effort by Google: they want the web to be faster and to work with less data exchange.
This is also a big part of PWAs: not having to go get everything from a server around the world all the time.
Google-hosting for AMP is fast, free and local.
When Cindy first heard that AMP caching was going straight to the Google crowd, she wondered why webmasters wouldn’t want to abuse the fact that Google was essentially offering a free CDN. When she spoke to John Mueller in Zurich about this, and he said that you could go ahead and do this sort of thing; Google might eventually figure out how to block this sort of use, but might also not bother.
This changed Cindy’s perspective on AMP: profiting from the free CDN usage inherent in AMP is not actually abuse to Google. Google wants to host your content. This makes it easier for Google to know a lot more about your content and its performance:
Cindy has already made bold claims about how mobile-first indexing is entity-first indexing.
When mobile-first indexing was first announced, topics like AMP and deep-linking were a big deal. Google has backed off on this and is pushing PWAs instead: AMP and deep-linking were too hard a lot of companies and PWAs are much easier.
If you look at how Google Play is organized, you can see entity-indexing at play. Google Play is organized by media:
This already shows a semantic understanding of what a content is and where it’s appropriate. Cindy expects that with PWAs, they’ll add a category for web content. If you search for an entity, such as Katy Perry, you get a result composed of different elements: picture, info, albums, songs, videos… It’s a beautiful and super interactive knowledge graph result.
A lot of the theme at Google I/O this year was how Google wants to bring more interactivity to search results. If Cindy were Google, she would move in this direction by moving web results into Google Play, where entity-indexing is already in place. In Google Play, relationships are mapped very clearly, but there isn’t as much spam, 404s, or garbage content. This would make it possible to impose stronger standards with mobile indexing for what constitutes quality content, and then to add it to a cleaner, entity-based, interactive index.
Though Cindy has been talking about this idea for nearly two years, it hasn’t happened yet–but she sees evidence that we’re moving in that direction.
Cindy is extremely interested in Google’s ability to “piecemeal” a page and remix it using AI.
AMP stories are one of the most evident examples of this new kind of content. In an AMP story, Google takes pictures and snippets of text from AMP pages and creates a slideshow (previously a video). It superimposes textual facts and pictures that might come from different AMP articles to create an engaging experience.
This used to be limited to celebrity bios, but the protocol has been opened up to anyone who wants to rank AMP stories. This will be a new SERP feature: “see stories on this topic”.
Another example are Google interviews and podcasts, which are often presented throughout the text, sliced and diced and remixed.
Whether this ability to lift and remix content is AI, or AI with a human assistance, Cindy finds the idea exciting. However, it has the potential to exclude webmasters: it’s a sign of Google’s intention to rival companies like Hulu, Netflix and cable companies as a short-form content creator. There’s a lot of money to be made with proprietary content.
The lack of attribution on new, remixed content is disappointing, but the capability to create this sort of content is still exciting.
Whenever something is new, there’s a shortage of it–but Google wants to show it off. As SEOs, adopting new features means that it ranks really well. Early adopters see huge benefits in doing things that Google announces at events like Google I/O.
This technique is not always fool-proof; you can get burned. There can be major issues with authorship and content attribution.
It’s not a matter of jumping on bandwagons: if no one else is doing it yet, you’re the one setting the pace. Being a super early adopter has benefits above and beyond adopting something when it becomes a best practice.
The image Googlebot is an interesting Googlebot in part because of the long-standing mixing of image content and shopping content, which has gotten more attention recently.
Cindy recently noticed that if you’re looking at image results and you click “change language”, it takes you to a landing pages with a list of languages. This language choice page was created for Google Products. What does this include? Shopping? Images, which is where she started the query?
This shows there’s some mixing across types of results.
Google has been using image learning and image AI for a long time. For example, if, in Google Shopping, you search for something such as “blue dress”, you can click on an item to get a carousel of related items. They’re not related by price or by manufacturer; they’re actually visually related. What Cindy found is that if the original picture is a model wearing a dress, all of the related items contain a model wearing a dress; if the original picture is a mannequin wearing a dress, all of the related items contain a mannequin.
For another example, when Google first launched support for Product Schema, you could click on an image in Google Image Search and Google would display the information like size, color, etc. drawn from the Schema.org markup as part of the image information. Now, however, they just show the image tag. This is evidence that Google is able to index images along with Schema, or at least to be aware that images might be associated with product schema.
To improve visibility and gain featured snippets for recipe blogs.
At this year’s Google I/O, there was discussion about a new use of hi-resolution images during the Developer Keynote. They suggested that high-resolution images will start ranking with a full-width image, not just a thumbnail placed off to the side.
If you want to “be the first on that boat,” there is special markup you need to use to indicate the high resolution images. The advantage is that many recipe sites already have high resolution images.
“Early-adopters rank well if there is no one else on the bandwagon because Google wants to show off new features.”
If you missed our voyage to space on June 27th, catch it here and discover all of the tips we sent into space.