... what do i do with the old ones?
I am currently rewriting my website, from the bottom up, and as part of this rewrite comes clean urls. How do I handle the 4000+ untidy urls in a way that google won't tell me to f. off?
<!-- m --><a class="postlink" href="http://domain.com/showpic.php?view=1&gallery=house&image=dscf0001&ext=jpg">http://domain.com/showpic.php?view=1&ga ... 01&ext=jpg</a><!-- m --> (what was I thinking?)
will now be similar to
<!-- m --><a class="postlink" href="http://domain.com/pictures/house/dscf0001">http://domain.com/pictures/house/dscf0001</a><!-- m -->
If I use 301 redirect in htaccess, will that slow the server down on every request, not to mention that I will have to hand code the new url.
Would it be better to have a 404 document which will scan the uri and redirect accordingly? (sill hand coded)
Can I get away with just redirecting showpic.php to /picutures which will show the galleries to be selected or will this confude google?
Any Ideas?
Thanks in advance
Tim
PS This is on a LAMP server.
I am currently rewriting my website, from the bottom up, and as part of this rewrite comes clean urls. How do I handle the 4000+ untidy urls in a way that google won't tell me to f. off?
<!-- m --><a class="postlink" href="http://domain.com/showpic.php?view=1&gallery=house&image=dscf0001&ext=jpg">http://domain.com/showpic.php?view=1&ga ... 01&ext=jpg</a><!-- m --> (what was I thinking?)
will now be similar to
<!-- m --><a class="postlink" href="http://domain.com/pictures/house/dscf0001">http://domain.com/pictures/house/dscf0001</a><!-- m -->
If I use 301 redirect in htaccess, will that slow the server down on every request, not to mention that I will have to hand code the new url.
Would it be better to have a 404 document which will scan the uri and redirect accordingly? (sill hand coded)
Can I get away with just redirecting showpic.php to /picutures which will show the galleries to be selected or will this confude google?
Any Ideas?
Thanks in advance
Tim
PS This is on a LAMP server.