Google fixes a big problem with AMP, now lets you view and share publisher’s own links – TechCrunch
Google today is rolling out a change to its AMP integration in Google Search that will let you view, copy and shareÃ‚Â the publisherÃ¢Â€Â™s ownÃ‚Â link to the webpage in question, instead of the AMP URL. The decision to make this change follows someÃ‚Â backlash from publishers who believedÃ‚Â Google wasÃ‚Â stealing their traffic by changing their own URLs to thoseÃ‚Â that had Ã¢Â€ÂœGoogleÃ¢Â€Â in the name, all in the name of mobile optimization.
Google AMP (Accelerated Mobile Pages), as you may recall, is GoogleÃ¢Â€Â™s project to speed up web browsing on mobile devices by offering optimized versions of publishersÃ¢Â€Â™ sites that arenÃ¢Â€Â™t bogged down by third-party scripts and other extension mechanisms that can slow or stop the page from rendering.
However, there has been some misunderstanding about how AMP works. One widely circulated blog post written back in October claimed Google was stealing traffic from publishers via its AMP pages. But that wasnÃ¢Â€Â™t true. Google does display the AMP URL in the search results, which serves up the page content from GoogleÃ¢Â€Â™s cache, but the traffic remains the publisherÃ¢Â€Â™s, and the content is served from the publisherÃ¢Â€Â™s site.
Still, there has been concern over this URL system.
TheÃ‚Â AMP URLs would redirect visitors to the publisherÃ¢Â€Â™s site as temporary redirects, not permanent ones, Search Engine Land explained last fall. Without support for direct links, some were worried that bookmarked URLs might stop working in the future, if Google made any changes. Plus, there was just general confusion from users over how to share the links. People would see the AMP URL in the address field, and they would not want to copy and paste it because it wasnÃ¢Â€Â™t the Ã¢Â€ÂœrealÃ¢Â€Â link to the webpage.
As Google saysÃ‚Â today in a blog post announcing the change:
Ã‚Â Ã¢Â€ÂœURLs and origins represent, to some extent, trust and ownership of content. When youÃ¢Â€Â™re reading a New York Times article, a quick glimpse at the URL gives you a level of trust that what youÃ¢Â€Â™re reading represents the voice of the New York Times. Attribution, brand, and ownership are clear.Ã¢Â€Â
Google AMP messed with that system.
Instead of one URL (the publisherÃ¢Â€Â™s), there were three. This includes the publisherÃ¢Â€Â™s URL, the AMP Cache URL Ã¢Â€Â“ the document thatÃ¢Â€Â™s served up through AMPÃ¢Â€Â™s cache, but generally invisible to users Ã¢Â€Â“ and the Google AMP Viewer URL, which is the AMP URL you see in the search results.
Google goes on to detail why those design choices were made, citing ease-of-use for publishers as one example. The company also explains how itÃ¢Â€Â™s able to pre-render AMP documents in hidden iframesÃ‚Â on the search results page in order to speed up the time it takes to load the linkÃ‚Â the user eventually clicks on. But this also means that the URLs users see have to be on the google.com origin.
To make users understand where the webpage content is actually coming from Ã¢Â€Â“ that is, not Google Ã¢Â€Â“ it pops up a header bar on the top of the page that will display the true origin of the page (e.g. Ã¢Â€Âœnytimes.comÃ¢Â€Â).
But when aÃ‚Â user wants to copy or share a webpage, they generally look toÃ‚Â the address bar. Since this is showing a google.com address, itÃ¢Â€Â™s not the link people want to bookmark or share with others.
Now Google is adding a button to theÃ‚Â header bar that will provide this info. This will display the publisherÃ¢Â€Â™s own permalink for the page in question. The feature allows users to use their browserÃ¢Â€Â™s native share functionality by long-tapping on this link, says Google.
The feature is already available in the iOS Google app and will roll out to the Android version in the coming weeks.
It also has under development a Web Share API that would allow AMP viewers to pull the original URL into the native sharing flow on the platform, instead of the AMP Viewer URL.
Google had already indicated it was working on just such a solution, given both publisher backlash and user confusion. Now that it has come to pass, more publishers may choose to participate in AMP since their own links will no longer beÃ‚Â entirely hidden.
Write a Reply or Comment:
You must be logged in to post a comment.