AMP pages no longer get preferential treatment in Google search
plausible.io
plausible.io
- https://blog.chromium.org/2020/05/introducing-web-vitals-ess... introduces these metrics, what they mean and how to measure them.
- https://developers.google.com/search/blog/2020/05/evaluating... talks about how the search engine experience will change
> The change for non-AMP content to become eligible to appear in the mobile Top Stories feature in Search will also roll out in May 2021. Any page that meets the Google News content policies will be eligible and we will prioritize pages with great page experience, whether implemented using AMP or any other web technology, as we rank the results.
> In addition to the timing updates described above, we plan to test a visual indicator that highlights pages in search results that have great page experience.
Seems like a positive change. It will mean extra work as developers improve the performance of their sites. But having clear metrics to improve will make that work tractable. Also, advocating for that work to senior management will be easier when it's so clearly tied to SEO.
The upshot is that ordinary users will experience a more performant web. Not overnight but over a few years, like the shift to HTTPS and supporting mobile web versions. Both of those changes were driven in part by the desire for better ranking on Google.
Out of 71 tracked articles on news sites, only 3 or 4 score 85 or higher in overall Performance as tested by Google Lighthouse.
Article Performance Leaderboard: https://webperf.xyz/
the amp detractors have always said that we don't need amp because authors can just make their websites faster instead. here's the chance to see whether or not that's true.
news organizations have generally terrible performance and deserve to be punished for it in search rankings.
Granted, it's hard so some may be satisfied with orange metrics.
But I've seen on all publisher-friendly communities I am in how much of an Earthquake the CWV Google Update has been, even if it is now pushed back.
Let's hope more and more follow that trend because nobody hate a fast-loading site with good content!
It was pushed back by 6 months, but it's live now.
I am actually fine waiting 200ms longer to get those.
This extension is also actually kinda interesting in that it embeds a small domain specific language [1] that's interpreted with a lex-style parser in JavaScript.
This can itself be a bit heavy on the CPU if a website uses it too judiciously!
[1] https://github.com/ampproject/amphtml/blob/main/extensions/a...
Hear that Google? The experience was so bad that I changed browsers to avoid it.
Google will eventually ban any big enough ad vendor tinkering too much with delayed loading.
They, obviously, cannot ban themselves.
Delayed/deferred loading is supposed to improve page performance metrics, not degrade them.
In light of this, I fail to see how you arrive at this conclusion after an article that essentially says that Google decided to de-prioritize AMP in search results and instead give top spots to well-performing websites regardless of whether they are AMP or not.
If anything, this move encourages delayed/deferred loading for all non-AMP websites, because that's one way to improve your website performance and get your search ranking higher.
I wonder how this affects that Australian law about having to tell news sites about algorithm changes, etc. or maybe is affected by.
https://www.legislation.gov.au/Details/C2021A00021
https://about.google/google-in-australia/an-open-letter/
Everyone loses, frankly. It was one monopoly versus another, and the Australian people were never a concern.
Edit: ah, there's now a provision for this:
> (ii) if the change relates to a matter of urgent public interest—no later than 48 hours after the change is made; and
Shouldn't the quality of a site's _content_ count more than its performance?
All that is a bit irrelevant, this whole thing is about the news carousel specifically, which is basically showing a bunch of articles in a carousel at the top of search results. Previously only AMP articles showed, now I'm guessing you need some minimum threshold of performance. Seems reasonable, you don't want really slow pages that would push away users.
But who this does help is websites who are capable of producing a fast experience and don't rely on a dozen ad-tech companies snippets, which will tend to be the smaller sites.
Most news on the internet is plagiarized off of a few original sources at best and then redistributed on various sites and portals.
This is a devastating problem for a democratic society. For example, local reporting in the United States has been eroded to the extreme. When a society does not have a commitment to factuality, people become more susceptible to fake news (propaganda), conspiracy theories (such as QAnon), and tend to become more uneducated. Yes, it is true, education can be very easily undone, including in highly intelligent, well-educated individuals.
Facts do not come naturally, nor do they come out of “progress”, such as technological progress. Factuality requires hard work and a lot of money, and it requires reporters on the ground, including in foreign places, such as in the case of foreign correspondents. Unfortunately, the use of foreign correspondents for American news services, physically on the ground in foreign lands, has almost been completely eliminated.
The lack of foreign correspondents means that when a crisis abroad occurs, Americans often have to fill in the gaps and infer what is going on. This allows bad actors to take control.
Of course people do not like to hear the facts. They are hard to listen to and believe in, but they are healthy, especially for a democratic and free society. Of course they are healthy for you as an individual.
The Financial Times has excellent reporting with foreign correspondents located in various countries across the world. The Financial Times also has great tech reporting. In the 8 years that I have been a subscriber, I have only found myself disappointed while reading one single article reporting on tech. Also, of course, I subscribe to local newspapers too.
All the data is here:
https://docs.google.com/spreadsheets/d/1sGKmbnW74u9r1GOzAQcI...
(It's "0.01" in the sheet, as I guess it considers the scores percentages.)
Semi-unrelated trivia: Google lighthouse's own website is a disaster[3] by their own standards (with a score of 28), which I find pretty ironic.
[1]: https://developers.google.com/speed/pagespeed/insights/?url=...
[2]: https://developers.google.com/speed/pagespeed/insights/?url=...
[3]: https://developers.google.com/speed/pagespeed/insights/?url=...
The AMP page will still load faster because it conforms to a spec which is known to be preload-safe. This means it can be served by services like search engines without any additional network activity, and with minimal layout calculations needed.
Ultimately that's what AMP was designed for. It's more than just a head-to-head speed comparison.
As a sidenote though, reddit's AMP implementation is horrendous for a dozen reasons. It's almost impossible to escape loading the real site, which is not at all within AMP's design guidelines.
> served by services like search engines without any additional network activity
You mean AMP pages egt preferntial treatment by Google, and all AMP-related Javascript (IIRC, almost 1 MB of it) is loaded the moment you search anything through Google.
When you hit an AMP page, that JS is already preloaded and, true, there's "no additional network activity".
I'd love for Google to serve my pages' Javascript as well when I search something, and get preferencial treatment, but alas.
Promoting pages in a carousel above-the-fold is preferential treatment. Preloading Amp pages however is not. This capability works with any implementation of an Amp Cache, including the one used by Microsoft's Bing.
Ah, I guess preferential treatment by Bing makes it alright. If we forget for a moment that Google has 92% market share among search engines.
I really like how transparent you've made: https://docs.google.com/spreadsheets/d/1sGKmbnW74u9r1GOzAQcI...
And I wanted to run something similar but for our own network of sites. (If so you can reach me on my email in profile). Have about 400 sites to access.
Cumulative Layout Shift is one of those things. Content blocks on the page need to have a fixed height, not one that is dynamic (which might happen with lazy-loaded content).
For some use cases, conditionally loading content (one of those being ads) becomes difficult/impossible if you're using a third party system and can't render server side.
This looks just the next step after PageSpeed and I have no idea why Google didn't push this before the whole debacle with AMP, such stupidity but expected nowadays from the tech giants...
Search was doing its own thing, and they didn't ever have any public speed metrics.
Core Web Vitals is a different approach: pages are compared to thresholds. A huge site perfectly delivered now likely scores lower than a tiny site sloppily delivered. (PageSpeed Insights now reports CWV metrics.) These are the kind of metrics you can use for search ranking, because they are about user experience instead of developer room for improvement (low-hanging fruit).
(I used to work on mod_pagespeed, which would automatically optimize sites, and I still work for Google. Speaking only for myself.)
You know it's true.
1. tap a Google search result link
2. tap the tiny "i" icon on the left side of the stupid AMP page header to display the actual URL of the page I'm trying to navigate to
3. tap the displayed URL itself in the AMP header
4. close reddit's "this looks better in the app!" bottom banner
5. scroll down and tap "VIEW ALL X COMMENTS"
So fast. So usable.
On the bright side, this rigmarole has really done wonders for my productivity because I've simply stopped bothering.
I hate that. It's self-fulfulling really isn't it, may as well simply read 'this banner not present in the app'.
A bit like those joke signs warning you not to steal/deface the sign.
javascript:(function()%7B(function%20()%20%7Bvar%20i%2C%20elements%20%3D%20document.querySelectorAll('body%20\*')%3Bfor%20(i%20%3D%200%3B%20i%20%3C%20elements.length%3B%20i%2B%2B)%20%7Bif%20(getComputedStyle(elements%5Bi%5D).position%20%3D%3D%3D%20'fixed')%20%7Belements%5Bi%5D.parentNode.removeChild(elements%5Bi%5D)%3B%7D%7D%7D)()%7D)()
javascript:var%20url%20=%20false;var%20links%20=%20document.getElementsByTagName('link');Object.keys(links).forEach(function(key)%7Bif(links%5Bkey%5D.rel%20!==%20'canonical')%7Breturn;%7D;url%20=%20links%5Bkey%5D.href;%7D);if(!url)%7B%20alert('No%20Canonical%20URL');%20%7D;if(url)%7Bdocument.location%20=%20url;%7D;To get a quick readable version you always add a i. to the URL, so i.reddit.com. I am afraid of the day they will remove that.
Use "old.reddit.com" (old style, best on desktop but ok on mobile) or "i.reddit.com" (minimalist, for mobile) if you want something usable.
Only option left is to find a content blocker for iPhone that auto-redirects www to old.
It’s really awful, but I’m hopeful these anti-patterns and other Reddit issues (because what is a preference cookie anyhow!?) accelerate alternatives.
New reddit is is a very strange design. I always thought the way it hides comment threads as a link to a new page was just a mobile thing, but no, that’s the design.
The old site is so so much better. Trying to get to it from a google search is infuriating, especially if you are trying to view multiple results. Imagine doing the above steps 5 times for 5 different results!
“Nudging” to install an app you use to collect a ton more data because you intentionally broke the website is fucking evil.
Maybe someone has a Reddit app that isn’t a data mining jerk. IDK. But if not, I still prefer to give no one extra data over just not giving it to Reddit.
Ain't going back either, the URL bar is at the bottom. It's magical ^^
9 out of 10 times AMP pages in Firefox failed to be scrollable. Like the static/fixed top and bottom banner somehow screwed up scroll behavior.
Do you remember mobile news websites circa 2015? It was full of so much ad tech that if a site didn't make your phone hot and crash the browser the best experience you could possibly get would be a couple ad and email form click throughs, maybe a video fading in over the entire content like some trashy mobile app, followed by a scroll jack, a backbutton jacking, then more videos just magically appearing in between paragraphs pushing them apart like some kind of infestation, it was just utterly unusable.
The text that you were lucky enough to catch would quickly fly up and down the screen as more ads start rendering and load in at every div tag with multiple jingles and voice-overs for car insurance and refinancing playing out of your phone all at once. You think "well maybe I really don't care that much about what that diplomat said after all". It was a complete waste of time. They were almost all like this as if there was some secret competition among the news sites, like as if some coveted award was at stake for the craziest most unusable experience.
I'm not sure how its even possible, but I encountered one page I swear hijacked the back button.
The website you're thinking of that does it is slashdot, sorry for the bad news. It's long been merely a shadow of the past.
Amp initially didn't allow JavaScript. It had a bunch of restrictions.
I honestly think it was good people doing it for a good cause but then the corporate meat grinding machine had to process it and they turned it into a power play and data mining operation.
Once again, the solution is inescapable both for /. and the goog; take big money out of tech. Every significant computer revolution basically started on that premise. Time to roll it again. Consolidated power breeds incompetency.
Our most noble task in life is to make the necessary possible and then inevitable
I dont check /. anymore, one of the major news outlets
Speaking from experience, it loads lightning-fast even on an ancient Android device on nerfed 2G data roaming internationally. And the user experience can't be beaten.
Make the web hypertext again!
The day every website out there makes fast and performant websites like the above without any stick or carrot, then you will have a point, but unfortunately we don't live in such a world.
> Congress Passes Bill To Counter The Rise In Anti-Asian Hate Crimes
...which despite the negative language is definitely a positive news story.
But... aren’t hate crimes already illegal? Was there some Asian Exclusion that is being removed? Is this feel good legislation? Or is this also an example of “world on fire” narrative?
That's good news.
By understanding the circumstances and work of the people you're managing, so that you can subtract confounding factors and separate their influence from everything else. There is absolutely no substitute for that, but because it takes actual work and attention, businesses the world over have been trying to replace it with paper thin metrics since time immemorial.
I'm pretty sure that's the primary reason, which won't change anytime soon.
I'd also expect many publishers that adopted AMP to jump ship now, which means it will slowly die away.
Slow, tracker-laden web pages are still terrible, AMP was just the wrong solution.
There are companies pushing the boundaries every day, with governments generally failing to even investigate unless there are enough complaints to raise attention.
Complaints by themselves depend only on shame, which most companies seem to avoid easily. Complaints that catch the attention of governments, on the other hand...
I wonder if they have hard guidelines? Something like "your page should load and render in 1000 ms" on a broadband connection.
while (true) {
Every available channel will fill with every available amount of content until the SNR gets so low that a different channel is created.
}I'd still take a mildly broken AMP page to read an article over the "intended experience" with ads and trackers everywhere and any attempts to block them would break the page further.
The fun part about ads and trackers is that they do not contribute anything functional to a page, so blocking them generally does not break anything.
Presumably the reason Google doesn't do this is that they'd have to punish many of the most popular websites, which might be seen as damaging the quality of their search results (at least in the short term).
Google clearly already knows whether a website is primarily a text-based site or a video-based site, as it displays the two differently in search results. If they immediately blacklisted any text-based site with autoplay video from ever appearing on the first page of search results it would cut about 50% of web bloat overnight.
Yeah they have competing interests when it comes to truly minimising unnecessary resource usage, but there's so much good that they could do without going anywhere near cutting into their own analytics.
That's literally what they're doing with the AMP requirement change, no? Instead of giving priority to AMP pages, they're giving priority to any pages which have good performance.
> If you want higher rankings and more traffic from search engines, you need to optimize your site for a better, more performant and faster user experience.
But wasn't this how things were meant to work before AMP? Google search never had harsh enough penalties to seriously deter bloat, and I don't know that they're going to change that, they're just going to remove the preferential treatment for AMP.
The amount of crap on media pages (while they wail about privacy) is absolutely staggering. How many trackers do these folks need?
I got to MSBNC - a place looking to take down this tracking panopticon system and they are shoving
demdex taboola scorecardresearch tvpixel chartbeat sail-horizon condustrcts imrworldwide hotjar connect.facebook.net womanear.com mparticle.com
etc.
I mean, seriously - why not just use one (like google) and be done.
Can anyone explain why the need so many beacons on a page?
While there is probably a bit of overlap, many of the above tools have very different use cases. For example, chartbeat is commonly used more on the editorial side for writers to track article performance but imrworldwide is a subdomain own by Neilson that they use to serve their sdk which offers metrics for preroll video ads. Hotjar provides user heat maps but sail-horizon is part of sailthru and used for email marketing.
>> The Top Stories carousel feature on Google Search will be updated to include all news content. This means that using the AMP format is no longer required and that any page, irrespective of its Core Web Vitals score or page experience status, will be eligible to appear in the Top Stories carousel.
It doesn't say AMP will not get preferential treatment, it just says your page doesn't have to be using AMP. Don't forget Google has Web Stories[0] to fill this gap as well.
AMP wasn’t cancer; The web itself is. Visit some non-major or local website and you’ll see they’re absolute rubbish, especially those that work on the web, like news agencies.
Newspaper dev shops probably don't have the money to justify a standalone "get rid of AMP" project. So it will take a while to see some migration away.
Anyone have a query that results in a carousel story that isn't an AMP one?
Edit: Found one. "Biden Covid" results in an NPR story in the carousel that is not AMP.
Also, it is fair ty say that the people who hate consequences AMP the most are those who use reddit and discussions generally. Because that is where amp fails the most. Which is pretty close to average user.
People who dont mind amp are the ones who primary use long form static pages ... which is minority of internet.
That isn't true. Google is able to cache AMP pages in their CDN and preload and pre-render them in the browser or in Google News. You can't beat that with even the most optimized site.
AMP, especially on iOS, is awkward for many reasons and having to support two formats by publishers isn't great, but it is unquestionably fast when rendered within a container that supports AMP.
Surely you can do that same pre-rendering yourself, and serve the result of it?
Depending on how confident they are that you are going to tap a given result, they can even preload the actual content and render it as hidden DOM so it can be displayed the moment you release your finger.
There is literally no possible way that a 'real' navigation (to a new page on a different domain) can compete with a simple DOM update.
https://groups.google.com/a/chromium.org/g/blink-dev/c/0nSxu...
https://developers.google.com/web/updates/2018/07/nostate-pr...
On your last sentence: no I don’t think so. There’s got to be some overhead in setting up a new JS/DOM environment, parsing the HTML and CSS, determining security constraints for the new domain name, stuff like that.
The team(s) attempting to incentivize page speed in the SERPS often seem to be working at cross purposes to other Google projects.
Other than that i have no real interest in AMP as an end-user.