Tuesday, 27 October 2015

Facebook just made it easier to talk to people you're not friends with

Fb-messenger
Feed-twFeed-fb

Chatting with strangers on Facebook just got a bit easier.

The social network is launching a new feature for Messenger called Message Requests, that makes it easier for people to receive (or ignore) messages from people they aren't friends with

Previously, messages that were sent by people who weren't friends (or friends of friends) were relegated to the "Other" inbox, a separate section within the messages tab on Facebook's website. The messages were easy to miss since new messages routed to the "other" section didn't surface in notifications. (Users also had the option of paying $1 to bypass the "Other" section.) Read more...

More about Facebook, Social Media, Tech, Facebook Messenger, and Apps Software

Are Your Analytics Telling the Right Story?

Posted by Bill.Sebald

A process can easily become a habit. A habit may not change without awareness or intervention.

Before it becomes a habit, a process should be adjusted to change along with new goals, constant learning, experimentation, and so on.

Considering your time in analytics, are you engaging in a process, or in an outdated habit?

That’s a real question that digital marketing practitioners should ask themselves. Inherently, marketers tend to be buried with work, reusing templates to speed up results. But many agencies lean on those templates a little too much, in my opinion.

Templates should never be written in stone.

If your company is pumping out canned reports, you’re not alone. I do the business development for our company and regularly ask prospects to explain or share the reports they’ve received in the past. Sometimes it’s truly discouraging, outdated, wasteful, and the reason businesses search for new SEO vendors.

Look—I’m all for scalability. It’s a huge help. But some things can’t be scaled and still be successful, especially in today’s SEO climate—or, frankly, marketing in general. Much of what was scalable in SEO prior to 2011 is now penalty-bait. Today’s analytics tools and platforms can slice and dice data faster than anything Ron Popeil ever sold, but the human element will always be necessary if you want your marketing to dominate.

Find the stories to tell

I like to tell stories. I’m real fun in the pub. What I’ve always loved about marketing is the challenge to not only find a story, but have that story change something for the better. I like adding my layer based on real data and experimenting.

Analytics work is all about finding the story. It’s detective work. It's equal parts Sherlock Holmes, Batman, and Indiana Jones. If you’re lucky, the story jumps out with very little digging. However, it’s more likely you’ll be going on some expeditions. It’s common to start with a hunch or random click through reports, but you need to always be looking for the story.

A great place to start is through client conversations. We schedule at least one monthly call with our clients, where it’s truly a discussion session. We get conversations going to pull intel out of the key stakeholders. Case in point: Recently, we discovered through an open discussion that one of our clients had great success with an earlier email campaign targeted to business owners. There was specific information customers positively responded to, which was helpful in recent content development on their website. It's amazing what you can learn by asking questions and simply listening to responses.

We should be true consultants, not report monkeys. Dive into the discussions started and enjoy the ride. I guarantee you’ll take note of a few ripe areas to review next time you log into your Google Analytics account.

An impromptu survey says it’s a time issue

Most SEO engagements are designed around a block of purchased hours. Hopefully the client understands they’re not only buying your time to complete SEO tasks, but also your expertise and analysis. If someone on your team were to say, “I don’t have time to do analysis because all my tasks used up their budget this month,” then you really need to question the value of the chosen tasks. Were they picked based on front-loaded analysis, or were they simply tasks pulled out of guesswork?

A few weeks ago I pushed a quick Survey Monkey survey out on Twitter and Linkedin. Thanks to a few retweets, 94 people responded (please consider the following results more directional than scientific—I’m well aware it’s a shallow survey pool). I asked two questions:

  1. If you work in-house or have clients, how often do you log into your clients’ analytics? (Multiple choices ranged from several times a day to a few times a month).
  2. Do you, or do you not, get enough time in Analytics to interpret the data?

The responses:

answers2

While some do make a habit of logging into analytics once or more times a day, more do not. Is it required to check under the hood every day? Personally, I believe it is—but your answer may vary on that one. If something went south overnight, I want to be aware before my client tells me. After all, that’s one of the things I’m paid for. I like the idea of being active—not reactive.

