Google AMP Is Live. Should a Luxury Retailer Care?

Posted by Sean on February 26, 2016

This week Google started showing AMP pages in its mobile search results. If you search for a news story on your phone, you’ll now see a carousel of articles near the top with a little lightning bolt on them, and when you tap one it opens more or less instantly. It’s genuinely fast. I’ve been tapping through stories just to watch them load.

AMP, Accelerated Mobile Pages, is an open-source project Google announced last October. The idea is a stripped-down version of HTML with strict rules about what you can and can’t use: very limited JavaScript, a fixed set of components, images loaded in a particular way. Pages built to that spec can be cached and served by Google, which is a big part of why they feel so quick.

The obvious question for anyone outside publishing is whether this is coming for the rest of us. Here’s where I’ve got to.

What it does right now

At the moment the visible benefit is for news. The carousel shows articles from publishers, and that’s where the AMP format is being pushed hardest. Google has said AMP itself isn’t a ranking signal, and the lightning bolt is mostly a reassurance to the user that the page will load fast.

For an ecommerce site, there’s no carousel to get into and no special treatment in the normal results today. So the direct, short-term benefit of building AMP product pages is close to nothing.

Why I’m still paying attention

I can’t see Google putting this much effort into a format and then leaving it in the news vertical. Speed on mobile has been a theme for a couple of years now, the mobile-friendly update last spring made it explicit, and AMP feels like the next step in that direction. I’d be surprised if we don’t see it extended in some form beyond news before long.

It’s also a fairly blunt reminder of how slow most mobile sites are. Ours included, if I’m honest. Tapping from an AMP news story to an ordinary retail product page is a bit of a shock; you notice the wait in a way you didn’t before.

The luxury problem

This is where it gets awkward for us. A luxury product page is built to do more than list a price. High-resolution photography from every angle, zoom, sometimes video, detail about the reference and its history, trust signals about authentication and warranty. That richness is a large part of how you justify asking someone to spend thousands of pounds through a phone screen.

AMP’s restrictions cut against almost all of that. Limited scripting means limited interactivity. The image handling is efficient but not exactly built for someone who wants to look closely at the dial. A checkout or an enquiry form on AMP is either impossible or very clunky right now.

So the trade is speed, which is real, against most of the interactivity that helps sell a watch. You also give up some control, because the page is served from Google’s cache rather than your own domain. That’s an easy swap for a news article. I’m much less sure about it for a page whose job is to make someone comfortable spending the price of a small car.

What I’d actually do

I’m not rebuilding anything this year on the strength of a news carousel. What I am doing is treating AMP as a sign of what Google wants, and working on the parts of that we control without adopting the format. That means:

  1. Getting the weight of our mobile product pages down. Image compression, fewer third-party scripts, lazy-loading anything below the fold.
  2. Looking hard at which tags and plugins we really need. Every tracking pixel added over the years costs a bit of load time, and nobody ever removes them.
  3. Keeping an eye on any sign of AMP being extended to non-news results, and being ready to test a template if that happens.

If you run a content-heavy site, a blog or editorial section, AMP is worth a test now, because that’s the part of the site that looks most like what Google is rewarding. For product pages I’d wait and see, and in the meantime make the normal pages faster, which we should have been doing anyway.

← Previous Draft Draft Index Next Draft →