![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have several questions about converting a site from ASP to PHP and the effect. 1. Will there be any adverse effect on SERPs or Page Rank by converting? |
|
2. URLs will be changed to - mysite.com/a/b/c.asp to mysite.com/a/b/c.php. Are these two URLs viewed by search engines as the same URL? |
|
3. Are there any other issues that I should be aware of, in regards to converting an existing site to PHP, as it relates to the SERPs and their current positions? |
#3
| |||
| |||
|
|
Good evening, craig wrote: I have several questions about converting a site from ASP to PHP and the effect. 1. Will there be any adverse effect on SERPs or Page Rank by converting? See 2. + 3. 2. URLs will be changed to - mysite.com/a/b/c.asp to mysite.com/a/b/c.php. Are these two URLs viewed by search engines as the same URL? No. So you'll loose PR from inbound links to the old URLs. You could either install 301 redirects from the old URLs to the new ones and hope that SE transfer the PR to the new URLs or don't change the URLs at all. You could configure your webserver to treat .asp as the suffix for PHP files or map .asp URLs to .php files, e.g. with mod_rewrite, if you are using apache. Exposing such 'implementation details' is a bad idea - no one really cares, if you are using PHP, ASP or whatever, so your URLs should better look like example.com/a/b/c>. As you see, you'll get into troubles, if you decide ti change the implementation. 3. Are there any other issues that I should be aware of, in regards to converting an existing site to PHP, as it relates to the SERPs and their current positions? SEs don't care, what you are using on the server-side to generate the documents - and (with a little bit work on the server-side) may not even be able to notice that there is server-side processing involved. HTH -- Benjamin Niemann Email: pink at odahoda dot de WWW: http://pink.odahoda.de/ |
![]() |
| Thread Tools | |
| Display Modes | |
| |