My client's programmer wants to change the site over to read Php vs. the shtml approach. Which is the best way to go ? Should we be implementing 301 redirects to the new php pages? Do we risk the danger in losing ranks?
Subscribe to HRA Now!
SEO Class in Chicago, IL
Learn How To Optimize Your Website on July 26, 2013
Looking for personalized in-depth SEO training among your peers?
High Rankings is offering a 1-day customized SEO training class in Chicago. Class size is limited so please sign-up now if you want in!
Are you a Google Analytics enthusiast?
Share and download Custom Google Analytics Reports, dashboards and advanced segments--for FREE!
www.CustomReportSharing.com
From the folks who brought you High Rankings!
More SEO Content
International SEM | Social Media | Search Friendly Design | SEO | Paid Search / PPC | Seminars | Forum Threads | Q&A | Copywriting | Keyword Research | Web Analytics / Conversions | Blogging | Dynamic Sites | Linking | SEO Services | Site Architecture | Search Engine Spam | Wrap-ups | Business Issues | HRA Questions | Online Courses
Switching Over From Shtml To Php
Started by
Pauline
, May 18 2004 10:23 AM
4 replies to this topic
#2
SearchRank
-
- Active Members
-
- 2,333 posts
HR 7
- Location:Phoenix, AZ
Posted 18 May 2004 - 11:21 AM
Either way is fine, yes and yes.
The file extension does not matter whether it be htm, html, asp, cfm, php, etc. You should most definitely set up 301 redirects and yes you will lose rankings but only temporarily. That is a normal process for any major site modifications.
The file extension does not matter whether it be htm, html, asp, cfm, php, etc. You should most definitely set up 301 redirects and yes you will lose rankings but only temporarily. That is a normal process for any major site modifications.
#3
Randy
-
- Moderator
-
- 17,540 posts
Convert Me!
Posted 18 May 2004 - 10:03 PM
One brief addition...
If there's any way you can maintain the base file names it would be wise. Then you can perform the 301's considerably easier by simply replacing the extension.
If there's any way you can maintain the base file names it would be wise. Then you can perform the 301's considerably easier by simply replacing the extension.
#4
kohashi
-
- Banned
-
- 15 posts
HR 2
- Location:Kathmandu, Nepal
Posted 23 May 2004 - 01:12 AM
isn't it possible to setup .anything to be interpretted by anything you choose? I believe so with MIME types or .htaccess I hear.
search google for 'forcetype php'
If you converted all the pages and then uploaded them as these new types you could manage to change over to php with little or no downtime.
search google for 'forcetype php'
If you converted all the pages and then uploaded them as these new types you could manage to change over to php with little or no downtime.
#5
scolling
-
- Active Members
-
- 203 posts
HR 4
- Location:UK
Posted 25 May 2004 - 04:43 AM
We've also come up against this "technology migration" issue as well. In our case we're migrating a cold-fusion site to ASP. Our approach has been to set up application mapping on all .cfm and .html files (which were the original extensions) to be treated as .asp files for the new site then we can publish pages using the old names, but they will be parsed as ASP files by the server.
However, as we have also significantly redesigned the site structure, added new pages etc. we have also published two versions of the new pages at the domain. One version in the new structure using a new, better, filename with the .asp extension, and the same page published in the old structure with the old filename and extensions (i.e. .cfm or .html). These pages all have the new navigation with the links pointing to the new .asp pages.
This increases admin for a while, but once the new pages have picked up their PR and ranking then we'll stop maintaining the copies that have the old names.
I can't comment on how effective this will be, or how long it will take before we can drop the old names as we're just implementing it now, but we're hopeful it will provide a smooth transition with little or no impact on the rankings.
Simon
However, as we have also significantly redesigned the site structure, added new pages etc. we have also published two versions of the new pages at the domain. One version in the new structure using a new, better, filename with the .asp extension, and the same page published in the old structure with the old filename and extensions (i.e. .cfm or .html). These pages all have the new navigation with the links pointing to the new .asp pages.
This increases admin for a while, but once the new pages have picked up their PR and ranking then we'll stop maintaining the copies that have the old names.
I can't comment on how effective this will be, or how long it will take before we can drop the old names as we're just implementing it now, but we're hopeful it will provide a smooth transition with little or no impact on the rankings.
Simon
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
