Google experimenting with hiding URLs in Chrome
Summary: In an effort to make phishing attacks more evident to the user, Chrome Canary is taking a tip from iOS Safari, emphasizing the domain and hiding the rest of the URL. — Jake Archibald, a “developer advocate” for Chrome at Google …
Context & Ripple Effects
This isn't Chrome's first flirtation with de-emphasizing the address bar: back in 2011, reports surfaced that Google was serious enough about letting users kill Chrome's URL bar entirely to build it as an option. What changed by May 2014 was the rationale — the pitch shifted from minimalism to security, with Chrome Canary testing a borrowed-from-iOS-Safari treatment that emphasizes the domain and hides the rest of the URL to make phishing attempts more visible.
First-order effects
- Chrome Canary testers lose the full URL display in favor of a domain-forwarded bar, while Safari's model becomes the reference design other browsers must now weigh against.
- Phishing pages lose their most reliable disguise — a convincing-looking long path on a lookalike domain — because the user's attention is forced onto the registrable domain itself.
Second-order effects
- Rival browsers face pressure to match Safari and Chrome on domain emphasis or explain why they still show raw URLs, turning an interface choice into a security-marketing differentiator.
- Publishers, developers, and support workflows that rely on sharing or reading exact URLs gain friction, pushing demand for share buttons, canonical-link tools, and better copy-URL affordances.
Third-order effects
- If browsers keep abstracting away raw addresses, the URL stops being the primary trust signal users inspect directly and becomes infrastructure the browser interprets on their behalf — shifting anti-phishing responsibility from user vigilance to browser UI design.
The trend: Browser makers are progressively redesigning the address bar around interpreted security signals rather than raw URLs, with Apple's Safari setting the pattern Chrome is now following.