Changing .htm to .shtml or .php to shtml search engines

Does anyone know if all pages in a fairly established site are changed from
..htm to .shtml or .php all of the search engine indexing will be lost? Other
than the file type change everything else remains the same including file
structure, linking etc..

David J.

David wrote:
> Does anyone know if all pages in a fairly established site are
> changed from .htm to .shtml or .php all of the search engine indexing
> will be lost? Other than the file type change everything else remains
> the same including file structure, linking etc..

Arrange a 301 redirect, and google understands, and the users that have
bookmarked parts of your site will thank you for not breaking their links.

If on apache, and mod_rewrite is possible for instance:

RewriteRule (.*)\.html$ $1.shtml [L,R=301]
--
Rik Wasmus

..oO(David)

>Does anyone know if all pages in a fairly established site are changed from
>.htm to .shtml or .php

There's no reason to do that. Cool URIs don't change, so keep the .htm.
If you need some server-side stuff like scripting or SSI you can do that
even on .htm files.

Micha

Michael Fesser wrote:
> .oO(David)
>
>> Does anyone know if all pages in a fairly established site are
>> changed from .htm to .shtml or .php
>
> There's no reason to do that. Cool URIs don't change, so keep the
> .htm.
> If you need some server-side stuff like scripting or SSI you can do
> that even on .htm files.

Parsing every .htm for the change it has some script in it is hardly
elegant.
Go for a 301 redirect. Browsers and search engineds understand that.
--
Rik Wasmus

Well, I was going to use ssi's for certain chunks of code (lots a pages) and
I am on a Win server. From a little research looks like there's no easy way
on a win server to 301 all pages like on Apache.

David




"Michael Fesser" <netizen@gmx.de> wrote in message
news:t2bmp25bu7piddatqe9i1adr1j1vb7u804@4ax.com...
> .oO(David)
>
>>Does anyone know if all pages in a fairly established site are changed
>>from
>>.htm to .shtml or .php
>
> There's no reason to do that. Cool URIs don't change, so keep the .htm.
> If you need some server-side stuff like scripting or SSI you can do that
> even on .htm files.
>
> Micha

..oO(Rik)

>Michael Fesser wrote:
>> .oO(David)
>>
>>> Does anyone know if all pages in a fairly established site are
>>> changed from .htm to .shtml or .php
>>
>> There's no reason to do that. Cool URIs don't change, so keep the
>> .htm.
>> If you need some server-side stuff like scripting or SSI you can do
>> that even on .htm files.
>
>Parsing every .htm for the change it has some script in it is hardly
>elegant.

It works well and doesn't cause much trouble for the server. If you use
PHP/SSI for more than just some little add-ons, then it will most likely
be used on every page anyway, so there's not really a problem by passing
all pages to the interpreter.

But if you don't like doing it that way - there are still other ways of
mapping URLs onto the file system. Keywords are mod_rewrite and content
negotiation (MultiViews), assuming an Apache webserver (you already
mentioned that some minutes ago in ciwah).

>Go for a 301 redirect. Browsers and search engineds understand that.

I consider that the worst idea of all, because it's completely
unnecessary and a sign of a broken URL design. The server should do the
work, not all the clients.

Micha