More notable is that most respondents didn’t feel they get enough time in analytics. That should absolutely change.

There was also a field for respondents to elaborate on their selections. There were several comments that jumped out at me:

“In house, day to day tasks and random projects prevent me from taking the deep dives in analytics that I feel are valuable.”

“It’s challenging to keep up with the changes and enhancements made in Google Analytics in particular, amongst other responsibilities and initiatives.”

“Too many things are on my plate for me to spend the time I know I should be spending in Google Analytics.”

“Finding the actionable info in Analytics always takes more time that expected—never enough time to crunch the numbers!”

“I log in to 'spot check' things but rarely do I get to delve into the data for long enough to suss out the issues and opportunities presented by the data.”

These results suggest that many marketers are not spending enough time with analytics. And possibly not because they don’t see the value, but simply because they don’t have time. “Either you run the day, or the day runs you (Jim Rohn)” is apropos here—you must make time. You need to get on top of all the people filling your plate. It’s not easy, but it needs to be done.

Get on top of those filling your plate. Kind of like professional crowd surfing.

Helpful resources

Dashboards are fantastic, but I rarely see them set up in analytics platforms. One of the best ways to get a quick glimpse of your key metrics are with dashboards. All good analytics platforms provide the ability to make custom dashboards. Get into work, grab a coffee, fire up the computer, click your dashboard bookmark. (I recommend that order!) Google Analytics, which most of us probably use, provides some decent options with their dashboards, though limited compared to enterprise analytics platforms.

However, this basic dashboard is the minimum you should review in analytics. We’ll get deeper soon.

Building these widgets are quite easy (I recently created a tutorial on my site). There are also websites that provide dashboards you can import into Google Analytics. Dashboard Junkie is a fun one. Here are some others from Econsultancy and Google themselves.

It’s not just analytics platforms that offer dashboards. There are several other vendors in the SEO space that port in analytics data and mesh with their own data—from Moz Analytics to SearchMetrics to Conductor to many, many others.

SEMrush has a unique data set that marketers should routinely review. While your traffic data in analytics will be truer, if you’re targeting pages you may be interested in monitoring keyword rank counts:

Are backlinks a target? Maybe you’d find Cognitive SEO’s dashboard valuable:

cognitive

RankRanger is another SaaS we use. It’s become way more than just our daily rank tracking software. The data you can port in creates excellent snapshots and graphs, and strong dashboards:

rankranger1

It also offers other graphing functionality to make pretty useful views:

While some of the bigger platforms, like SearchMetrics and Conductor, make it easier to get a lot of information within one login, I’m still finding myself logging into several programs to get the most useful data possible. C’est la vie.

Analytics is your vehicle to identifying problems and opportunity

Remember, dashboards are simply the “quick and dirty” window into your site. They help spotlight drastic changes, and make your website’s general traction more visible. Certainly valuable for when your CMO corners you by the Keurig machine. It’s a state of the union, but doesn’t focus on subsections that may need attention.

Agencies and consultants tend to create SEO reports for their clients as a standard practice, though sometimes these reports become extremely boilerplate. Boilerplate reports essentially force you to look under the same rocks month after month. How can you get a bigger view of the world if you never leave your comfortable neighborhood? A new routine needs to be created by generating new reports and correlations, finding trends that were hidden, and using all the tools at your disposal (from Analytics to link tools to competitive tools).

Your analytics app is not a toy—it’s the lifeblood of your website.

Deeper dives with Google Analytics

Grouped pages lookup

A quick way to look at chunks of the site is by identifying a footprint in the URL and searching with that. For example, go to Behavior > Site Content > All Pages or Landing Pages. Then, in the search bar right below the graph, search for the footprint. For example, take www.mystoreisdabomb.com/blog/2015/ as a real URL. if you want to see everything in the blog, enter */blog/ into the search bar. This is especially useful in getting the temperature of an eCommerce category.

Segment sessions with conversions/transactions

