Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Well, that's my point, it's not trivial to automatically recognize which photos are content and which are style. You want to have many content photos, but having many style photos probably means cruft.

How do you recognize which is which?



Same way almost all browsers offer a Reading view. They still show the article image. Doesn't seem to be that hard of a problem.


How does AMP recognize this right now?


It doesn't, it just forces you to display the pages through Google, stripping everything else, which is much easier to implement than recognizing if a web page's heft is because of legitimate content or ads.


So what difference would it make? After all, this is the result after AMP has done all its cleaning, which would give you a pretty accurate measure for page weight. What remains is the actual content of the page. It's the cruft that should be penalized, not the actual content.


Exactly what my sibling comment said, it's the publisher (presumably a human) who does the cleaning. It's not as easy to get a bot to clean things up and then measure weight, and the various "Readability" views aren't always correct (they're using heuristics).

Sounds like a publisher-assisted "readability view" would solve both problems, though. It would allow the user to view a "lighter" version of the page and search engines could just measure how large the "non-light" version is and penalize accordingly. I'm afraid that would incentivize the publisher to put ads and other crap in the "light" view, though.


AMP doesn't do the cleaning.

You as the publisher/author have to implement an AMP page yourself and then alert Google of its existence.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: