![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
1) Search engine page ranking will plummet in the short term. 2) Existing bookmarked pages will no longer be reachable. We would value any opinion and/or advice on these issues. |
#3
| |||
| |||
|
|
You're on Apache, so you can use mod_rewrite to forward *.html to *.php. |
|
You can do this by enabling content negotiation |
#4
| |||
| |||
|
|
.htaccess was the route I was headed. Can you provide re-assurance that going down this road will not impact on existing SE page ranking ? |
#5
| |||
| |||
|
|
On Sun, 28 Sep 2008 10:16:27 +0000 (UTC) Joe Makowiec said : You're on Apache, so you can use mod_rewrite to forward *.html to *.php. ..htaccess was the route I was headed. Can you provide re-assurance that going down this road will not impact on existing SE page ranking ? You can do this by enabling content negotiation This is an interesting one which I will also pursue. Thanks for your help. |
#6
| |||
| |||
|
|
On 28 Sep 2008 in macromedia.dreamweaver, Ronnie MacGregor wrote: 1) Search engine page ranking will plummet in the short term. 2) Existing bookmarked pages will no longer be reachable. We would value any opinion and/or advice on these issues. You're on Apache, so you can use mod_rewrite to forward *.html to *.php. |
|
Make sure you include a "301" status code. That will tell the search engines that the page has a new address: |
|
While you're at it... I notice that the pages are of the form /somename/somename.html (ie /Morzine/Morzine.htm). You might take this opportunity to get the names shortened to just "somename", without trailing slash or extension. So the URI for Morzine would be http://chaletjacinthe.com/Morzine http://www.w3.org/Provider/Style/URI |
![]() |
| Thread Tools | |
| Display Modes | |
| |