Google Site Wide Ranking Factors Decoded: Unmasking QualityNsrNsrData (New Site Rank)

Note: This is part 2 of 3 articles today on NSR. Part 1 is here. Part 3 is here. Note that this is not official advice from Google. It is SEO theory based on my own primary analysis of Google patents and code leaks. The Google API leak exposes data structures and protocol buffers, not the live executing C++/Elixir code or algorithmic weights. Take for example siteQualityStddev ; While the attribute exists, no one outside Google knows its exact mathematical multiplier in real-time query retrieval. Treat most leaked parameters similarly. Some parameters listed may be inactive or superseded in production.

When the 14,000-file Google Content Warehouse API leak exposed the internal plumbing of Google search, lots of the SEO industry suffered from a collective case of shiny-object syndrome. Commentators (even myself) fixated on clickstream metrics, sandboxing debates, and isolated feature flags, treating the repository like an unorganised garage sale.

Meanwhile, right in plain sight, the master switchboard for domain-wide trust and site quality sat largely undocumented by the mainstream news: QualityNsrNsrData.

For over a decade, Google’s public relations team maintained a firm party line: Google does not use a generalised, site-wide quality score; every page stands on its own merits. The API leak indicates that the picture is more complicated.

Through the New Site Rank (NSR) architecture, Google maintains a sophisticated telemetry engine that grades, chunks, and scores entire domains before individual pages ever compete in real-time retrieval.

This article, I think, is the first public compilation of this proto as the sitewide quality list. QualityNsrNsrData is the actual module that lists Google’s sitewide ranking signals (although not the only one).

QualityNsrNsrData is New Site Rank.

Part 1: The Evolution from a mental or isolated concept.

Fast forward to May 2024, and the GitHub API source code revealed that NSR had matured into a sprawling, production-grade telemetry pipeline.

2019 Slides to 2024 API Schema

To understand the weight of QualityNsrNsrData, we have to look backwards. In 2019, internal slide decks leaked to the public, introducing the concept of New Site Rank (NSR)—an evaluation layer designed to assess new and existing domains utilising human rater training patterns.

At the time, sceptics dismissed it as an experiment.

The QualityNsrNsrData module is the code-level manifestation of those early slides. It bridges historical intent with modern machine learning, translating abstract quality rater guidelines into concrete, automated code variables.

Part 2: Why the SEO Industry Missed the Big Picture

While automated scrapers indexed the module name immediately, very few analysts recognised QualityNsrNsrData as the holy grail of site-wide algorithmic control. Why did the broader industry drop the ball?

• The Confirmation Bias Trap: Because Google spokespeople repeatedly denied the existence of domain-wide quality metrics, most SEO professionals assumed site-wide penalties and scores were a myth.
• Information Overload: Sifting through thousands of complex Elixir and Python data schemas requires deep forensic engineering patience. Most commentators lacked the bandwidth to trace how individual modules execute upstream.
• Failure to Connect the Dots: Very few researchers bridged the historical gap between the 2019 NSR slide leaks and the 2024 API codebase.

We can now unlock this module for what it truly is: Google’s master control panel for systemic domain evaluation.

I missed it too until I started to investigate what NSR meant in the Google leak (I had put working out that until later; there was no obvious proof of what it signified in the leak).

Part 3: Anatomy of the Site-Wide Telemetry Engine

The architecture of QualityNsrNsrData is divided into distinct functional categories that dictate how a website is perceived by core ranking systems like Mustang.

1. Core NSR & Trust Metrics

• nsr: The primary numerical score assigned to a site chunk, grading overall domain authority and reliability.
• priorAdjustedNsr: A comparative baseline tracking whether a domain sits above or below the expected average for its specific content niche.
• nsrOverrideBid: An emergency manual switch (go/nsr-override-bid) enabling engineers to unconditionally override NSR during severe ranking anomalies or safety crises.

2. Statistical Variance and Consistency Checks

Google doesn’t just look at a site’s masterpiece articles; it evaluates systemic predictability:

• siteQualityStddev: Estimates the standard deviation (spread) of page-level quality ratings across the domain. High variance signals an erratic site that mixes great content with low-grade filler, dragging down baseline trust.
• chardVariance & nsrVariance: Statistical error models that measure how uniformly good or bad a site’s text content is across its entire URL structure.

3. Spam, AI Abuse, and Clutter Filters

