Does SEOMOZ bot not know where to look for AJAX site snapshots?

[FuboTV]

snapshot://www.fubo.tv/?escaped_fragment=video/Nigeria_out_to_stop_Messi

page: http://www.fubo.tv/video/Nigeria_out_to_stop_Messi

[SamWeber]

Not being web developers on the help team, I'm hesitant diving into the code and tell you what's wrong here. Running some quick searches on Google though, it does look like there may be something wrong with the site setup. I'd really recommend reviewing the article I linked to above. It's a little old but the material is still relevant.

Once everything is corrected, Roger still may not be able to read the content. The workaround presented above was to show a potential solution but it isn't a guaranteed fix since he does have issues understanding AJAX in general.

http://www.moz.com/blog/create-crawlable-link-friendly-ajax-websites-using-pushstate

I definitely understand how frustrating this can be and wish I could do more to help. Hopefully someone in the community will be able to dive in a bit more on the technical web dev side of things.

[FuboTV]

We are already using pushstate on supported browsers via angularjs ui.router library, which is why you see clean URL on our site without #! notation...

[SamWeber]

Hi there,

This question is a bit intricate.

With AJAX content like this, I know Google's full specifications: https://developers.google.com/webmasters/ajax-crawling/docs/specification indicate that the #! and ?escaped_fragment= technique works for their crawlers. However, Roger is a bit picky and isn't robust enough yet to use only the sitemap as the reference in this case. Luckily, one of our wonderful users came up with a solution using pushState() method.

Click here to find out how to create crawl-able content using pushState . This should help our crawler read AJAX content. I hope this helps

[spencerhjustice]

I can't answer the question exactly, but I did notice that if you go to the url directly, the content displays properly but returns a 404 error. That may cause issues. It doesn't appear to be affecting Google's crawl but I could see it messing up Moz's crawler, especially because I'm fairly positive that Bing doesn't handle ajax properly.