The Google Webmaster Help Forum Provides Publishers with Support on All Things AMP

It’s been about a month since the launch of AMP in the Top Stories section of Google Search. Now, when you search for a story or topic on Google from a mobile device, web pages created in the AMP open-source format will appear where relevant and load extremely fast. Early testing shows that web pages built with AMP load an average of four times faster and use 10 times less data than equivalent non-AMP pages!

In order to help publishers adopt AMP for their websites, Google recently launched an Accelerated Mobile Pages category within the Webmaster Help Community. In this forum publishers can ask questions and share insights about making their AMPs eligible to be shown on Google Search.

Join the conversation in the community here: goo.gl/lG0SBE

Here are some of the most common questions we’ve seen raised in the help forum:

Q: I’m considering creating AMP pages for my website. What  is the benefit? What types of sites and pages is AMP for?

Using the AMP format will make it far more compelling for people to consume and engage with your content on mobile devices. Users love content that loads fast and without any fuss. We have seen people read more and consume more content that loads in an instant. Learn more about the benefits of AMP on this FAQ.  The goal is for all published content, from news stories to videos and from blogs to photographs and GIFs, to work using Accelerated Mobile Pages.

Q: We are getting thousands of errors logged in Search Console for AMP pages with invalid structured data; however, we already fixed these issues, and now all our pages validate. Why are we still seeing errors?

The short answer is that changes to your AMP HTML take a while to be reflected in Search Console. For a more in-depth answer, Google’s Webmaster Trends Analyst John Mueller shared a detailed post on Search Console latency challenges.

Q: Our AMP pages are not showing up in the Top Stories carousel. What should we do?

The Top Stories carousel requires Schema markup of either the Article or VideoObject types or their subtypes, such as NewsArticle and BlogPost. Developers can validate their structured data using this testing tool.

Posted by Elena Legeros, on behalf of the AMP Team

The Google Webmaster Help Forum Provides Publishers with Support on All Things AMP

Local Language AMP NewsLab Office Hours

We’ve had a great response to our English language AMP office hours, but we know that English isn’t everyone’s native language.

For the next two weeks, we’re rolling out a new series of office hours in French, Italian, German, Spanish, Brazilian Portuguese, Russian, Japanese, and Indonesian and invite everyone to learn about AMP in their native language. Native language speaking Partner Managers, Technical Managers, Product Managers, and Engineers from Google will be on hand to answer your questions.

First we will reintroduce you to AMP and how it works, before diving into the technical specs and various components of AMP. You can add your questions via the Q and A app on the event pages below, and we will answer them during the office hours. You can also watch them on the News Lab YouTube page after the event.

Check out the lineup below and join the discussion.

  • French
    • Introduction to AMP – Mar. 7 @ 1700 CET with Cecile Pruvost, Industry Manager
    • AMP Anatomy – Mar. 14 @ 1700 CET with Emeric Studer, Technology Manager
  • Italian
    • Introduction to AMP – Mar. 8 @ 1500 CET with Luca Forlin Head of International Play Newsstand Partnerships
    • AMP Anatomy – Mar. 15 @ 1500 CET with Flavio Palandri Antonelli, AMP Software Engineer
  • German
    • Introduction to AMP – Mar. 9 @ 1700 CET with Nadine Gerspacher, Partner Development Manager
    • AMP Anatomy – Mar. 18 @ 1600 CET with Paul Bakaus, Developer Advocate
  • Spanish
    • Introduction to AMP – Mar. 9 @ 1430 CET with Demian Renzulli, Technical Solutions Consultant
    • AMP Anatomy – Mar. 16 @ 1430 CET with Julian Toledo, Developer Advocate
  • Brazilian Portuguese
    • Introduction to AMP – Mar. 10 @ 1430 BRT with Carol Soler, Strategic Partner Manager
    • AMP Anatomy – Mar. 17 @ 1430 BRT with Breno Araújo, Technology Manager
  • Russian
  • Japanese
  • Indonesian

Tomo Taylor, AMP Community Manager

 

Local Language AMP NewsLab Office Hours

AMPing up Drupal

Posted by Matthew Tift, Lullabot
This post originally appeared at https://www.lullabot.com/articles/amping-up-drupal

Today we are proud to announce a new Drupal 8 module that provides support for the Accelerated Mobile Pages (AMP) Project. The AMP Project is a new open source initiative which drastically improves the performance of the mobile web. In January 2016 Lullabot and Google started working together to create the Drupal AMP module. A beta version of AMP module for Drupal 8 is available immediately, and we are starting work on a Drupal 7 version of the module that will be available in mid-March.

In many cases, the mobile web is a slow and frustrating experience. The AMP Project is an open source initiative that embodies the vision that publishers can create mobile optimized content once and have it load instantly everywhere. When AMP was first introduced last October, many commentators immediately compared it to Facebook’s Instant Articles and Apple’s News app. One of the biggest differentiators between AMP and other solutions is the fact that AMP is open source.

AMP HTML is, essentially, a subset of HTML. And it really makes the web fast. AMP HTML is designed to support smart caching, predictable performance, and modern, beautiful mobile content. Since AMP HTML is built on existing web technologies, publishers continue to host their own content, craft their own user experiences, and flexibly integrate their advertising and business models — all using familiar tools, which will now include Drupal!

One of the most touted features of Drupal is its flexibility, so making Drupal produce AMP HTML has required a lot of careful consideration of the design approach. To make Drupal output AMP HTML, we have created an AMP module, AMP theme, and a PHP Library.

When the AMP module is installed, AMP can be enabled for any content type. At that point, a new AMP view mode is created for that content type, and AMP content becomes available on URLs such as node/1/amp or node/article-title/amp. We also created special AMP formatters for text, image, and video fields.

The AMP theme is designed to produce the very specific markup that the AMP HTML standard requires. The AMP theme is triggered for any node delivered on an /amp path. As with any Drupal theme, the AMP theme can be extended using a subtheme, allowing publishers as much flexibility as they need to customize how AMP pages are displayed. This also makes it possible to do things like place AMP ad blocks on the AMP page using Drupal’s block system.

The PHP Library analyzes HTML entered by users into rich text fields and reports issues that might make the HTML non-compliant with the AMP standard. The library does its best to make corrections to the HTML, where possible, and automatically converts images and iframes into their AMP HTML equivalents. More automatic conversions will be available in the future. The PHP Library is CMS agnostic, designed so that it can be used by both the Drupal 8 and Drupal 7 versions of the Drupal module, as well as by non-Drupal PHP projects.

We have done our best to make this solution as turnkey as possible, but the module, in its current state, is not feature complete. At this point only node pages can be converted to AMP HTML. The initial module supports AMP HTML tags such as amp-ad, amp-pixel, amp-img,amp-video, amp-analytics, and amp-iframe, but we plan to add support for more of theextended components in the near future. For now the module supports Google Analytics, AdSense, and DoubleClick for Publisher ad networks, but additional network support is forthcoming.

While AMP HTML is already being served by some of the biggest publishers and platforms in the world — such as The New York Times, The Economist, The Guardian, BBC, Vox Media, LinkedIn, Pinterest, and many more! — you don’t have to be a large publisher to take advantage of AMP. Today, any Drupal 8 site can output AMP HTML using the AMP module. We invite you to try it out and let us know what you think!

Finally, if you are interested in this topic and want to learn more about publishing AMP with Drupal, please leave a comment on our DrupalCon New Orleans proposal.

AMPing up Drupal