Google says links in mobile search results will soon take you to AMP version of page, if available, not the traditional HTML page
With yesterday's coverage of more rumours … Andrew Tarantola / Engadget : Google's speeding up mobile web search results for all sites Jordan Novet / VentureBeat : Google Search expands AMP support in developer preview Christopher Ratcliff / Search Engine Watch : Google AMP is coming to organic search results Nate Swanner / The Next Web : Google is bringing AMP to mobile search so it will be the new normal Duncan Jaffrey / Ausdroid : Google is getting ready to AMP Australia Mark Bergen / Recode : Google's speedy mobile publishing tool is now coming for the entire web Tweets: Nilay Patel / @reckless : By far the biggest news in a huge day for news. Google's Instant Articles competitor will take over mobile search http://www.theverge.com/... Amazon Dash / @anildash : Google AMP pages will now be displayed by default for all search results. We're back to WAP! http://www.theverge.com/...
Context & Ripple Effects
AMP launched in October 2015 as a stripped-down page format — restricting Javascript and banning tags like iframes — explicitly framed as Google's answer to Facebook's Instant Articles. Through 2016 Google staged the rollout: AMP pages got highlighted in mobile results in February, then the format expanded beyond news into site navigation and self-updating pages in April.
This announcement is the pivot from carrot to default: AMP stops being an opt-in badge and becomes where mobile search traffic actually lands. That makes AMP's constraints the de facto spec for the mobile web, and it sets up the publisher-abuse problem Google would later address with its content parity requirement for 2018.
First-order effects
- Publishers with AMP pages see their mobile search traffic routed to the AMP version automatically, while sites without AMP versions keep the traditional HTML page — making AMP adoption the price of competing for mobile clicks.
- Users land on pages that load faster but run under AMP's restricted format, so ad and analytics vendors serving those publishers must work within the constrained runtime.
Second-order effects
- Facebook's Instant Articles loses its differentiation: Google matches the fast-mobile-reading experience at search scale, pressuring publishers to pick a constrained format rather than build both.
- Publishers now maintain two versions of every page (AMP and canonical), doubling maintenance work and shifting power toward whoever controls the cache and rendering — Google.
Third-order effects
- If the pattern holds, search engines stop indexing the open web and start serving their own rendering of it, with publishers building to platform-specific specs to stay visible — the structural tension that later forced Google to mandate content parity between AMP and original pages.
The trend: Search is becoming a rendering platform: Google increasingly decides which version of a page users see, and publishers build to the platform's spec to stay in the results.