So often in SEO we spend our time analyzing what’s not working or posing as a barrier. This report helps us take a look at what is performing (by leads or sales generated) and the customer behavior, channels, and demographic information that goes along with that. Then we can identify opportunities to make use of our success and improve our overall inbound strategy.

Below is a deeper dive into the conversions “Lead Generation” segment, although these same reports can just as aptly be applied to transactions. Ultimately, there are a lot of ways to slice and dice the analysis, so you’ll have to know what makes sense for your client, but here are three different reports from this segment that provided useful insights that will enhance our strategy.

  • Conversions
    One of the easy and most valuable ones! Directions: Under any report, go to Add a Segment > Sessions with Conversions > Apply.
  • Demographics – age, gender, location
    For example, our client is based in Pennsylvania, but is receiving almost as many request form submissions from Texas and New York, and has a high ratio of request form submissions to visitors for both of these other states. Given our client’s industry, this gives us ideas on how to market to these individuals and additional information the Texans may need given the long distance.
  • Mobile – overview, device type, landing pages
    For this client, we see more confirmation of what has been called the “micro-moment” in that our mobile users spend less time on the site, view less pages per visit, have a higher bounce rate, and are more likely to be new users (less brand affinity). This would indicate that the site is mobile optimized and performing as expected. From here, I would next go into mobile traffic segments to find pages that aren’t receiving a lot of mobile traffic, but are similar to those that are, and find ways to drive traffic to those pages as well.
  • Acquisition
    Here we’re looking at how the inbound channels stack up for driving conversions. Organic and Paid channels are neck and neck, although referral and social are unexpected wins (and social, glad we’ve proven your viability to make money!). We’ll now dig deeper into the referring sites and social channels to see where the opportunities are here.

Assisted conversions

There’s more to the story than last click. In Analytics, go to Conversions > Multi-Channel Funnels > Assisted conversions. Many clients have difficulty understanding the concept of attribution. This report seems to provide the best introduction to the world of attribution. Last click isn’t going to be replaced anytime soon, but we can start to educate and optimize for other parts of the funnel.

True stories from analytics detective work

Granted, this is not a post about favorite reports. But this is a post about why digging through analytics can open up huge opportunities. So, it’s real-life example time from Greenlane’s own experience!

Story 1: The Forgotten Links

The client is a big fashion brand. They’ve been a popular brick-and-mortar retail destination since the early 80s, but only went online in 1996. This is the type of company that builds links based on their brand ambassadors and trendy styles. SEO wasn’t the mainstream channel it is today, so it’s likely they had some serious architecture changes since the 90s, right?

For this company, analytics data can only be traced back about seven years. We thought, “Let’s take a look at what drove traffic in their early years. Let’s see if there were any trends that drove volume and sales where they may be slipping today. If they had authority then, and are slipping now, it might be easier to recoup that authority versus building from scratch.”

The good news—this brand had been able to essentially maintain the authority they launched with, as there were not any real noticeable gaps between search data then and search data today. But, in the digging, we uncovered a gem. We found a lot of URLs that used to draw traffic that are not on their tree today. After digging furthur, we found a redesign occurred in the late 90s. SEO wasn’t factored in, creating a ton of 404s. These 404s were not even being charted in Google Webmaster Tools, yet they are still being linked to today from external sites (remember, GWT is still quite directional in terms of the data they provide). Better yet, we pulled links from OSE and Majestic, and saw that thousands of forgotten links existed.

This is an easy campaign—create a 301 redirect matrix for those dead pages and bring those old backlinks to life.

But we kept wondering what pages were out there before the days where analytics was implemented. Using the Wayback Machine, we found that even more redesigns had occurred in the first few years of the site’s life. We didn’t have data for these pages, so we had to get creative. Using Screaming Frog, we crawled the Wayback Machine to pull out URLs we didn’t know existed. We fed them into the link tools, and sure enough, there were links there, too.

Story 2: To “View All” or Not To “View All”

Most eCommerce sites have pagination issues. It’s a given. A seasoned SEO knows immediately to look for these issues. SEOs use rel=”next” and “prev” to help Google understand the relationships. But does Google always behave the way we think they should? Golly, no!

