5 ms·
Google restricts access to the search results carousel to AMP. If they did it in a neutral manner by measuring performance almost all of the criticism would eva
by acdha 8y ago
Google restricts access to the search results carousel to AMP. If they did it in a neutral manner by measuring performance almost all of the criticism would evaporate.
- kodablah 8y agoEek, I wasn't aware they were still doing that, but I confirmed myself. I abhor the practice here, and am now committed to not clicking any more AMP links.
- dmix 8y agoI just searched "news" in Google on mobile and 2 links were non-AMP in my carousel... (ctvnews.ca and thestar.com) but they were heavily optimized in an AMP-like way.
- ebikelaw 8y agoThis is not true and you can demonstrate this for yourself by just searching on Google three or four times and looking at the carousel. Only the top stories and breaking news / live coverage carousels require AMP.
- kodablah 8y ago> Only the top stories and breaking news / live coverage carousels require AMP. I took that to be what the parent meant. And it's not cool and has never been cool, but I thought they backed off for some reason.
- acdha 8y agoThat is what I meant and it does appear that they've backed off at least for the top stories results, which is welcome.
- nkristoffersen 8y agoThat does not align with their documentation. https://developers.google.com/search/docs/guides/mark-up-listings https://developers.google.com/search/docs/guides/mark-up-lis... The search results you see just put in the effort to provide structured data to google. You can do this easily and without any AMP integrations by simply embedding structured data (such as JSON-LD) on the page.
- manigandham 8y agoExcept the reality is different. Sightings of non-AMP links in the top carousel are basically 0.
- derefr 8y agoEmbedded "microformats" like JSON-LD (or, say, Dublin Core RDF metadata) are somewhat problematic, in that they're not covered by the HTML standards, and not documented on any of the "HTML5 tutorial" sites—since they're something "above" HTML. (It'd be a bit like expecting such sites to document how to write inline SVG in your HTML5 document.) So there's no "effortless" way for knowledge of HTML-embedded microformats to filter down to most HTML document authors or web-app theme creators. They have to actually go and seek such knowledge out. And often they don't know what they don't know†, so they have no reason to. Essentially anything on the web that requires or relies on an HTML-embedded microformat to work, is instantly relegated to being an "SEO black art" that just gets passed around in blog posts read by bigcorp web-app devs and no one else. --- † This is one big part of what the people who dislike minification, WASM, etc. are complaining about re: the "readable" web. It used to be that you'd discover techniques like this by just looking at a bigcorp's production web pages and seeing how they work. That's far harder today than it used to be, and it's only going to get even harder in the future.
- manigandham 8y agoRE: the last point, that doesn't seem so. Desktop apps have always been opaque, same as server backends. If anything, the rise of SPAs, WebAssembly, Service Workers and JS in general means you can see a lot more of the action in your browser rather than it being hidden away somewhere. WebAssembly expressly has a textual representation so that it can be inspected, it's part of the spec. And for everything else that's compiled, there are always decompilers to give you the source, often times at great quality. HTTP/2 is binary (and by default encrypted) but nobody notices because browsers and tools transparently convert it to text for you, even though there were plenty of complaints that it would be hard to inspect.
- exotree 8y agoThis is false. Carousel links do not need to be AMP. To be in the carousel, however, you must be approved by Google News publisher center—AMP not required.
- acdha 8y agoIt's possible that they've changed their implementation but it absolutely was not the case for at least the first year or so. It was one of the reasons why I switched exclusively to Brave on mobile because they didn't serve AMP to that user agent, which meant that Google search results loaded faster (that 100KB of render-blocking JavaScript meant a LOT of time looking at empty pages on the subway) and weren't broken if you tried to share or save the URLs. Testing just now, I see only AMP links in the carousel but there are queries where a non-AMP link has sufficient rank to be featured in the top stories section.