We use Ajax throughout our website and our Ajax apps were built prior to google’s hashbang (#!) solution.
To make our pages readable to search engines and non-Javascript-enabled browsers we set up a ‘parallel universe’ and send static urls to search engines and non-Javascript-enabled browsers and # fragment to Javascript-enabled browsers, for example:
<a href="category/subcategory2/page.html" onClick="navigate('category/subcategory1/page.html#subcategory2'); return false">subcategory2</a>
Until now we had considered the hashbang (#!) solution too costly to implement.
Does panda change that?
In the ‘parallel universe’ google sees separate pages and unlike the user with a Javascript-enabled browser doesn’t know how or if the pages are related.
Google sees this:
www.example.com/category/subcategory1/page.html
www.examplecom/category/subcategory2/page.html
Users with Javascript-enabled browsers see this:
www.example.com/category/subcategory1/page.html
www.example.com/category/subcategory1/page.html#subcategory2
In a panda world do the following static urls sent to search engines risk being interpreted as near-duplicate content?
www.example.com/category/subcategory1/page.html
www.example.com/category/subcategory2/page.html