"““““““““““““““ Posted by Suzzicks What are “fraggles” in SEO and how do they relate to mobile-first..."

“““““““““““““““

Posted by Suzzicks

What are “fraggles” in SEO and how do they relate to mobile-first indexing, entities, the Knowledge Graph, and your day-to-day work? In this glimpse into her 2019 MozCon talk, Cindy Krum explains everything you need to understand about fraggles in this edition of Whiteboard Friday.

Click on the whiteboard image above to open a high resolution version in a new tab!

Video Transcription

Hi, Moz fans. My name is Cindy Krum, and I’m the CEO of MobileMoxie, based in Denver, Colorado. We do mobile SEO and ASO consulting. I’m here in Seattle, speaking at MozCon, but also recording this Whiteboard Friday for you today, and we are talking about fraggles.

So fraggles are obviously a name that I’m borrowing from Jim Henson, who created “Fraggle Rock.” But it’s a combination of words. It’s a combination of fragment and handle. I talk about fraggles as a new way or a new element or thing that Google is indexing.

Fraggles and mobile-first indexing

Let’s start with the idea of mobile-first indexing, because you have to kind of understand that before you can go on to understand fraggles. So I believe mobile-first indexing is about a little bit more than what Google says. Google says that mobile-first indexing was just a change of the crawler.

They had a desktop crawler that was primarily crawling and indexing, and now they have a mobile crawler that’s doing the heavy lifting for crawling and indexing. While I think that’s true, I think there’s more going on behind the scenes that they’re not talking about, and we’ve seen a lot of evidence of this. So what I believe is that mobile-first indexing was also about indexing, hence the name.

Knowledge Graph and entities

So I think that Google has reorganized their index around entities or around specifically entities in the Knowledge Graph. So this is kind of my rough diagram of a very simplified Knowledge Graph. But Knowledge Graph is all about person, place, thing, or idea.

Nouns are entities. Knowledge Graph has nodes for all of the major person, place, thing, or idea entities out there. But it also indexes or it also organizes the relationships of this idea to this idea or this thing to this thing. What’s useful for that to Google is that these things, these concepts, these relationships stay true in all languages, and that’s how entities work, because entities happen before keywords.

This can be a hard concept for SEOs to wrap their brain around because we’re so used to dealing with keywords. But if you think about an entity as something that’s described by a keyword and can be language agnostic, that’s how Google thinks about entities, because entities in the Knowledge Graph are not written up per se or their the unique identifier isn’t a word, it’s a number and numbers are language agnostic.

But if we think about an entity like mother, mother is a concept that exists in all languages, but we have different words to describe it. But regardless of what language you’re speaking, mother is related to father, is related to daughter, is related to grandfather, all in the same ways, even if we’re speaking different languages. So if Google can use what they call the “topic layer"and entities as a way to filter in information and understand the world, then they can do it in languages where they’re strong and say, “We know that this is true absolutely 100% all of the time.”

Then they can apply that understanding to languages that they have a harder time indexing or understanding, they’re just not as strong or the algorithm isn’t built to understand things like complexities of language, like German where they make really long words or other languages where they have lots of short words to mean different things or to modify different words.

Languages all work differently. But if they can use their translation API and their natural language APIs to build out the Knowledge Graph in places where they’re strong, then they can use it with machine learning to also build it and do a better job of answering questions in places or languages where they’re weak. So when you understand that, then it’s easy to think about mobile-first indexing as a massive Knowledge Graph build-out.

We’ve seen this happening statistically. There are more Knowledge Graph results and more other things that seem to be related to Knowledge Graph results, like people also ask, people also search for, related searches. Those are all describing different elements or different nodes on the Knowledge Graph. So when you see those things in the search, I want you to think, hey, this is the Knowledge Graph showing me how this topic is related to other topics.

So when Google launched mobile-first indexing, I think this is the reason it took two and a half years is because they were reindexing the entire web and organizing it around the Knowledge Graph. If you think back to the AMA that John Mueller did right about the time that Knowledge Graph was launching, he answered a lot of questions that were about JavaScript and href lang.

When you put this in that context, it makes more sense. He wants the entity understanding, or he knows that the entity understanding is really important, so the href lang is also really important. So that’s enough of that. Now let’s talk about fraggles.

Fraggles = fragment + handle

So fraggles, as I said, are a fragment plus a handle. It’s important to know that fraggles — let me go over here —fraggles and fragments, there are lots of things out there that have fragments. So you can think of native apps, databases, websites, podcasts, and videos. Those can all be fragmented.

Even though they don’t have a URL, they might be useful content, because Google says its goal is to organize the world’s information, not to organize the world’s websites. I think that, historically, Google has kind of been locked into this crawling and indexing of websites and that that’s bothered it, that it wants to be able to show other stuff, but it couldn’t do that because they all needed URLs.

But with fragments, potentially they don’t have to have a URL. So keep these things in mind — apps, databases and stuff like that — and then look at this. 

So this is a traditional page. If you think about a page, Google has kind of been forced, historically by their infrastructure, to surface pages and to rank pages. But pages sometimes struggle to rank if they have too many topics on them.

So for instance, what I’ve shown you here is a page about vegetables. This page may be the best page about vegetables, and it may have the best information about lettuce, celery, and radishes. But because it’s got those topics and maybe more topics on it, they all kind of dilute each other, and this great page may struggle to rank because it’s not focused on the one topic, on one thing at a time.

Google wants to rank the best things. But historically they’ve kind of pushed us to put the best things on one page at a time and to break them out. So what that’s created is this “content is king, I need more content, build more pages” mentality in SEO. The problem is everyone can be building more and more pages for every keyword that they want to rank for or every keyword group that they want to rank for, but only one is going to rank number one.

Google still has to crawl all of those pages that it told us to build, and that creates this character over here, I think, Marjory the Trash Heap, which if you remember the Fraggles, Marjory the Trash Heap was the all-knowing oracle. But when we’re all creating kind of low- to mid-quality content just to have a separate page for every topic, then that makes Google’s life harder, and that of course makes our life harder.

So why are we doing all of this work? The answer is because Google can only index pages, and if the page is too long or too many topics, Google gets confused. So we’ve been enabling Google to do this. But let’s pretend, go with me on this, because this is a theory, I can’t prove it. But if Google didn’t have to index a full page or wasn’t locked into that and could just index a piece of a page, then that makes it easier for Google to understand the relationships of different topics to one page, but also to organize the bits of the page to different pieces of the Knowledge Graph.

