Difference between revisions of "AMP (Accelerated Mobile Pages)"

From Seobility Wiki
Jump to: navigation, search
(→‎Disadvantages)
(→‎Disadvantages)
Line 37: Line 37:
 
A possible disadvantage is the comparatively difficult implementation of AMP. While Google offers solid resources and tutorials, that doesn't mean they're easy to implement. AMP also has limited support for Google Analytics. While basic metrics such as visitors and engagement can be captured, there are few ways to optimize user experience.
 
A possible disadvantage is the comparatively difficult implementation of AMP. While Google offers solid resources and tutorials, that doesn't mean they're easy to implement. AMP also has limited support for Google Analytics. While basic metrics such as visitors and engagement can be captured, there are few ways to optimize user experience.
  
−
Another drawback is that there are limitations to designing your website in terms of functionality. For example, AMP pages can’t display email pop-ups and opt-in forms, sidebar widgets, strategically placed social share buttons, and much more. This could result in losing email subscribers and leads.
+
Another drawback is that there are limitations to designing your website in terms of functionality. For example, AMP pages can’t display email [[Pop-up|pop-ups]] and opt-in forms, sidebar widgets, strategically placed social share buttons, and much more. This could result in losing email subscribers and leads.
  
 
Last but not least, using a [[Content Delivery Network (CDN)|Content Delivery Network]] creates a certain dependency because AMP pages are usually loaded via Google's cache server. Since nobody but Google itself can control these servers, this leads to a dependency that can be detrimental in the long run.
 
Last but not least, using a [[Content Delivery Network (CDN)|Content Delivery Network]] creates a certain dependency because AMP pages are usually loaded via Google's cache server. Since nobody but Google itself can control these servers, this leads to a dependency that can be detrimental in the long run.

Revision as of 14:51, 22 January 2020

What are AMPs?

Accelerated Mobile Pages (AMP) is an open source project that has the purpose to improve the performance of websites on mobile devices. Basically, they are HTML pages that are very lightweight and enable short loading times by not offering certain functions. Accelerated Mobile Pages was created by Google, Twitter and a number of other companies in response to projects such as Facebook Instant Articles and Apple News.

The technology behind AMP enables lightweight pages that can be loaded faster by smartphone and tablet users. The shorter loading times improve user experience and therefore are an important factor for mobile SEO. AMPs offer mobile users a good user experience even with a low bandwidth internet connection. In addition, most AMPs are stored by Google, so they can be delivered to search engine users with virtually no delay. According to Google, AMPs only use a tenth of the data that regular web pages need and are usually loaded in less than a second.

How it works

The AMP framework uses reduced versions of HTML, CSS, and JavaScript for website creation and optionally a Content Delivery Network (CDN) for the delivery of pages. AMP HTML is a lighter HTML version by Google that does not contain many of the elements that usually slow web pages down. Some tags that work for regular web page code cannot be used for AMP. Such HTML tags not supported by AMP include base, frame, frameset, param, applet, and the input elements textarea, select, or option. Img, video, audio and iframe have been replaced by AMP-specific tags.

JavaScript and CSS used for AMP are also limited versions, which are used to achieve faster loading times. Note that certain design elements such as transitions or animations cannot be realized with AMP due to these restrictions.

You can also use two CDNs for AMP to deliver your pages even faster to search engine users. One of these CDNs is Google’s AMP Cache, the second is operated by Cloudflare.

Accelerated Mobile Pages are hosted on a special server. A rel="amphtml" tag refers from the desktop version to the AMP page. The AMP page, in turn, contains a canonical tag that refers to the desktop page to signal that this is the original page and to avoid duplicate content. A second version of the mobile page is stored on a Google cache server at gstatic.com. This one is also linked to the desktop page via a canonical tag. The AMP page stored on the cache server is delivered to search engine users.

Importance for SEO

Accelerated Mobile Pages benefit from an eye-catching display in Google's mobile search results. Articles are displayed on mobile devices in a carousel above other search results, even if the latter are more up-to-date. Although AMPs were initially mainly used by news sites, blog content and other websites now appear at the top of the carousel and are labeled as fast mobile pages with a flash. This increases users’ awareness of these sites.

Accelerated Mobile Pages in mobile search results

Screenshot with display of AMPs in mobile search results of google.com

AMP pages also reduce bounce rates, because, with AMP technology, content is loaded in fractions of a second, significantly reducing users’ frustration due to waiting times and thereby keeping visitors on your site. This increases the time spent on your site, which correlates directly with a higher ranking in Google's search results.

As the importance of page speed and user experience for rankings has increased due to Google's Mobile First approach, the presence - or absence - of AMP pages on a mobile website could become a ranking factor in the future. Although accelerated mobile pages are not yet an official ranking factor, so-called "Mobilegeddon" already signaled a first shift of Google towards punishing web pages not optimized for mobile devices by eliminating these web pages from search results.

Who are AMPs suitable for?

In the test phase, news publishers such as Washington Post and other magazines with text-based content, in particular, were able to benefit from the prominent display on Google. Since AMP is an open source project, however, new features are constantly being added, so that large online shops are now testing AMPs and the benefits are gradually becoming interesting for all types of web content.

Disadvantages

A possible disadvantage is the comparatively difficult implementation of AMP. While Google offers solid resources and tutorials, that doesn't mean they're easy to implement. AMP also has limited support for Google Analytics. While basic metrics such as visitors and engagement can be captured, there are few ways to optimize user experience.

Another drawback is that there are limitations to designing your website in terms of functionality. For example, AMP pages can’t display email pop-ups and opt-in forms, sidebar widgets, strategically placed social share buttons, and much more. This could result in losing email subscribers and leads.

Last but not least, using a Content Delivery Network creates a certain dependency because AMP pages are usually loaded via Google's cache server. Since nobody but Google itself can control these servers, this leads to a dependency that can be detrimental in the long run.

Related links

Similar articles