Background:
I’m working on a number of web applications that are built using AngularJS. Our AngularJS applications is a SPA (Single Page Application). We are conforming to the AJAX Crawling Specifications as defined by google and generally adopted by the bot and crawling communities ( https://developers.google.com/webmasters/ajax-crawling/docs/specification). I am surprised to see that twitter cards do not support hashbang ("#!" - aka shebang) style URLs. While I don’t expect your twitter bot to handle the rendering of the page like my browser does (typically organizations like mine will implement an SEO Service, and we are no different), I would however expect the twitter bot to handle the URL (even if it converts the “#!” to “?escaped_fragment=”.
My Questions:
- Why is this not supported? This is a widely used web standard
- Why does the twitter bot explicitly strip out anything to the right of the “#!”?
- Is support for this on the roadmap, or will twitter continue to exclude this standard?
- Is there a workaround that I’m just not aware of?
This is easy enough for me to work around if I provide a “tweet” button, but this means that any user that copies one of my URLs to their clipboard to tweet on their own will find the link to be broken.