So this page about vegetables could be indexed and organized under the vegetable node of the Knowledge Graph. But that doesn’t mean that the lettuce part of the page couldn’t be indexed separately under the lettuce portion of the Knowledge Graph and so on, celery to celery and radish to radish. Now I know this is novel, and it’s hard to think about if you’ve been doing SEO for a long time.

But let’s think about why Google would want to do this. Google has been moving towards all of these new kinds of search experiences where we have voice search, we have the Google Home Hub kind of situation with a screen, or we have mobile searches. If you think about what Google has been doing, we’ve seen the increase in people also ask, and we’ve seen the increase in featured snippets.

They’ve actually been kind of, sort of making fragments for a long time or indexing fragments and showing them in featured snippets. The difference between that and fraggles is that when you click through on a fraggle, when it ranks in a search result, Google scrolls to that portion of the page automatically. That’s the handle portion.

So handles you may have heard of before. They’re kind of old-school web building. We call them bookmarks, anchor links, anchor jump links, stuff like that. It’s when it automatically scrolls to the right portion of the page. But what we’ve seen with fraggles is Google is lifting bits of text, and when you click on it, they’re scrolling directly to that piece of text on a page.

So we see this already happening in some results. What’s interesting is Google is overlaying the link. You don’t have to program the jump link in there. Google actually finds it and puts it there for you. So Google is already doing this, especially with AMP featured snippets. If you have a AMP featured snippet, so a featured snippet that’s lifted from an AMP page, when you click through, Google is actually scrolling and highlighting the featured snippet so that you could read it in context on the page.

But it’s also happening in other kind of more nuanced situations, especially with forums and conversations where they can pick a best answer. The difference between a fraggle and something like a jump link is that Google is overlaying the scrolling portion. The difference between a fraggle and a site link is site links link to other pages, and fraggles, they’re linking to multiple pieces of the same long page.

So we want to avoid continuing to build up low-quality or mid-quality pages that might go to Marjory the Trash Heap. We want to start thinking in terms of can Google find and identify the right portion of the page about a specific topic, and are these topics related enough that they’ll be understood when indexing them towards the Knowledge Graph.

Knowledge Graph build-out into different areas

So I personally think that we’re seeing the build-out of the Knowledge Graph in a lot of different things. I think featured snippets are kind of facts or ideas that are looking for a home or validation in the Knowledge Graph. People also ask seem to be the related nodes. People also search for, same thing. Related searches, same thing. Featured snippets, oh, they’re on there twice, two featured snippets. Found on the web, which is another way where Google is putting expanders by topic and then giving you a carousel of featured snippets to click through on.



 So we’re seeing all of those things, and some SEOs are getting kind of upset that Google is lifting so much content and putting it in the search results and that you’re not getting the click. We know that 61% of mobile searches don’t get a click anymore, and it’s because people are finding the information that they want directly in a SERP.

That’s tough for SEOs, but great for Google because it means Google is providing exactly what the user wants. So they’re probably going to continue to do this. I think that SEOs are going to change their minds and they’re going to want to be in those windowed content, in the lifted content, because when Google starts doing this kind of thing for the native apps, databases, and other content, websites, podcasts, stuff like that, then those are new competitors that you didn’t have to deal with when it was only websites ranking, but those are going to be more engaging kinds of content that Google will be showing or lifting and showing in a SERP even if they don’t have to have URLs, because Google can just window them and show them.

So you’d rather be lifted than not shown at all. So that’s it for me and featured snippets. I’d love to answer your questions in the comments, and thanks very much. I hope you like the theory about fraggles.

Video transcription by Speechpad.com

Sign up for The Moz Top 10, a semimonthly mailer updating you on the top ten hottest pieces of SEO news, tips, and rad links uncovered by the Moz team. Think of it as your exclusive digest of stuff you don’t have time to hunt down but want to read!

”

- http://monleyhomes.blogspot.com/2019/11/all-about-fraggles-fragment-handle.html
from Tumblr https://monleyhomes.tumblr.com/post/189369227690”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in.html
from Tumblr https://monleyhomes.tumblr.com/post/189371382055”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_29.html
from Tumblr https://monleyhomes.tumblr.com/post/189374049645”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_75.html
from Tumblr https://monleyhomes.tumblr.com/post/189376746610”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_0.html
from Tumblr https://monleyhomes.tumblr.com/post/189379758940”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_13.html
from Tumblr https://monleyhomes.tumblr.com/post/189382404905”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_63.html
from Tumblr https://monleyhomes.tumblr.com/post/189385024150”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_49.html
from Tumblr https://monleyhomes.tumblr.com/post/189387205555”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_30.html
from Tumblr https://monleyhomes.tumblr.com/post/189388855605”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_64.html
from Tumblr https://monleyhomes.tumblr.com/post/189391171225”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_95.html
from Tumblr https://monleyhomes.tumblr.com/post/189394125430”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_73.html
from Tumblr https://monleyhomes.tumblr.com/post/189396930775”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_69.html
from Tumblr https://monleyhomes.tumblr.com/post/189400073365”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_14.html
from Tumblr https://monleyhomes.tumblr.com/post/189402741820”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_67.html
from Tumblr https://monleyhomes.tumblr.com/post/189405432750

"Posted by Joel.Mesherghi For some organizations, mobile apps can be an important means to capturing..."

“““““““““““““““““““““““““““““““““““““““““““““““

Posted by Joel.Mesherghi

For some organizations, mobile apps can be an important means to capturing new leads and customers, so it can be alarming when you notice your app visits are declining.

However, while there is content on how to optimize your app, otherwise known as ASO (App Store Optimization), there is little information out there on the steps required to diagnose a drop in app visits.

Although there are overlaps with traditional search, there are unique factors that play a role in app store visibility.

The aim of this blog is to give you a solid foundation when trying to investigate a drop in app store visits and then we’ll go through some quick fire opportunities to win that traffic back.

We’ll go through the process of investigating why your app traffic declined, including:

1. Identifying potential external factors
2. Identifying the type of keywords that dropped in visits
3. Analyzing app user engagement metrics

And we’ll go through some ways to help you win traffic back including:

1. Spying on your competitors
2. Optimizing your store listing
3. Investing in localisation

Investigating why your app traffic declined

Step 1. Identify potential external factors

Some industries/businesses will have certain periods of the year where traffic may drop due to external factors, such as seasonality.

Before you begin investigating a traffic drop further:

• Talk to your point of contact and ask whether seasonality impacts their business, or whether there are general industry trends at play. For example, aggregator sites like SkyScanner may see a drop in app visits after the busy period at the start of the year.
• Identify whether app installs actually dropped. If they didn’t, then you probably don’t need to worry about a drop in traffic too much and it could be Google’s and Apple’s algorithms better aligning the intent of search terms.

