Some people prefer use trailing slash for urls for example http://example.com/something/ instead of http://example.com/something, actually, according to RFC 3986 it does make a difference. Any two URLs are not a character-by-character match (ignoring URL encoding which does not apply in this case) are considered to indicate different resources. This means that client agents such as Google, Yahoo, MSN, and all other search engines, crawlers, systems and all browsers are violating the specification if they assume the two URLs are the same.
Well, to avoid this problem we can follow this steps to modify the .htaccess:
# Custom Fix
# Only if url does not contain already a trailing slash "/" or a file extension ".xxxxx" at the end
# trailing slash fix
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !(\.[a-zA-Z0-9]{1,5}|/)$
RewriteRule (.*)$ http://example.com/$1/ [R=301,L]
# Only if url does not contain already a trailing slash "/" or a file extension ".xxxxx" at the end
# trailing slash fix
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_URI} !(\.[a-zA-Z0-9]{1,5}|/)$
RewriteRule (.*)$ http://example.com/$1/ [R=301,L]
Post new comment