A search marketer named Erfan Amizi brought them to Rand Fishkin’s attention<\/a>, and we analyzed them<\/a>. <\/p>\n Pandemonium ensued.<\/p>\n As you might imagine, it’s been a crazy 48 hours for us all and I have completely failed at being on vacation.<\/p>\n Naturally, some portion of the SEO community has quickly fallen into the standard fear, uncertainty and doubt spiral.<\/p>\n Reconciling new information can be difficult and our cognitive biases can stand in the way<\/a>. <\/p>\n It’s valuable to discuss this further and offer clarification so we can use what we’ve learned more productively. <\/p>\n After all, these documents are the clearest look at how Google actually considers features of pages that we have had to date. <\/p>\n In this article, I want to attempt to be more explicitly clear, answer common questions, critiques and concerns and highlight additional actionable findings.<\/p>\n Finally, I want to give you a glimpse into how we will be using this information to do cutting-edge work for our clients. The hope is that we can collectively come up with the best ways to update our best practices based on what we’ve learned.<\/p>\n Let’s start by addressing what people have been saying in response to our findings. I’m not a subtweeter, so this is to all of y’all and I say this with love. 😆<\/p>\n No, in large part, you did not.<\/p>\n Generally speaking, the SEO community has operated based on a series of best practices derived from research-minded people from the late 1990s and early 2000s. <\/p>\n For instance, we’ve held the page title in such high regard for so long because early search engines were not full-text and only indexed the page titles.<\/p>\n These practices have been reluctantly updated based on information from Google, SEO software companies, and insights from the community. There were numerous gaps that you filled with your own speculation and anecdotal evidence from your experiences. <\/p>\n If you’re more advanced, you capitalized on temporary edge cases and exploits, but you never knew exactly the depth of what Google considers when it computes its rankings. <\/p>\n You also did not know most of its named systems, so you would not have been able to interpret much of what you see in these documents. So, you searched these documents for the things you understand and concluded that you know everything here.<\/p>\n That is the very definition of confirmation bias.<\/p>\n In reality, there are many features in these documents that none of us knew.<\/em> <\/p>\n Just like the 2006 AOL search data leak<\/a> and the Yandex leak<\/a>, there will be value captured from these documents for years to come. Most importantly, you also just got actual confirmation<\/strong> that Google uses features that you might have suspected. There is value in that if only to act as proof when you are trying to get something implemented with your clients.<\/p>\n Finally, we now have a better sense of internal terminology. One way Google spokespeople evade explanation is through language ambiguity. We are now better armed to ask the right questions and stop living on the abstraction layer.<\/p>\n Sure. As an early and continued proponent of market segmentation in SEO<\/a>, I obviously think we should be focusing on our customers. <\/p>\n Yet we can’t deny that we live in a reality where most of the web has conformed to Google<\/a> to drive traffic.<\/p>\n We operate in a channel that is considered a black box. Our customers ask us questions that we often respond to with “it depends.” <\/p>\n I’m of the mindset that there is value in having an atomic understanding of what we’re working with so we can explain what it depends on<\/em>. That helps with building trust and getting buy-in to execute<\/a> on the work that we do. <\/p>\n Mastering our channel is in service of our focus on our customers.<\/p>\n Skepticism in SEO is healthy. Ultimately, you can decide to believe whatever you want, but here’s the reality of the situation:<\/p>\n I can say with absolute confidence<\/strong> that the leak is real and has been definitively verified in several ways, including through insights from people with deeper access to Google’s systems. <\/p>\n In addition to my own sources, Xoogler Fili Wiese<\/a> offered his insight on X<\/a>. Note that I’ve included his call out even though he vaguely sprinkled some doubt on my interpretations without offering any other information. But that’s a Xoogler for you, amiright?<\/em> 😆<\/p>\n Finally, the documentation references specific internal ranking systems that only<\/em> Googlers know about. I touched on some of those systems and cross-referenced their functions with detail from a Google engineer’s resume.<\/p>\n Oh, and Google just verified it in a statement<\/a> as I was putting my final edits on this. <\/p>\n No doubt. <\/p>\n I’ll see you on page 2 of the SERPs while I’m having mine medium with cheese, mayo, ketchup and mustard.<\/p>\n So, let me get this straight: you think a marvel of modern technology that computes an array of data points across thousands of computers to generate and display results from tens of billions of pages in a quarter of a second that stores both clicks and impressions as features is incapable of performing basic division on the fly?<\/p>\n … OK.<\/p>\n I agree with this. We all have the potential to be wrong in our interpretation here due to the caveats<\/a> that I highlighted. <\/p>\n To that end, we should take measured approaches in developing and testing hypotheses based on this data. <\/p>\n The conclusions I’ve drawn are based on my research into Google and precedents in Information Retrieval, but like I said it is entirely possible that my conclusions are not absolutely correct.<\/p>\n No. <\/p>\n The misconfigured documentation deployment happened in March. There’s some evidence that this has been happening in other languages (sans comments) for two years<\/a>.<\/p>\n The documents were discovered in May. Had someone discovered it sooner, it would have been shared sooner. <\/p>\n The timing of AI Overviews has nothing to do with it. Cut it out.<\/p>\n This is immaterial. Based on the dates in the files, it’s at least newer than August 2023.<\/p>\n We know that commits to the repository happen regularly, presumably as a function of updated code. We also know that much of the documentation has not changed in subsequent deployments. <\/p>\n We also know that when this code was deployed, it featured exactly the 2,596 files we have been reviewing, and many of those files were not previously in the repository. Unless whoever\/whatever did the git push did so with out-of-date code, this was the latest version at the time.<\/p>\n The documentation has other markers of recency, like references to LLMs and generative features, which suggests that it is at least from the past year.<\/p>\n Either way, it has more detail than we have ever seen and is fresh enough for our consideration.<\/p>\n That is correct. I indicated as much in my previous article.<\/p>\n What I did not do was segment the modules into their respective service. I took the time to do that now.<\/p>\n Here’s a quick and dirty classification of the features broadly classified by service based on ModuleName:<\/p>\n Of the 14,000 features, roughly 8,000 are related to Search.<\/p>\n Sure.<\/p>\n It’s a list of variables with descriptions that gives you a sense of the level of granularity Google uses to understand and process the web.<\/p>\n If you care about ranking factors, this documentation is Christmas, Hanukkah, Kwanzaa and Festivus.<\/p>\n Why would I bury something and then encourage people to go look at the documents themselves and write about their own findings?<\/p>\n Make it make sense.<\/em><\/p>\n This is a choice and, perhaps, a function of me purposely not being prescriptive with how I presented the findings.<\/p>\n What we’ve learned should at least enhance your approach to SEO strategically in a few meaningful ways and can definitely change it tactically. I’ll discuss that below.<\/p>\n I’ve been asked a lot of questions in the past 48 hours, so I think it’s valuable to memorialize the answers here.<\/p>\n It’s all <\/em>very interesting to me, but here’s a finding that I did not include in the original article:<\/p>\n Google can specify a limit of results per content type.<\/strong><\/p>\n In other words, they can specify only X number of blog posts or Y number of news articles that can appear for a given SERP.<\/p>\n Having a sense of these diversity limits could help us decide which content formats to create when selecting keywords to target.<\/p>\n For instance, if we know that the limit for blog posts is three and we don’t think we can outrank any of them, then maybe a video is a more viable format for that keyword.<\/p>\n Search has many layers of complexity. Even though we have a broader view of things, we don’t know which elements of the ranking systems trigger them or why.<\/p>\n We now have more clarity on the signals and their nuances.<\/p>\n Andrew Shotland is the authority on that. He and his group at Local SEO Guide have begun to dig into things from that perspective<\/a>.<\/p>\n I have not dug into that, but there are 23 modules with YouTube prefixes.<\/p>\n Someone should definitely do and interpretation of it.<\/p>\n The simple answer is it’s hard to know.<\/p>\n I want to continue to emphasize the idea that Google’s scoring functions behave differently depending on your query and context. Given the evidence in the SERPs, there are different ranking systems that activate for different verticals.<\/p>\n To illustrate this point, the Framework for evaluating web search scoring functions<\/a> patent shows that Google has the capability to run multiple scoring functions simultaneously and decide which result set to use once the data is returned.<\/p>\n While we have many of the features that Google is storing, we do not have enough information about the downstream processes to know exactly what will happen for any given space. <\/p>\n That said, there are some indicators of how Google accounts for some spaces like Travel.<\/p>\n The QualityTravelGoodSitesData module has features that identify and score travel sites, presumably to give them a Boost over non-official sites.<\/p>\n I don’t know.<\/p>\n I also don’t know exactly how smallPersonalSite<\/strong> is defined or used, but I do know that there is a lot of evidence of small sites <\/a>losing most of their traffic<\/a> and Google is sending less traffic to the long tail of the web<\/a>.<\/p>\n That’s impacting the livelihood of small businesses<\/a>. And their outcry seems to have fallen on deaf ears.<\/p>\n Signals like links and clicks inherently support big brands. Those sites naturally attract more links, and users are more compelled to click on brands they recognize.<\/p>\n Big brands can also afford agencies like mine and more sophisticated tooling for content engineering, which allows them to demonstrate better relevance signals.<\/p>\n It’s a self-fulfilling prophecy, making it increasingly difficult for small sites to compete in organic search. <\/p>\n If the sites in question were considered “small personal sites,” then Google should give them a fighting chance with a boost that offsets big brands’ unfair advantage.<\/p>\n I don’t. <\/p>\n I think they generally are well-meaning folks who do the hard job of supporting many people based on a product that they have little influence over and is difficult to explain.<\/p>\n They also work in a public multinational organization with many constraints. The information disparity creates a power dynamic between them and the SEO community. <\/p>\n Googlers could, however, dramatically improve their reputations and credibility among marketers and journalists by saying “no comment” more often rather than providing misleading, patronizing or belittling responses like the one they made about this leak. <\/p>\n However, it’s worth noting that the PR respondent, Davis Thompson<\/a>, has been doing comms for Search for just the last two months, and I’m sure he is exhausted.<\/p>\n I was not able to find anything directly related to SGE\/AIO, but I have already presented a lot of clarity on how that works<\/a>. <\/p>\n I did find a few policy features for LLMs. This suggests that Google determines what content can or cannot be used from the Knowledge Graph with LLMs.<\/p>\n There is something related to video content. Based on the write-ups associated with the attributes, I suspect that they use LLMs to predict the topics of videos.<\/p>\n Some conversations I’ve had and observed over the past two days has helped me recontextualize my findings – and also dig for more things in the documentation.<\/p>\n Someone with knowledge of Google’s internal systems was able to answer that the Baby Panda references an older system and is not the Helpful Content Update. <\/p>\n I, however, stand by my hypothesis that HCU exhibits similar properties to Panda, and it likely requires similar features to improve for recovery.<\/p>\n A worthwhile experiment would be trying to recover traffic to a site hit by HCU by systematically improving click signals and links to see if it works. If someone with a site that’s been struck wants to volunteer as tribute, I have a hypothesis I’d like to test on how you can recover. <\/p>\n Derek Perkins and @SemanticEntity brought to my attention<\/a> on X that the leaks have been available across languages in Google’s client libraries for Java, Ruby and PHP.<\/p>\n The difference with those is that there is very limited documentation in the code.<\/p>\n Google is attempting to determine the amount of effort employed when creating content. Based on the definition, we don’t know if all content is scored this way by an LLM or if it is just content that they suspect is built using generative AI.<\/p>\n Nevertheless, this is a measure you can improve through content engineering<\/a>.<\/p>\n The significance of a page update impacts how often a page is crawled and potentially indexed. Previously, you could simply change the dates on your page and it signaled freshness to Google, but this feature suggests that Google expects more significant updates to the page.<\/p>\n According to the description of this feature, Penguin had pages that were considered protected based on the history of their link profile.<\/p>\n This, combined with the link velocity signals, could explain why Google is adamant that negative SEO attacks with links are ineffective. <\/p>\n We’ve heard that “toxic backlinks” are a concept that simply used to sell SEO software. Yet there is a badbacklinksPenalized feature associated with documents. <\/p>\n In the blog BlogPerDocData module there is a copycat score without a definition, but is tied to the docQualityScore. <\/p>\n My assumption is that it is a measure of duplication specifically for blog posts.<\/p>\n Although I haven’t come across anything suggesting that mentions are treated as links<\/a>, there are lot of mentions of mentions as they relate to entities.<\/p>\n This simply reinforces that leaning into entity-driven strategies with your content<\/a> is a worthwhile addition to your strategy.<\/p>\n Googlebot’s fetching mechanism is capable of more than just GET requests. <\/p>\n The documentation indicates that it can do POST, PUT or PATCH requests as well.<\/p>\n The team previously discussed POST requests<\/a>, but the other two HTTP verbs weren’t previously revealed. If you see some anomalous requests in your logs, this may be why.<\/p>\n We’ve long believed that leveraging UGC is a scalable way to get more content onto pages and improve their relevance and freshness. <\/p>\n This ugcDiscussionEffortScore suggests that Google is measuring the quality of that content separately from the core content. <\/p>\n When we work with UGC-driven marketplaces and discussion sites, we do a lot of content strategy work related to prompting users to say certain things. That, combined with heavy moderation of the content, should be fundamental to improving the visibility and performance of those sites.<\/p>\n We know that intent is a heavy component of Search, but we only have measures of this on the keyword side of the equation. <\/p>\n Google scores documents this way as well, and this can be used to stop a page from being considered for a query with informational intent.<\/p>\n We’ve worked with clients who actively experimented with consolidating informational and transactional page content, with the goal of improving visibility for both types of terms. This worked to varying degrees, but it’s interesting to see the score effectively considered a binary based on this description. <\/p>\n I’m excited to see how the documentation reverberates across the space. <\/p>\n Natzir’s Google’s Ranking Features Modules Relations: <\/strong>Natzir builds a network graph visualization tool<\/a> in Streamlit that shows the relationships between modules.<\/p>\n WordLift’s Google Leak Reporting Tool<\/strong>: Andrea Volpini built a Streamlit app<\/a> that lets you ask custom questions about the documents to get a report. <\/p>\n The power is in the crowd and the SEO community is a global team. <\/p>\n I don’t expect us to all agree on everything I’ve reviewed and discovered, but we are at our best when we build on our collective expertise. <\/p>\n Here are some things that I think are worth doing.<\/p>\n If you haven’t had the chance to dig into the documentation on HexDocs or you’ve tried and don’t know here to start, worry not, I’ve got you covered. <\/p>\n One thing that annoys me about HexDocs is how the left sidebar covers most of the names of the modules. This makes it difficult to know what you’re navigating to. <\/p>\n If you don’t want to mess with the CSS, I’ve made a simple Chrome extension<\/a> that you can install to make the sidebar bigger. <\/p>\n Here are some strategic things that you should more seriously consider as part of your SEO efforts. <\/p>\n If you are <\/em>already doing all these things, you were right, you do know everything, and I salute you. 🫡<\/p>\n SEO and UX need to work more closely together <\/strong><\/p>\n With NavBoost, Google is valuing clicks as one of the most important features, but we need to understand what session success means. <\/p>\n A search that yields a click on a result where the user does not perform another search can be a success even if they did not spend a lot of time on the site. That can indicate that the user found what they were looking for. <\/p>\n Naturally, a search that yields a click and a user spends 5 minutes on a page before coming back to Google is also a success. We need to create more successful sessions.<\/p>\n SEO is about driving people to the page, UX is about getting them to do what you want on the page. We need to pay closer attention to how components are structured and surfaced to get people to the content that they are explicitly looking for and give them a reason to stay on the site. <\/p>\n It’s not enough to hide what I’m looking for after a story about your grandma’s history of making apple pies with hatchets (or whatever recipe sites are doing these days). Rather, it should be more about providing the exact information, clearly displaying it, and enticing the user to remain on the page with something additionally compelling.<\/p>\n Pay more attention to click metrics<\/strong><\/p>\n We treat Search Analytics data as outcomes, but Google’s ranking systems treat them as diagnostic features. <\/p>\n If you rank highly and you have a ton of impressions and no clicks (aside from when SiteLinks throws the numbers off) you likely have a problem. <\/p>\n What we are definitively learning is that there is a threshold of expectation for performance based on position. When you fall below that threshold you can lose that position.<\/p>\n Content needs to be more focused <\/strong><\/p>\n We’ve learned definitively that Google uses vector embeddings to determine how far off given a page is from the rest of what you talk about. <\/p>\n This indicates that it will be challenging to go far into upper funnel content successfully without a structured expansion or without authors who have demonstrated expertise in that subject area. <\/p>\n Encourage your authors to cultivate expertise in what they publish across the web and treat their bylines like the gold standard that it is.<\/p>\n SEO should always be experiment-driven<\/strong><\/p>\n Due to the variability of the ranking systems, you cannot take best practices at face value for every space. You need to test, learn and build experimentation in every SEO program. <\/p>\n Large sites leveraging products like SEO split testing tool Searchpilot are already on the right track, but even small sites should test how they structure and position their content and metadata to encourage stronger click metrics. <\/p>\n In other words, we need to actively test the SERP, not just the site.<\/p>\n Pay attention to what happens after they leave your site<\/strong><\/p>\n We now have verification that Google is using data from Chrome as part of the search experience. There is value in reviewing the clickstream data from SimilarWeb and Semrush.<\/p>\n Trends provide to see where people are going next and how you can give them that information without them leaving you.<\/p>\n Build keyword and content strategy around SERP format diversity<\/strong><\/p>\n Google potentially limits the number of pages of certain content types ranking in the SERP, so checking the SERPs should become part of your keyword research. <\/p>\n Don’t align formats with keywords if there’s no reasonable possibility of ranking.<\/p>\n Tactically, here are some things you can consider doing differently. Shout out to Rand because a couple of these ideas are his.<\/p>\n Page titles can be as long as you want <\/strong><\/p>\n We now have further evidence that the 60-70 character limit is a myth. <\/p>\n In my own experience we have experimented with appending more keyword-driven elements to the title and it has yielded more clicks because Google has more to choose from when it rewrites the title.<\/p>\n Use fewer authors on more content<\/strong><\/p>\n Rather than using an array of freelance authors, you should work with fewer that are more focused on subject matter expertise and also write for other publications.<\/p>\n Focus on link relevance from sites with traffic<\/strong><\/p>\n We’ve learned that link value is higher from pages that prioritized higher in the index. Pages that get more clicks are pages that are likely to appear in Google’s flash memory. <\/p>\n We’ve also learned that Google highly values relevance. We need to stop going after link volume and solely focus on relevance.<\/p>\n Default to originality instead of long form<\/strong><\/p>\n We now know originality is measured in multiple ways and can yield a boost in performance. <\/p>\n Some queries simply don’t require a 5,000-word blog post (I know, I know). Focus on originality and layer more information in your updates as competitors begin to copy you.<\/p>\n Make sure all dates associated with a page are consistent<\/strong><\/p>\n It’s common for dates in schema to be out of sync with dates on the page and dates in the XML sitemap. All of these need to be synced to ensure Google has the best understanding of how hold the content is. <\/p>\n As you refresh your decaying content, make sure every date is aligned so Google gets a consistent signal.<\/p>\n Use old domains with extreme care<\/strong><\/p>\n If you’re looking to use an old domain, it’s not enough to buy it and slap your new content on its old URLs. You need to take a structured approach to updating the content to phase out what Google has in its long-term memory. <\/p>\n You may even want to avoid there being a transfer of ownership in registrars until you’ve systematically established the new content.<\/p>\n Make gold-standard documents<\/strong><\/p>\n We now have evidence that quality raters are doing feature engineering for Google engineers to train their classifiers. You want to create content that quality raters would score as high quality so your content has a small influence over the next core update. <\/p>\n It’s shortsighted to say nothing should change. Based on this information, I think it’s time for us to reconsider our best practices.<\/p>\n Let’s keep what works and dump what’s not valuable. Because, I tell you what, there’s no text-to-code ratio in these documents, but several of your SEO tools will tell you your site is falling apart because of it.<\/p>\n A lot of people have asked me how can we repair our relationship with Google moving forward. <\/p>\n I would prefer that we get back to a more productive space to improve the web. After all, we are aligned in our goals of making search better.<\/p>\n I don’t know that I have a complete solution, but I think an apology and owning their role in misdirection would be a good start. I have a few other ideas that we should consider.<\/p>\n I’ve seen some fantastic things come out of the SEO community in the past 48 hours. <\/p>\n I’m energized by the fervor with which everyone has consumed this material and offered their takes – even when I don’t agree with them. This type of discourse is healthy and what makes our industry special. <\/p>\n I encourage everyone to keep going. We’ve been training our whole careers for this moment.<\/p>\n Editor’s note: Join Mike King and Danny Goodwin at SMX Advanced<\/strong> for a late-breaking session exploring the leak and its implications. Learn more here.<\/a><\/em><\/p>\nReactions to the leak: My thoughts on common criticisms <\/h2>\n
‘We already knew all that’<\/h3>\n
‘We should just focus on customers and not the leak’<\/h3>\n
‘The leak isn’t real’<\/h3>\n
\n
![\"Fili](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/fili-wiese-x-correction.png.webp\")
<\/figure>\n‘This is a Nothingburger’<\/h3>\n
‘It doesn’t say CTR, so it’s not being used’<\/h3>\n
‘Be careful with drawing conclusions from this information’<\/h3>\n
‘The leak is to stop us from talking about AI Overviews’<\/h3>\n
‘We don’t know how old it is’<\/h3>\n
![\"Yoshi](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/yoshi-code-bot-version.png.webp\")
<\/figure>\n![\"Videocontentsearchgenerativepredictionfeatures\"](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/videocontentsearchgenerativepredictionfeatures.png.webp\")
<\/figure>\n‘This all isn’t related to search’<\/h3>\n
![\"Service](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/service-distribution-leaked-docs.png\")
<\/figure>\n‘It’s just a list of variables’<\/h3>\n
‘It’s a conspiracy! You buried [thing I’m interested in]’<\/h3>\n
‘This won’t change anything about how I do SEO’<\/h3>\n
FAQs about the leaked docs<\/h2>\n
What were the most interesting things you found?<\/h3>\n
What should we take away from this leak?<\/h3>\n
What are the implications for local search?<\/h3>\n
What are the implications for YouTube Search?<\/h3>\n
How does this impact the (_______) space?<\/h3>\n
![\"Web](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/web-scoring-functions.png.webp\")
<\/a><\/figure>\n![\"Quality](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/quality-travelgoodsitesdata.png.webp\")
<\/figure>\nDo you really think Google is purposely torching small sites?<\/h3>\n
![\"Referrals](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/referrals-top-170-sites-vs-long-tail.jpg.webp\")
<\/figure>\nDo you think Googlers are bad people?<\/h3>\n
Is there anything related to AI Overviews?<\/h3>\n
![\"Llmpolicymetadata\"](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/llmpolicymetadata.png.webp\")
<\/figure>\nIs there anything related to generative AI?<\/h3>\n
![\"Videocontentsearchgenerativetopicpredictionfeatures\"](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/videocontentsearchgenerativetopicpredictionfeatures.png.webp\")
<\/figure>\nNew discoveries from the leak<\/h2>\n
Baby Panda is not HCU<\/h3>\n
The leaks technically go back two years<\/h3>\n
![\"Derek](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/derek-perkins-x-contentwarehouse-github-2022.png.webp\")
<\/figure>\nThere is a content effort score maybe for generative AI content<\/h3>\n
![\"Contenteffort\"](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/contenteffort.png.webp\")
<\/figure>\nThe significance of page updates is measured<\/h3>\n
![\"Lastsignificantupdate\"](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/lastsignificantupdate.png.webp\")
<\/figure>\nPages are protected based on earlier links in Penguin<\/h3>\n
![\"Penguinearlyanchorprotected\"](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/penguinearlyanchorprotected.png.webp\")
<\/figure>\nToxic backlinks are indeed a thing<\/h3>\n
![\"Anchorcount\"](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/anchorcount.png.webp\")
<\/figure>\nThere’s a blog copycat score<\/h3>\n
![\"Copycatscore\"](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/copycatscore.png.webp\")
<\/figure>\nMentions matter a lot<\/h3>\n
![\"Mention](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/mention-name-profile-referent.png.webp\")
<\/figure>\nGooglebot is more capable than we thought<\/h3>\n
![\"Postdata\"](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/postdata.png.webp\")
<\/figure>\nSpecific measures of ‘effort’ for UGC <\/h3>\n
![\"Ugcdiscussioneffortscore\"](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/ugcdiscussioneffortscore.png.webp\")
<\/figure>\nGoogle detects how commercial a page is<\/h3>\n
![\"Commercialscore\"](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/commercialscore.png.webp\")
<\/figure>\nCool things I’ve seen people do with the leaked docs<\/h2>\n
![\"Google](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/google-ranking-features-modules-relations.png.webp\")
<\/figure>\nDirection on how to move forward in SEO<\/h2>\n
How to read the documents<\/h3>\n
\n
![\"Google](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/google-api-content-warehouse-version-5.png.webp\")
<\/figure>\n\n
![\"Hexdocs](\"https:\/\/searchengineland.com\/wp-content\/seloads\/2024\/05\/hexdocs-google-api-content-warehouse.png.webp\")
<\/figure>\nHow your approach to SEO should change strategically<\/h3>\n
How your approach to SEO should change tactically<\/h3>\n
Bottom line<\/h3>\n
How Google can repair its relationship with the SEO community<\/h2>\n
\n
Everybody keep up the good work<\/h2>\n
\n