Step 2. Identify the type of keywords that dropped in visits

Like traditional search, identifying the type of keywords (branded and non-branded), as well as the individual keywords that saw the biggest drop in app store visits, will provide much needed context and help shape the direction of your investigation. For instance:

If branded terms saw the biggest drop-off in visits this could suggest:

1. There has been a decrease in the amount of advertising spend that builds brand/product awareness
2. Competitors are bidding on your branded terms
3. The app name/brand has changed and hasn’t been able to mop up all previous branded traffic

If non-branded terms saw the biggest drop off in visits this could suggest:

1. You’ve made recent optimisation changes that have had a negative impact
2. User engagement signals, such as app crashes, or app reviews have changed for the worse
3. Your competition have better optimised their app and/or provide a better user experience (particularly relevant if an app receives a majority of its traffic from a small set of keywords)
4. Your app has been hit by an algorithm update

If both branded and non-branded terms saw the biggest drop off in visits this could suggest:

1. You’ve violated Google’s policies on promoting your app.
2. There are external factors at play

To get data for your Android app

To get data for your Android app, sign into your Google Play Console account.

Google Play Console provides a wealth of data on the performance of your android app, with particularly useful insights on user engagement metrics that influence app store ranking (more on these later).

However, keyword specific data will be limited. Google Play Console will show you the individual keywords that delivered the most downloads for your app, but the majority of keyword visits will likely be unclassified: mid to long-tail keywords that generate downloads, but don’t generate enough downloads to appear as isolated keywords. These keywords will be classified as “other”.

Your chart might look like the below. Repeat the same process for branded terms.

Above: Graph of a client’s non-branded Google Play Store app visits. The number of visits are factual, but the keywords driving visits have been changed to keep anonymity.

To get data for your IOS app

To get data on the performance of your IOS app, Apple have App Store Connect. Like Google Play Console, you’ll be able to get your hands on user engagement metrics that can influence the ranking of your app.

However, keyword data is even scarcer than Google Play Console. You’ll only be able to see the total number of impressions your app’s icon has received on the App Store. If you’ve seen a drop in visits for both your Android and IOS app, then you could use Google Play Console data as a proxy for keyword performance.

If you use an app rank tracking tool, such as TheTool, you can somewhat plug gaps in knowledge for the keywords that are potentially driving visits to your app.

Step 3. Analyze app user engagement metrics

User engagement metrics that underpin a good user experience have a strong influence on how your app ranks and both Apple and Google are open about this.

Google states that user engagement metrics like app crashes, ANR rates (application not responding) and poor reviews can limit exposure opportunities on Google Play.

While Apple isn’t quite as forthcoming as Google when it comes to providing information on engagement metrics, they do state that app ratings and reviews can influence app store visibility.

Ultimately, Apple wants to ensure IOS apps provide a good user experience, so it’s likely they use a range of additional user engagement metrics to rank an app in the App Store.

As part of your investigation, you should look into how the below user engagement metrics may have changed around the time period you saw a drop in visits to your app.

• App rating
• Number of ratings (newer/fresh ratings will be weighted more for Google)
• Number of downloads
• Installs vs uninstalls
• App crashes and application not responding

You’ll be able to get data for the above metrics in Google Play Console and App Store Connect, or you may have access to this data internally.

Even if your analysis doesn’t reveal insights, metrics like app rating influences conversion and where your app ranks in the app pack SERP feature, so it’s well worth investing time in developing a strategy to improve these metrics.

One simple tactic could be to ensure you respond to negative reviews and reviews with questions. In fact, users increase their rating by +0.7 stars on average after receiving a reply.

Apple offers a few tips on asking for ratings and reviews for IOS app.

Help win your app traffic back

Step 1. Spy on your competitors

Find out who’s ranking

When trying to identify opportunities to improve app store visibility, I always like to compare the top 5 ranking competitor apps for some priority non-branded keywords.

All you need to do is search for these keywords in Google Play and the App Store and grab the publicly available ranking factors from each app listing. You should have something like the below.

Brand	Title	Title Character length	Rating	Number of reviews	Number of installs	Description character length
COMPETITOR 1	[Competitor title]	50	4.8	2,848	50,000+	3,953
COMPETITOR 2	[Competitor title]	28	4.0	3,080	500,000+	2,441
COMPETITOR 3	[Competitor title]	16	4.0	2566	100,000+	2,059
YOUR BRAND	​[Your brands title]	37	4.3	2,367	100,000+	3,951
COMPETITOR 4	[Competitor title]	7	4.1	1,140	100,000+	1,142
COMPETITOR 5	[Competitor title]	24	4.5	567	50,000+	2,647

     Above: anonymized table of a client’s Google Play competitors

From this, you may get some indications as to why an app ranks above you. For instance, we see “Competitor 1” not only has the best app rating, but has the longest title and description. Perhaps they better optimized their title and description?

We can also see that competitors that rank above us generally have a larger number of total reviews and installs, which aligns with both Google’s and Apple’s statements about the importance of user engagement metrics.

With the above comparison information, you can dig a little deeper, which leads us on nicely to the next section.

Optimize your app text fields

Keywords you add to text fields can have a significant impact on app store discoverability.

As part of your analysis, you should look into how your keyword optimization differs from competitors and identify any opportunities.

For Google Play, adding keywords to the below text fields can influence rankings:

• Keywords in the app title (50 characters)
• Keywords in the app description (4,000 characters)
• Keywords in short description (80 characters)
• Keywords in URL
• Keywords in your app name

When it comes to the App Store, adding keywords to the below text fields can influence rankings:

• Keywords in the app title (30 characters)
• Using the 100 character keywords field (a dedicated 100-character field to place keywords you want to rank for)
• Keywords in your app name

To better understand how your optimisation tactics hold up, I recommended comparing your app text fields to competitors.

For example, if I want to know the frequency of mentioned keywords in their app descriptions on Google Play (keywords in the description field are a ranking factor) than I’d create a table like the one below.

Keyword	COMPETITOR 1	COMPETITOR 2	COMPETITOR 3	YOUR BRAND	COMPETITOR 4	COMPETITOR 5
job	32	9	5	40	3	2
job search	12	4	10	9	10	8
employment	2	0	0	5	0	3
job tracking	2	0	0	4	0	0
employment app	7	2	0	4	2	1
employment search	4	1	1	5	0	0
job tracker	3	0	0	1	0	0
recruiter	2	0	0	1	0	0

     Above: anonymized table of a client’s Google Play competitors

