Accelerated Mobile Pages
{{ safesubst:#invoke:Unsubst||$N=Use mdy dates |date=__DATE__ |$B= }}
The Accelerated Mobile Pages (AMP) Project is a website publishing technology developed by Google as a competitor to Facebook's Instant Articles.[1]
History
Announcement and launch
The AMP Project was announced by Google on October 7, 2015 following discussions with its partners in the テンプレート:Ill (DNI), and other news publishers and technology companies around the world, about improving the performance of the mobile web. More than 30 news publishers and several technology companies (including Twitter, Pinterest, LinkedIn and WordPress) were initially announced as collaborators in the AMP Project.
AMP pages first appeared to web users in February 2016, when Google began to show the AMP versions of webpages in mobile search results. Initially links to AMP pages were restricted to a “Top Stories” section of Google's mobile search results; by September 2016 Google started linking to AMP content in the main mobile search results area.[2] AMP links in Google search are identified with an icon.
According to one of the co-founders of the AMP Project, Malte Ubl, AMP was originally called PCU,[3] which stood for Portable Content Unit.
Growth and expansion
In September 2016, Microsoft announced support for AMP in the Bing apps for iOS and Android.[4]
In February 2017, a year after the public launch of AMP, Adobe reported AMP pages accounted for 7% of all web traffic for top publishers in the United States.[5]
In May 2017, Google reported 900,000 web domains were publishing AMP pages with more than two billion AMP pages published globally.[6]
In June 2017, Twitter started linking to AMP pages from its iOS and Android apps.[7]
In September 2018, Microsoft began rolling out its own Bing AMP viewer and AMP cache.[8]
Technology
Online Format
AMP pages are published on-line and can be displayed in most current browsers.[9] When a standard webpage has an AMP counterpart, a link to the AMP page is usually placed in an HTML tag in the source code of the standard page. Because most AMP pages are easily discoverable by web crawlers, third parties such as search engines and other referring websites can choose to link to the AMP version of a webpage instead of the standard version.
AMP framework
The AMP framework consists of three components: AMP HTML, which is standard HTML markup with web components; AMP JavaScript, which manages resource loading; and AMP caches, which serve and validate AMP pages.[10]
Most AMP pages are delivered by Google's AMP cache, but other companies can support AMP caches. Internet performance and security company Cloudflare launched an AMP cache in March 2017.[11]
Third party integration
Any organization or individual can build products or features which will work on AMP pages, provided they comply with the AMP Project specifications. As of July 2017, the AMP Project's website listed around 120 advertising companies and around 30 analytics companies as AMP Project participants.[12]
Performance
Google reports that AMP pages served in Google search typically load in less than one second and use ten times less data than the equivalent non-AMP pages.[13] CNBC reported a 75% decrease in mobile page load time for AMP Pages over non-AMP pages,[14] while Gizmodo reported that AMP pages loaded three times faster than non-AMP pages.[15]
Parity with canonical pages
Google has announced that as of February 1, 2018, it will require the content of canonical pages and those displayed through AMP be substantially the same.[16] This is aimed at improving the experience of users by avoiding common difficulties with the user interface, and increase security and trust (see below).
Reception
General criticism
AMP has been widely criticized by many in the tech industry[17][18][19][20][21][22][23] for being an attempt by Google to exert its dominance on the Web by dictating how websites are built and monetized, and that "AMP is Google's attempt to lock publishers into its ecosystem".[24] AMP has also been linked to Google's attempt to deprecate URLs so that users will not be able to immediately see whether they are viewing a webpage on the open Web or an AMP page that is hosted on Google's servers.[25]
"There is a sense in which AMP is a Google-built version of the web," Joshua Benton, director of the Nieman Journalism Lab at Harvard University. "We are moving from a world where you can put anything on your website to one where you can’t because Google says so."... "AMP is an example of Google dialing up its anti-competitive practices under the nose of the competition regulators," said Ramon Tremosa, a Spanish member of the European Parliament[26]
Comparison to other formats
AMP is often compared to Facebook Instant Articles and Apple News.[27][28] All three formats were announced in 2015 with the stated goal of making mobile content faster and easier to consume.[29][30] AMP Project supporters claim that AMP is a collaborative effort among publishers and technology companies, and that AMP is designed to work on the web instead of proprietary mobile apps.
Google's Richard Gingras said:
“There's a very big difference between having a proprietary platform that says it's open, and having an open-source platform that is open to anyone to modify and adapt. It's the difference between saying come into my walled garden vs. not having a walled garden.”[31]
However, some critics believe that AMP is an impending walled garden as Google begins to host AMP-restricted versions of their websites directly on google.com:
They say AMP is not actually supporting the open web because it is a “fork” or variation on HTML and one that Google essentially controls...Some publishers have complained that as Google prioritizes AMP links—as it recently said it will do in mobile search—media companies will lose even more control because AMP pages are hosted and controlled by Google. “Our mobile search traffic is moving to be majority AMP (google hosted and not on our site) which limits our control over UI, monetization et al,” said one digital media executive.[32]
Google control
Matthew Ingram of Fortune expressed concerns about Google's role and motives regarding the AMP Project:
“In a nutshell, these publishers are afraid that while the AMP project is nominally open-source, Google is using it to shape how the mobile web works, and in particular, to ensure a steady stream of advertising revenue… More than anything else, the concerns that some publishers have about AMP seems to be part of a broader fear about the loss of control over distribution in a platform-centric world, and the risks that this poses to traditional monetization methods such as display advertising.”[31]
These charges were rebutted by Google. Madhav Chinnappa stated that AMP must be a collaborative industry initiative in order for it to succeed in the long term:
“I get a little bit irritated when sometimes people call it Google’s AMP, because it’s not … AMP was created as an open source initiative and that for me is the reason for its success.”[33]
In September 2018, Google began to transition AMP to a more open governance model, with a technical steering committee composed of AMP-using publishers.[34]
WordPress
December 7, 2018, AMP announced their official WordPress plugin[35], which allowed to transform WordPress websites into include AMP-ready pages.
As AMP started to become more popular, many other WordPress developers helped to contribute towards WordPress AMP-specific resources[36].
Monetization
Some publishers reported that AMP pages generate less advertising revenue per page than non-AMP pages.[37] The Wall Street Journal’s Jack Marshall said:
"AMP pages rely heavily on standardized banner ad units, and don’t allow publishers to sell highly-customized ad units, sponsorships or pop-up ads as they might on their own properties"[38]
Other publishers have reported better success with AMP monetization. The Washington Post has been able to generate approximately the same amount of revenue from AMP pages as from standard mobile pages, according to director of product Joey Marburger. CNN chief product officer Alex Wellen said AMP Pages “largely monetize at the same rate” as standard mobile pages.[39]
To improve advertising performance, the AMP Project launched the AMP Ads Initiative which includes support for more advertising formats and optimizations to improve ad load speed.[40][41]
Exploitation for malicious purposes
Some observers believe AMP allows more effective phishing attempts. One serious flaw, noted by tech writer Kyle Chayka, is that disreputable parties who misuse AMP (as well as Facebook's similar Instant Articles) enable junk websites to share many of the same visual cues and features found on legitimate sites. “All publishers end up looking more similar than different. That makes separating the real from the fake even harder,” said Chayka.[42]
In September 2017, Russian hackers used an AMP vulnerability in phishing e-mails sent to investigative journalists critical of the Russian government, and hacked into their websites.[42] Google announced on November 16, 2017 that it will stop allowing sites using AMP for formatting to bait-and-switch sites.[16] Google said beginning February 2018, AMP pages must contain content nearly identical to that of the standard page they're replicating.
References
- ↑ Bohn, Dieter (2016年8月2日). “Google’s Instant Articles competitor is about to take over mobile search”. The Verge. . May 25, 2017閲覧.
- ↑ “Google opens the AMP fire hose” (en-US). Search Engine Land. (2016年10月3日) . August 31, 2017閲覧.
- ↑ “AMP Contributor Summit 2018 Keynote”. YouTube. The AMP Channel. . October 11, 2018閲覧.
- ↑ “Bing App joins the AMP open-source effort” (英語). Bing Webmaster Blog. (2016年9月23日) . April 8, 2019閲覧.
- ↑ “Google AMP: One Year Later | Adobe” (en-US). Digital Marketing Blog by Adobe. (2017年2月23日) . August 31, 2017閲覧.
- ↑ “Turbocharging AMP – AMP” (英語). www.ampproject.org. . August 31, 2017閲覧.
- ↑ “Twitter ramps up AMP” (en-US). Search Engine Land. (2017年7月7日) . August 31, 2017閲覧.
- ↑ “Introducing Bing AMP viewer and Bing AMP cache” (英語). Bing Webmaster Blog. (2018年9月19日) . April 8, 2019閲覧.
- ↑ “Supported Browsers” (英語). www.ampproject.org. . September 7, 2018閲覧.
- ↑ “Overview – AMP” (英語). www.ampproject.org. . August 31, 2017閲覧.
- ↑ Inc., Cloudflare,. “Cloudflare Announces Ampersand, the First Open AMP Cache, to Give Publishers More Control of their Mobile-Optimized Content” (en-US). GlobeNewswire News Room . August 31, 2017閲覧.
- ↑ “Supported Platforms, Vendors and Partners – AMP” (英語). www.ampproject.org. . August 31, 2017閲覧.
- ↑ “Search results are officially AMP’d”. Google (2016年9月20日). . August 31, 2017閲覧.
- ↑ “CNBC – AMP” (英語). www.ampproject.org. . August 31, 2017閲覧.
- ↑ “Gizmodo – AMP” (英語). www.ampproject.org. . August 31, 2017閲覧.
- ↑ 16.0 16.1 “Google will stop letting sites use AMP format to bait and switch readers”. The Verge . November 20, 2017閲覧.
- ↑ at 08:25, Scott Gilbertson 19 May 2017. “Kill Google AMP before it kills the web”. www.theregister.co.uk. . April 16, 2019閲覧.
- ↑ “AMP letter”. ampletter.org. . April 16, 2019閲覧.
- ↑ “AMP for email is a terrible idea”. . April 16, 2019閲覧.
- ↑ “Web developers publish open letter taking Google to task for locking up with web with AMP”. Boing Boing. . April 16, 2019閲覧.
- ↑ Bohn, Dieter (2018年3月8日). “Inside Google’s plan to make the whole web as fast as AMP”. The Verge. . April 16, 2019閲覧.
- ↑ Bright, Peter (2018年3月10日). “Google claims it’s going to build its proprietary AMP using Web standards”. Ars Technica. . April 16, 2019閲覧.
- ↑ “Google Announces Plan to Improve URLs for AMP Pages, But Even If It Happens, Which Remains Uncertain, AMP Will Still Suck”. . April 16, 2019閲覧.
- ↑ at 21:33, Kieren McCarthy in San Francisco 30 Oct 2017. “Google AMP supremo whinges at being called out on team's bulls***”. www.theregister.co.uk. . April 16, 2019閲覧.
- ↑ at 01:36, Shaun Nichols in San Francisco 7 Sep 2018. “Official: Google Chrome 69 kills off the World Wide Web (in URLs)”. www.theregister.co.uk. . April 16, 2019閲覧.
- ↑ Scott, Mark (2018年6月1日). “Google’s mobile web dominance raises competition eyebrows”. POLITICO. . April 16, 2019閲覧.
- ↑ Novet, Jordan (2016年8月14日). “Why I prefer Google AMP pages to Facebook Instant Articles” (en-US). VentureBeat. . February 28, 2019閲覧.
- ↑ Travis, Ben (2016年12月13日). “Your Guide to Mobile Publishing Formats: AMP, Facebook Instant Articles, and Apple News | Viget” (英語). viget.com. . February 28, 2019閲覧.
- ↑ “Introducing Instant Articles | Facebook Media”. . August 31, 2017閲覧.
- ↑ “Apple Announces News App for iPhone & iPad” (en-US). Apple Newsroom . August 31, 2017閲覧.
- ↑ 31.0 31.1 Ingram, Mathew. “Google Says It Wants to Help Publishers Fight Facebook”. Fortune. . 2017閲覧.
- ↑ “Google Says It Wants to Help Publishers Fight Facebook”. Fortune. . April 16, 2019閲覧.
- ↑ “'It's not our project' says Google of AMP as the open format gains advantage over Facebook’s Instant Articles” (英語). The Drum . 2017閲覧.
- ↑ “Answering its critics, Google loosens reins on AMP project” (en-US). TechCrunch . September 18, 2018閲覧.
- ↑ “The Official AMP Plugin for WordPress – AMP” (英語). www.ampproject.org. AMP Project. . 7 December 2018閲覧.
- ↑ “WPZA's AMP Guides” (英語). WPZA. WPZA. . 20 January 2019閲覧.
- ↑ “Publishers are pleasantly surprised by Google AMP traffic - Digiday” (en-US). Digiday. (2016年10月14日) . August 31, 2017閲覧.
- ↑ “Publishers are struggling with AMP page monetization | Search Engine Watch”. . 2017閲覧.
- ↑ Marshall, Jack (2016年10月28日). “Google AMP Gets Mixed Reviews From Publishers” (en-US). Wall Street Journal. ISSN 0099-9660 . August 31, 2017閲覧.
- ↑ “AMP Ads – AMP” (英語). www.ampproject.org. . August 31, 2017閲覧.
- ↑ “Growing the AMP Ads Initiative – AMP” (英語). www.ampproject.org. . August 31, 2017閲覧.
- ↑ 42.0 42.1 “Russian hackers exploited a Google flaw — and Google won't fix it” (en-US). Salon. (2017年9月24日) . November 20, 2017閲覧.
External links
- 公式ウェブサイト
- AMP by Example, official tutorial