This document discusses Accelerated Mobile Pages (AMP) and its benefits for SEO. AMP aims to make mobile web content load nearly instantly by enforcing strict performance standards. It outlines how AMP works by pre-rendering pages and caching them globally via Google servers. The document argues that mobile usage will continue growing and speed is critical, so AMP can provide major SEO advantages by optimizing the mobile user experience. It provides resources for publishers to learn more and get started with AMP.
4. @Mike_Arnesen upbuild.io
▸ AMP: Accelerated Mobile Pages
▸ UX: User Experience
▸ JS: JavaScript
▸ JSON: JavaScript Object Notation
▸ CSS: Cascading Style Sheets
▸ Cache: To store (a webpage) for future use
GLOSSARY
5. @Mike_Arnesen upbuild.io
▸ Pre-render: To process (a webpage) in
advance
▸ Native Apps: Downloadable apps for iOS
and Android
▸ Progressive Web Apps: Browser-based app
experiences
▸ iFrame: A tag used to display another
page’s content on the page you’re on.
▸ SEO: Get on my level
GLOSSARY
15. @Mike_Arnesen upbuild.io
▸ Mobile web reach is 2.5x
the reach of native apps
▸ Mobile users spend 86%
of their time in apps
▸ 80% of that pie is Facebook,
YouTube, and Facebook
Messenger.
NATIVE APPS
21. @Mike_Arnesen upbuild.io
"AMP STANDS FOR ACCELERATED MOBILE
PAGES, WHICH IS KIND OF STUPID AND I’M
NEVER GOING TO SAY IT AGAIN.”
Malte Ubl
AMP’s Tech Lead
22.
23. @Mike_Arnesen upbuild.io
“PAY ATTENTION TO AMP. IT’S
GOING TO BE REALLY BIG. FIGURE
OUT WITH YOUR DEVELOPERS HOW
TO IMPLEMENT IT.”
Gary Illyes
Google Webmaster Trends Analyst
43. News publishers only
Immediate ad support
Menus supported
Forms form supported
Product/recipe/review sites
Global rollout
New releases weekly
EVOLUTION
OF AMP
48. @Mike_Arnesen upbuild.io
▸No external stylesheets (i.e., CSS)
▸50kb limit on inline stylesheets
▸Width/height must be specified
▸AMP-specific tags keep you in the fast lane
▸No resizing above-the-fold (i.e., in-viewport)
A STRICTER HTML
58. @Mike_Arnesen upbuild.io
via <amp-iframe>
▸ Include the amp-iframe
component script
▸ Use for non-supported
content
▸ iframes must be at least
600px away from the top
AND THE REST
59. @Mike_Arnesen upbuild.io
via <amp-iframe>
▸ Include the amp-iframe
component script
▸ Use for non-supported
content
▸ iframes must be at least
600px away from the top
AND THE REST
iframes
always suck.
86. @Mike_Arnesen upbuild.io
▸ Mobile UX is only becoming more important
THE PROS
MANY SEO
RANKING FACTORS
ARE STRAIGHT-UP UX
BEST PRACTICES
87. @Mike_Arnesen upbuild.io
▸ Mobile UX (AKA, SEO) is only becoming more important
▸ AMP provides a fantastic experience to mobile users
THE PROS
88. @Mike_Arnesen upbuild.io
▸ Mobile UX (AKA, SEO) is only becoming more important
▸ AMP provides a fantastic experience to mobile users
▸ The AMP symbol will(has?) become the new “mobile-friendly” in
Google.
THE PROS
89. @Mike_Arnesen upbuild.io
▸ Mobile UX (AKA, SEO) is only becoming more important
▸ AMP provides a fantastic experience to mobile users
▸ The AMP symbol will(has?) become the new “mobile-friendly” in
Google.
▸ It’s your only way into Top Stories on mobile.
THE PROS
93. @Mike_Arnesen upbuild.io
▸ The project is still evolving
▸ Things break
▸ Proprietary and homegrown CMSes are expensive to change
THE CONS
94. @Mike_Arnesen upbuild.io
▸ The project is still evolving
▸ Things break
▸ Proprietary and homegrown CMSes are expensive to change
THE CONS
#OPENSOURCE
4EVER
95. @Mike_Arnesen upbuild.io
▸ The project is still evolving
▸ Things break
▸ Proprietary and homegrown CMSes are expensive to change
▸ It’s Google-only
THE CONS
96. @Mike_Arnesen upbuild.io
▸ The project is still evolving
▸ Things break
▸ Proprietary and homegrown CMSes are expensive to change
▸ It’s Google-only
THE CONS
BUT, SPEED
IS SPEED