Closed Frozenlock closed 10 years ago
After reading more on the subject, I realize that it really isn't something tower
can do anything about.
It looks like the simplest solution would be to use different subdomains for other languages in combination with providing a :local-selector
to the wrap-tower
middleware.
Hey, sorry for the huge delay getting back to you on this - was on vacation + trying to not multitask for once ;-)
It looks like the simplest solution would be to use different subdomains for other languages in combination with providing a :local-selector to the wrap-tower middleware.
Yup, that sounds good.
As a general principle, if you want an URL to rank for specific [possibly dynamic] content, then there'll need to be a 1-to-1 relationship between the URL and the content. So in this case that means that the content language will need to be specified in the URL somehow.
Subdomains are one way to go, but I generally prefer avoiding them when possible (for SEO reasons and to cut down on administrative headache). Something like "mydomain.com/en" is another alternative.
I noticed that while I can easily rank up in the default language (en), my website doesn't appear at all in other languages.
I read the Google best practices and the mention how one should use a different URL for a different language.
Should I change my site structure to have multiple urls, or is there a way to get
tower
powered sites to be crawled in all languages?