As expected, even though it took so long, Google finally announced on Google+ that they have revamped the Crawl Errors report for Android Apps in the Google Search Console.
Google said they updated and simplified the app crawl error types in the Google Search Console. Google said you will now see three error types in the App Crawl Status report including:
- Package not found (unchanged)
- URI unsupported (unchanged)
- Removed from index (new)
If you had any errors dating back to December 11th, you would now see them because Google refreshed the data to go back until then.
Personally, I see no errors for the Search Engine Roundtable apps, which I am a bit confused by, but I guess is a good thing. Here is a screen shot:
Google has a pretty detailed help page on the errors you may see, they include:
Package not found
Google could not find the Android Application Package (APK) in the Google Play store.
URI unsupported
The associated URI failed to launch the application.
Content mismatch
The content of the app page should be essentially the same as the content of the web page. The text need not be identical, but the topic should be the same, and users should be able to accomplish the same tasks on both the app and the web page. Determine whether you need to fix the content discrepancies, or the web-to-app mapping. A mismatch can also occur when a robots.txt file blocks resources on the app page, so the app page renders differently than the web page. Open the Blocked Resources Report to see whether your web page has blocked resources.
Back button violation
When a visitor deep-links from Google search results in a browser into a page in your app, the back button does not return them to the search results page. Google requires that a user be able to back out of an application page to the Google search results page in the browser.
Removed from index
There are pages in your app that do not meet our standards. This typically means that users cannot find what they were looking for on your app page, and so we omit the app link from our search results.
So I am error free, but I kind of wanted to share some live errors with you all.
Forum discussion at Google+.