From the above table, I can see that the number 1 ranking competitor (competitor 1) has more mentions of “job search” and “employment app” than I do.

Whilst there are many factors that decide the position at which an app ranks, I could deduce that I need to increase the frequency of said keywords in my Google Play app description to help improve ranking.

Be careful though: writing unnatural, keyword stuffed descriptions and titles will likely have an adverse effect.

Remember, as well as being optimized for machines, text fields like your app title and description are meant to be a compelling “advertisement” of your app for users..

I’d repeat this process for other text fields to uncover other keyword insights.

Step 2. Optimize your store listing

Your store listing in the home of your app on Google Play. It’s where users can learn about your app, read reviews and more. And surprisingly, not all apps take full advantage of developing an immersive store listing experience.

Whilst Google doesn’t seem to directly state that fully utilizing the majority of store listing features directly impacts your apps discoverability, it’s fair to speculate that there may be some ranking consideration behind this.

At the very least, investing in your store listing could improve conversion and you can even run A/B tests to measure the impact of your changes.

You can improve the overall user experience and content found in the store listing by adding video trailers of your app, quality creative assets, your apps icon (you’ll want to make your icon stand out amongst a sea of other app icons) and more.

You can read Google’s best practice guide on creating a compelling Google Play store listing to learn more.

Step 3. Invest in localization

The saying goes “think global, act local” and this is certainly true of apps.

Previous studies have revealed that 72.4% of global consumers preferred to use their native language when shopping online and that 56.2% of consumers said that the ability to obtain information in their own language is more important than price.

It makes logical sense. The better you can personalize your product for your audience, the better your results will be, so go the extra mile and localize your Google Play and App Store listings.

Google has a handy checklist for localization on Google Play and Apple has a comprehensive resource on internationalizing your app on the App Store.

Wrap up

A drop in visits of any kind causes alarm and panic. Hopefully this blog gives you a good starting point if you ever need to investigate why an apps traffic has dropped as well as providing some quick fire opportunities to win it back.

If you’re interested in further reading on ASO, I recommend reading App Radar’s and TheTool’s guides to ASO, as well as app search discoverability tips from Google and Apple themselves.

Sign up for The Moz Top 10, a semimonthly mailer updating you on the top ten hottest pieces of SEO news, tips, and rad links uncovered by the Moz team. Think of it as your exclusive digest of stuff you don’t have time to hunt down but want to read!

”

- http://monleyhomes.blogspot.com/2019/11/app-store-seo-how-to-diagnose-drop-in.html
from Tumblr https://monleyhomes.tumblr.com/post/189288975260”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some.html
from Tumblr https://monleyhomes.tumblr.com/post/189291367820”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_25.html
from Tumblr https://monleyhomes.tumblr.com/post/189294231850”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_69.html
from Tumblr https://monleyhomes.tumblr.com/post/189297252915”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_24.html
from Tumblr https://monleyhomes.tumblr.com/post/189300328090”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_83.html
from Tumblr https://monleyhomes.tumblr.com/post/189303133745”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_14.html
from Tumblr https://monleyhomes.tumblr.com/post/189305828455”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_78.html
from Tumblr https://monleyhomes.tumblr.com/post/189307629490”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_26.html
from Tumblr https://monleyhomes.tumblr.com/post/189309367610”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_88.html
from Tumblr https://monleyhomes.tumblr.com/post/189311771435”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_70.html
from Tumblr https://monleyhomes.tumblr.com/post/189314797415”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_74.html
from Tumblr https://monleyhomes.tumblr.com/post/189317785280”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_54.html
from Tumblr https://monleyhomes.tumblr.com/post/189320765410”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_75.html
from Tumblr https://monleyhomes.tumblr.com/post/189323541010”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_80.html
from Tumblr https://monleyhomes.tumblr.com/post/189326104760”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_99.html
from Tumblr https://monleyhomes.tumblr.com/post/189327913635”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_27.html
from Tumblr https://monleyhomes.tumblr.com/post/189329540700”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_65.html
from Tumblr https://monleyhomes.tumblr.com/post/189331822370”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_28.html
from Tumblr https://monleyhomes.tumblr.com/post/189334778995”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_93.html
from Tumblr https://monleyhomes.tumblr.com/post/189337695855”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_58.html
from Tumblr https://monleyhomes.tumblr.com/post/189340639535”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_56.html
from Tumblr https://monleyhomes.tumblr.com/post/189343259745”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_21.html
from Tumblr https://monleyhomes.tumblr.com/post/189345854330”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_33.html
from Tumblr https://monleyhomes.tumblr.com/post/189347838410”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_92.html
from Tumblr https://monleyhomes.tumblr.com/post/189349381760”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_38.html
from Tumblr https://monleyhomes.tumblr.com/post/189351656220”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_16.html
from Tumblr https://monleyhomes.tumblr.com/post/189354630595”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_52.html
from Tumblr https://monleyhomes.tumblr.com/post/189357529125”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_29.html
from Tumblr https://monleyhomes.tumblr.com/post/189360437080”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_12.html
from Tumblr https://monleyhomes.tumblr.com/post/189362995060”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_34.html
from Tumblr https://monleyhomes.tumblr.com/post/189365572115”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_35.html
from Tumblr https://monleyhomes.tumblr.com/post/189367483055”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_7.html
from Tumblr https://monleyhomes.tumblr.com/post/189369227750”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_6.html
from Tumblr https://monleyhomes.tumblr.com/post/189371382205”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_55.html
from Tumblr https://monleyhomes.tumblr.com/post/189374049755”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_39.html
from Tumblr https://monleyhomes.tumblr.com/post/189376746760”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_48.html
from Tumblr https://monleyhomes.tumblr.com/post/189379758800”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_91.html
from Tumblr https://monleyhomes.tumblr.com/post/189382404800”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_20.html
from Tumblr https://monleyhomes.tumblr.com/post/189385023990”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_9.html
from Tumblr https://monleyhomes.tumblr.com/post/189387205500”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_30.html
from Tumblr https://monleyhomes.tumblr.com/post/189388855535”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_0.html
from Tumblr https://monleyhomes.tumblr.com/post/189391171160”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_89.html
from Tumblr https://monleyhomes.tumblr.com/post/189394125180”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_46.html
from Tumblr https://monleyhomes.tumblr.com/post/189396930660”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_11.html
from Tumblr https://monleyhomes.tumblr.com/post/189400073105”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_18.html
from Tumblr https://monleyhomes.tumblr.com/post/189402741700”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_31.html
from Tumblr https://monleyhomes.tumblr.com/post/189405432665

