A common tracking technique is to put personalized information in the ETag, e.g. ETag: W/your-login-id-plus-content-hash

Thus, to be truly stateless, the request would also have to prevent conditional GET requests (If-None-Match, If-Modified-Since)

From the Chrome anti-tracking team, we agree that SXGs should require mitigations for cross-site information flow. We think the suggestions here should be adopted, though of course details like how to trigger such a credential-less navigation still need to be worked out.

A minor quibble/note, the last two points as written require a distinct distributor origin per publisher origin, which seems off. (It even risks the SXG prefetch leaking the distributor origin via DNS and SNI.) I would suggest rephrasing it as: the path + query string of the navigation needs to be some specific deterministic function of the SXG target URL. For instance, https://distributor.example/.well-known/sxg/[some encoding or cryptographic hash of target URL].