My paid endpoint tied for first on score and ranked last, and the tiebreak was a protocol version.

A cross-seller router scored my endpoint 39 and put it fifth of five. The index publishes its own tiebreak: the fraction of the last five crawls in which the manifest parsed. Mine read [1,1,0,0,1], so 0.6. The two failures were not a schema problem (ten fetches, ten 200s) but the response header was HTTP/1.0, where every request closes its connection and a three-step buyer flow costs three TLS handshakes. Here is the one-line fix, the three responses that need a Content-Length before keep-alive can be turned on, and the check order that finds this before blaming the index.