Example 2 is a company that sells barware online. They have a lot of products, and tend to show only “page 1” of a given category. Yet, the analytics showed instances where Google preferred to show the view all page. These were long "view all" pages, which, after comparing to the “page 1” pages, showed a much lower bounce rate and higher conversions. Google seemed to prefer them in several cases anyway, so a quick change to default to “view all” started showing very positive returns in three months.

Story 3: Selling What Analytics Says to Sell

I have to change some details of this story because of NDAs, but once upon a time there was a jewelry company that sold artisan products. They were fond of creating certain kinds of keepsakes based on what sold well in their retail stores. Online, though, they weren't performing very well selling these same products. The website was fairly new and hadn't quite earned the footing they thought their brand should have, but that wasn't the terminal answer we wanted to give them. Instead, we wanted to focus on areas they could compete with, while building up the entire site and turning their offline brand into an online brand.

Conversion rates, search metrics, and even PPC data showed a small but consistent win on a niche product that didn't perform nearly as well in the brick-and-mortar stores. It wasn't a target for us or the CEO. Yet online, there was obvious interest. Not only that, with low effort, this series of products was poised to score big in natural search due to low competition. The estimated search volume (per Google Keyword Planner) wasn't extraordinary by any stretch, but it led to traffic that spent considerable dollars on these products. So much so, in fact, that this product became a focus point of the website. Sometimes, mining through rocks can uncover gold (jewelry pun intended).

Conclusion

My biggest hope is that your takeaway after reading this piece is a candid look at your role as an SEO or digital marketer. You’re a person with a “unique set of skills,” being called upon to perform works of brilliance. Being busy does create pressure; that pressure can sometimes force you to look for shortcuts or “phone it in.” If you really want to find the purest joy in what you’ve chosen as a career, I believe it’s from the stories embedded within the data. Go get ’em, Sherlock!


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!

Snapchat or Instagram? Deciding Which Platform Is Ideal for Your Visual Content

ag-snapchat-instagram-560

Is visual content part of your social media marketing? Are you trying to decide whether to use Instagram or Snapchat? Snapchat and Instagram share the same basic purpose. While many businesses want to know which is better for marketing, the truth is both have value. In this article you’ll find insights to help you decide whether your visual […]

This post Snapchat or Instagram? Deciding Which Platform Is Ideal for Your Visual Content first appeared on Social Media Examiner.
Social Media Examiner - Your Guide to the Social Media Jungle

6 Tips to Get Your Business Started on Social Media

dt-6-tips-social-media-560

Do you want to create a business presence on social media? Looking for tips to get started? Setting up a good foundation on social media can help you build visibility and connections for your business. In this article you’ll discover six tips to get your business started on social media. #1: Create Profiles on Multiple Social […]

This post 6 Tips to Get Your Business Started on Social Media first appeared on Social Media Examiner.
Social Media Examiner - Your Guide to the Social Media Jungle

Monday, 26 October 2015

Facebook's new notifications tab could replace your calendar reminders

Fb-notifications-1
Feed-twFeed-fb

Of all the ways the Facebook app has changed over the years, its notifications tab is one of the few areas that has remained mostly untouched.

Until now.

The company will begin to roll out a new look for the notifications tab in its iOS and Android apps in the coming weeks; the redesign will add a suite of assistant-like reminders about your day, friends and other topics based on your preferences and previous activity.

The changes, which Mashable first previewed in April, have been in the works for some time. The updated notifications tab will surface contextual reminders in the form of cards. If you've liked the page of a certain team or athlete, for instance, you may see a card alerting you to an upcoming game. Or you may see cards telling you about TV shows you like airing that night. Read more...

More about Facebook, Social Media, Tech, Apps Software, and Apps And Software

How to Get Your App Content Indexed by Google

Posted by bridget.randolph

As mobile technology becomes an increasingly common way for users to access the internet, you need to ensure that your mobile content (whether on a mobile website or in a mobile app) is as accessible to users as possible. In the past this process has been relatively siloed, with separate URLs for desktop and mobile content and apps tucked away in app stores.