"Posted by Suzzicks What are “fraggles” in SEO and how do they relate to mobile-first indexing,..."

““““““““““““““

Posted by Suzzicks

What are “fraggles” in SEO and how do they relate to mobile-first indexing, entities, the Knowledge Graph, and your day-to-day work? In this glimpse into her 2019 MozCon talk, Cindy Krum explains everything you need to understand about fraggles in this edition of Whiteboard Friday.

Click on the whiteboard image above to open a high resolution version in a new tab!

Video Transcription

Hi, Moz fans. My name is Cindy Krum, and I’m the CEO of MobileMoxie, based in Denver, Colorado. We do mobile SEO and ASO consulting. I’m here in Seattle, speaking at MozCon, but also recording this Whiteboard Friday for you today, and we are talking about fraggles.

So fraggles are obviously a name that I’m borrowing from Jim Henson, who created “Fraggle Rock.” But it’s a combination of words. It’s a combination of fragment and handle. I talk about fraggles as a new way or a new element or thing that Google is indexing.

Fraggles and mobile-first indexing

Let’s start with the idea of mobile-first indexing, because you have to kind of understand that before you can go on to understand fraggles. So I believe mobile-first indexing is about a little bit more than what Google says. Google says that mobile-first indexing was just a change of the crawler.

They had a desktop crawler that was primarily crawling and indexing, and now they have a mobile crawler that’s doing the heavy lifting for crawling and indexing. While I think that’s true, I think there’s more going on behind the scenes that they’re not talking about, and we’ve seen a lot of evidence of this. So what I believe is that mobile-first indexing was also about indexing, hence the name.

Knowledge Graph and entities

So I think that Google has reorganized their index around entities or around specifically entities in the Knowledge Graph. So this is kind of my rough diagram of a very simplified Knowledge Graph. But Knowledge Graph is all about person, place, thing, or idea.

Nouns are entities. Knowledge Graph has nodes for all of the major person, place, thing, or idea entities out there. But it also indexes or it also organizes the relationships of this idea to this idea or this thing to this thing. What’s useful for that to Google is that these things, these concepts, these relationships stay true in all languages, and that’s how entities work, because entities happen before keywords.

This can be a hard concept for SEOs to wrap their brain around because we’re so used to dealing with keywords. But if you think about an entity as something that’s described by a keyword and can be language agnostic, that’s how Google thinks about entities, because entities in the Knowledge Graph are not written up per se or their the unique identifier isn’t a word, it’s a number and numbers are language agnostic.

But if we think about an entity like mother, mother is a concept that exists in all languages, but we have different words to describe it. But regardless of what language you’re speaking, mother is related to father, is related to daughter, is related to grandfather, all in the same ways, even if we’re speaking different languages. So if Google can use what they call the “topic layer"and entities as a way to filter in information and understand the world, then they can do it in languages where they’re strong and say, “We know that this is true absolutely 100% all of the time.”

Then they can apply that understanding to languages that they have a harder time indexing or understanding, they’re just not as strong or the algorithm isn’t built to understand things like complexities of language, like German where they make really long words or other languages where they have lots of short words to mean different things or to modify different words.

Languages all work differently. But if they can use their translation API and their natural language APIs to build out the Knowledge Graph in places where they’re strong, then they can use it with machine learning to also build it and do a better job of answering questions in places or languages where they’re weak. So when you understand that, then it’s easy to think about mobile-first indexing as a massive Knowledge Graph build-out.

We’ve seen this happening statistically. There are more Knowledge Graph results and more other things that seem to be related to Knowledge Graph results, like people also ask, people also search for, related searches. Those are all describing different elements or different nodes on the Knowledge Graph. So when you see those things in the search, I want you to think, hey, this is the Knowledge Graph showing me how this topic is related to other topics.

So when Google launched mobile-first indexing, I think this is the reason it took two and a half years is because they were reindexing the entire web and organizing it around the Knowledge Graph. If you think back to the AMA that John Mueller did right about the time that Knowledge Graph was launching, he answered a lot of questions that were about JavaScript and href lang.

When you put this in that context, it makes more sense. He wants the entity understanding, or he knows that the entity understanding is really important, so the href lang is also really important. So that’s enough of that. Now let’s talk about fraggles.

Fraggles = fragment + handle

So fraggles, as I said, are a fragment plus a handle. It’s important to know that fraggles — let me go over here —fraggles and fragments, there are lots of things out there that have fragments. So you can think of native apps, databases, websites, podcasts, and videos. Those can all be fragmented.

Even though they don’t have a URL, they might be useful content, because Google says its goal is to organize the world’s information, not to organize the world’s websites. I think that, historically, Google has kind of been locked into this crawling and indexing of websites and that that’s bothered it, that it wants to be able to show other stuff, but it couldn’t do that because they all needed URLs.

But with fragments, potentially they don’t have to have a URL. So keep these things in mind — apps, databases and stuff like that — and then look at this. 

So this is a traditional page. If you think about a page, Google has kind of been forced, historically by their infrastructure, to surface pages and to rank pages. But pages sometimes struggle to rank if they have too many topics on them.

So for instance, what I’ve shown you here is a page about vegetables. This page may be the best page about vegetables, and it may have the best information about lettuce, celery, and radishes. But because it’s got those topics and maybe more topics on it, they all kind of dilute each other, and this great page may struggle to rank because it’s not focused on the one topic, on one thing at a time.

Google wants to rank the best things. But historically they’ve kind of pushed us to put the best things on one page at a time and to break them out. So what that’s created is this “content is king, I need more content, build more pages” mentality in SEO. The problem is everyone can be building more and more pages for every keyword that they want to rank for or every keyword group that they want to rank for, but only one is going to rank number one.

Google still has to crawl all of those pages that it told us to build, and that creates this character over here, I think, Marjory the Trash Heap, which if you remember the Fraggles, Marjory the Trash Heap was the all-knowing oracle. But when we’re all creating kind of low- to mid-quality content just to have a separate page for every topic, then that makes Google’s life harder, and that of course makes our life harder.

So why are we doing all of this work? The answer is because Google can only index pages, and if the page is too long or too many topics, Google gets confused. So we’ve been enabling Google to do this. But let’s pretend, go with me on this, because this is a theory, I can’t prove it. But if Google didn’t have to index a full page or wasn’t locked into that and could just index a piece of a page, then that makes it easier for Google to understand the relationships of different topics to one page, but also to organize the bits of the page to different pieces of the Knowledge Graph.

