Yahoo Makes Secure Search The Default
Yahoo has now joined Google in making all searches people do automatically go through a secure server, to help prevent eavesdropping by outsiders. Unlike Google, however, Yahoo has failed to make an important change to how “referrer” data is passed along …
Context & Ripple Effects
Yahoo's switch follows the template Google set when Firefox made Google secure search the default back in March 2012, which is when the industry first saw keyword referrals collapse into "not provided" in analytics reports. By moving its own searches onto HTTPS, Yahoo is standardizing the eavesdropping protection across the two biggest engines rather than leaving it as a Google differentiator.
The wrinkle is execution: where Google paired HTTPS with stripping query terms from referrer headers, Yahoo reportedly skipped that step, meaning destination sites can still see what users searched for. It also lands awkwardly for a company that took flak in October 2012 for resisting a "Do Not Track" default alongside its search partner Microsoft — see the earlier Do Not Track standoff — so privacy posture is again running ahead of privacy mechanics.
First-order effects
- Publishers and analytics tools continue receiving full keyword-level referrer data from Yahoo search traffic while equivalent Google traffic shows as "not provided", making Yahoo the only major engine preserving that signal.
- Webmasters who had written off organic keyword reporting after Google's 2012 change regain a partial data source, but only for the smaller share of queries that run through Yahoo.
Second-order effects
- Microsoft's Bing, already entangled with Yahoo through their search partnership, faces pressure to decide whether matching Google's strict referrer stripping or Yahoo's leakier approach better serves its own advertiser-and-publisher relationships.
- Privacy advocates get a concrete inconsistency to point at — HTTPS that blocks outsiders but still hands the destination site the query — which raises the reputational cost of partial encryption rollouts.
Third-order effects
- If HTTPS-by-default becomes table stakes for every major engine, referrer handling shifts from a technical detail to a competitive lever, and the industry moves structurally toward encrypted search where keyword visibility for site owners depends on each engine's policy choices rather than any shared standard.
The trend: Search engines are converging on HTTPS-by-default, turning how much referrer data survives the encryption into the new competitive fault line between engines and the main determinant of what site owners can still measure.