But as app and mobile web usage continues to rise, the ways in which people access this content is beginning to converge, which means it's becoming more important to keep all of these different content locations linked up. This means that the way we think about managing our web and mobile content is evolving:

So how do we improve the interaction between these different types of content and different platforms, getting to the point of being able to have a single URL which takes the user to the most appropriate version of the content based on their personal context?

The first step is to ensure that we are correctly implementing deep linking (e.g., linking to a particular screen within an app) for apps which have comparable webpage content, to allow for our app content to rank in mobile search.

Image credit: Google Developers

Google indexation provides benefits for both Android and iOS apps. The benefits for Android apps are twofold:

  • users searching on an Android device who have not yet installed your app will see the app show up in mobile search results; and
  • Android users who do have your app installed will get query autocompletions when they use browser search which can include results from your app, as well as seeing enhanced display elements in the SERP (such as the app icon). It’s basically like rich snippets for apps.

Image credit: Google Developers

On iOS, app ranking is currently only supported for apps already installed on the device. Apple users should see search results which include links to installed apps and also include the enhanced display elements mentioned above.

In addition, Google recently announced that mobile apps which use the new App Indexing API for deep linking may receive a rankings boost in mobile web search. They are releasing a new and improved version of Google Now, "Now on Tap," in their latest OS update (Android M), which allows you to search content across your phone without navigating out of whatever app (or website) you are currently using. The catch is, that app content has to be in their index in order to be included in a "Now on Tap" search.

It’s not just Google, either; Apple is implementing their own version of a search index to allow iOS9 users to search and discover web and app content without using a third-party search engine, Bing has its own approach to app indexation and ranking, and other services aren’t far behind.

This post, however, will focus on how to setup your Android and iOS apps to appear in Google search results. While the idea of app indexation isn’t new, it is an area of rapid innovation and the process for getting your apps indexed by Google has recently been simplified. This post is therefore intended to provide a brief overview of that process and to serve as an update to the information which is currently available.

The implementation

The good news is that it’s getting simpler to add the relevant markup to your web content and get your app content indexed and ranking in mobile search results.

The basic process is only three steps:

  1. Support HTTP deep links in your mobile app. For iOS you will need to do this by setting up support for "Universal Links." "Universal Links" are what Apple calls HTTP links that have a single URL which can open both a specific page on a website and the corresponding view in an app.
    Note: At this point, you can register your app with Google, associate it with your website and stop there—as long as you are using the same URLs for your web content and your app content, they should be able to automatically crawl, index, and attempt to rank your app content based on your website’s structure. However, implementing App Indexing and explicitly mapping your web content to your app content using on-page markup can provide additional benefits and allow for a bit more control. Therefore, I recommend following the full process, if possible.
  2. Implement Google App Indexing using the App Indexing API for Android, or by integrating the App Indexing SDK for iOS 9.
  3. Explicitly map your web pages to their corresponding app screens using either a rel=alternate link element on the individual page, by referencing the app URLs in your XML sitemaps, or by using schema.org markup.

You can find a more step-by-step explanation of this process (looking at Android and iOS separately) below.


The app indexation process used to be a bit more complex, because HTTP links aren’t supported by older iOS versions. Instead, developers had to use something called "Custom URL Schemes" to link to iOS app content. This meant that you essentially had to create a unique scheme for your app URLs and then add support for these in the app code.

Custom URL schemes have a couple other downsides besides adding complexity, namely:

  • different app developers can claim the same custom URL scheme, whereas with HTTP links you can associate the app to a particular domain or set of domains; and
  • with custom URL schemes, tapping the URL when the app isn’t installed results in a broken link (because it only links to content within the app), whereas HTTP links are web links as well and can take the user to a webpage if the app isn’t installed (as long as the URL is the same for both the app view and the corresponding webpage).

While you can still use the custom URL scheme approach, the good news is that Google’s App Indexing is now compatible with HTTP deep link standards for iOS 9, which Apple calls "Universal Links."

