The Google Search Console’s Coverage error report is very helpful but can be confusing. What do each of these errors mean? What should you do about them?
Google does not index pages listed as an error in it’s coverage report. If you want Google to index these pages, you’ve got some things to fix.
Something happened with your server when Google last requested this page.
Sometimes things just happen, and you can’t do anything about it. If you find a lot of 5xx errors, you might need to upgrade to a better web host.
There might be a loop of very long, daisy-chain of redirects for this page. Google stopped following these redirects and has kicked you page out of the index.
Trace the chain of redirects and fix them so they go immediately to the destination URL. A tool like http://redirectdetective.com/ can help you figure this out.
These errors are now reported under the “indexed, though blocked by robots.txt” warning in Search Console.
If you want this page in the index. change your robots.txt file to allow Google to view the page. Google’s robots.txt checker tool can help see which line in your robots.txt file is causing the problem.
A robots meta tag on your site is telling Google not to index this page.
If you want this page in the index, you need to remove this tag from the HTML of your page.
Google thinks you meant this page to be a 404 error. This is likely because there’s little to no content on the page. As a result, it’s not being indexed.
If you want this page indexed by Google, add more and unique content to the page. If you don’t care, just move on.
To view this page, a visitor needs permission. The Googlebot does not have permission, so the page is not in its index.
If you want the page indexed, you’ll need to grant Google permission to view the page.
You submitted a page (either through a sitemap or through an internal link) to Google but it doesn’t exist.
If the page no longer exists, remove it from your XML sitemap. If it should be live, you need to re-add it.
This is a catch-all for other problems Google encountered while viewing this page.
Who knows? This could be many different things. You’re going to have to check this out on a case-by-case basis.
To learn more, check out Google’s documentation on these errors: https://support.google.com/webmasters/answer/7440203