I will let google answer to your question: http://googlewebmastercentral.blogspot.com/2008/09/dynamic-urls-vs-static-urls.html In the article: Which can Googlebot read better, static or dynamic URLs? […]While static URLs might have a slight advantage in terms of clickthrough rates because users can easily read the urls, the decision to use database-driven websites does not imply a significant disadvantage in terms … Read more
There are two steps to solve this problem. First, create a new route or change the default route to accept an additional parameter: routes.MapRoute( “Default”, // Route name “{controller}/{action}/{id}/{ignoreThisBit}”, new { controller = “Home”, action = “Index”, id = “”, ignoreThisBit = “”} // Parameter defaults ) Now you can type whatever you want to … Read more
Be careful with allowing a page to render using the same method as Stack overflow. http://stackoverflow.com/questions/820493/random-text-can-cause-problems Black hats can this to cause duplicate content penalty for long tail competitors (trust me). Here are two things you can do to protect yourself from this. HTTP 301 redirect any inbound display url that matches your ID but … Read more
Try this rule: RewriteCond %{REQUEST_FILENAME}.html -f RewriteRule !.*\.html$ %{REQUEST_FILENAME}.html [L] This will rewrite all requests that can be mapped to an existing file when appending a .html.
Tim Berners-Lee (the architect of the WWW) wrote a great article about this subject about 10 years ago. Your example is a bad URL — but not just because it has both an id and a “slug” (the abbreviated, hyphenated form of the page title). Putting the page title into your URL is problematic in … Read more
Just add an .htaccess file to the root folder of your site (for example, /home/domains/domain.example/htdocs/) with the following content: RewriteEngine on RewriteCond %{REQUEST_FILENAME} !-d RewriteCond %{REQUEST_FILENAME}\.php -f RewriteRule ^(.*)$ $1.php More about how this works in these pages: mod_rewrite guide (introduction, using it), reference documentation
There’s no ambiguity here: RFC3986 says no, that is, URIs cannot contain unicode characters, only ASCII. An entirely different matter is how browsers represent encoded characters when displaying a URI, for example some browsers will display a space in a URL instead of ‘%20’. This is how IDN works too: punycoded strings are encoded and … Read more
According to this article, you want a mod_rewrite (placed in an .htaccess file) rule that looks something like this: RewriteEngine on RewriteRule ^/news/([0-9]+)\.html /news.php?news_id=$1 And this maps requests from /news.php?news_id=63 to /news/63.html Another possibility is doing it with forcetype, which forces anything down a particular path to use php to eval the content. So, in … Read more
The slugs make the URL more user-friendly and you know what to expect when you click a link. Search engines such as Google, rank the pages higher if the searchword is in the URL.
I recently wrote a URL encoder, so this is pretty fresh in my mind. http://site/gwturl#user:45/comments All the characters in the fragment part (user:45/comments) are perfectly legal for RFC 3986 URIs. The relevant parts of the ABNF: fragment = *( pchar / “/” / “?” ) pchar = unreserved / pct-encoded / sub-delims / “:” / … Read more