To be fair, the "standard" part of this proposal doesn't really have anything to do with headless browsers. You could just as easily have a typical server-side app that generates these URLs as appropriate.
For example, a common approach to presenting content in an AJAXy kind of way is to just put a path after the hash. E.g.
http://www.example.com#/products/bungee-cords
It's probably really easy for the web app to figure out the right content to serve up for #/products/bungee-cords, headless browser or not.
I know you'll be saying, "Of course, but apps should be doing that anyway with progressive enhancement." That's all well and good, but that leads to two separate sets of URLs: one that most users see, and one that search engines see. This fixes that.
I'm perplexed by this. I pay $44/month for Blue Shield California health insurance. Prior to that I live in Washington state and paid only $37/month. Clearly, I'm a recent graduate, and I'm young and healthy, so lots of people won't be able to get that sort of policy. But the article specifically addresses young, healthy, recent graduates!
For some reason the Blue Shield website isn't responding for me right now, but I just checked out Anthem CA's website (the other Blue Cross/Blue Shield company in CA) and they have a bunch of plans listed right off the bat that start at $80:
https://express.rwsol.com/roi/getCCRecommendations.do?produc...
Now, is $80 really that expensive for health insurance?
For example, a common approach to presenting content in an AJAXy kind of way is to just put a path after the hash. E.g.
It's probably really easy for the web app to figure out the right content to serve up for #/products/bungee-cords, headless browser or not.
I know you'll be saying, "Of course, but apps should be doing that anyway with progressive enhancement." That's all well and good, but that leads to two separate sets of URLs: one that most users see, and one that search engines see. This fixes that.