Google Will Stop Letting Sites Use AMP Format To Bait and Switch Readers (theverge.com)
"Google today announced a forthcoming update to its Accelerated Mobile Pages, or AMP, web format that aims to discourage website owners from misusing the service," reports The Verge. "The company says that, starting in February 2018, AMP pages must contain content nearly identical to that of the standard page they're replicating." From the report: Currently, because AMP pages load faster and more clutter-free versions of a website, they naturally contain both fewer ads and less links to other portions of a site. That's led some site owners to publish two versions of a webpage: a standard page and an AMP-specific one that acts a teaser of sorts that directs users to the original. That original page, or canonical page in Google parlance, is by nature a slower loading page containing more ads and with a potentially lower bounce rate, which is the percentage of viewers who only view one page before leaving. Now, Google is cracking down on that behavior. "AMP was introduced to dramatically improve the performance of the web and deliver a fast, consistent content consumption experience," writes Ashish Mehta, an AMP product manager. "In keeping with this goal, we'll be enforcing the requirement of close parity between AMP and canonical page, for pages that wish to be shown in Google Search as AMPs."
I remember when Google just indexed web pages and tried to provide relevant search results.
That original page, or canonical page in Google parlance ...
Ubuntu AMP pages can show whatever they want because they're also canonical pages. :-)
It must have been something you assimilated. . . .
News outlets colluded with Russian intelligence to create a narrative that Google is making a change to its AMP service? Quick, somebody alert the bastions of alternative truth, Fox News and Alex Jones!
FACT: Nobody gives half a shit.
FACT!111eleven!!
We used to have a Bill of Rights. Now, with the rights gone, all we have left is the bill.
Because if something says AMP on the search result I can pretty much guarantee it's not something i want to look at and can ignore.
No idea why, but the correlation is strong.
How many sites are getting on to the front page where they have no page behind them, and the URL is nothing more than a search argument being passed to a domain? How does a page that does not exist get "found" by google's indexing? It doesn't. It's backdoor payment functionality.
Astalavista.box.sk
by TheSpoom (715771) Uncaring Linux user here. I have nothing to add to this but please continue. *munches popcorn*
...And... , you're on the hook.
Google is now just as much about power as companies like Microsoft, Apple and Oracle. You should not get into bed with them that easily.
Well, don't worry about that. We can get you back before you leave. (Dr. Who)
Yeah, but he's one of Google customers.
And this definitely doesn't provide him with relevant results to his searches.
That is, he's an advertiser, and this doesn't provide more eyeballs to his search trying to find the most appropriate victims to inflict his ads upon.
(None of the customer gives a shit if the "product", i.e "the users owning the above-mentioned eyeballs" is having a better time...
This fucking article must be yet another campain by PETA about fair treatment of farm animals...)
"Sufficiently advanced satire is indistinguishable from reality." - [Tips: 1DrYakQDKCQ6y52z6QbnkxHXAocMZJE61o ]
In the meantime our business moved location 8 months ago, and despite various requests, Google is still failing to update our Google Maps entry. It does nothing with the requests. It is impossible to contact a human being. They don't give a f**ck. What a shitty company. But I'm glad the advertising/privacy selling company wants to police the web, seems like great way to spend their time.
AMP is about Google trying to hoover up the web's content and host it themselves to harvest all the data they can and deny this valuable resource to website owners. Oh, and only Google advertising platforms are properly supported in AMP.
The claim that AMP is about speed is spurious. AMP pages are fast, but that is because they are stripped down, with many parts of the HTML/JS/CSS standard removed. If you build a version of your website as stripped down as an AMP page, the performance difference is a wash. These removed functionalities happen to include pretty much everything that a publisher can use to make money without Google.
I hated AMP as soon as it arrived because you need to develop and maintain two completely separate websites basically, a horror show. And one of those websites -- AMP -- is completely non-standard.
You can't even use server-side includes or an included CSS page, all the CSS has to be hard-coded into the head on the page.
This is why many people wrote a smaller AMP "teaser" page that simply linked to the full HTML5 version.
They're disallowing that tactic now and hopefully that will kill AMP once and for all. Who wants to maintain a hard-coded AMP website? And what about all the AMP "teaser" pages out there already, will they be disallowed?
By the way, I never found any speed difference whatsoever between AMP pages and our regular HTML5 pages, despite all the server-side includes in the latter. If you write good, clean, validated code, rather than the garbage on most websites, you're fine.
My feeling is that this new dictum will kill AMP for sure this time. If webmasters simply said "No" to AMP, it would die.
I really wish Google, apparently with the collusion of the websites, would stop shoving AMP down my throat in the first place. Since they helpfully nuked text reflow on zoom in the Android libraries, I've been using Opera as my main mobile browser because it fixes this. Except for AMP pages, where I'm stuck with their fixed format until I tap through to the original page. How about a 'load canonical page' setting in the google search options?
> I don't want to see fucking tap and die sets, I want to see a fucking nut.
When you want to get a nut, might I suggest xvideos.com
On mobile they just feel useless, but on the desktop it totally scales up to the full browser window (hey, your device is 6 inch, isn't it? 22 inch? I do not believe you!) and no site ever implements redirects from mobile to desktop versions, only the other way round. Then the mobile users share urls with you and you have to figure out where to remove "/amp/", "m." or similar parts of the url.
I guess now the teaser in the AMP page will have to link to the "canonical" page that has the same teaser that links to the actual page with the real content (maybe use a little Javascript to swap in the correct link). Users are gonna *love* all that extra clicking.
Never saw the point of AMP anyway. Google should have simply extended mobile Chrome to support Chrome extensions and then install an ad blocker by default. That would solve the majority of performance issues. AMP is a workaround for the real solution: Let users control what content they want to see via browser extensions.
Also, with AMP, you lose page view tracking, which was probably the point of using a teaser: To count the number of visitors to the website to know what content is working and what isn't. AMP generally takes away page views and therefore useful knowledge.