Geo-targeting a sub-folder that's had url's rewritten from a sub-domain
-
I have a client that's setting up a section of his site in a different language, and we're planning to geo-target those pages to that country. I have suggested a sub-folder solution as it's the most cost effective solution, and it will allow domain authority to flow into those pages.
His developer is indicating that they can only set this up as a sub-domain, for technical reasons, but they're suggesting they can rewrite the url's to appear as sub folder pages.
I'm wondering how this will work in terms of geo-targeting in Google Webmaster Tools. Do I geo-target the sub domain or the sub folder i.e. does Google only see urls or does it physically see those pages on the sub-domain?
It seems like it might be a messy solution. Would it be a better idea just to forget about the rewrites and live with the site being a sub domain?
Thanks,
-
Ok. Thanks for the advise, Ryan.
-
My first suggestion is to push further on the "developer" issue. As an SEO, it is important to have the ability to implement recommended changes as required. If the changes are not implemented for whatever reason, results are affected.
We all work very hard to achieve the best results for our clients. Two common reasons a client might offer for not implementing a change are "my software wont support the change" and "my developer wont support the change". This topic will likely arise again on other matters. Additionally, I recommend a direct line of communication between an SEO and developer when possible. Each party can gain a higher understanding and appreciation for the other, miscommunications can be minimized and it simply creates a better working environment.
With the above noted, your decision to move the subdomain into the main site is the commonly accepted best practice. You are consolidating your DA. While Google has made some recent changes with respect to subdomains, it is still the best practice to make the change you have recommended to your client.
If the URLs are properly rewritten at the server level, no one will even know the actual path of the files. Anyone who visits the URL will simply see the page with a 200 response (all ok) header code returned. You can and should test this change after it is implemented.
Robots.txt can be used to block access to the sub-domain if you wish.
-
Thanks Ryan.
I've no direct contact with the developer, so I can't answer those questions. I'm afraid I just have to work with what my client is telling me.
By what you're saying, and if done correctly, the pages would look to google as if they were in a folder on that domain e.g. website.com/language-site, and we would geo-target that folder, and not the sub domain?
Then we'd need to find a way to stop the search engines crawling the sub-domain. Would this be done in the robots.txt file?
Do you think it we'd be just better off using the sub-domain and forgetting about the rewrites. The main reason I'm advising him to go for a folder structure is because of the uncertainty of domain authority flowing to a sub-domain.
-
I firmly believe software and developers should enable site owners the freedom to make changes as they see fit. When a developer or software are not able to readily implement SEO best practices, it's time to look for alternatives.
Is the software being used a particular CMS or e-commerce solution which is in an earlier stage of development? How experienced is the developer?
If the URLs were rewritten (server-side) to provide the target pages with a normal header response code the process should work. My biggest concern is ensuring the sub-domain URLs are not crawled otherwise there would be a duplicate content issue.
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
-
International SEO setup issues canonical URL
My site is www.grocare.com for one region and in.grocare.com for another region. Both of them have the same content except the currency for particular regions. Someone told me that google will take the content as duplicate and not rank either. I have setup hreflang and targeted different regions for both in the search console. I read many article which say canonical urls need to be setup for international seo sites. But Im not sure how to setup canonical urls and whether they are the right way to go . i just don't want my content deranked. Now i have setup hreflang properly after asking the moz community itself. So im hoping to get some help with this query too. TIA
International SEO | | grocare0 -
Google Search Console "International Targeting" is reporting errors that are not present on my site
We are currently handling search for a global brand www.example.com/ which has presence in many countries worldwide. To help Google understand that there is an alternate version of the website available in another language, we have used hreflang tags. These hreflang tags are implemented only via the XML sitemap across all geo-locations. Under the “Search Analytics -> International Targeting” section, in Google Search Console, for the Malaysian website (www.example.com/my/), there are a number of “no-return tags (sitemaps)” errors arising. For example, for India as a geo-location, there is one ‘en-IN’ – no return tags (sitemaps) errors listed. The error is listed below: Originating URL - www.example.com/my/xyz/ Alternate URL - www.example.com/in/xyz/ When the XML sitemap for the URL – www.example.com/in/ was checked for the hreflang tags, it was noticed that the implementation of hreflang tags for the URL – www.example.com/in/xyz/ was perfectly fine and it was providing a return tag to the URL – www.example.com/my/xyz/. After the code level verification, it was identified that the implementation of hreflang tags was perfectly fine via the XML sitemap. Even though at the code level it was verified that the implementation is fine, the error still persists in Google Search Console. Kindly suggest a solution to this situation, and also advise the effects of these errors on search engine performance
International SEO | | Starcom_Search0 -
International targeting
I'm offering an international service to any country from any destination, The website main language is English and i have 4 other languages as subdirectories, https://beassistance.com https://beassistance.com/de/ https://beassistance.com/es/ https://beassistance.com/fr/ https://beassistance.com/ru/ I'm looking to target by language not country, Should i choose "unlisted" for all the subdirectories? my second question regards the meta tags , my current meta tag rel="alternate" hreflang="ru-ru" href="https://beassistance.com/ru/" /> And i'm thinking about using rel="alternate" hreflang="ru" href="https://beassistance.com/ru/" /> Is that best practice to target by the language? Update I already have Hreflang Sitemap <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" <br="">xmlns:xhtml="http://www.w3.org/1999/xhtml">
International SEO | | MTBE
<url><loc>https://beassistance.com</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url></urlset> <url><loc>https://beassistance.com/de/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url> <url><loc>https://beassistance.com/fr/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url> <url><loc>https://beassistance.com/es/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url> <url><loc>https://beassistance.com/ru/</loc>
<xhtml:link<br>rel="alternate"
hreflang="en"
href="https://beassistance.com"
/>
<xhtml:link<br>rel="alternate"
hreflang="de"
href="https://beassistance.com/de/"
/>
<xhtml:link<br>rel="alternate"
hreflang="fr"
href="https://beassistance.com/fr/"
/>
<xhtml:link<br>rel="alternate"
hreflang="es"
href="https://beassistance.com/es/"
/>
<xhtml:link<br>rel="alternate"
hreflang="ru"
href="https://beassistance.com/ru/"
/></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></xhtml:link<br></url>1 -
Getting pages that load dynamically into the SE's
SEO'ers, Am dealing with an issue I cannot figure out the best way to handle. Working on a website that shows the definitions of words which are loaded dynamically from an open source. Source such as: wiktionary.org When you visit a particular page to see the definition of the word, say; www.example.com/dictionary/example/ the definition is there. However, how can we get all the definition pages to get indexed in search engines? The WordPress sitemap plugin is not picking up these pages to be added automatically - guess because it's dynamic - but when using a sitemap crawler pages are detected. Can anybody give advice on how to go about getting the 200k+ pages indexed in the SE's? If it helps, here's a reference site that seems to load it's definitions dynamically and has succeeded in getting its pages indexed: http://www.encyclo.nl/begrip/sample
International SEO | | RonFav0 -
Duplicate content on .co.uk and .com TLDs with different domain authority
What's the best approach to take for a site that has identical content on the .co.uk and .com versions of the root domain? The .co.uk version has a significantly higher domain authority (54 vs 32 according to Open Site Explorer - see attached screenshot). But it's an international company with its largest customer base in North America and customers in over 60 countries. The company does not intend to localize content. My initial thought before seeing the domain authority was to 301 redirect the .co.uk to the .com domain to consolidate all the link equity under one international TLD. However, I wondered if the higher domain authority for .co.uk would be passed on if we did this. I figured that a non-UK audience would be more likely to trust a .com site. I still think 301 redirecting .co.uk to .com might be the best strategy in the long term. But is there likely to be a dip in rankings and organic search volume in the short term until .co.uk is replaced in the index by .com? I'd really appreciate your thoughts on this. CbVnfSO.png
International SEO | | Torchbox0 -
Multilingual Sitemap with some non-matching URLs
The website has two languages, English (.com/en-int/) and French (.com/fr-fr/). Some pages only exist in French, and some only in English, but there are many that are a 1-to-1 match. So, my questions is, in the multilingual sitemap, should I only include the URLs that are alternates, and then create a 2nd sitemap for all non-matching URLs? Or should I have 3 sitemaps: 1) Multilingual sitemap for all matching URLs (https://support.google.com/webmasters/answer/26208650 , 2) English sitemap for only URLs not included in multilingual sitemap, 3) French sitemap for only URLs not included in multilingual sitemap. And then create a sitemap index file to link to all 3 sitemaps.
International SEO | | Alex.Weintraub0 -
Shall I automatically redirect international visitors from www.domain.com to e.g. www.domain.com/es? What is best SEO practice?
We have chosen the one domain approach with our international site having different language versions in subdirectory of main domain:
International SEO | | lcourse
www.domain.com/es
www.domain.com/it
etc. What is SEO-wise best practice for implementing international index pages. I see following options: entering www.domain.com will display without redirection the index page in language of user (e.g based on IP or browser) in www.domain.com
Example: www.booking.com entering www.domain.com will always show English index page.
Additionally one may display a message in the header if IP from other country with link to other language version.
Example: www.apple.com entering www.domain.com will always redirect automatically to country specific subdirectory based on IP
Example: www.samsung.com Any thoughts/suggestions on what may be best solution from a SEO perspective? For a user I believe options 1) & 3) are preferable.0 -
Which hreflang tag to use for .eu domain
Hi there, We're trying to solve a problem with one of our domains, we have a .eu CCTLD and we're trying to implement hreflang tags. On our US and UK sites, we use "en-us" and "en-gb", but it's not clear how to approach this european problem, as there is not a "en-eu" tag. The site is in English, but serves several European countries speaking different languages. What's the best hreflang code to use in this situation? Any help much appreciated, Thanks!
International SEO | | dennis.globalsign0