How to fight back against Google AMP as a web user and a web developer

Post by dmitriid » Fri, Dec 06, 2019, 5:28 AM UTC

gregable wrote: post #442

dmitriid wrote: post #376

Earlier quoted context omitted.

Hello, gregablr who works on AMP and forgets to disclose it: No, AMP is not "just HTML". It's not HTML5-compliant. It requires js to run and display properly (because Web Components), it gets preferential treatment in Google Search. It's not plain HTML.

Any AMP page can be HTML5 compliant. AMP doesn't require that the page pass an HTML5 validator, but is entirely compatible with HTML5. JavaScript and Web Components are part of the HTML5 standard. This is simply the Extensible Web ( https://www.w3.org/community/nextweb/2013/06/11/the-extensib... ) My profile discloses that I work on AMP.

Post by girvo » Fri, Dec 06, 2019, 5:54 AM UTC

progval wrote: post #412

thereisnospork wrote: post #403

Earlier quoted context omitted.

>> That is why AMP has been successful >This is not. If google removes ranking incentive, people will forget about AMP the next day Google giving ranking incentive to sites that are faster seems like the exact sort of thing they should be doing.

Except that it's now giving a huge boost to websites that use a specific technology to be fast; instead of just boosting all fast websites like it used to. Sites can be fast even if they don't use AMP.

Post by 827djdjs6 » Fri, Dec 06, 2019, 6:07 AM UTC

soyyo wrote: post #30

I worked on amp for a leading newspaper, and everyone who says that amp is about "making the web faster on mobile" is either very naive or doing marketing for google. For publishers, amp is about trying to top the results on google search and capture traffic, it's their only motivation to publish their content using amp, and the only metric they look in order to evaluate the results. Once they have their amp content,…

Post by stephenr » Fri, Dec 06, 2019, 6:47 AM UTC

gregable wrote: post #441

JoshMnem wrote: post #437

Earlier quoted context omitted.

It's the other way around -- AMP pages show a blank page for 8 seconds for people with ad-blockers because of that CSS rule.

The behavior you describe occurs if the useragent blocks the URL https://cdn.ampproject.org/v0.js which does not have anything to do with ads or analytics. Certainly an ad blocker can be used to block any URL, but I don't know of any that block this one by default. If there are any, let me know and I'm happy to file issues to get that fixed! If a user chooses to block this particular resource which the page needs to…

Post by stephenr » Fri, Dec 06, 2019, 6:52 AM UTC

bscphil wrote: post #445

joshuamorton wrote: post #367

Earlier quoted context omitted.

A priori not anymore so than otherwise downranking slow sites. The missing piece here is how using amp is beneficial to Google or harmful to consumers/other search engines to make it anticompetative.

> how using amp is beneficial to Google You are correct, most people are leaving this out. I think an emphasis on asking why Google is pushing AMP, and whether that interest aligns with consumers, would be helpful in this thread.