> Google would know that you clicked on the link, and the URL you visited but that doesn't necessarily mean they know what the content on the page you requested

> Google would know that you clicked on the link, and the URL you visited but that doesn't necessarily mean they know what the content on the page you requested was. SE is only supposed to be used for public pages ("Cache-Control: public") which will be the same for every user. If they have the URL they can just request the page themselves to see the content. > It should always display where content is coming from. And with SE it does show where the content came from. Not the cache, which is irrelevant, but the original source. Or do you want it to show all the routers and CDN platforms which were involved in getting the data from the publisher's server to your PC? > At this point we really need a separate browser feature that shows us what server we're actually communicating with (host, cache, CDN, etc). We have that; it's called developer tools. As there can be many resources from many different sources making up a single page the results are too complex to reduce to a single line in the address bar, but they are available for those who are interested.