Tag: AMP

AMP Support is Coming to Gmail Later This Year

Google has announced a new AMP for Email developers preview for companies to create more interactive emails.  The feature, which is part of the Gmail developer program, will be generally available and supported in the email service later this year.

With AMP for Email, you’ll be able to quickly take actions like submit an RSVP to an event, schedule an appointment, or fill out a questionnaire right from the email message. Many people rely on email for information about flights, events, news, purchases and beyond—more than 270 billion emails are sent each day! AMP for Email will also make it possible for information to easily kept up-to-date, so emails never get stale and the content is accurate when a user looks at it.

Once AMP for Email fully rolls out, it will be much more like a website in your email than a static message.

AMP URLs to Finally Remove the Google Prefix

Google is embarking on a new way for AMP, Accelerated Mobile Pages, are rendered that preserves the original URL.  This is a big deal as the current way that these optimized mobile pages are shown by URL introduces doubt for readers as to the original source.

First, in case you don’t know what Accelerated Mobile Pages are exactly, it is a caching system that Google uses to speed up the delivery of webpages to your mobile device.  Generally these are generated as google.com/amp/ then the site name or page.  The reason for this is due to privacy concerns of Google caching the originating URL

When we first launched AMP in Google Search we made a big trade-off: to achieve the user experience that users were telling us that they wanted, instant loading, we needed to start loading the page before the user clicked. As we detailed in a deep-dive blog post last year,  privacy reasons make it basically impossible to load the page from the publisher’s server. Publishers shouldn’t know what people are interested in until they actively go to their pages. Instead, AMP pages are loaded from the Google AMP Cache but with that behavior the URLs changed to include the google.com/amp/ URL prefix.

This trade-off has created concerns over the validity of the source information.

%d bloggers like this: