Hocalwire Daily Roundup | Google To Clarify E-E-A-T & Quality Rater Guidelines Documentation.
- Today's HDR Update for 7 Feb, 2024
- 1) Google To Clarify E-E-A-T & Quality Rater Guidelines Documentation.
- 2) Google Case Study Reveals Search Console Evolution Via APIs
- 3) Google Sitemaps Bug With Hyphenated File Names
Google is taking steps to clarify its E-A-T (Expertise, Authoritativeness, Trustworthiness) and Quality Rater Guidelines documentation, aiming to provide clearer guidance for webmasters and content creators. Additionally, a recent Google case study highlights the evolution of Search Console through the use of APIs, showcasing advancements in data accessibility and functionality. However, a bug related to hyphenated file names has been identified in Google Sitemaps, potentially impacting website indexing and visibility.
Google To Clarify E-E-A-T & Quality Rater Guidelines Documentation
Google's Search Liaison, said we should expect to see more clarification from Google on its creating helpful content page, specific to the section "Get to know E-E-A-T and the quality rater guidelines
Excellent content is ranked by Google using a variety of automatic factors. Our systems look for the most helpful stuff and then rank it accordingly. To achieve this, they identify a variety of characteristics that can assist in determining which content exemplifies the elements of E-E-A-T, or experience, expertise, authoritativeness, and trustworthiness.
Google Case Study Reveals Search Console Evolution Via APIs
Google's case study shows how APIs can change what it means to use Search Console and evolve how it's accessed in the future.
A recent Google case study demonstrates how data may be examined and changed inside a content management system or a paid SEO dashboard thanks to Search Console APIs. Despite being a case study, the post ends with a call to action that describes how Google is leveraging APIs to change the search console from a SaaS to a data stream that can be edited in any GUI you choose.
Google Sitemaps Bug With Hyphenated File Names
Google might be having some weird bug with XML sitemap files that have hyphens within the final name. So if your sitemap file name is /sitemap-10.xml it will trigger a "couldn't fetch" error, but using /sitemap10.xml with the same file will not trigger any errors. This error shows up in the Google Search Console sitemaps section.
That's all folks for the day from the Hocalwire Team. We will get back with more updates tomorrow!!
If you want to reach out to Hocalwire to learn about our awesome Newsroom CMS, reach us by clicking here.