You should still add markup to any webpages which have content corresponding to a particular app screen. Think of it like like rel=canonical or like mobile switchboard tags, but for apps. Be aware that when Google finds a link between a webpage and an app page which they think are equivalent, they will compare the two pages and you will receive a ‘Content Mismatch’ error in the Search Console if they don’t believe the content is similar enough.

Getting Android apps indexed in Google

Step 1: Support HTTP deep links in your app by adding intent filters to your manifest.

An intent filter is a way of specifying how an app responds to a particular action. Intent filters for deep links have three required elements: <action>, <category>, and <data>. You can find more guidance on this from Google Developers. Here is their example of an intent filter which enables support for HTTP deep links:

<intent-filter android:label="@string/filter_title_viewrecipes">

<action android:name="android.intent.action.VIEW" />
<category android:name="android.intent.category.DEFAULT" />
<category android:name="android.intent.category.BROWSABLE" />
<data android:scheme="http"
android:host="recipe-app.com"
android:pathPrefix="/recipes" />
</intent-filter>
</activity>

Noindex option:
Just like for websites, you can add noindex directives for app content as well. Include a noindex.xml file in your app to indicate which deep links should not be indexed, and then reference that file in the app’s manifest (AndroidManifest.xml) file. You can find more detail on how to create and reference the noindex.xml file here.

Step 2: Associate your app to your site in Google Search Console.

This is done in Google Search Console (you can also do it from the Developer Console). As long as your app is set up to support deep links, this step is technically all you have to do to allow Google to start indexing your app. It will allow Google to index and crawl your app automatically by attempting to figure out the app structure from your website structure.

However, if you do stop here, you will not have as much control over how Google understands your content, which is why the explicit mapping of pages to app versions is recommended. Also, if you can’t use the API for some reason, you need to make sure that Googlebot can access your content. You can check that this is configured correctly in your site’s robots.txt file by testing some of your deep links using the robots.txt tester tool in the Search Console.

Step 3: Implement app indexing using the App Indexing API.

Using the App Indexing API is definitely worthwhile; apart from anything else, apps which use the API should receive a rankings boost in mobile search results, and you don’t need to worry about Googlebot struggling to access your content.

The App Indexing API allows you to annotate information about the activities within your app that support deep links (as laid out in your intent filters). For details on how to set this up, see the Google Developers guidance.

Step 4: Test your implementation.

You can test your implementation (always on a fresh installation of your app!) with the following tools. (Find more info about how to use each of these tools here.)

Android Debug Bridge – to test deep links from the command line

Fetch as Google (Search Console) – to test what Google sees when it crawls your app deep links

You can also track search traffic to these deep links in the Search Console’s Search Analytics report.

Getting iOS apps indexed in Google

Step 1: Support HTTP deep links in your app by setting up support for "Universal Links."

To support universal links in your iOS app, you need to first ensure that your app handles these links correctly by adopting the UIApplicationDelegate methods (if it doesn’t already use this protocol). Once this is in place, you can associate your app with your domain.

You’ll do this by:

  • adding an "associated domains" entitlement file to your app’s project in XCode that lists each domain associated with your app; and
  • uploading an apple-app-site-association file to each of these domains with the content your app supports—note that the file must be hosted at the root level and on a domain that supports HTTPS.

To learn more about supporting Universal Links, view the Apple Developer guidance.

Step 2: Register your app with Google (using the GoogleAppIndexing SDK for iOS 9).

You’ll need to add the App Indexing SDK to your app using the CocoaPods dependency manager. For step by step instructions, check the Google Developers’ guide. Basically what this does is allows you to register your app with Google, just like Android apps are registered via the Search Console. This also means that Google can now read the apple-app-site-association file to understand what URLs your app can open.

Step 3: Test your implementation.

You can test whether this is set up correctly by tapping a universal link in Safari on an iOS 9 device and checking that it opens the right location in your app.

Mapping your webpages to your app with on-page markup or sitemaps

