{"id":2216,"slug":"google-search-pipeline-genuine-unknowns","title":"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","kind":"reference","scope":"business","status":"internal","audiences":["kevin","candid-team"],"topics":["google-search-pipeline"],"reference_body":"**Claim:** What is genuinely unknown / what Google won't disclose:\n\n- **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.\"\n- **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.\n- **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.\n- **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.\"\n- **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.\n\n**Source:** Compass_artifact research document; named Google representatives (Splitt) on render-queue opacity.\n\n**Confidence:** High on enumeration of unknowns. The honest framing is exactly that they ARE unknown.\n\n**Caveat:** When a vendor claims to have decoded any of these, the appropriate response is skepticism, not curiosity.","rationale_body":null,"metadata":null,"links":{"outgoing":[],"incoming":[{"slug":"research-brief-google-search-lifecycle-june-2026","title":"Research brief: the lifecycle of a website in Google Search — from launch to mature standing and the perpetual re-evaluation that follows (June 2026)","kind":"reference","scope":"business","link_type":"relates-to"},{"slug":"research-brief-launch-build-technical-foundation-june-2026","title":"Research brief: the launch-build technical foundation — what the technology must get right before a new site can be found (June 2026)","kind":"reference","scope":"business","link_type":"relates-to"},{"slug":"launch-build-technical-foundation-genuine-unknowns","title":"Genuine unknowns in the launch-build technical foundation — Google publishes no numerical weightings; PageRank-flow magnitude unquantified; render-queue behavior for new low-authority sites under-measured; AI-surface signal weighting undisclosed; CWV thresholds shift","kind":"reference","scope":"business","link_type":"relates-to"},{"slug":"research-brief-new-site-timing-benchmarks-june-2026","title":"Research brief: how long does it actually take a new website to move through Google's pipeline — a methodology-graded benchmark report (June 2026)","kind":"reference","scope":"business","link_type":"relates-to"}]},"created_at":"2026-06-25T15:19:39.341Z","updated_at":"2026-06-25T17:07:10.774Z"}