Does bing accept meta name="fragment" for AJAX crawling?

[MarloSchneider]

I have a case in which the whole site is AJAX, the method to appease to crawlers used is

 <meta< span="">name="fragment" content="!">  Which is the new HTML5 PushState that Bing said it supports (At least I think it is that)

This approach works for Google, but Bing isn't showing anything.
Does anyone know if Bing supports this and we have to alter something or if not is there a known work around?

The only other logic we have is to recognize the bing user agent and redirect to the rendered page, but we were worried that could cause some kind of cloaking penalty</meta<>

[Tom-Anthony]

Hey Spencer,

Normally you'd use the meta fragment directive you mention for pages that don't have #! in the URL (see section 3 here: https://developers.google.com/webmasters/ajax-crawling/docs/getting-started) to indicate to crawlers that this site is AJAX.

When crawlers account the #! they usually search for the 'crawl friendly' version of that URL which is specified by the 'escaped_fragment' URL parameter. The directive above indicates to crawlers that even though they don't see a hash they are on an AJAX page.

The #! approach was an interim method that sites used, which is gradually being replaced by the alternative approach that HTML5 PushState allows.

I think if you're still confused the easiest solution would be to get some example URLs for your site (or at least the pattern of the URLs and what markup they have etc., and whether they are indexed).

Hope this helps!

-Tom