"but I recently had my site revamped by a professioal developer"
Professional? Developer, hmmm. To me a professional should know about these types of issues, I havent' made a .php page for years, all are parsed php with .htm extensions, it's simply too easy to do that to even consider any other option, and since every page of every site I do is scripted, there's no reason not to use .htm always, or nothing, as some people prefer, although I prefer to have an extension if only for old time's sake.
This might only be me, but when I see a site that uses php, asp, aspx, jsp etc, it's not a good first sign, it assumes the same processing language will always be running your website, which it may not be. Much safer to just stick with plain old htm, which is what the user is always receiving anyway, the php/asp/asp/jsp is really only relevant to the server, and aren't necessary at all.
It will be a good day when professional developers understand enough about seo and good site urls [good urls don't change] to stop making these types of mistakes.
By the way, I just checked an old site I did for someone, and they had switched it to shtml, probably to include nav bars or something, thinking they were all clever, not realizing the site was always setup to run as php if required. All their backlinks picked up over the last year, broken, all pages now treated as duplicate content by search engines, sad. I'm starting to think the number of actually professional web developers is MUCH smaller than we believe, by a very large percentage.
|