Crawl Status report (mobile apps)
The Crawl Status report for apps shows crawl errors that Googlebot encountered when crawling your mobile app, as well as the number of app pages successfully indexed by Google. For crawl errors, the report shows where these errors were encountered, and suggestions for fixing these errors.
Looking for the Crawl Errors report for websites?
Using the report
The landing page of the Crawl Status report contains a chart showing both the total number of crawl errors and the number of app pages indexed over time, and a table that lists errors by type. Note that the error counts are estimates based on a sampling of your app's pages.
- To see which pages are affected by a specific error, click on an error row in the errors table to drill down to see details for that error. This subpage shows an incidence graph of that error over time, and list of a sampling of pages affected by that error.
- Click on an affected page to see a list of steps to fix that error on that page.
App crawl errors
The report can show the following error types:
Google could not find the Android Application Package (APK) in the Google Play store.
Ensure that you have registered your application in the Google Play store and that your Search Console property uses the exact same package ID as the Google Play store. Read more about App Indexing for Google Search.
The associated URI failed to launch the application.
- Make sure your Android manifest supports HTTP URLs. You must specify intent filters in your manifest that show how to reach specific content inside your app. See Add HTTP URL support to your app. Click any URI you want to troubleshoot to see the details page. From there, you can open the URL, which provides the ADB command to conveniently troubleshoot URIs with your emulator.
- Make sure that the package ID in all URLs is spelled exactly as registered in Google Play.
- Troubleshoot URIs with the Android Bridge Driver command. Click any URI you want to troubleshoot to see the details page. From there, you can open the app URL, which provides the ADB command to conveniently troubleshoot URIs with your emulator.
There is a difference in content between the app page and the associated web page.
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.
- Ensure that the general content of your app page matches that of the corresponding web page. If your application page differs too much from your web page content, Google might not surface your app's URL. If this is the case, update your app content to better correspond to your web page content.
- Ensure that you are mapping the app URI to the intended web URL, wherever you handle that mapping.
- You might also check that Google's view of the page is not different from the user's view of the page, by using the Fetch as Google tool for both the web page and the app page.
Your app page seems to be associated with the entirely wrong web page; for example, the web page is about dachshunds, but the app page is a Google Play installation page. This is a similar to the "content mismatch" error, but the degree of difference is much greater, and we think that you made a mistake in your association.
To fix:Ensure that you are mapping the intended app URI to the intended web URL.
The app page at the given URI cannot be opened for some reason (for example, it causes the app to crash).
Ensure that the URI shown can be opened by your mobile app.
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.
Ensure that a user clicking a back button in the app can return to the web search results page.
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.
Use Fetch as Google to see how Google sees your app page. If you notice any obvious problems, fix them. Google periodically recrawls app pages, so if your issue is fixed, it should reappear in the index.