App deep links are the latest kid on the block for organic search. Their speed is picking up at a more rapid pace than one can imagine. As much as 15% of the Google searches on Android now give back deep links to apps via App Indexing, for signed-in users. Within the past quarter, numerous clicks on app deep links rose by as high as 10 times.
Google received a lot of feedback from developers and experienced great outcomes for many implementations apart from others which were positive learning experiences since the App Indexing in June was opened up. Google now aims to share 4 key steps for monitoring performance of the app and driving user engagement:
1. Provide app developers access to Webmaster Tools
- App indexing involves collaboration between the webmaster and the app development team. Information is displayed in Webmaster Tools which is the key for app developers for doing a good job. What is available at present includes:
- Mistakes in indexed pages located within the apps
- Weekly clicks as well as impressions from within the app deep link through Google search
- Statistics on the sitemap in case one has implemented app deep links
Over and above this, Google is now planning to add more in the coming months
Few developers have access to Webmaster Tools, Google has observed. Google has advised that app development teams should get all of the data they require to resolve app-related issues and ensure accessibility to Webmaster Tools.
2. Get to known how your app is performing in search results
You need to explore the manner in which your app is engaging with search results. Two new ways for tracking performance for app deep links are:
Google can now send the weekly clicks as well as impression update to the Message center in the Webmaster Tools account.
The quantity of the traffic driven by app deep links to the app provide employing the use of referrer information can now be tracked-most specifically the referrer action in the ACTION_VIEW intent. The information can be integrated with Google Analytics for simpler access. Users can understand how to track referrer information on Google’s Developer site.
3. Ensure that major app resources can be crawled
Content mismatch errors are usually caused by blocked resources seen in the Webmaster Tools’ Crawl Errors report. Access is also needed to all the resources vital for rendering the app page. Google is then able to find out if the associated web page contains the same content as the app page.
For finding as well as fixing these issues, Google has also displayed specific resources it cannot access which are crucial for rendering the app page. In case the content mismatch error is seen for the app, users should check out step 5 of the detailed dialogues, specifically the list of blocked resources:
4. Be wary of Android App errors
For helping clients to check errors while indexing the app, messages are send for all app errors that are being detected and also show most of them in the “Android apps” tab of the Crawl errors report.
Additionally, content mismatch and intent URI not supported error alerts now have 3 new error types:
- APK not found: This means Google cannot find the package matching the app
- No first-click free: The link to to the app does not lead to direct access to the content and needs a login for access
- Back button violation: Google does not find search results from the back button after following the link to the app
Major errors are caused by general setting within the app, says Google. This includes a blocked resource or region picker that comes up when the user tried to open up the app from search. Getting a hold of these issues and resolving them solves the problem for involved URIs.
Google has also asked users in search of happiness to drop by their Webmaster help forum for any additional help or query resolution.Want to be Better at App Performance Monitoring & Driving User Engagement? Here Are the 4 Steps by Google!,