/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Google announces that Google AMP cache will display publisher URLs and drop the Google AMP URL prefix in search results, starting in the second half of 2018

Google announced today that it is well on its way to solving one of the most annoying (to publishers) “features” of AMP …

Search Engine Land Michelle Robbins

Context & Ripple Effects

When Google built Accelerated Mobile Pages as its answer to Facebook's Instant Articles, the deal was speed at a cost: since mid-2016, mobile search links have routed readers to the AMP copy hosted on Google's cache under a google.com/amp prefix, stripping publishers of their own URL in the address bar (links in mobile search defaulting to AMP versions). Publishers have treated that lost branding and analytics visibility as one of AMP's most resented trade-offs.

This announcement removes that cost: from the second half of 2018, the AMP cache will display the publisher's URL instead of the Google prefix. It lands alongside Google's other concession to publisher complaints — the content-parity requirement taking effect in February that stops AMP pages from being thin teasers — together signaling Google defending AMP adoption rather than expanding its reach.

First-order effects

  • Publishers regain their domain name in the browser when readers arrive via AMP results, restoring the URL-level branding and direct-traffic attribution the google.com/amp prefix had taken away.

Second-order effects

  • With the two most-cited objections addressed — stolen URLs and teaser pages — publishers who held back from AMP have less reason to, which feeds more inventory into the AMP ad formats Google detailed back in early 2016 (ads launching in AMP search results).

Third-order effects

  • The trajectory runs from special-cased format toward ordinary fast page: once the cache hides itself behind publisher URLs, the remaining justification for AMP's privileged treatment erodes — a path that ends with Google later removing AMP's search-ranking preference entirely while staying 'fully committed' to the tech (the 2020 end of preferential rankings).

The trend: Google is progressively dissolving AMP's separate identity — from walled cache to publisher-branded URLs to rank-neutral treatment — trading the format's exclusivity for continued publisher participation.

Discussion

  • @cramforce Malte Ubl on x
    You don't like http://google.com/amp URLs? Neither do we And so we are making the changes to no longer need them while retaining the performance & privacy benefits of AMP. Read this post for details & thanks so much for all the feedback! https://amphtml.wordpress.com/ ...
  • @robpegoraro Rob Pegoraro on x
    Finally! Now can Apple please fix its source-obscuring Apple News addresses? http://twitter.com/...
  • @ia @ia on x
    “We are huge fans of meaningful URLs ourselves and recognize that this isn't ideal.” Huge fans? Who wrote this? http://twitter.com/...