So this page about vegetables could be indexed and organized under the vegetable node of the Knowledge Graph. But that doesn’t mean that the lettuce part of the page couldn’t be indexed separately under the lettuce portion of the Knowledge Graph and so on, celery to celery and radish to radish. Now I know this is novel, and it’s hard to think about if you’ve been doing SEO for a long time.

But let’s think about why Google would want to do this. Google has been moving towards all of these new kinds of search experiences where we have voice search, we have the Google Home Hub kind of situation with a screen, or we have mobile searches. If you think about what Google has been doing, we’ve seen the increase in people also ask, and we’ve seen the increase in featured snippets.

They’ve actually been kind of, sort of making fragments for a long time or indexing fragments and showing them in featured snippets. The difference between that and fraggles is that when you click through on a fraggle, when it ranks in a search result, Google scrolls to that portion of the page automatically. That’s the handle portion.

So handles you may have heard of before. They’re kind of old-school web building. We call them bookmarks, anchor links, anchor jump links, stuff like that. It’s when it automatically scrolls to the right portion of the page. But what we’ve seen with fraggles is Google is lifting bits of text, and when you click on it, they’re scrolling directly to that piece of text on a page.

So we see this already happening in some results. What’s interesting is Google is overlaying the link. You don’t have to program the jump link in there. Google actually finds it and puts it there for you. So Google is already doing this, especially with AMP featured snippets. If you have a AMP featured snippet, so a featured snippet that’s lifted from an AMP page, when you click through, Google is actually scrolling and highlighting the featured snippet so that you could read it in context on the page.

But it’s also happening in other kind of more nuanced situations, especially with forums and conversations where they can pick a best answer. The difference between a fraggle and something like a jump link is that Google is overlaying the scrolling portion. The difference between a fraggle and a site link is site links link to other pages, and fraggles, they’re linking to multiple pieces of the same long page.

So we want to avoid continuing to build up low-quality or mid-quality pages that might go to Marjory the Trash Heap. We want to start thinking in terms of can Google find and identify the right portion of the page about a specific topic, and are these topics related enough that they’ll be understood when indexing them towards the Knowledge Graph.

Knowledge Graph build-out into different areas

So I personally think that we’re seeing the build-out of the Knowledge Graph in a lot of different things. I think featured snippets are kind of facts or ideas that are looking for a home or validation in the Knowledge Graph. People also ask seem to be the related nodes. People also search for, same thing. Related searches, same thing. Featured snippets, oh, they’re on there twice, two featured snippets. Found on the web, which is another way where Google is putting expanders by topic and then giving you a carousel of featured snippets to click through on.



 So we’re seeing all of those things, and some SEOs are getting kind of upset that Google is lifting so much content and putting it in the search results and that you’re not getting the click. We know that 61% of mobile searches don’t get a click anymore, and it’s because people are finding the information that they want directly in a SERP.

That’s tough for SEOs, but great for Google because it means Google is providing exactly what the user wants. So they’re probably going to continue to do this. I think that SEOs are going to change their minds and they’re going to want to be in those windowed content, in the lifted content, because when Google starts doing this kind of thing for the native apps, databases, and other content, websites, podcasts, stuff like that, then those are new competitors that you didn’t have to deal with when it was only websites ranking, but those are going to be more engaging kinds of content that Google will be showing or lifting and showing in a SERP even if they don’t have to have URLs, because Google can just window them and show them.

So you’d rather be lifted than not shown at all. So that’s it for me and featured snippets. I’d love to answer your questions in the comments, and thanks very much. I hope you like the theory about fraggles.

Video transcription by Speechpad.com

Sign up for The Moz Top 10, a semimonthly mailer updating you on the top ten hottest pieces of SEO news, tips, and rad links uncovered by the Moz team. Think of it as your exclusive digest of stuff you don’t have time to hunt down but want to read!

”

- http://monleyhomes.blogspot.com/2019/11/all-about-fraggles-fragment-handle.html
from Tumblr https://monleyhomes.tumblr.com/post/189369227690”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in.html
from Tumblr https://monleyhomes.tumblr.com/post/189371382055”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_29.html
from Tumblr https://monleyhomes.tumblr.com/post/189374049645”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_75.html
from Tumblr https://monleyhomes.tumblr.com/post/189376746610”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_0.html
from Tumblr https://monleyhomes.tumblr.com/post/189379758940”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_13.html
from Tumblr https://monleyhomes.tumblr.com/post/189382404905”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_63.html
from Tumblr https://monleyhomes.tumblr.com/post/189385024150”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_49.html
from Tumblr https://monleyhomes.tumblr.com/post/189387205555”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_30.html
from Tumblr https://monleyhomes.tumblr.com/post/189388855605”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_64.html
from Tumblr https://monleyhomes.tumblr.com/post/189391171225”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_95.html
from Tumblr https://monleyhomes.tumblr.com/post/189394125430”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_73.html
from Tumblr https://monleyhomes.tumblr.com/post/189396930775”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_69.html
from Tumblr https://monleyhomes.tumblr.com/post/189400073365”

- http://monleyhomes.blogspot.com/2019/11/posted-by-suzzicks-what-are-fraggles-in_14.html
from Tumblr https://monleyhomes.tumblr.com/post/189402741820

"“““““““““““““““““““““““““““““““““““““““““““““ Posted by Joel.Mesherghi For some organizations,..."

““““““““““““““““““““““““““““““““““““““““““““““

Posted by Joel.Mesherghi

For some organizations, mobile apps can be an important means to capturing new leads and customers, so it can be alarming when you notice your app visits are declining.

However, while there is content on how to optimize your app, otherwise known as ASO (App Store Optimization), there is little information out there on the steps required to diagnose a drop in app visits.

Although there are overlaps with traditional search, there are unique factors that play a role in app store visibility.

The aim of this blog is to give you a solid foundation when trying to investigate a drop in app store visits and then we’ll go through some quick fire opportunities to win that traffic back.

We’ll go through the process of investigating why your app traffic declined, including:

1. Identifying potential external factors
2. Identifying the type of keywords that dropped in visits
3. Analyzing app user engagement metrics

And we’ll go through some ways to help you win traffic back including:

1. Spying on your competitors
2. Optimizing your store listing
3. Investing in localisation

Investigating why your app traffic declined

Step 1. Identify potential external factors

Some industries/businesses will have certain periods of the year where traffic may drop due to external factors, such as seasonality.

Before you begin investigating a traffic drop further:

• Talk to your point of contact and ask whether seasonality impacts their business, or whether there are general industry trends at play. For example, aggregator sites like SkyScanner may see a drop in app visits after the busy period at the start of the year.
• Identify whether app installs actually dropped. If they didn’t, then you probably don’t need to worry about a drop in traffic too much and it could be Google’s and Apple’s algorithms better aligning the intent of search terms.

