Since the launch of the Index Coverage Report<\/a>, website owners are already sharing their feedback with Google about improvements they would like to see in the future.
Therefore, the changes to the index coverage report that will be available today are based on feedback from the webmaster community.
“Based on the feedback we have received from the community, we are offering significant improvements to the report. This way you will be better informed about problems that may prevent Google<\/a> from crawling and indexing your site.”<\/p>\n\n\n\n
![\"SEO](\"https:\/\/seo-marketing.koeln\/wp-content\/uploads\/2023\/09\/seo-audit.6458562697da5da907b7b01fc9c6cdc7.jpg.webp\")
<\/figure>\n\n\n\nChanges to the Search Console index coverage report<\/strong><\/h2>\n\n\n\nThe list of changes to the index coverage report in the Search Console includes the following:<\/p>\n\n\n\n
\n- The removal of the generic problem type of “crawl anomaly” – All crawl errors<\/a> are now assigned to a problem that contains a better solution.<\/li>\n\n\n\n
- Pages that have been submitted but blocked and indexed by robots.txt are now marked as “indexed but blocked” (warning) instead of “submitted but blocked” (error).<\/li>\n\n\n\n
- The addition of a new problem: “Indexed without content<\/a>” (warning).<\/li>\n\n\n\n
- Soft 404 reporting is now more accurate.<\/li>\n<\/ul>\n\n\n\n
This means there is now no more guesswork when it comes to crawl errors<\/a>, as the “crawl anomaly” problem has instead been replaced with specific problems and solutions.<\/p>\n\n\n\nWebsite owners will now clearly recognize and know if a page indexed by Google is blocked by robots.txt, because instead of “submitted<\/strong> but blocked” the message will now show “indexed<\/strong> but blocked”. It is a completely different thing whether a URL<\/a> has been registered or indexed and the report has now been updated to show this.<\/p>\n\n\n\nThe Soft 404 reports should therefore be more accurate. There is also a new problem called “indexed<\/a> without content”. Let’s take a closer look at this problem together in case it appears in one of your reports.<\/p>\n\n\n\nThis is what the Search Console help page tells us about indexed without content<\/strong>:<\/p>\n\n\n\n“This page appears in the Google index, but for some reason Google could not read the content<\/a>. Possible reasons for this are that your page may be obfuscated for Google or the page may be in a format that Google<\/a> cannot index. This is not a case of blocking by robot.txt.”<\/p>\n\n\n\n![\"GOOGLE](\"https:\/\/seo-marketing.koeln\/wp-content\/uploads\/2023\/09\/landscape.d595eb7b.einstellungen_auf_google_aenderungen.2bcf1e8dadb862da42415cb9c0eb0c66.jpg-1024x576.webp\")
<\/figure>\n\n\n\nSo if you encounter the problem indexed without content <\/strong>, this means that the URL<\/a> is in Google’s index, but the web crawler cannot view the content.
This could mean that you have inadvertently published a blank page. Another reason could be that there is an error on your site that is preventing Google from rendering the content<\/a>.<\/p>\n\n\n\nFor further assistance to fix the error without content indexed<\/strong>, our recommendation to all website owners is to run the affected page through the Google<\/a> URL check tool.
This is because the URL inspection tool renders the page as Google<\/a> perceives it. This can help to understand why the content is not visible to Google’s web crawlers.<\/p>\n\n\n\nThese changes are now displayed in the index coverage report. Site operators may now be able to recognize new types of errors or changes in the number of problems.<\/p>\n","protected":false},"excerpt":{"rendered":"
To better inform website owners about indexing issues, the Google Search Console index coverage report will receive a total of 4 updates. This index coverage report was first introduced in 2018 with the launch of the revamped Google Search Console and is still new compared to other reports offered by Google.Since the launch of the […]<\/p>\n","protected":false},"author":2,"featured_media":1851,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[114],"tags":[],"class_list":["post-8743","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-seo-blog-en"],"_links":{"self":[{"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/posts\/8743","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/comments?post=8743"}],"version-history":[{"count":3,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/posts\/8743\/revisions"}],"predecessor-version":[{"id":38628,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/posts\/8743\/revisions\/38628"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/media\/1851"}],"wp:attachment":[{"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/media?parent=8743"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/categories?post=8743"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/tags?post=8743"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
This means there is now no more guesswork when it comes to crawl errors<\/a>, as the “crawl anomaly” problem has instead been replaced with specific problems and solutions.<\/p>\n\n\n\n Website owners will now clearly recognize and know if a page indexed by Google is blocked by robots.txt, because instead of “submitted<\/strong> but blocked” the message will now show “indexed<\/strong> but blocked”. It is a completely different thing whether a URL<\/a> has been registered or indexed and the report has now been updated to show this.<\/p>\n\n\n\n The Soft 404 reports should therefore be more accurate. There is also a new problem called “indexed<\/a> without content”. Let’s take a closer look at this problem together in case it appears in one of your reports.<\/p>\n\n\n\n This is what the Search Console help page tells us about indexed without content<\/strong>:<\/p>\n\n\n\n “This page appears in the Google index, but for some reason Google could not read the content<\/a>. Possible reasons for this are that your page may be obfuscated for Google or the page may be in a format that Google<\/a> cannot index. This is not a case of blocking by robot.txt.”<\/p>\n\n\n\n So if you encounter the problem indexed without content <\/strong>, this means that the URL<\/a> is in Google’s index, but the web crawler cannot view the content. For further assistance to fix the error without content indexed<\/strong>, our recommendation to all website owners is to run the affected page through the Google<\/a> URL check tool. These changes are now displayed in the index coverage report. Site operators may now be able to recognize new types of errors or changes in the number of problems.<\/p>\n","protected":false},"excerpt":{"rendered":" To better inform website owners about indexing issues, the Google Search Console index coverage report will receive a total of 4 updates. This index coverage report was first introduced in 2018 with the launch of the revamped Google Search Console and is still new compared to other reports offered by Google.Since the launch of the […]<\/p>\n","protected":false},"author":2,"featured_media":1851,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[114],"tags":[],"class_list":["post-8743","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-seo-blog-en"],"_links":{"self":[{"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/posts\/8743","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/comments?post=8743"}],"version-history":[{"count":3,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/posts\/8743\/revisions"}],"predecessor-version":[{"id":38628,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/posts\/8743\/revisions\/38628"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/media\/1851"}],"wp:attachment":[{"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/media?parent=8743"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/categories?post=8743"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/seo-marketing.koeln\/en\/wp-json\/wp\/v2\/tags?post=8743"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/figure>\n\n\n\n
This could mean that you have inadvertently published a blank page. Another reason could be that there is an error on your site that is preventing Google from rendering the content<\/a>.<\/p>\n\n\n\n
This is because the URL inspection tool renders the page as Google<\/a> perceives it. This can help to understand why the content is not visible to Google’s web crawlers.<\/p>\n\n\n\n