Once you’ve set up the deep linking support for your Android and/or iOS app(s), the final step is to explicitly identify the corresponding webpages to the correct app screens using one of the supported markup options. This step allows you to indicate more clearly to Google what the relationship is between a given page and its corresponding app link (both of which should already share the same URL if you are using HTTP links). Following this step also allows you to indicate the relationship to Bing crawlers, which otherwise wouldn’t see the app content, and to allow Apple to index your iOS app.

You can do this mapping either in the head of the individual page using a link element, using schema.org markup (for Android only), or in an XML sitemap.

A note on formats for app links

The format for an Android HTTP link uses the format of:

android-app://{package_name}/http/{host_path}

The {package_name} is the app’s "Application ID," which is how it is referenced in the Google Play Store. So a link to the (example) Gizmos app might look like this:

android-app://com.gizmos.android/http/gizmos.com/example

For iOS links, you use the app’s iTunes ID instead of the Package Name. So an iOS app URL uses this format:

ios-app://{itunes_id}/{scheme}/{host_path}

For HTTP links the {scheme} is "http," which would mean your URL would look like this:

ios-app://{itunes_id}/http/{host_path}

How to reference your app links

Note: Google provides guidance on the three currently supported deep link methods here.

Option 1: Link rel=alternate element

To add an app link reference to an individual page, you can use an HTML <link> element in the <head> of the page.

Here is an example of how this might look if you have both an iOS and Android app:

<html>
<head>
...
<link rel="alternate" href="android-app://com.gizmos.android/http/gizmos.com/example" />
<link rel="alternate" href="ios-app://123456/http/gizmos/example" /></head>
<body> … </body>

Option 2: Schema.org markup (currently supported on Android only)

Alternatively, if you have an Android app, you can use schema.org markup for the ViewAction potential action on an individual page to reference the corresponding app link.

Here is an example of how this might look:

script type="application/ld+json">
{
"@context": "http://schema.org",
"@type": "WebPage",
"@id": "http://gizmos.com/example",
"potentialAction": {
"@type": "ViewAction",
"target": "android-app://com.gizmos.android/http/gizmos.com/example"
}
}
</script>

Option 3: Add your app deep links to your XML sitemap

Instead of marking up individual pages, you can use an <xhtml:link> element in your XML sitemap, inside the <url> element specifying the relevant webpage.

Here is an example of how this would look if you have both an iOS and an Android app:

<?xml version="1.0" encoding="UTF-8" ?>
http://www.sitemaps.org/schemas/sitemap/0.9"
xmlns:xhtml="http://www.w3.org/1999/xhtml">
<url>
http://gizmos.com/example
<xhtml:link rel="alternate" href="ios-app://123456/http/gizmos/example" /></url>
<xhtml:link rel="alternate" href="android-app://com.gizmos.android/http/gizmos.com/example" />
...
</urlset>

Additional information

What about apps which don’t have corresponding web pages?

Unfortunately, as of this writing, Google does not officially offer app indexation for apps which don’t have corresponding web content. However, they are trying to move in this direction, and as such are beginning to try this out with a handful of apps with “app-only” content. If you have an app with app-only content, and would like to get this content indexed, you can express interest using this form.

What about getting my app indexed in Bing?

Bing supports two open standard options for linking webpages to app links:

To learn more about how to implement these types of markup, see the guidance on the Bing blog.

Quick reference checklists

Will Critchlow recently spoke about app indexation in his presentation at Searchlove London. He provided two useful checklists for Android and iOS app indexing:

Image source: http://www.slideshare.net/DistilledSEO/searchlove-...

To learn more about app indexing by Google, check out Emily Grossman and Cindy Krum’s excellent post over on SearchEngineLand.


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!

Facebook Freebooting: What Marketers Need to Know

ms-facebook-freebooting-560

Do you use video in your marketing? Want to make sure your copyright is protected? There are simple steps you can take to brand your videos so you’re protected if people upload them to Facebook as their own. In this article you’ll discover how to protect your video content from freebooting on Facebook. What Is Freebooting? Freebooting […]

This post Facebook Freebooting: What Marketers Need to Know first appeared on Social Media Examiner.
Social Media Examiner - Your Guide to the Social Media Jungle