Step 2. Identify the type of keywords that dropped in visits

Like traditional search, identifying the type of keywords (branded and non-branded), as well as the individual keywords that saw the biggest drop in app store visits, will provide much needed context and help shape the direction of your investigation. For instance:

If branded terms saw the biggest drop-off in visits this could suggest:

1. There has been a decrease in the amount of advertising spend that builds brand/product awareness
2. Competitors are bidding on your branded terms
3. The app name/brand has changed and hasn’t been able to mop up all previous branded traffic

If non-branded terms saw the biggest drop off in visits this could suggest:

1. You’ve made recent optimisation changes that have had a negative impact
2. User engagement signals, such as app crashes, or app reviews have changed for the worse
3. Your competition have better optimised their app and/or provide a better user experience (particularly relevant if an app receives a majority of its traffic from a small set of keywords)
4. Your app has been hit by an algorithm update

If both branded and non-branded terms saw the biggest drop off in visits this could suggest:

1. You’ve violated Google’s policies on promoting your app.
2. There are external factors at play

To get data for your Android app

To get data for your Android app, sign into your Google Play Console account.

Google Play Console provides a wealth of data on the performance of your android app, with particularly useful insights on user engagement metrics that influence app store ranking (more on these later).

However, keyword specific data will be limited. Google Play Console will show you the individual keywords that delivered the most downloads for your app, but the majority of keyword visits will likely be unclassified: mid to long-tail keywords that generate downloads, but don’t generate enough downloads to appear as isolated keywords. These keywords will be classified as “other”.

Your chart might look like the below. Repeat the same process for branded terms.

Above: Graph of a client’s non-branded Google Play Store app visits. The number of visits are factual, but the keywords driving visits have been changed to keep anonymity.

To get data for your IOS app

To get data on the performance of your IOS app, Apple have App Store Connect. Like Google Play Console, you’ll be able to get your hands on user engagement metrics that can influence the ranking of your app.

However, keyword data is even scarcer than Google Play Console. You’ll only be able to see the total number of impressions your app’s icon has received on the App Store. If you’ve seen a drop in visits for both your Android and IOS app, then you could use Google Play Console data as a proxy for keyword performance.

If you use an app rank tracking tool, such as TheTool, you can somewhat plug gaps in knowledge for the keywords that are potentially driving visits to your app.

Step 3. Analyze app user engagement metrics

User engagement metrics that underpin a good user experience have a strong influence on how your app ranks and both Apple and Google are open about this.

Google states that user engagement metrics like app crashes, ANR rates (application not responding) and poor reviews can limit exposure opportunities on Google Play.

While Apple isn’t quite as forthcoming as Google when it comes to providing information on engagement metrics, they do state that app ratings and reviews can influence app store visibility.

Ultimately, Apple wants to ensure IOS apps provide a good user experience, so it’s likely they use a range of additional user engagement metrics to rank an app in the App Store.

As part of your investigation, you should look into how the below user engagement metrics may have changed around the time period you saw a drop in visits to your app.

• App rating
• Number of ratings (newer/fresh ratings will be weighted more for Google)
• Number of downloads
• Installs vs uninstalls
• App crashes and application not responding

You’ll be able to get data for the above metrics in Google Play Console and App Store Connect, or you may have access to this data internally.

Even if your analysis doesn’t reveal insights, metrics like app rating influences conversion and where your app ranks in the app pack SERP feature, so it’s well worth investing time in developing a strategy to improve these metrics.

One simple tactic could be to ensure you respond to negative reviews and reviews with questions. In fact, users increase their rating by +0.7 stars on average after receiving a reply.

Apple offers a few tips on asking for ratings and reviews for IOS app.

Help win your app traffic back

Step 1. Spy on your competitors

Find out who’s ranking

When trying to identify opportunities to improve app store visibility, I always like to compare the top 5 ranking competitor apps for some priority non-branded keywords.

All you need to do is search for these keywords in Google Play and the App Store and grab the publicly available ranking factors from each app listing. You should have something like the below.

Brand	Title	Title Character length	Rating	Number of reviews	Number of installs	Description character length
COMPETITOR 1	[Competitor title]	50	4.8	2,848	50,000+	3,953
COMPETITOR 2	[Competitor title]	28	4.0	3,080	500,000+	2,441
COMPETITOR 3	[Competitor title]	16	4.0	2566	100,000+	2,059
YOUR BRAND	​[Your brands title]	37	4.3	2,367	100,000+	3,951
COMPETITOR 4	[Competitor title]	7	4.1	1,140	100,000+	1,142
COMPETITOR 5	[Competitor title]	24	4.5	567	50,000+	2,647

     Above: anonymized table of a client’s Google Play competitors

From this, you may get some indications as to why an app ranks above you. For instance, we see “Competitor 1” not only has the best app rating, but has the longest title and description. Perhaps they better optimized their title and description?

We can also see that competitors that rank above us generally have a larger number of total reviews and installs, which aligns with both Google’s and Apple’s statements about the importance of user engagement metrics.

With the above comparison information, you can dig a little deeper, which leads us on nicely to the next section.

Optimize your app text fields

Keywords you add to text fields can have a significant impact on app store discoverability.

As part of your analysis, you should look into how your keyword optimization differs from competitors and identify any opportunities.

For Google Play, adding keywords to the below text fields can influence rankings:

• Keywords in the app title (50 characters)
• Keywords in the app description (4,000 characters)
• Keywords in short description (80 characters)
• Keywords in URL
• Keywords in your app name

When it comes to the App Store, adding keywords to the below text fields can influence rankings:

• Keywords in the app title (30 characters)
• Using the 100 character keywords field (a dedicated 100-character field to place keywords you want to rank for)
• Keywords in your app name

To better understand how your optimisation tactics hold up, I recommended comparing your app text fields to competitors.

For example, if I want to know the frequency of mentioned keywords in their app descriptions on Google Play (keywords in the description field are a ranking factor) than I’d create a table like the one below.

Keyword	COMPETITOR 1	COMPETITOR 2	COMPETITOR 3	YOUR BRAND	COMPETITOR 4	COMPETITOR 5
job	32	9	5	40	3	2
job search	12	4	10	9	10	8
employment	2	0	0	5	0	3
job tracking	2	0	0	4	0	0
employment app	7	2	0	4	2	1
employment search	4	1	1	5	0	0
job tracker	3	0	0	1	0	0
recruiter	2	0	0	1	0	0

     Above: anonymized table of a client’s Google Play competitors

