Second, we always set up 301 redirects for old pages from a site to their appropriate new pages when we re-launch a site. We just picked up a client and the old site apparently got too fancy with their AJAX/HTML5 stuff and used a hashbang notation (i.e. example.com/#!menu-chicken ). Does anyone know a best practice way of handling that?
I found that the site DOES support AJAX Crawling ( https://developers.google.com/webmasters/ajax-crawling/docs/getting-started ) which we can redirect, but has anyone had to deal with redirecting sites based on this? Are we gonna need to set up redirects on the server for the AJAX Crawling, and then write a client side redirect on the home page?
Brian LePore
First, I am happy that 24ways is back.
Second, we always set up 301 redirects for old pages from a site to their appropriate new pages when we re-launch a site. We just picked up a client and the old site apparently got too fancy with their AJAX/HTML5 stuff and used a hashbang notation (i.e. example.com/#!menu-chicken ). Does anyone know a best practice way of handling that?
I found that the site DOES support AJAX Crawling ( https://developers.google.com/webmasters/ajax-crawling/docs/getting-started ) which we can redirect, but has anyone had to deal with redirecting sites based on this? Are we gonna need to set up redirects on the server for the AJAX Crawling, and then write a client side redirect on the home page?