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
-
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 -
Hreflang tag on every page?
Hello Moz Community, I'm working with a client who has translated their top 50 landing pages into Spanish. It's a large website and we don't have the resources to properly translate all pages at once, so we started with the top 50. We've already translated the content, title tags, URLs, etc. and the content will live in it's own /es-us/ directory. The client's website is set up in a way that all content follows a URL structure such as: https://www.example.com/en-us/. For Page A, it will live in English at: https://www.example.com/en-us/page-a For Page A, it will live in Spanish at https://www.example.com/es-us/page-a ("page-a" may vary since that part of the URL is translated) From my research in the Moz forums and Webmaster Support Console, I've written the following hreflang tags: /> For Page B, it will follow the same structure as Page A, and I wrote the corresponding hreflang tags the same way. My question is, do both of these tags need to be on both the Spanish and English version of the page? Or, would I put the "en-us" hreflang tag on the Spanish page and the "es-us" hreflang tag on the English page? I'm thinking that both hreflang tags should be on both the Spanish and English pages, but would love some clarification/confirmation from someone that has implemented this successfully before.
International SEO | | DigitalThirdCoast0 -
In the U.S., how can I stop the European version of my site from outranking the U.S. version?
I've got a site with two versions – a U.S. version and a European version. Users are directed to the appropriate version through a landing page that asks where they're located; both sites are on the same domain, except one is .com/us and the other is .com/eu. My issue is that for some keywords, the European version is outranking the U.S. version in Google's U.S. SERPs. Not only that, but when Google displays sitelinks in the U.S. SERPs, it's a combination of pages on the European site and the U.S. site. Does anyone know how I can stop the European site from outranking the U.S. site in the U.S.? Or how I can get Google to only display sitelinks for pages on the U.S. site in the U.S. SERPs? Thanks in advance for any light you can shed on this topic!
International SEO | | matt-145670 -
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 -
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 -
Auto-Redirecting Homepage on Multilingual Site
The website has an auto-redirecting homepage on a multilingual site. Here is some background: User visits the site for first time > sent to javascript age verification page with country of origin selector. If selects "France" then served French page (.com/fr-fr/). If selects any other country, then served English page (.com/en-int/). A cookie is set, and next time the user visits the site, they are automatically served the appropriate language URL. 1st Question: .com/ essentially does not exist. It is being redirected to .com/en-int/ as this is the default page. Should this be a 301 redirect since I want this to serve as the new homepage? 2nd Question:. In the multilingual sitemap, should I still set .com/ as the hreflang="x-default" even though the user is automatically redirected to a language directory? According to Google, as just released here: http://googlewebmastercentral.blogspot.com/2014/05/creating-right-homepage-for-your.html "automatically serve the appropriate HTML content to your users depending on their location and language settings. You will either do that by using server-side 302 redirects or by dynamically serving the right HTML content. Remember to use x-default rel-alternate-hreflang annotation on the homepage / generic page even if the latter is a redirect page that is not accessible directly for users." So, this is where I am not clear. If use a 302 redirect of .com/ to either .com/en-int/ or .com/fr-fr/, won't I then lose the inbound link value and DA/PA of .com/ if I just use a 302? Note: there is no .com/ at this moment. Any advice is appreciated. Thanks,Alex
International SEO | | Alex.Weintraub0 -
International SEO Subfolders / user journey etc
Hi According to all the resources i can find on Moz and elsewhere re int seo, say in the context of having duplicate versions of US & UK site, its best to have subfolders i.e. domain.com/en-gb/ & domain.com/en-us/ however when it comes to the user journey and promoting web address seems a bit weird to say visit us at: domain.com/en-us/ !? And what happens if someone just enters in domain.com from the US or UK ? My client wants to use an IP sniffer but i've read thats bad practice and should employ above style country/language code instead, but i'm confused about both the user journey and experience in the case of multiple sub folders. Any advice much appreciated ? Cheers Dan
International SEO | | Dan-Lawrence0 -
Sub-domains or sub-directories for country-specific versions of the site?
What approach do you think would be better from an SEO perspective when creating country-targeted versions for an eCommerce site (all in the same language with slight regional changes) - sub-domains or sub-directories? Is any of the approaches more cost effective, web development-wise? I know this topic's been under much debate and I would really like to hear your opinion. Many thanks!
International SEO | | ramarketing0