URL Rewriting Best Practices

[TheDude]

Thanks for the response Dmitrii!

Thanks for for confirming that I don't need to update the webpage file names.

Do you know if redirecting the old directories to the new ones (using the the rewrite below) is all I need to do regarding redirects? In other words, when redirecting directories using the rewrite below is there any need to redirect the old URL format (small_blue_widget.htm) to the new (small-blue-widget)? My understanding is no, all I need to do is redirect the directories; but please share your knowledge.Thanks in advance!

<code>RewriteRule ^old/(.*)$ /new/$1 [L,R=301]</code> 

[DmitriiK]

the rule you wrote wont work.

What it will do is redirect this: _domain.com/old/small_blue_widget.htm _to this: domain.com/new/small_blue_widget.htm

To remove the extension would be:

<code>RewriteRule ^([^\.]+)$ $1.htm [NC,L]</code>

[TheDude]

Hey Dmitrii,

This rewrite that I posted above...

RewriteRule ^old/(.*)$ /new/$1 [L,R=301]

...isn't intended to remove the file extensions. I'm using it to redirect the old directory structure to our new directory structure.

I was asking if using this rewrite when changing my directory structure will be all I need in regards to having all the necessary redirects in place to not negatively affect our SEO/SERP rankings. Any idea?

Also, would you recommend the rewrite you provided above over the one below when removing file extensions?

RewriteBase /
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME}.html -f
RewriteRule ^(.*)$ $1.html

Let me know if I'm being clear enough Thanks!

[DmitriiK]

Yes, I believe so, that's the only rewrite you'd need not to mess up rankings.

I don't know if one of codes is better than another. All I know that my piece of code is working and i haven't used the one you wrote. It seems ok to me, but just test it. If it works, I don't think there is any difference.

[TheDude]

Thanks for the help Dmitrii!

Both the rewrite I posted above and yours for removing file extensions failed to work. However, it seems this one does the trick (taken from the Apache help forums).

RewriteCond %{THE_REQUEST} ^[A-Z]{3,}\s([^.]+).htm [NC,OR]
RewriteCond %{THE_REQUEST} ^[A-Z]{3,}\s([^.]+).php [NC]
RewriteRule ^ %1 [R,L]

[TheDude]

Another question just popped into my head...

Once our new website directory structure and URL format has been rewritten, redirected and indexed by search engines, would it make sense to edit the actual webpage file names (replacing the underscores w/ hyphens) and then remove the URL rewrite that replaces the underscores with the hyphens? Or is this not recommended?

[DmitriiK]

Well, I thought that's what you were going to do and use rewrite just for deleting file extensions. Honestly, I'd leave file extensions and rename files to hyphens. This way there is no server processing involved.

[TheDude]

Hey Dmitrii,

I was planning on using two rewrites.

One rewrite for replacing the underscores with hyphens.

And another rewrite for removing the file extensions.

Just so I fully understand, you recommend implementing the rewrite for replacing the underscores with hyphens in our .htaccess file. Then once the new URLs are indexed, change the webpage file names themselves by replacing the underscores with hyphens, make the newly named files live and remove this rewrite from our .htaccess. Is my understanding correct?

Again...thanks for all of your help!

[DmitriiK]

I'm saying rename files first and do rewrite for removing extensions.

You will have to do rewrite for replacing underscores with hyphens anyway, just for redirect purposes.

So, rename files from underscores to hyphens; do rewrite rule for underscore to hyphens to insure old pages are being redirected; do another rewrite for removing file extensions. In som time (2-3-4 months) when old file names (with underscores) are out of google index, delete first rewrite.

[TheDude]

Thanks for clearing that up and all of the help!