From the above table, I can see that the number 1 ranking competitor (competitor 1) has more mentions of “job search” and “employment app” than I do.

Whilst there are many factors that decide the position at which an app ranks, I could deduce that I need to increase the frequency of said keywords in my Google Play app description to help improve ranking.

Be careful though: writing unnatural, keyword stuffed descriptions and titles will likely have an adverse effect.

Remember, as well as being optimized for machines, text fields like your app title and description are meant to be a compelling “advertisement” of your app for users..

I’d repeat this process for other text fields to uncover other keyword insights.

Step 2. Optimize your store listing

Your store listing in the home of your app on Google Play. It’s where users can learn about your app, read reviews and more. And surprisingly, not all apps take full advantage of developing an immersive store listing experience.

Whilst Google doesn’t seem to directly state that fully utilizing the majority of store listing features directly impacts your apps discoverability, it’s fair to speculate that there may be some ranking consideration behind this.

At the very least, investing in your store listing could improve conversion and you can even run A/B tests to measure the impact of your changes.

You can improve the overall user experience and content found in the store listing by adding video trailers of your app, quality creative assets, your apps icon (you’ll want to make your icon stand out amongst a sea of other app icons) and more.

You can read Google’s best practice guide on creating a compelling Google Play store listing to learn more.

Step 3. Invest in localization

The saying goes “think global, act local” and this is certainly true of apps.

Previous studies have revealed that 72.4% of global consumers preferred to use their native language when shopping online and that 56.2% of consumers said that the ability to obtain information in their own language is more important than price.

It makes logical sense. The better you can personalize your product for your audience, the better your results will be, so go the extra mile and localize your Google Play and App Store listings.

Google has a handy checklist for localization on Google Play and Apple has a comprehensive resource on internationalizing your app on the App Store.

Wrap up

A drop in visits of any kind causes alarm and panic. Hopefully this blog gives you a good starting point if you ever need to investigate why an apps traffic has dropped as well as providing some quick fire opportunities to win it back.

If you’re interested in further reading on ASO, I recommend reading App Radar’s and TheTool’s guides to ASO, as well as app search discoverability tips from Google and Apple themselves.

Sign up for The Moz Top 10, a semimonthly mailer updating you on the top ten hottest pieces of SEO news, tips, and rad links uncovered by the Moz team. Think of it as your exclusive digest of stuff you don’t have time to hunt down but want to read!

”

- http://monleyhomes.blogspot.com/2019/11/app-store-seo-how-to-diagnose-drop-in.html
from Tumblr https://monleyhomes.tumblr.com/post/189288975260”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some.html
from Tumblr https://monleyhomes.tumblr.com/post/189291367820”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_25.html
from Tumblr https://monleyhomes.tumblr.com/post/189294231850”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_69.html
from Tumblr https://monleyhomes.tumblr.com/post/189297252915”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_24.html
from Tumblr https://monleyhomes.tumblr.com/post/189300328090”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_83.html
from Tumblr https://monleyhomes.tumblr.com/post/189303133745”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_14.html
from Tumblr https://monleyhomes.tumblr.com/post/189305828455”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_78.html
from Tumblr https://monleyhomes.tumblr.com/post/189307629490”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_26.html
from Tumblr https://monleyhomes.tumblr.com/post/189309367610”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_88.html
from Tumblr https://monleyhomes.tumblr.com/post/189311771435”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_70.html
from Tumblr https://monleyhomes.tumblr.com/post/189314797415”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_74.html
from Tumblr https://monleyhomes.tumblr.com/post/189317785280”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_54.html
from Tumblr https://monleyhomes.tumblr.com/post/189320765410”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_75.html
from Tumblr https://monleyhomes.tumblr.com/post/189323541010”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_80.html
from Tumblr https://monleyhomes.tumblr.com/post/189326104760”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_99.html
from Tumblr https://monleyhomes.tumblr.com/post/189327913635”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_27.html
from Tumblr https://monleyhomes.tumblr.com/post/189329540700”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_65.html
from Tumblr https://monleyhomes.tumblr.com/post/189331822370”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_28.html
from Tumblr https://monleyhomes.tumblr.com/post/189334778995”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_93.html
from Tumblr https://monleyhomes.tumblr.com/post/189337695855”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_58.html
from Tumblr https://monleyhomes.tumblr.com/post/189340639535”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_56.html
from Tumblr https://monleyhomes.tumblr.com/post/189343259745”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_21.html
from Tumblr https://monleyhomes.tumblr.com/post/189345854330”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_33.html
from Tumblr https://monleyhomes.tumblr.com/post/189347838410”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_92.html
from Tumblr https://monleyhomes.tumblr.com/post/189349381760”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_38.html
from Tumblr https://monleyhomes.tumblr.com/post/189351656220”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_16.html
from Tumblr https://monleyhomes.tumblr.com/post/189354630595”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_52.html
from Tumblr https://monleyhomes.tumblr.com/post/189357529125”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_29.html
from Tumblr https://monleyhomes.tumblr.com/post/189360437080”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_12.html
from Tumblr https://monleyhomes.tumblr.com/post/189362995060”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_34.html
from Tumblr https://monleyhomes.tumblr.com/post/189365572115”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_35.html
from Tumblr https://monleyhomes.tumblr.com/post/189367483055”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_7.html
from Tumblr https://monleyhomes.tumblr.com/post/189369227750”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_6.html
from Tumblr https://monleyhomes.tumblr.com/post/189371382205”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_55.html
from Tumblr https://monleyhomes.tumblr.com/post/189374049755”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_39.html
from Tumblr https://monleyhomes.tumblr.com/post/189376746760”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_48.html
from Tumblr https://monleyhomes.tumblr.com/post/189379758800”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_91.html
from Tumblr https://monleyhomes.tumblr.com/post/189382404800”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_20.html
from Tumblr https://monleyhomes.tumblr.com/post/189385023990”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_9.html
from Tumblr https://monleyhomes.tumblr.com/post/189387205500”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_30.html
from Tumblr https://monleyhomes.tumblr.com/post/189388855535”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_0.html
from Tumblr https://monleyhomes.tumblr.com/post/189391171160”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_89.html
from Tumblr https://monleyhomes.tumblr.com/post/189394125180”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_46.html
from Tumblr https://monleyhomes.tumblr.com/post/189396930660”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_11.html
from Tumblr https://monleyhomes.tumblr.com/post/189400073105”

- http://monleyhomes.blogspot.com/2019/11/posted-by-joelmesherghi-for-some_18.html
from Tumblr https://monleyhomes.tumblr.com/post/189402741700