Packt+ | Advance your knowledge in tech

You're reading from AMP: Building Accelerated Mobile Pages Create lightning-fast mobile pages by leveraging AMP technology

Product type Paperback

Published in Oct 2017

Publisher Packt

ISBN-13 9781786467317

Length 370 pages

Edition 1st Edition

Languages

JavaScript

Tools

AMP

Concepts

Web Design

Author (1):

O'Donoghue

View More author details

Table of Contents (24) Chapters

Title Page

Credits

About the Author

Acknowledgements

About the Reviewer

www.Packtpub.com

Customer Feedback

Preface

1. Ride the Lightning with AMP

2. Building Your First AMP Page FREE CHAPTER

3. Making an Impression - Layout and Page Design in AMP

4. Engaging Users with Interactive AMP Components

5. Building Rich Media Pages in AMP

6. Making Contact - Forms in AMP

7. Dynamic Content and Data-Driven Interaction

8. Programming in AMP - amp-bind

9. When AMP Is Not Enough - Enter the iframe

10. Ads and Analytics in AMP

11. AMP Deployment and Your Web Presence

12. AMP - Where It's At and Where It's Going

13. AMP Components

14. Actions and Events

15. amp-bind Whitelisted Functions

JavaScript whitelisted functions

16. amp-bind Permitted Attribute Bindings

Criticism of AMP

It would be remiss not to briefly revisit the main criticisms of the AMP project here. Since its launch, there have been three main criticisms leveled at the AMP project. These criticisms come from open web advocates who believe certain parts of the project are incompatible with a distributed and open web. These criticisms are:

The AMP Cache URL
The AMP lightning symbol in search results
The SEO benefits of the AMP Top Stories carousel

AMP Cache URL

As we saw in Chapter 1, Ride the Lightning with AMP, when an AMP page is served from the AMP Cache, which sits on a Google domain, the original URL is obscured, and the address bar shows a URL that starts with a Google domain. The original URL is buried in the AMP URL, but most users won't see it. This can dilute your brand.

When the source URL is obscured, it's not hard to see how the content of a domain might be attributed incorrectly. When an AMP page is displayed with google.com as the domain in the address bar, a user unfamiliar...