Switching From Asp To Php - Affects On Ranking
#1
Posted 25 June 2007 - 11:27 AM
i've done this before and it seems google was slow to assign a new PR to the changed site.
is this something that should really be avoided?
i guess i can just name the pages ".asp" and use htaccess to run them as php, but i'd rather not?
anyone have experience with this situation?
#3
Posted 25 June 2007 - 12:16 PM
#5
Posted 26 June 2007 - 08:09 AM
There is a crazy notion that pages produced by scripts have to be located in a "cgibin" or "cgi" area. This is exposing the mechanism of how you run your server. You change the mechanism (even keeping the content the same ) and whoops - all your URIs change.
It doesn't explicitly mention SEO or even redirects, but he's right: cool URLs don't change. I imagine the guy knows what he's talking about - didn't he invent something ... ?
Maybe, with this transition away from ASP, you can work on getting the URLs platform independent? Instead of http://domain.com/folder/file.asp you could just use http://domain.com/folder/file/ (and use the default file handler, if you don't want to use extensionless files).
John
Added: I run into the same problem on my sites as well - but I'm getting better at it. Sigh. It's just too easy to do it for a short term benefit...
#6
Posted 26 June 2007 - 12:00 PM
With both Apache + .htaccess and IIS + Application Extensions would allow you to change the page extension to anything you want. Does the page extension play any roll in rankings?
The example I can think of off the top of my head is Ars Technica ( http://www.arstechnica.com ) whose index page is actually index.ars and not any real file extension type. If you have a really short keyword, would it be worth your time to take that keyword and make that the file extension for all your pages?
#7
Posted 26 June 2007 - 01:37 PM
John
#8
Posted 27 June 2007 - 07:55 AM
#9
Posted 27 June 2007 - 08:12 AM
Example:
Old: /folder/page.htm
New: /folder/page.htm/default.asp
When a client accesses "/folder/page.htm" the server will issue a redirect to the version with the trailing slash (it would be a good idea to check to make sure that your server does a 301 redirect for that), which will then access the script in that folder. Within that script you could set up a normal 301 redirect to the actual new page. You can use that trick for all sorts of files that need to be redirected (if you do not have access to .htaccess or use a non-Apache server).
Hope it helps!
John
Reply to this topic

0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users






