I have a multilingual website with the following structure:  example.com       &lt;--- Main english version example.com/fr    &lt;--- The french version   Is it important for SEO reasons to put a trailing slash in example.com/fr and make it example.com/fr/ or is it not important?
45567
Does it make any difference to SEO ratings what-so-ever if your url has a trailing slash:  http://www.example.com/some/slug/paths/   as opposed to one that does not:  http://www.example.com/some/slug/paths
63702
After reading  about spacing and punctuation, I was left wondering about an issue that didn't seem to be addressed: using \frenchspacing together with the modified punctuation \@., \@?, etc.  As far as I can tell visually, using \frenchspacing together with these commands works correctly (i.e., it seems like nothing breaks, and the extra space is suppressed as normal), but are there problems that can arise from doing so?   Moreover, when using \frenchspacing, "should" I still use \@. and its friends where it would ordinarily be necessary, in case someone wants to remove \frenchspacing later? Would accommodating (hypothetical) future editors in this way be "standard", "above and beyond the call of duty", or "crazy"?
7008
I'm working for a website to convert the website URL to an SEO friendly URL. I plan to use this:  example.com/category-name/pageid-123-page-name  I looked at some similarly categorized, highly ranked websites. They have the same structure, except for one thing. In one case, the URL format was  example.com/category-name/pageid-123-page-name.html  Another was   example.com/category-name/pageid-123-page-name.php  Now I know the text in URLs help with SEO. Is it more helpful to have a file extension? If yes, which one is better?  Or if my current plan is okay, will it be better with a / at the end?
100409
I am asking this because whenever I hover over a link to a home page (e.g. http://www.example.com), I notice that a trailing slash is always added (as observed on the status bar of the browser) whether the home page link contains a href attribute that ends with a slash or not. But whenever I am on the home page, the URL on display will not have a trailing slash.  I tried entering a slash to the URL in the URL bar. And with Firebug enabled, I notice that the site always return a 200 OK status. An article  discussing this states that having a slash at the end will avoid a 301 redirection. But I am not seeing any redirection, even on  page.  Could this be a browser feature that is appending the slash?
4831
I added a comment to  but something strange is happening. The end code reads "); but SO decided to change that to ";);.    I did not add a ; in front of the ).  To further explain what's happening here, the following:  "http://example.com/." http://example.com/. "http://example.com." http://example.com. "http://example.com" http://example.com   renders as:
26690
Other than for historical reasons, is there is reason to have “www” in a URL?  Should I create a permanent redirect from www.xyz.com to xyz.com, or from xyz.com to www.xyz.com? Which one would you suggest and why?
69138
The situation  Across the entire domain, we'd like the URLs to hide file extensions and remove trailing slashes, independent of the domain name itself (as in, works on any domain).  Sample of our directory structure  We're not using index.* files except for the homepage.   /  /index.php /account.php /account  /subscriptions.php  /login.php /login  /reset-password.php     The goal  Some examples of how these files might be requested, and how they should look in the browser:   / and index.php --> mydomain.com (literally just the bare domain name). /account.php or /account/ or /account --> mydomain.com/account /account/subscriptions.php or /account/subscriptions/ or /account/subscriptions --> mydomain.com/account/subscriptions   As you can see, there are several ways to access each webpage, but no matter which of the 2 or 3 ways you use to get there, it only shows the one preferred URL in the browser.  The question  How is this done with .htaccess using mod_rewrite?  I've banged my head against the wall trying to figure this out, but in general, the rewrite flow would seem to be something like this:   External 301 redirect ( mydomain.com/account/ --> mydomain.com/account ) Internally append .php ( mydomain.com/account --> mydomain.com/account.php )   I've been Googling this all day, read thousands of lines of documentation and config texts, and have tried several dozen times... I think more brains on this would help a lot.  UPDATE  We found an answer our question (see below).
106890
Attention I have already a possible answer and will add it soon. I thought it would be useful to have a solution about it on the site. (Other answers are naturally welcome too).  Question How to activate or suppress the french spacing before some punctuations like a colon in the text argument of \href locally (for one specific \href) and globally? Switching the language is not an answer!  Minimal examples for tests (the argument of \href should normally be a valid url, so it is a bit unfair to add an example without a colon in the link):  pdflatex  With pdflatex it depends on the link how the argument of \href is printed:  \documentclass{article} \usepackage[french]{babel}  \usepackage{hyperref}  \begin{document} With pdflatex no french spacing in links with colons:   \href{link}{a:b}  \href{link:colon}{a:b}  \end{document}     lualatex  With lualatex the spaces are always there:  \documentclass{article} \usepackage[french]{babel}  \usepackage{hyperref}  \begin{document} With lualatex always spaces:  \href{link}{a:b}  \href{link:colon}{a:b}  \end{document}
53557
Google clearly states that duplicate content within a single, or multiple, domains is not advised. This is understood, but I am not sure of any exceptions for sites with region-specific content that is often replicated across locales.  For example, a site's /en-us/about page could be identical to /en-uk/about, whereas most likely /en-ja/about is unique.  Are GYM smart enough to understand that the initial URL depth is a locale specifier? Is there any robots.txt or header, etc, trickery that I should include to outline the site's international structure?
16854
I have a website running in English and Japanese and the default language is Japanese.  What are the advantages of one over the other solution:   Solution 1. When accessing example.com, you will see only Japanese. When accessing example.com/en, you will see only English. Solution 2. When you access example.com, it will redirect you to example.com/ja, where you will see only Japanese. English site is still example.com/en.
35215
I've enabled the Locale and Content Translation module but am having trouble understanding how to do something that it seems should be working.  Basically I have a page, we'll say '/about' and it's in English.  I click translate, I have a few languages enabled, so I click to add translation for Japanese. It brings up the interface for making a new page. I change some stuff to Japanese, and set the URL alias to be /about ('about') like the english page.  I've setup my language options to use the "Session" detection method.  The result I'm wanting to achieve, but not getting is to have:  www.example.com/about -- to go to english (this works) www.example.com/about?language=ja -- to go to the Japanese translation, this does not work, it just loads up the English page.   It seems like this would be the normal functionality so I feel like I'm missing something here.
10708
Some questions, for example    Instead of using a correct URL, such as  http://meta.stackexchange.com/questions/79543/٩●̮̮̃-̃۶-forbid-unicode   are using  https://superuser.com/questions/516363/what-is-the-��-character   What is causing this behavior?
53216
We are currently maintaining country folders like  www.example.net/de/ www.example.net/fr/   Now we are thinking about Swiss with 3 languages (it, de, fr). I think it's bad to change all the current directories. Is it okay to only add the region if necessary? For example:  www.example.net/de/ = German speaking, not Swiss www.example.net/fr/ www.example.net/it/ www.example.net/de-CH/ = German speaking, Swiss only www.example.net/it-CH/ www.example.net/fr-CH/   So: Is it for SEO okay to mix the subfolder structure between /lang/ &amp; /lang-country/?
100680
Should the slash be avoided?  For example every week/day in my head is translated to every week or day. I think I started using slashes because I saw them used in forums and in articles.  Is using slashes U.S. specific, while British English is against it? Or do I understand it wrong?  P.S. If you find any spelling errors here, please let me know.
48532
Is it better to have separate country specific domains (which costs more money) or sub domains which define the country, for better SEO?  e.g.   example.com example.com.au example.co.uk   vs   example.com au.example.com uk.example.com   Assumption: The search engine web master tools, each sub domain are associated to a country. Example au.example.com is associated to the country Australia.  Update #1  I understand that both methods do work, especially when i utilize the assumption, listed above. The question is about: Which method is better? Is there such a small SEO difference between them? Is the first method way way way better than the second with getting better SEO results?  Update #2  A number of folks have suggested that the following is a good/better approach:   example.com/ example.com/au example.com/uk      By adding a country specific ISO   code to the end of the url/the first   folder of the domain can be recognised   as the country.   But a number of SEO mates have suggested that this is a valuable waste of folder level space. Er.. how can I explain. OK, it's been suggested by some SEO experts that if the number of levels or folders in the domain exceeds 5 then the page drops dramatically in importance. Basically, you don't want to make it deep. As such, adding the country as the first level can be considered a waste, especially when it can be handled by the domain OR sub domain - hence the question :)
88071
I have organised my site by language using the following structure:  www.domain.com    #spanish language version homepage www.domain.com/en #english language version homepage   The site is of Spanish subject matter hence Spanish language takes priority at root of domain. Although the site is new at this stage I would hope searching for the domain from google.com and google.es would return English and Spanish versions respectively.  Are there any particular steps I need take to separate the two. Should I add them both as individual sites in Google's webmaster tools and also should I submit individual site maps for each 'site' or as a whole?   Thanks in advance.
44679
I have a website with url like that :  www.xxxxxx.com/card/wow/20-euros   In term of SEO is it better to use slash or hyphen?  www.xxxxxx.com/card-wow-20-euros   Even though it will be trickier with hyphen to route correctly with only hyphen ...  Or it doesn't matter?