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
-
Top 10 SEO Experts in the World
Here are some of the top SEO experts in the world known for their contributions to the field, thought leadership, and innovative strategies: Rand Fishkin - Co-founder of Moz and SparkToro, widely known for his insights and contributions to SEO. Neil Patel - Co-founder of Crazy Egg, Hello Bar, and KISSmetrics, renowned for his SEO and digital marketing expertise. 3.. Brian Dean - Founder of Backlinko, famous for his advanced SEO strategies and detailed guides. Rafay Waqar - Co-founder of SEOServices and a LinkedIn influencer, he provide valuable insights into search engine algorithms and updates. Barry Schwartz - Founder of Search Engine Roundtable, known for his in-depth coverage of SEO news and trends. Aleyda Solis - International SEO consultant and founder of Orainti, recognized for her expertise in technical SEO and international SEO strategies. Bill Slawski - Director of SEO Research at Go Fish Digital, known for his deep understanding of search engine patents and algorithms. Vanessa Fox - Creator of Google Webmaster Central and author of "Marketing in the Age of Google," known for her expertise in technical SEO and analytics. Ann Smarty - Founder of Viral Content Bee and a well-known figure in the SEO community for her content marketing and link-building expertise. Cyrus Shepard - Former Head of SEO at Moz and founder of Zyppy, known for his comprehensive SEO knowledge and actionable insights.
International SEO | | cupll.rs11 -
International SEO - Targeting US and UK markets
Hi folks, i have a client who is based in italy and they set up a site that sells travel experiences in the sout of Italy (the site currently sit on a server in Italy). The site has been set up as gTLDs: www.example.com They only want to target the US and the UK market to promote their travel experiences and the site has only the english version (the site does not currently offer an italian version). If they decide to go for the gTLDs and not actually change to a ccTLDs (which would be ideal from my point of view) how are the steps to be taken to set this up correctly on GSC? They currently only have one property registered on GSC: www.exapmple.com therefore i guess the next steps are: Add new property - www.example.com/uk and and set up geo targeting for UK Existing property - www.example.com/ set up geo targeting for US In case the client does not have the budget to optimise the content for american and british languages, would still make sense to have 2 separate property in GSC (example.com for US market and example.com/uk for UK market)? Few considerations: Add canonical tag to avoid duplicate content across the two versions of the site (in the event there is no budget to optimise the content for US and UK market)? Thank you all in advance for looking into this David
International SEO | | Davide19840 -
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 -
Google does not index UK version of our site, and serves US version instead. Do I need to remove hreflanguage for US?
Webmaster tools indicates that only 25% of pages on our UK domain with GBP prices is indexed.
International SEO | | lcourse
We have another US domain with identical content but USD prices which is indexed fine. When I search in google for site:mydomain I see that most of my pages seem to appear, but then in the rich snippets google shows USD prices instead of the GBP prices which we publish on this page (USD price is not published on the page and I tested with an US proxy and US price is nowhere in the source code). Then I clicked on the result in google to see cached version of page and google shows me as cached version of the UK product page the US product page. I use the following hreflang code: rel="alternate" hreflang="en-US" href="https://www.domain.com/product" />
rel="alternate" hreflang="en-GB" href="https://www.domain.co.uk/product" /> canonical of UK page is correctly referring to UK page. Any ideas? Do I need to remove the hreflang for en-US to get the UK domain properly indexed in google?0 -
How to best set up international XML site map?
Hi everyone, I've been searching about a problem, but haven't been able to find an answer. We would like to generate a XML site map for an international web shop. This shop has one domain for Dutch visitors (.nl) and another domain for visitors of other countries (Germany, France, Belgium etc.) (.com). The website on the 2 domains looks the same, has the same template and same pages, but as it is targeted to other countries, the pages are in different languages and the urls are also in different languages (see example below for a category bags). Example Netherlands:
International SEO | | DocdataCommerce
Dutch domain: www.client.nl
Example Dutch bags category page: www.client.nl/tassen Example France:
International domain: www.client.com
Example French bags category page: www.client.com/sacs When a visitor is on the Dutch domain (.nl) which shows the Dutch content, he can switch country to for example France in the country switch and then gets redirected to the other, international .com domain. Also the other way round. Now we want to generate a XML sitemap for these 2 domains. As it is the same site, but on 2 domains, development wants to make 1 sitemap, where we take the Dutch version with Dutch domain as basis and in the alternates we specify the other language versions on the other domain (see example below). <loc>http://www.client.nl/tassen</loc>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="http://www.client.com/sacs"
/></xhtml:link<br> Is this the best way to do this? Or would we need to make 2 site maps, as it are 2 domains?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 -
Best URL structure for Multinational/Multilingual websites
Hi I am wondering what the best URL format to use is when a website targets several countries, in several languages. (without owning the local domains, only a .com, and ideally to use sub-folders rather than sub-domains.) As an example, to target a hotel in Sweden (Google.se) are there any MUST-HAVE indicators in the URL to target the relevant countries? Such as hotelsite.com**/se/**hotel-name. Would this represent the language? Or is it the location of the product? To clarify a bit, I would like to target around 10 countries, with the product pages each having 2 languages (the local language + english). I'm considering using the following format: hotelsite.com/en/hotel-name (for english) and hotelsite.com/se/hotel-name (for swedish content of that same product) and then using rel=”alternate” hreflang=”se-SV” markup to target the /se/ page for Sweden (Google.se) and rel=”alternate” hreflang=”en” for UK? And to also geotarget those in Webmaster tools using those /se/ folders etc. Would this be sufficient? Or does there need to be an indicator of both the location, AND the language in the URLs? I mean would the URL's need to be hotelsite.com/se/hotel-name/se-SV (for swedish) or can it just be hotelsite.com/se/hotel-name? Any thoughts on best practice would be greatly appreciated.
International SEO | | pikka0 -
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