I'm using mod-rewrite to give me some lovely urls: example.com/nice-friendly-urls but should I have 'em

 

example.com/nice-friendly-urls

 

or

 

example.com/nice-friendly-urls/

 

So should I have a slash or not a slash - they won't be going any lower than an initial folder.. so what do you think? I can't have both as google see 'em as duplicate content!

 

Ive used mod-rewrite with wordpress on my website. Its now displaying URL's like this:

 

http://www.domain.co.uk/v1/updates/v2-in-the-works

http://domain.co.uk/policy

http://domain.co.uk/tutorials

 

So I would go with the 1st one

Yeah, I would agree, no slah, so go with the 1st one

I think the no-slash option is best.

well... I wouldn't be so sure if I was you....

Search engines do funny things sometime, read this

 

Hope this helps

 

Oli

great article - the mind boggles! It's a confusing world out there!

Very confusing...

crawlers are very funny sometimes...

 

I've had an example recently where I used modrewrite on a guestbook I wrote for the pagination to look better so instead of guestboob.php?page=2 I had guestbook/page2...

 

Well google started indexing funny things thinking guestbook/ was a folder and as I had the main navigation on that guestbook page got really confused and indexed all my normal pages (index.php, news.php....) as guestbook/index.php guestbook/news.php....

 

i prefer to mod rewrite to .htm pages to be honest. solves the issue anyway.

it depends.

with a trailing slash it means you are requesting a folder. (which usually brings up the index page for that folder) no trailing slash means you are requesting a file. However, most servers will look for a file then if no file is found it'll look for a folder. To avoid unnessesasy lookups, use trailing slashes.

i prefer to mod rewrite to .htm pages to be honest. solves the issue anyway.

 

True, but it's nice to say, example dot com slash whatever