: Which of these 3 URL-Rewritings are better SEO friendly URLs? Imagine my current flat-file no-CMS website with an URL like http://example.com/en/tomato. This is of course very unsexy and could
Imagine my current flat-file no-CMS website with an URL like example.com/en/tomato.
This is of course very unsexy and could be anything really from tomato soup, tomato the music band, tomato the movie, or more unlikely but still... just about tomatos!
So, I want to make it more specific for both real humans as well as search engines. Given: both the language code and short filename code are essential and cannot be replaced so somewhere there has got to be en and tomato preciding/following whatever delimiter like / for .htaccess to do the correct invisible redirects to /tomato.php?language=en.
Some options occured in my mind for the added words in URL:
A example.com/en/tomato/just-about-tomatos
B example.com/en/tomato/just-about-tomatos.htm
C example.com/just-about-tomatos/en/tomato
D example.com/en/tomato_just_about_tomatos
E example.com/en/tomato-just-about-tomatos
Question1: Which of these is the best for humans as well as search engines?
Question2: Which single elegant rule should make this happen in .htaccess?
Thanks for your suggestions and answers! Much appreciated.
More posts by @Bryan171
4 Comments
Sorted by latest first Latest Oldest Best
Using hyphens is good for SEO and this technique is favorable for SEO type URL writing.
We use different types of URL's but they are not supportable for SEO.
Just want to clarify what Eric Vold write about the parameter (?lang=en)
Turns out that Google does not recommend using this kind of parameter as it is confusing for visitors (and other factors).
The best option from your list would be A as seriocomic suggested, but even better if you put it this way:
en.example.com/tomato/just-about-tomatos
I think you might have selected the best answer prematurely?
Question 1:
My pick would be example.com/en/tomato/just-about-tomatos - my rationale being:
/en/ is a primary language folder that encompasses all of the content therein so is best suited to appear directly after the domain, and is the best choice for multi-lingual implementation after a) new domain, and b) sub-domain.
/just-about-tomatos is the page - so should reside at the end. There is no need to write .htm at the end since you're rewriting the URL and users DON'T CARE what language/platform you use.
Question 2:
In order to add the just-about-tomatos part into your URL you'd probably have to look at creating a mapping system since that phase doesn't appear in your existing URL.
the .htm is good because it lets users know what file type the page is. I wouldn't suggest using /en/ in the url because you want all users to come/link to the same page regardless of the language, and simply have the language changed via url query string paramater.
So I would suggest:
website.com/tomato/just-about-tomatos.htm?lang=en
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.