20+ GOOGLE SEARCH CONSOLE ERRORS: HOW TO DETECT AND CORRECT THEM

1. DNS Errors
2. Server connectivity
3. Server error
4. Redirection error
5. The submitted URL returns a soft 404.
6. The submitted URL could not be found (404)
7. The submitted URL has been blocked due to another 4xx problem.
8. Indexed, not submitted in sitemap
9. The page has been indexed without content
10. Indexed, but blocked by robots.txt
11. The submitted URL contains the tag ‘noindex’.
12. URL sent returns an unauthorised request (401)
13. The submitted URL returns the error 403
14. Blocked by a page removal tool
15. Tracked: currently unindexed
16. Discovered: currently unindexed
17. Alternative page with appropriate canonical label
18. Duplicate: no canonical version has been indicated by the user.
19. Duplicate: Google has chosen a canonical version different from the user’s version.
20. Offers”, “review” or “aggregaterating” must be specified.
21. The “price” field is missing
22. The score is missing the maximum and minimum values.
23. The value of the property “reviewcount” must be positive
24. Clickable elements are too close to each other
25. No viewport has been defined
26. Content is wider than the screen
27. The text is too small to read

Error that occurs when the server tries to read the domain and cannot do so due to an error in the DNS. If you do not have the resources to fix it, you should contact your hosting provider.

This error appears when Google finds the server down when it tries to crawl our website. In Google Search Console, we will see a graph warning us of the errors that have been found over time.

It indicates that there has been a server error (5xx), so we must check that it is working and that there are no incidents in its operation.

Google tells us that there has been a redirection error in the URL and it has not been able to crawl it. We should check that there is no chain or loop of redirects or that the page is not redirected to a URL that is too long or incorrect.

Error telling us that the page returns a correct response code (200) but the content looks like a 404 page, so we should check and correct it if we want it to be indexed properly.

Google tells us that the URL we have submitted in the sitemap returns a 404 error, so it cannot index it. To fix it, we should remove the URL from the sitemap or check why the page is giving this error and correct it.

The URL could not be indexed as it is giving a 4xx response code (different from 401, 403 and 404). We will have to check what response code it is giving and why so that we can fix it and Google can index the page correctly. If we do not want to index it, we must remove it from the sitemap.

The URL has been indexed, but not sitemapped. To solve this, we must add it to the sitemap if we want to index it or add the noindex tag and block it in the robots.txt if we do not want to index it.

Google indexed the page, but could not find any content on it. We should check that the content is not being password-locked and that there are no rendering problems.

Indicates that this page has been submitted for indexing, but is blocked by the robotst.txt file. To solve it, we must remove it from the sitemap if we don’t want it to be indexed, or remove the block in the robotst.txt file if we want Google to index it.

It indicates that this page has been added to the sitemap for indexing, but at the same time, it is being indicated in the robots tag or HTTP header not to be indexed. To solve this, we must remove it from the sitemap if we don’t want it indexed, or remove the noindex from the robots tag (or directly remove the robots tag if we don’t use it for anything else) if we want it to be added to Google’s (and other search engines’) index.

Google tells us that the URL has been submitted correctly in the sitemap but that it returns a 401 error, so it is not accessible. To fix it, we should check this error and make sure we return a 200 or we should remove it from the sitemap if we don’t want it to be indexed.

It indicates that the submitted URL returns a 403 (forbidden) status error and cannot be indexed. If the URL must be accessible to all users, we must fix the 403 error. However, if we do not want it to be indexed, we must remove it from the sitemap.

It indicates that the URL has been removed from Google’s index using the Google Search Console tool and will not be indexed again. To solve this, we should add the noindex tag to the URL to prevent Google from indexing it again after 90 days.

Google has crawled the URL but has not yet been able to index it. Normally, this error appears in very new URLs. In this case, we will have to wait a few days for Google to index the page. If this does not happen, we will have to improve its content and linking so that Google considers it appropriate to index it.

Google has discovered the URL but has not yet crawled and indexed it. Normally, you will only have to wait a few days for the URL to be indexed. If this is not the case, we should check the logs to see that the Google robot can access the content without problems.

It indicates all the pages that have not been indexed because Google has detected the canonical tag pointing to another page. Therefore, Google follows the instruction to only index that page. In this case, we should either remove the URL from the sitemap if we do not want it to be indexed or remove the canonical tag if we want both URLs to be indexed.

Google has detected duplicate content on two pages and the user has not indicated a canonical tag on either page, so Google will decide which page to show and which not to show. In this case, we should correct the duplicate content or add a canonical tag on one of the two pages and remove the one we don’t want to index from the sitemap.

Google has decided that the best quality page, and therefore the one it will show, is not the canonical version, but another one. To correct this, we will have to use the URL inspector of Google Search Console to find out which URL has been selected by Google as canonical and study why.

The page does not contain these elements in the Schema markup and at least one of them should appear. To correct this, we will have to add them manually or configure the plugins we use to add the Schema markup to our page.

In the Schema markup of the page, the “price” field, which is necessary for product pages, for example, is not indicated. We shall add this field with the format “12.34”, without any currency symbol.

If we use product ratings, we must indicate what the minimum and maximum value is. This error tells us that we are not doing it and, therefore, that we should add it in our code. Normally, a value of 5 is used as maximum and a value of 1 (or 0) as minimum.

When using product ratings, we must indicate how many ratings we have. Logically, this value can never be negative. If we get a negative result, we must review the programming to correct the error.

This usability warning indicates that the clickable elements of our page are too close together, so the user may click one instead of the other by mistake. Usually refers to browsing on mobile devices. To correct this, we will need to redesign our page to add more separation between these buttons or links.

The page contains no viewport, which tells browsers how to adjust the page according to the type of device. To correct it, we will have to add this tag in the code of our page with the configuration we want. Related to this error, it is important not to use oversized images or fixed elements that make the page scroll horizontally, as this is not a very good practice.

This error indicates that the content is too wide and therefore horizontal scrolling is enabled on the page. To solve this problem, we must make sure that the page has the CSS well implemented to adapt to all the resolutions of the different devices.

Google tells us that the text on our page is too small to be displayed correctly, which makes it necessary to zoom in to read it correctly. To correct it, we simply have to make the text larger or configure it to adapt correctly according to the device.