Moz Q&A is closed.
After more than 13 years, and tens of thousands of questions, Moz Q&A closed on 12th December 2024. Whilst we’re not completely removing the content - many posts will still be possible to view - we have locked both new posts and new replies. More details here.
Redirect the main site to keyword-rich subfolder / specific page for SEO
-
Hi,
I have two questions.
Question 1: is it worthwhile to redirect the main site to keyword-rich subfolder / specific page for SEO? For example, my company's webpage is www.example.com. Would it make sense to redirect (301) the main site to address www.example.com/service-one-in-certain-city ? I am asking this as I have learned that it is important for SEO to have keywords in the URL, and I was thinking that we could do this and include the most important keywords to the subfolder / specific URL. What are the pros and cons of this? Should I create folders or pages just the sake of keywords?
Question 2: Most companies have their main URL shown as www.example.com when you access their domain. However, some multi-language sites show e.g. www.example.com/en or www.example.com/en/main when you type the domain to your web browser to access the site. I understand that this is a common practice to use subdomains or folders to separate different language versions.
My question is regarding subfolders. Is it better to have only the subfolder shown (www.example.com/en) or should I also include the specific page's URL after the subfolder with keywords (www.example.com/en/main or www.example.com/en/service-one-in-certain-city)? I don't really understand why some companies show only the subfolder of a specific language page and some the page's URL after the subfolder.
Thanks in advance,
Sam
-
Thanks. One more question: does this also mean that the main page www.example.com/index.php (whether the index.php is shown to the user or not) gets all the same domain authority as the domain itself (www.example.com) as it is the main page?
-
Choose a domain and stick with it, then build pages out from there. Redirect the non-www to the www (if this is what you choose to go with) and forget about the rest... redirect site-wide.
Admittedly I'm simplifying it for two reasons: 1.) I'm not quite sure I get it, this is rather confusing and 2.) it is that simple.
You want a domain and then you want pages and subdirectories targeting your keywords. That's it that's all. I would not build links for the non-www if you are going to redirect for the www. Build links for the domain you settle on.
I'm not sure I'm helping but hope so!
-
Thanks a lot for your comments and advice, now things are starting to get more clear for me. However, I have one more question. I have now completed a detailed level of analysis and I discovered the following.
Our company is having these domains (same structure as in these):
When you go to either of these addresses, it is directed by using 301 to the following URL: http://namegroup.com/en/accounting-outsourcing-and-legal-services (no external linking root domains)
In addition, in the past some part of the link building has been made to http://www.namegroup.com (15 linking root domains), some to http://namegroup.com (1 linking root domain), some to www.name-group.com (6 linking root domains), some to http://namegroup.com/en/main (2 linking root domains). And now all is directed by using 301 to http://namegroup.com/en/accounting-outsourcing-and-legal-services (no external linking root domains). These pages have been the main page at the time these links were created.
It would make the most sense for me to start using www.namegroup.com as the main URL (as this URL has the most linking root domains), and then redirect all the rest here by using 301. And when possible, change the link in the rest of the linking domains to direct to www.namegroup.com
It is quite a big mess now, and I would like to bring some order and consistency here (also use in the future only this form). Why I am wondering whether I should make this, is that since I optimized the title tags and changed the URL for the current one (http://namegroup.com/en/accounting-outsourcing-and-legal-services) some weeks ago, we are ranking very well in Google for some of the most important keywords that we now have in the title tag and URL (we are in first page of SERP, in third and sixth place). I think it is mostly because of optimizing the title tags (but perhaps there is effect of the URL change as well).
Should I still do the change, and start using www.namegroup.com as the main domain, and redirect all others by using 301 there? What do you think?
If I would not change anything, and would keep the current main page URL, should I focus my link building for the URL http://namegroup.com or http://namegroup.com/en/accounting-outsourcing-and-legal-services? Somehow I feel like I would not like to focus the link building for the current URL, in case we decide to change it in the future (it is also quite long) and would prefer to focus link building for http://namegroup.com or www.namegroup.com.
Thank you in advance for your valuable comments.
Best regards
Sam
-
I agree with Chris and Jesse here!
For question one, you should not do this just because you want to have keywords in your URL as Google is more looking in to the quality of content that is available on the site instead of relaying only on keywords based domains and URLs. You can also go with the Jesse’s idea to create an internal page that contains keywords you want!
For question 2 I believe it’s your I will not comment until you asked me to move to sub domain.... sub folders are fine but Google treats sub domains as a separate domain but for sub folder both versions are just fine to me!
Hope this helps!
-
Sam, from an SEO standpoint, there's no need to jump through any hoops in order to get keyword into your URLs as the value that that brings is negligible and still decreasing. On the other hand, it can bring value in the form of click throughs once the result makes near the top of the the search results.
As far as the folders and URLs go, a URL that shows the directory (folder) but no page name is simply the default page for that directory. Just as the /index.php isn't usually shown in the URL for a domiain's homepage (the default page for the domain), the /index.php is often not shown in the URL for the default page in a directory.
-
Question 1: No! Why not just create the internal page and have it target the specific keyword? Your homepage is your brand, not a product/service page. Those are internal. They will rank for whatever you are targeting (if your SEO campaign is strong). Why are you worried about what your homepage ranks for?
Short answer: No. Make internal product/service pages targeting specific keywords and do not redirect your home page.
Question 2: Huh? Those two examples seemed exactly the same to me. Are you asking why some pages will show a sub directory and some pages will show the html page in the URL? If so, it's all in your structure. It doesn't really matter which way you wanna do it but having multiple directories may give you the opportunity to attach keyword targets such as "example.com/services/stuff-i-do.html" as opposed to "example.com/stuff-i-do.html"
The former example will bring the word "services" into your string.. IF you are trying to get your page to just read "example.com/services" then just create that directory and drop an index page in.
Hope this answers your questions or at least comes close.
Got a burning SEO question?
Subscribe to Moz Pro to gain full access to Q&A, answer questions, and ask your own.
Browse Questions
Explore more categories
-
Moz Tools
Chat with the community about the Moz tools.
-
SEO Tactics
Discuss the SEO process with fellow marketers
-
Community
Discuss industry events, jobs, and news!
-
Digital Marketing
Chat about tactics outside of SEO
-
Research & Trends
Dive into research and trends in the search industry.
-
Support
Connect on product support and feature requests.
Related Questions
-
Redirect to 'default' or English (/en) version of site?
Hi Moz Community! I'm trying to work through a thorny internationalization issue with the 'default' and English versions of our site. We have an international set-up of: www.domain.com (in english) www.domain.com/en www.domain.com/en-gb www.domain.com/fr-fr www.domain.com/de-de and so on... All the canonicals and HREFLANGs are set up, except the English language version is giving me pause. If you visit www.domain.com, all of the internal links on that page (due to the current way our cms works) point to www.domain.com/en/ versions of the pages. Content is identical between the two versions. The canonical on, say, www.domain.com/en/products points to www.domain.com/products. Feels like we're pulling in two different directions with our internationalization signals. Links go one way, canonical goes another. Three options I can see: Remove the /en/ version of the site. 301 all the /en versions of pages to /. Update the hreflangs to point the EN language users to the / version. **Redirect the / version of the site to /en. **The reverse of the above. **Keep both the /en and the / versions, update the links on / version. **Make it so that visitors to the / version of the site follow links that don't take them to the /en site. It feels like the /en version of the site is redundant and potentially sending confusing signals to search engines (it's currently a bit of a toss-up as to which version of a page ranks). I'm leaning toward removing the /en version and redirecting to the / version. It would be a big step as currently - due to the internal linking - about 40% of our traffic goes through the /en path. Anything to be aware of? Any recommendations or advice would be much appreciated.
International SEO | | MaxSydenham0 -
Using a top level domain name and directing it to a subfolder
Hi, we have a large international network. Our main website sits on .com domain and is used by the UK market. We have an international site in a subdirectory .com/dk/ for Denmark for example. We have also purchased the domain name www.ourcompany.dk/. Should we be forwarding the domain name (www.ourcompany.dk/) to point to the subdirectory www.ourcomany.com.dk/ so in the browser it shows up as www.ourcompany.dk or should we be displaying it as www.ourcompany.com/dk/? Are there any pros and cons to this method? Which one is best and are there any benefits in SEO. Ideally we want the .com domain name to have the best domain authority so would this impact it in any way? Any tips would be great.
International SEO | | Easigrass0 -
Is using JavaScript to render translations safe for International SEO?
Hello World! Background: I am evaluating a tool/service that a company wants to use for managing the translated versions of their international/multi-lingual websites: https://www.transifex.com/product/transifexlive/ Transifex is asking webmaster to "simply add a snippet of JavaScript" to their website(s); the approved translations are added by the business in the back-end; and the translated sites are made live with the click of a button (on/to the proper ccTLD, sub-domain, or sub-directory, which is specified). CONCERN: Even though I know Google reads JavaScript for crawling and ranking,
International SEO | | SixSpokeMedia64
I am concerned because I see the "English text" when I view the source-code on the "German site", and I wonder if this is really acceptable? QUESTION: Is a service like this (such as Transifex using JavaScript to render translations client-side) safe for indexing and ranking for my clients' international search engine visibility, especially via Google? Thank you!0 -
How to interlink 16 different language versions of site?
I remember that Matt Cutts recommended against interlinking many language versions of a site.
International SEO | | lcourse
Considering that google now also crawls javascript links, what is best way to implement interlinking? I still see otherwhise extremely well optimized large sites interlinking to more than 10 different language versions e.g. zalando.de, but also booking.com (even though here on same domain). Currently we have an expandable css dropdown in the footer interlinking 16 different language versions with different TLD. Would you be concerned? What would you suggest how to interlink domains (for user link would be useful)?0 -
Can multiple hreflang tags point to one URL? International SEO question
Moz, Hi Moz, Can multiple hreflang tags point to a single URL? For example, if I have a Canadian site (www.example.com/ca) that targets French and English speakers can I have the following: or would I use: Any insight would be very helpful and greatly appreciated! Thank you in advance!
International SEO | | DA20131 -
What is the proper way to setup hreflang tags on my English and Spanish site?
I have a full English website at http://www.example.com and I have a Spanish version of the website at http://spanish.example.com but only about half of the English pages were translated and exist on the Spanish site. Should I just add a sitemap to both sites with hreflang tags that point to the correct version of the page? Is this a proper way to set this up? I was going to repeat this same process for all of the applicable URLs that exist on both versions of the website (English and Spanish). Is it okay to have hreflang="es" or do I need to have a country code attached as well? There are many Spanish speaking countries and I don't know if I need to list them all out. For example hreflang="es-bo" (Bolivia), hreflang="es-cl" (Chile), hreflang="es-co" (Columbia), etc... Sitemap example for English website URL:
International SEO | | peteboyd
<url><loc>http://www.example.com/</loc></url> Sitemap example for Spanish website URL:
<url><loc>http://spanish.example.com/</loc></url> Thanks in advance for your feedback and help!0 -
Multilingual Ecommerce Product Pages Best Practices
Hi Mozzers, We have a marketplace with 20k+ products, most of which are written in English. At the same time we support several different languages. This changes the chrome of the site (nav, footer, help text, buttons, everything we control) but leaves all the products in their original language. This resulted in all kinds of duplicate content (pages, titles, descriptions) being detected by SEOMoz and GWT. After doing some research we implemented the on page rel="alternate" hreflang="x", seeing as our situation almost perfectly matched the first use case listed by Google on this page http://support.google.com/webmasters/bin/answer.py?hl=en&answer=189077. This ended up not helping at all. Google still reports duplicate titles and descriptions for thousands of products, months after setting this up. We are thinking about changing to the sitemap implementation rel="alternate" hreflang="X", but are not sure if this will work either. Other options we have considered include noindex or blocks with robots.txt when the product language is not the same as the site language. That way the feature is still open to users while removing the duplicate pages for Google. So I'm asking for input on best practice for getting Google to correctly recognize one product, with 6 different language views of that same product. Can anyone help? Examples: (Site in English, Product in English) http://website.com/products/product-72 (Site in Spanish, Product in English) http://website.com/es/products/product-72 (Site in German, Product in English) http://website.com/de/products/product-72 etc...
International SEO | | sedwards0 -
Redirecting users based on location
My site is available in EN, DE, SW, SP, FR, IT, CH and JP. However, the EN sites ranks much better than the other languages, and even when searching in another language the EN homepage is normally the result that appears. Would it be worthwhile to automatically redirect users to the site in the same language they are searching in or country they are searching from? If so, how do I go about this? Thanks!
International SEO | | theLotter0