All geek questions in one place

How is indexing a Google app different from links on Facebook?

  • Both of them seem to provide the ability to add the concept of urls to native applications.
  • As far as I understand, Facebook tried to set the standard with application links for the problem
  • I'm not sure where indexing the Google app is at odds with the same idea.

Android application indexing indicates how the application is indexed to match relevant content on the Internet.

where as

App links say app-app binds certain content

Both offer, have a url-like structure for targeting certain content to applications intended for use outside the application (maybe this is another application or a web application)

What I want to know:

  • When creating my application, I have to make both applications or applications that can be used both for both (starting from the standard one), and how to benefit from both?
+6
source share
4 answers

You can implement both. AppIndexing now affects personalized search rankings , so it can give better results for your Android users.

Quote from the page above in case the link rots:

Starting today, we will begin to use information from indexed applications as a rating factor for registered users who have the application installed. In As a result, we can now add content from indexed applications more noticeably in the search.

If you have a large audience on Android, I would recommend using AppIndexing. If you have many Facebook users, I would recommend using apps. If you have both, do both!

To answer your question, you cannot rely on App Links to do AppIndexing, but you can probably work at the same time with minimal extra effort.

Edit

To better answer your question, you should be able to structure the expected URIs equally for both. This would allow Intent to be processed in the Android client to support both inbound and URIs of AppIndexing applications.

Edit 2

An example URI structure for supporting AppIndexing and AppLinks applications.

Say you have an Android application called SuperLinks with the package name com.example.superlinks, you want to create a scheme to access a specific resource called examplelink # 1234. Your URI scheme will be superlink: // examplelink / 1234, which you could implement the Android client interface once by adding 2 different fragments to the head of the web page.

Your AndroidManifest.xml will contain Intent filters for processing the scheme you created as such ( Help ): ... <activity android:name=".YourActivity" android:label="@string/app_name" > ... <intent-filter> <action android:name="android.intent.action.VIEW" /> <category android:name="android.intent.category.DEFAULT" /> <data android:scheme="superlinks" /> </intent-filter> </activity> ... Note that action flags and categories are necessary for the application to appear as an option in the selection when the user tries to open one of your schema links.

To support AppIndexing, add the following to your page title ( Help ): <head> ... <link rel="alternate" href="android-app://com.example.superlinks/superlinks/examplelink/1234" /> ... </head>

To support AppLinks, you must add the following to your page Link : <head> ... <meta property="al:android:url" content="superlinks://examplelink/1234"> <meta property="al:android:package" content="com.example.superlinks"> <meta property="al:android:app_name" content="SuperLinks"> ... </head>

+5
source

You must implement both.

In fact, you can have the same (or very similar) code on the application side to handle the incoming link, but on the server side you must implement both.

+1
source

Indexing applications allows you to index Google applications as websites (in a simple way, indexing a Google application registers your application with the Google search engine). Deep links to your Android app appear in Google search results, allowing users to quickly go to your own mobile phone, landing exactly on the right content in your app.

If your application is registered in google indexing and you are going to search in google search now, then the following has happened: -

enter image description here

see this link: - https://developers.google.com/app-indexing/

This is an official example of application indexing code .

Application indexing is used to index your application in the google index, and whenever a user searches for the content of your application in a Google search, it shows the link of your application in a Google search.

Note: -

If you have a website, you need to register using the Google Developer Console. (See video from this link and the time is 2.50 s)

0
source

In terms of implementation, the integration of these standards is basically the same. These are simple ways to turn your website into a link that also points to your application when necessary. To implement, you simply add the appropriate meta tags to your site.

For indexing Google apps, this is simply a <link/> , for example:

 <link rel="alternate" href="myapp://stuff?params=1&params=2"/>

For AppLinks, these are just custom Facebook tags, for example:

 <meta property="al:android:url" content="myapp://stuff?params=1&params=2" /> <meta property="al:android:package" content="com.myapp.package" /> <meta property="al:android:app_name" content="My App" />

Basically, you have to implement both, because Google and Facebook are viciously fighting for control over mobile eyeballs. Google will never use the Facebook standard and vice versa.

Functionally, they are completely different:

  • Indexing the Google App will basically change your page search result in the search results in the app when you add the appropriate tags.
  • Links to Facebook applications are used by App Invites and the Ads product to determine how to open the application. We have not yet seen any other significant differences in binding when adding tags.

If you don't want to worry about installing this, check out branch.io (the service I'm working on). We act as your site and automatically enter the correct meta tags, so you don’t need to worry about it.

0
source

Source: https://habr.com/ru/post/983070/

More articles:


All Articles