.HTACCESS AddType application/x-httpd-php .htm .html Any Issues with SEO

[Capere Spiritum]

Hi All,

I have a newly created website in php using CMSMS. I have read about using an .HTACCESS file with 'AddType application/x-httpd-php .htm .html'

The above will 'display' pages as html files extension rather than php.

I don't know if this is a good idea or not.

Does anyone know of any issues (good or bad) regarding SEO? Or for that matter issues with CMSMS and the above .htaccess file?

Happy New Year to One and All...

[SteveGerencser]

There is no valid SEO reason to add server load to your site this way.. The only time we do this is when we are working with a .html site and want to add php functionality without changing URLs to .php..

[Capere Spiritum]

Thanks Steve, much appresciated...

[radhika]

I use this for some html pages to display as .shtml, so 'virtual includes' works. But remember if you use this tecnique for lot of pages, it uses significant of resources.

If you are going to expand your web site, it might be better you use real .html extention from now on.

Not to scare you, just my thoughts...

.

[weegillis]

... The only time we do this is when we are working with a .html site and want to add php functionality without changing URLs to .php..

And pretty much a necessity during a transition from URL's containing /index.html (URI absolute in the SERP's) to / (URI default of folder undefined in the SERP's). For a time I've foisted PHP on .html pages just for immediacy. Eventually, when all the internal "/index.html" hook references are long gone, one can switch to the appropriate extension, such as .php, .shtml, etc. and with proper redirects in place, reduce remaining .html pages to peripheral roles.

As has been mentioned, the server load makes it an imperative to not sit around too long with the added type configured for pages that search engines favor or main pages on a site. You'll want the best performances for the first time referred visitor. They will wait a little longer for internal browsing.

Problem I find is that once the directive is in place, I forget about it, and put off the short and long term adjustments for an extended period. Working alone, I find it can take ages to actually transform a site with any thoroughness. Meanwhile its pages while PHP enabled are taking longer to download than their .html stand-alones. And now that the cat is out of the bag, so to speak, I can't very well put it back without users noticing right away the lack of uniqueness and timeliness that pre-processing affords.