[Continued from https://productforums.google.com/forum/#!topic/webmasters/wZEY_QZicxg;context-place=forum/webmasters]

Google Search Console Message:

This week we received a GSC Message stating that the deep links are not correctly configured.

IMG1

IMG2

This is the first message of its kind since December 2014 when we implemented the App Index mechanism.

Our setup of the App Index has not changed since then (except that we added a few pages, we are now at 20 pages - it grows by design with 3 pages / year).

Environment:

Desktop site: http://www.feestdagen-belgie.be/
Mobile site: http://m.feestdagen-belgie.be/
Android App: https://play.google.com/store/apps/details?id=com.macjeryseydesign.android.mfdbapp

The ecosystem is configured for App Indexing combined with the Mobile SEO pattern "Separate URL's" since December 2014 and it worked great until now. The initial setup was reviewed with the help of @JohnMu , see https://productforums.google.com/forum/#!category-topic/webmasters/mobile/VckmhD1tRgc The details about the setup are also documented in this article http://rolf.huijbrechts.be/portfolio/mfdb-app-deep-linking/

The Mobile SEO pattern "Separate URL's" is configured for 20 pages, the other desktop pages do not have a custom mobile equivalent (meaning that the responsive desktop website page will be displayed for those which is what we want).

The App Indexing mechanism uses a custom URI Scheme, e.g. -d "fdbappindex://verlengde-weekends-2018-belgie"

Details:

It is strange that it reports 443 Pages with error "Intent URI not supported" although only 20 pages are configured (tagged) for the App Index. Secondly, the total number of pages in the Google Index for the desktop website is 4701. I double-checked the tagging of the desktop website and the mobile website, and the code in the Android App, and they are still valid.

Our test scripts for ADB also works fine, e.g. "adb shell am start -W -a android.intent.action.VIEW -d "fdbappindex://verlengde-weekends-2018-belgie" com.macjeryseydesign.android.mfdbapp" does open that specific Android screen.

The GSC Error Details for each page contains in section "3 Test The App" an ADB command that you can use to verify if it working correctly. That command gives is "adb shell am start -a android.intent.action.VIEW -d http://www.feestdagen-belgie.be/verlengde-weekends-2018-belgie com.macjeryseydesign.android.mfdbapp". It is a surpriuse that it uses the HTTP URI Scheme (http://), although I'm using a custom URI scheme (fdbappindex://) for the App Index.

Questions

Can someone please help me to identify what is happening because I cannot find the reason for receiving that GSC Message. The tests for the App Index pass for 100%.

And we definitely want to keep the App Index alive for that website/webap/app. It is such a great feature for our users that have the App installed.

Thanks for your time, Rolf.