Google announces support for Signed Exchanges in Chrome, which will show the original, correct URL for a page in the address bar for AMP pages
It's only supported on Chrome right now — When you click a link on your phone with a little lightning bolt next to it in Google search, you're getting something in the AMP format.
Context & Ripple Effects
Since Google began routing mobile search clicks to AMP versions of pages in 2016, publishers have chafed at one detail: the address bar showed a Google-hosted URL, not their own. The fixes so far have been cosmetic — an anchor button added to AMP pages so readers could see and share the real link, and a promised switch to display publisher URLs in the AMP cache.
Signed Exchanges attack the problem at the protocol level: Chrome can verify that a page served from Google's infrastructure is genuinely the publisher's content, so the browser can safely display the original URL. The announcement matters because it removes the main technical excuse for the google.com/amp prefix — though only on Chrome, which leaves every other browser still showing the old behavior.
First-order effects
- Publishers whose traffic flows through Google's AMP cache now see their own URLs appear in Chrome's address bar on Android, restoring brand attribution and shareability without changing how pages are delivered.
- The change applies only to Chrome, so Firefox, Safari, and other browsers continue displaying Google-hosted AMP URLs for the same clicks.
Second-order effects
- Browser vendors that built features around user frustration with AMP URLs lose part of their pitch — Brave's De-AMP, which bypasses Google-hosted pages entirely, was answering the same complaint Signed Exchanges now defuses on Chrome.
- Publishers weighing whether AMP's speed benefit justifies handing delivery to Google get a stronger case for staying in the program, since the attribution objection shrinks where Chrome dominates.
Third-order effects
- If signed-content verification becomes standard across browsers, the line between 'the publisher's site' and 'a copy served by a platform' blurs structurally: platforms can host and serve content while browsers attest its origin — shifting trust from domain names to cryptographic signatures.
The trend: Google has spent three years incrementally conceding the URL-attribution fight over AMP, moving from cosmetic patches toward protocol-level proofs that let platforms serve content without erasing the publisher's identity.