Genuine unknowns in the Google Search pipeline — exact queue priority math, render-queue position, signal weightings, re-rendering triggers, whether/when a page will ever rank

Claim: What is genuinely unknown / what Google won't disclose:

• Exact crawl-queue priority math and the render-queue position — Splitt calls the render queue deliberately opaque; "there is not that much that you can do about rendering… in terms of changing the queue position."
• The weightings behind any signal — the 2024 leak listed attributes (including hostAge, siteAuthority, NavBoost-related click signals) but no weights, and Google cautioned against over-reading it. Whether/how each is currently used is not confirmed.
• Any precise timeline for launched → stably ranking. Google gives ranges and explicitly declines numbers; the "couple of months to half a year+" trust-accrual window is the closest on-record anchor and is itself hedged.
• The precise trigger heuristics for whether/when a page is re-rendered or re-evaluated — Splitt: "I still haven't fully grasped what exactly triggers the heuristics."
• Whether a given page will ever be indexed or rank at all — Google is explicit that indexing isn't guaranteed, ranking isn't guaranteed, and indexed pages can drop out over time.

Source: Compass_artifact research document; named Google representatives (Splitt) on render-queue opacity.

Confidence: High on enumeration of unknowns. The honest framing is exactly that they ARE unknown.

Caveat: When a vendor claims to have decoded any of these, the appropriate response is skepticism, not curiosity.