\n the new kid on the block in organic search, and they’re picking up speed faster than you can say
\n “schema.org ViewAction”<\/span>! For signed-in users, 15% of Google searches
\n on Android now return deep links to apps through App Indexing. And over just the past quarter,
\n we’ve seen the number of clicks on app deep links jump by 10x.\n<\/p>\n
\n We’ve gotten a lot of feedback from developers and seen a lot of implementations gone right and \n App indexing is a team effort between you (as a webmaster) and your app development team. We show \n…and we plan to add a lot more in the coming months!\n<\/p>\n \n We’ve noticed that very few developers have access to Webmaster Tools. So if you want your app \n Any verified site owner can \n How are users engaging with your app from search results? We’ve introduced two new ways for you to \n Blocked resources are one of the top reasons for the “content mismatch” errors you see in \n To help you find and fix these issues, we now show you the specific resources we can’t access that \n To help you identify errors when indexing your app, we’ll send you messages for all app errors we \n In addition to the currently available “Content mismatch” and “Intent URI not supported” error \n In our experience, the majority of errors are usually caused by a general setting in your app \n Good luck in the pursuit of appiness! As always, if you have questions, you can drop by our
\n others that were good learning experiences since we
\n opened up App Indexing back in June<\/a>.
\n We’d like to share with you four key steps to monitor app performance and drive user engagement:\n<\/p>\nGive your app developer access to Webmaster Tools<\/h2>\n
\n information in Webmaster Tools that is key for your app developers to do their job well. Here’s
\n what’s available right now:\n<\/p>\n\n
\n development team to get all of the information they need to fix app-related issues, it’s essential
\n for them to have access to Webmaster Tools.\n<\/p>\n
\n add a new user<\/a>.
\n Pick restricted or full permissions, depending on the
\n level of access<\/a>
\n you’d like to give:\n<\/p>\n![](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-314181232b62.png\")
<\/p>\nUnderstand how your app is doing in search results<\/h2>\n
\n track performance for your app deep links:\n<\/p>\n\n
\n Message center<\/a>
\n in your Webmaster Tools account.\n <\/li>\n
\n information—specifically, the referrer extra in the ACTION_VIEW<\/code> intent. We’re
\n working to integrate this information with Google Analytics for even easier access. Learn
\n how to track referrer information<\/a>
\n on our Developer site.\n <\/li>\n<\/ul>\nMake sure key app resources can be crawled<\/h2>\n
\n Webmaster Tools’
\n Crawl Errors report<\/a>.
\n We need access to all the resources necessary to render your app page. This allows us to assess
\n whether your associated web page has the same content as your app page.\n<\/p>\n
\n are critical for rendering your app page. If you see a content mismatch error for your app, look
\n out for the list of blocked resources in “Step 5” of the details dialog:\n<\/p>\n![](\"https:\/\/alienroad.com\/wp-content\/uploads\/kb-gorsel\/g-7b91fa6b9ea8.png\")
<\/p>\nWatch out for Android App errors<\/h2>\n
\n detect, and will also display most of them in the “Android apps” tab of the
\n Crawl Errors report<\/a>.\n<\/p>\n
\n alerts, we’re introducing three new error types:\n<\/p>\n\n
\n first-click free<\/a>
\n <\/strong>: the link to your app does not lead directly to the content, but requires login to
\n access.\n <\/li>\n
\n did not return to search results.\n <\/li>\n<\/ul>\n
\n (for example, a blocked resource, or a region picker that pops up when the user tries to open the
\n app from search). Taking care of that generally resolves it for all involved URIs.\n<\/p>\n
\n Webmaster help forum<\/a>.\n<\/p>\n