The inner workings of Google’s search engine is one of the internet’s best-kept secrets. They are extremely complicated and crucial systems that most outsiders don’t fully understand. However, a recent significant leak exposed thousands of internal Google Search API documents, offering a rare look into how Google ranks content and operates its search engine. The WITHIN Team has carefully reviewed these documents, uncovering key insights and exploring their implications for marketers and brands.
Questions have long been raised about the role of site authority in Google’s ranking algorithm. Although Google has previously denied using “site authority” as a measurement metric, the leaked documents suggest they do assess factors contributing to a website’s authority when ranking search results. While the exact impact on overall rankings and scoring remains unclear, the significance of site authority is supported by the longstanding importance of backlinks in Google’s algorithm. (Backlinks from reputable and relevant websites serve as a strong indicator of the quality and reliability of the content on the linked site.)
Despite common assumptions, clicks play a crucial role in your overall ranking within Google’s NavBoost system. (NavBoost uses past searches to predict which websites are most helpful for navigation-based queries — a search where the user’s main goal is to find a specific website or location.) The leaked documents highlight that clicks, click-through rates, and the engagement of those clicks are key factors in the NavBoost ranking system. It was also revealed that Google uses a squashing function to compress and normalize click data. This method helps prevent manipulation by ensuring that the data reflects genuine user behavior, rather than artificial boosts from bots or coordinated click efforts.
There’s been a long-standing debate about whether Google uses a “sandbox” or site segregation measures for new websites. In search-engine optimization (SEO) terms, a “sandbox” refers to a probationary period where new websites or those lacking trust signals are kept separate from the main search index so they don’t have to compete with established sites. The leaked documents suggest that Google might use various factors, including data from Chrome users who interact with the site, to assess a website’s trustworthiness. Essentially, these sites likely go through a review process before being fully integrated into the main search index and competing for higher rankings.
The recent data leak revealed various ranking systems employed by Google, each playing a unique role in the search and information processing. These systems are integrated through Spanner, a database management system that synchronizes and processes data across Google’s global network. Below is a detailed look at some of these key systems:
Note. This information was taken from Mike´s King Article titled “Secrets from the Algorithm: Google Search’s Internal Engineering Documentation Has Leaked.”
While the leak doesn’t provide an exact roadmap, it does provide valuable insights. Here’s how to leverage them going forward:
1. Create a Comprehensive SEO Content Strategy: Focus on creating high-quality, valuable content that is relevant to the page it is posted on and any pages it links to. Relevant, well-linked content can improve a page’s authority in Google’s algorithm, while incorrectly linked content can have the opposite effect. At WITHIN, our approach has been in line with this best practice, emphasizing the importance of relevance in both on-site and off-site content.
2. Enhance Page Engagement: Every piece of content and each page should provide users with exactly what they are searching for. At WITHIN, our focus on optimizing user experience and providing relevant content has proven effective in boosting engagement and maintaining or enhancing SERP standings. Keep in mind that poor engagement indicators, such as high bounce rates and low interaction rates, can negatively impact your SERP rankings, thus reducing visibility and site traffic.
3. Optimize Site Navigation: Implement structured site navigation to clearly define hierarchy, categorize content, and guide users effectively. WITHIN’s approach to building clear and effective navigation has long supported these best practices, as it enhances user experiences while also helping Google’s bots efficiently find, crawl, and index your pages – which is crucial for maintaining your site’s ranking.
4. Manage Product Reviews: Google consistently highlights the importance of reviews, and the recent leak suggests that negative reviews can adversely affect search engine results page (SERP) indexing. At WITHIN, we guide our clients to adopt best practices for managing reviews, emphasizing thoughtful responses to negative feedback, which can improve the customer’s experience and potentially result in more positive reviews. Additionally, ensure all reviews on your site are properly displayed and use structured data to accurately communicate this information to Google’s bots.
5. Develop Localized SEO Strategies: Tailor your SEO strategies so that users can easily find your products or services in their local area. Ensure your website includes language options for the countries you serve and that stock and inventory information is up-to-date for each e-commerce site location. Consistently maintaining your business’s name, address, and phone number across all directories is crucial to boost local SEO as well. At WITHIN, integrating these practices into our clients’ strategies is standard, ensuring they align with local requirements and the latest industry insights.
6. Build Authority with Links: WITHIN has always advocated for adopting ethical (or “white hat”) strategies to create valuable content that naturally attracts more links to your site. Supplementing these efforts with performance PR and sponsored content can boost your brand’s visibility. We understand that these strategies are crucial for gaining high-quality backlinks and improving your site’s authority — key factors in Google’s ranking algorithm. Be aware that Google closely watches these practices, and manipulating them could lead to penalties.
7. Optimize Title Tags and Click Rates: The recently released documents highlight the importance of title tags in search result determinations, emphasizing the need for optimized title tags to ensure Google indexes your pages accurately. Additionally, click-through rates have been deemed a crucial metric for user engagement within Google’s algorithm, underscoring the importance of crafting compelling titles that drive clicks. At WITHIN, optimizing these elements has always been a core practice, validated further by the latest leaks.
8. Create Concise, Valuable Content: We have always advised our clients to create concise and original content, which not only aligns with Google’s preferences but also enhances user engagement and comprehension. When creating content for SEO, consider these three key points:
At WITHIN, we have always prioritized understanding as much as possible about SERPs and the essential strategies for driving website traffic. We take pride in our proactive approach to SEO, from managing reviews and optimizing navigation to building authority through ethical link-building practices.
While the leaked documents offer a rare look into Google’s ranking algorithms, they ultimately reinforce the core principles of user-centric SEO. The key takeaways are clear: prioritizing user experience with high-quality content, optimized navigation, and ethical practices is essential for long-term success. These documents confirm that Google’s systems are designed to prevent manipulation and reward websites that genuinely meet user needs. By partnering with SEO experts like the team at WITHIN, and focusing on genuine user benefits rather than trying to manipulate Google’s algorithms, you can position your brand for success.
Get industry insights and news directly to your inbox.
Thank you. Check your email for details on your request.
Cookie | Duration | Description |
---|---|---|
__hssrc | session | This cookie is set by Hubspot whenever it changes the session cookie. The __hssrc cookie set to 1 indicates that the user has restarted the browser, and if the cookie does not exist, it is assumed to be a new session. |
checkForPermission | 10 minutes | This cookie is set by Beeswax to determine whether the user has accepted the cookie consent box. |
cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
CookieLawInfoConsent | 1 year | Records the default button state of the corresponding category & the status of CCPA. It works only in coordination with the primary cookie. |
elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
JSESSIONID | session | The JSESSIONID cookie is used by New Relic to store a session identifier so that New Relic can monitor session counts for an application. |
viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
Cookie | Duration | Description |
---|---|---|
__cf_bm | 30 minutes | This cookie, set by Cloudflare, is used to support Cloudflare Bot Management. |
__hssc | 30 minutes | HubSpot sets this cookie to keep track of sessions and to determine if HubSpot should increment the session number and timestamps in the __hstc cookie. |
bcookie | 2 years | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
bscookie | 2 years | LinkedIn sets this cookie to store performed actions on the website. |
lang | session | LinkedIn sets this cookie to remember a user's language setting. |
lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
Cookie | Duration | Description |
---|---|---|
_uetsid | 1 day | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
_uetvid | 1 year 24 days | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
Cookie | Duration | Description |
---|---|---|
__hstc | 1 year 24 days | This is the main cookie set by Hubspot, for tracking visitors. It contains the domain, initial timestamp (first visit), last timestamp (last visit), current timestamp (this visit), and session number (increments for each subsequent session). |
__lotl | 5 months 27 days | This cookie is set by Lucky Orange to identify the traffic source URL of the visitor's orginal referrer, if any. |
_ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
_gcl_au | 3 months | Provided by Google Tag Manager to experiment advertisement efficiency of websites using their services. |
_gd_session | 4 hours | This cookie is used for collecting information on users visit to the website. It collects data such as total number of visits, average time spent on the website and the pages loaded. |
_gd_svisitor | 2 years | This cookie is set by the Google Analytics. This cookie is used for tracking the signup commissions via affiliate program. |
_gd_visitor | 2 years | This cookie is used for collecting information on the users visit such as number of visits, average time spent on the website and the pages loaded for displaying targeted ads. |
_gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
_hjAbsoluteSessionInProgress | 30 minutes | Hotjar sets this cookie to detect the first pageview session of a user. This is a True/False flag set by the cookie. |
_hjFirstSeen | 30 minutes | Hotjar sets this cookie to identify a new user’s first session. It stores a true/false value, indicating whether it was the first time Hotjar saw this user. |
_hjIncludedInPageviewSample | 2 minutes | Hotjar sets this cookie to know whether a user is included in the data sampling defined by the site's pageview limit. |
_lo_uid | 2 years | This cookie is set by Lucky Orange as a unique identifier for the visitor. |
_lo_v | 1 year | This cookie is set by Lucky Orange to show the total number of visitor's visits. |
_lorid | 10 minutes | This cookie is set by Lucky Orange to identify the ID of the visitors current recording. |
hubspotutk | 1 year 24 days | HubSpot sets this cookie to keep track of the visitors to the website. This cookie is passed to HubSpot on form submission and used when deduplicating contacts. |
IR_gbd | session | Impact Radius sets this cookie to store a unique ID which is used to identify the user's device, when they return to the websites that used the same network. |
Cookie | Duration | Description |
---|---|---|
__qca | 1 year 26 days | The __qca cookie is associated with Quantcast. This anonymous data helps us to better understand users' needs and customize the website accordingly. |
_fbp | 3 months | This cookie is set by Facebook to display advertisements when either on Facebook or on a digital platform powered by Facebook advertising, after visiting the website. |
_mkto_trk | 2 years | This cookie, provided by Marketo, has information (such as a unique user ID) that is used to track the user's site usage. The cookies set by Marketo are readable only by Marketo. |
B | 1 year | This Cookie is used by Yahoo to anonymously store data related to user's visits, such as the number of visits, average time spent on the website and what pages have been loaded. This data helps to customize website content to enhance user experience. |
bito | 1 year 1 month | This cookie is set by Beeswax for advertisement purposes. |
bitoIsSecure | 1 year 1 month | Beeswax sets this cookie for targeting and advertising. The cookie is used to serve the user with relevant advertisements based on real time bidding. |
fr | 3 months | Facebook sets this cookie to show relevant advertisements to users by tracking user behaviour across the web, on sites that have Facebook pixel or Facebook social plugin. |
mc | 1 year 1 month | Quantserve sets the mc cookie to anonymously track user behaviour on the website. |
MUID | 1 year 24 days | Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. |
test_cookie | 15 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
tuuid | 2 years | The tuuid cookie, set by BidSwitch, stores an unique ID to determine what adverts the users have seen if they have visited any of the advertiser's websites. The information is used to decide when and how often users will see a certain banner. |
tuuid_lu | 2 years | This cookie, set by BidSwitch, stores a unique ID to determine what adverts the users have seen while visiting an advertiser's website. This information is then used to understand when and how often users will see a certain banner. |
Cookie | Duration | Description |
---|---|---|
__pdst | 1 year | No description available. |
_an_uid | 7 days | No description available. |
_dc_gtm_UA-61749619-1 | 1 minute | No description |
_dlt | 1 day | No description |
_hjSession_1771567 | 30 minutes | No description |
_hjSessionUser_1771567 | 1 year | No description |
_nx-nocache | session | No description available. |
6suuid | 2 years | No description available. |
A3 | 1 year | No description |
ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/ | session | No description |
AnalyticsSyncHistory | 1 month | No description |
BIGipServerab44web-nginx-app_https | session | No description |
bounceClientVisit3783c | 30 minutes | No description |
bounceClientVisit3783v | 30 minutes | No description |
dgzsdl08v4 | 10 minutes | No description |
IR_11658 | session | No description |
li_gc | 2 years | No description |
tableau_locale | session | No description available. |
tableau_public_negotiated_locale | session | No description available. |
test | 1 year | No description available. |