Google to Roll Out Accelerated Mobile Pages to Everyone, Get Your Content Ready Now

SMS Text
Google to Roll Out Accelerated Mobile Pages

Google announced its plans to roll out accelerated mobile pages in February 2016, following successful testing of the new technology.

The search giant first unveiled its AMP technology two months ago, touting it as an open-source content delivery platform that can load web pages instantly after being clicked on from a Google search.

Initially, this technology was tested with a select few publishers. Now, by late February, everyone will be able to take advantage of the new technology.

You don’t have to wait until then to get your content ready. You shouldn’t wait, either. According to Google’s John Mueller, this is going to be “next year’s hottest new website technology.”

Mueller also added that if you’re a web developer, you’re most certainly going to be asked about it. Whether you’re an SEO, a developer, or just website owner — it’s best to become acquainted with this new technology now and start implementing it.

Creating an Accelerated Mobile Page

To get started, create your first AMP page following the instructions and code provided by Google on this web page.

In the page linked to above, Google walks you through the simple steps of creating an AMP page. This consists of adding a piece of boilerplate code, adding a marked up image, and then styling the page using CSS.

When all your code and markup is in place, you can validate it using a tool provided by Google in the walkthrough. If the code validates, you can then publish your first AMP page.

From what I can tell, these are steps that will have to be followed for all content you wish to turn into AMP pages going forward. If you want a head start, you can start creating AMP pages now.

Google is encouraging publishers to get started as soon as possible, adding: “Content you publish to your sites today will be eligible to show up in the demo now, and soon in Google search.”

According to Mueller, a lot more information about the AMP project will be coming in the new year

Featured Image Credit: Ilin Sergey / Shutterstock.com

Matt Southern

Matt Southern

Lead News Writer
Matt Southern is the lead news writer at Search Engine Journal. His passion for helping people in all aspects of online marketing flows through in the expert industry coverage he provides.
Matt Southern
Get the latest news from Search Engine Journal!
We value your privacy! See our policy here.
  • http://www.bigskywords.com/ Greg Strandberg

    You need longer content. Just because it’s an update it doesn’t mean you have to shirk off.

    Of course, if that’s how you want to run your brand, SEJ, and if that’s how you want us to view your expertise, Matt, by all means, continue.

  • Roger Rogerson

    I might have to go read up on this, as it’s beginning to sound like a bundled/library approach.

    Of course, this makes learning to speed up a site a complete and utter waste of time, and means all the hours spent tweaking numerous sites to make them lighter and faster was also wasted.
    Wonderful.

  • http://www.refreshcartridges.co.uk/ Ryan Carson

    As far as I can see, there’s no support for forms on here, so I don’t see this being of relevance in it’s current state for e-commerce websites. I’m not keen on the idea of forking HTML in general but I guess we’ll see if this can really speed up web-pages over time.

    Currently it looks like they’ve reduced the number of allowable HTML elements and determined that AMP pages will have a small subset of jQuery available to them preloaded for some dynamicism. Unless they’re going to be maxing out the number of simultenaous connections, or enforcing other page fize limits I don’t see it having much of an impact, from an outsiders point of view anyway.

    You’d proably get similar results by simply optimizing your current pages by properly compressing images, reducing the number of calls to and from your server through combining images and reducing the amount of javascript needed. UNless they’re using a different protocol for AMP pages in the background perhaps?

    Either way, for the moment, I’ll stick to regular, non-AMP HTML until the evidence comes to the contrary and support is fairly widespread.

  • http://www.pglinfo.ca pglinfo

    I think I am going to try this, Every avantages that you can have on your website is a good thing.