• spambrainLavcScore: Direct integration with SpamBrain, evaluating site-level abuse, low quality, and security vulnerabilities.
• racterScores: Tied to internal Project Racter initiatives, identifying scaled, automated, low-value AI text generation.
• clutterScore: A penalty vector penalising domains flooded with excessive, distracting ads or aggressive UI pop-ups (go/clutter-v0).

4. Brand Affinity & Graph Topologies

• pnav & pnavClicks: Navigational query fractions measuring direct brand search volume and user loyalty.
• site2vecEmbeddingEncoded: Compact vector representations of the entire site’s semantic profile, optimised for fast retrieval in Google’s “superroot” architecture.
• sitePr: Modernised domain-level PageRank estimates tracking incoming link equity distribution.

Part 4: What QualityNsrNsrData Means for Modern SEO

The exposure of QualityNsrNsrData fundamentally shifts how we must approach technical and content strategy:

1. The Death of Mixed-Quality Content: Because variables like siteQualityStddev punish variance, publishing low-effort AI fluff alongside high-end journalism actively poisons the domain’s baseline trust score.
2. Systemic Health Over Isolated Optimisation: You cannot out-optimise a bad site architecture with keyword tweaks. Google evaluates the collective “content-DNA” of your site chunks.
3. The Necessity of Brand Building: High pnav and direct traffic fractions act as a defensive moat against core algorithm updates, proving real-world demand outside of algorithmic manipulation.

Reference: All QualityNsrNsrData Variables Explained

1. Core NSR & Scoring Metrics

2. Content Quality & Classifier Models

Here is a table for article, text quality, and domain focus metrics:

3. Statistical Variance & Consistency

4. Spam, Abuse & Machine-Generated Content

5. Video & Shopping Specific Models

6. Site Architecture, Chunking & Identifiers

7. Traffic, Engagement & Graph Topologies

8. Authority & Special Signals

Conclusion

The discovery of QualityNsrNsrData as Google’s list of core site-wide ranking signals is a watershed moment for search marketing. QualityNsrNsrData is the leaked Protocol Buffer in which Google stores its bundle site-level quality scores.

It is the closest thing the 2024 documents give us to a list of sitewide Google ranking signals in one place.

It proves that Google’s algorithm is not merely a decentralised collection of isolated page evaluations, but a unified ecosystem governed by systemic, site-wide trust metrics. For advanced SEOs, understanding this schema transforms the job from a guessing game of heuristics into precise engineering alignment.

---

Disclaimer: Note that this is not official advice from Google. It is an opinion. It is SEO theory based on my own primary analysis of Google patents and code leaks. Any article (like this) dealing with the Google Content Data Warehouse leak requires a lot of logical inference when putting together the framework for SEOs, as I have done with this article. I urge you to double-check my work and use critical thinking when applying anything about the leaks to your site. My aim with these articles is essentially to confirm that Google does, as it claims, try to identify trusted sites to rank in its index. The aim is to irrefutably confirm white hat SEO has purpose in 2026 – and that purpose is to build high-quality websites.

The Google API leak exposes data structures and protocol buffers, not the live executing C++/Elixir code or algorithmic weights. Take for example siteQualityStddev; While the attribute exists, no one outside Google knows its exact mathematical multiplier in real-time query retrieval. Treat most leaked parameters similarly. Some parameters listed may be inactive or superseded in production. Modern search models (like RankEmbedBERT) don’t use fixed C++ formulas at all. They rely on neural network weights trained on millions of interactions. You can’t “decode” a neural network’s decision-making just by looking at its input schema. Also note I only discuss sales, editorial and marketing-related attributes. I do not explore attributes tied to Abuse, Sensitive or Inappropriate classifiers in documents in any of my writings (and will not). (My thesis builds on this: “There was a leak of Google documents which named certain components of Google’s ranking system, but the documents don’t go into specifics of the curves and thresholds“ – The most direct and significant acknowledgement of this is from within the context of the DOJ’s antitrust litigation based on a call dated February 18, 2025, with Google Engineer HJ Kim). I view the leaks as an architectural map of possibilities, not a cheat code. I suggest you do the same. Feedback and corrections welcome.

Disclosure: I use generative AI when specifically writing about my own experiences, ideas, stories, concepts, tools, tool documentation or research. My tool of choice for this process is Google Gemini Pro 2.5 Deep Research and later models. I have over 25 years of experience writing about accessible website development and SEO (search engine optimisation). All content was conceived, edited, and verified as correct by me, Shaun Anderson, aka Hobo (and is under constant development). Corrections and contributions welcome. See my AI policy.