Include mobile and international versions of pages to sitemap or not?
-
My pages already have alternate and hreflang references to point to international and mobile versions of the content. If I add 5 language desktop versions and 5 language mobile versions as https://support.google.com/webmasters/answer/2620865?hl=en explains, my sitemap will get bulky.
What are the pros and cons for referencing all page versions in sitemap and for include just general (English/Desktop) version in sitemap?
-
What are the pros and cons for referencing all page versions in sitemap and for include just general (English/Desktop) version in sitemap?
Let me clarify, you want to know the pros and cons of putting all page versions in sitemaps, or just doing the english/desktop and letting Google figure it out.
List All Content in Sitemaps
-
Pros
-
If the sitemaps are set up in a logical fashion, this makes for an easy way to see indexation issues.
-
You can use hreflang in the sitemaps rather than on the page. This reduces page code and ups page speed, albeit slightly.
-
You are guaranteed that search engine will find all of the content.
-
Cons
-
Lots of sitemaps to make and maintain.
Sitemap just main content (desktop/english)
-
Pros
-
Easier to maintain.
-
Search engines are much better today at finding most versions of content.
-
Cons
-
Run the risk of content not being indexed correctly.
-
Some content might not be found and indexed.
-
You could not easily verify indexation.
-
If any onsite code was removed that told Google where to go, then the possibility of indexation issues increase.
Hope that helps answer your question!
-
-
Yes sure, I know that, but you didn't answer my question.
-
When you have a high number of URLS for both Mobile and desktop, it is recommend to create different site maps for every version and connect them together. This way google will be able to find every version of your website and as a result you will have more URLs crawled and Indexed in the google SERPs.
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 Two Subdomains Showing Up in Google Search Results
Hi I have a client that is having two subdomains showing up SERP when you Google their name. Here are the details. They have two subdomains us.companyname.com and en.companyname.com us.companyname.com is for the US and has completely different products and content than en.companyname.com en.companyname.com is the site designed for Europe and it is in English. How can I make it so that only the us. version shows up in the search results? Thanks in advance!
International SEO | | JohnWeb120 -
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 -
Is this setup of Hreflang xml sitemap correct?
Hi, I'm trying to setup hreflang for 2 domains. One is purely a US site and the other domain has the language-country as subdomains. For example: http://www.websiteUSA.com (Targets English - USA) https://www.websiteINT.com/en-CA (Targets English - Canada) https://www.websiteINT.com/fr-CA (Targets French - Canada) https://www.websiteINT/es (Targets Spanish) ..and so on and so forth for about 12 of these international URLs. I created an XML sitemap that looks something like this: <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9" xmlns:xhtml="http://www.w3.org/1999/xhtml"><url><loc>http://www.websiteUSA.com</loc></url></urlset> <url><loc>https://www.websiteINT.com/en-CA</loc></url> <url><loc>https://www.websiteINT.com/fr-CA</loc></url> Question 1: Is this correct? In my actual file, I have all the countries listed and self-referencing. Question 2: I'm hosting this file at https://www.websiteINT.com/hreflang.xml AND at http://www.websiteUSA.com/hreflang.xml. Is this correct? Question 3: Will this help the SERPs direct english speakers from the US to http://www.websiteUSA.com while show SERPs for say English Speakers in Canada to https://www.websiteINT.com/en-CA? Question 4: For some reason, when I put up the xml site, it only listed each URL once instead of the full XML file. Should I have uploaded a text file instead? It doesn't seem to render correctly. Thank you!
International SEO | | SylviaH0 -
Canonical and hreflang mess of international desktop and mobile site versions
Hello, I have an interesting case and I am lost in it. There are two versions of the site: desktop and mobile. And there are also international versions: English and Spanish. I'm stuck at implementation of canonical tags. Currently my setup has the following: English (default) desktop page has these: English Mobile page has these: Spanish Desktop version: Spanish Mobile version: But I somewhat feel that I messed the things... Could you guys point me to what I did wrong and explain how to set it right? Also, if you know URLs of blog posts or articles, where similar case is explained - share with me please.
International SEO | | poiseo0 -
Does Google take into account the place where the server is hosted to rank the pages.
Does Google take into account the place where the server is hosted to rank the pages. What I mean is, if I have a server in USA and I am working for the Spain marketplace: Will Google rank better my pages for this market if the server were hosted in Spain?
International SEO | | NorbertoMM0 -
International Landing Page Strategy
Hello, I'm looking for some insight in an area that I don't have much experience in - hoping the community can help! We are a healthcare staffing company serving clients in the U.S. (www.bartonassociates.com). We are interested in attracting clients in Australia and New Zealand. I'm wondering if anyone as experience with best practices for doing so (both from an SEO and PPC perspective). Would it be best to purchase .au and .nz domains for these landing pages and link back to our US site for more information (or even recreate a modified version of our US site for .au and .nz). My concern here is duplicate content issues, among other things. Or, would it be better to create Australia and New Zealand focused landing pages on our US site and drive PPC there? My concern here is that we would never get organic traffic from Australia and New Zealand to our US site, in light of the competition. Also, the messaging would be a bit mixed if targeting all three countries. Our core term is "locums" and "locum tenens". Greatly appreciate any insight from you guys. Thanks, Jason
International SEO | | ba_seomoz0 -
Internationally targetted subdomains and Duplicate content
A client has a site they'd like to translated into French, not for the french market but for french speaking countries. My research tells me the best way to implement this for this particular client is to create subfolders for each country. For ease of implementation I’ve decided against ccTLD’s and Sub Domains. So for example… I'll create www.website.com/mr/ for Mauritania and in GWT set this to target Mauritania. Excellent so far. But then I need to build another sub folder for Morocco. I'll then create www.website.com/ma/ for Morocco and in GWT set this to target Morocco. Now the content on these two sub folders will be exactly the same and I’m thinking about doing this for all French speaking African countries. It would be nice to use www.website.com/fr/ but in GWT you can only set one Target country. Duplicate content issues arise and my fear of perturbing the almighty Google becomes a possibility. My research indicates that I should simply canonical back to the page I want indexed. But I want them both to be indexed surely!? I therefore decided to share my situation with my fellow SEO’s to see if I’m being stupid or missing something simple both a distinct possibility!
International SEO | | eazytiger0 -
International SEO - auto geo-targetting
I read with interest the recent post on international SEO and the top level domain architecture approaches to local content: http://www.seomoz.org/ugc/folders-vs-subdomains-vs-cctld-in-international-seo-an-overview#jtc135670 The issue I have is a little more complex: The business sells a wide variety of products (37) but one is by far and away the biggest and most popular. This means that due to the link profile of the various country sites and HQ site, search engines categorise the site according to this product (this is easily seen with the Google Adplanner) and the other product lines suffer as a result. The current architecture is to have a .com site and then individual ccTLD country sites, again with all products on each site. This creates an issue as in most countries the brand is not strong (compared to the keyword names and search volumes of the products) and so it is not that effective in generating organic traffic. The .com hogs much of the inbound links and the country sites themselves are not that well optimised for a number of reasons. A proposed solution has been to leverage the strength of the .com and the search volume for the product names, and to produce thematic sites based on each product: productA.brand.com
International SEO | | StevieCC
productB.brand.com
productC.brand.com In this way, the sites, content and link profiles are aligned around the more desirable products and we can expect improved organic search performance as a result (or at least ensure relevant traffic finds the relevant content fast). In terms of providing localised content, the plan was to use content mirroring and to then assign each content mirror to a specific geo-location using the webmaster tools console (and other SE equivilents). This is shown I think in one of Rand's videos. ProductA.brand.com/de/de Germany site for product A with unique German content
ProductA.brand.com/fr/fr French site for product A with unique French content This makes economic sense to me as to utilise the ccTLDs would result in hundreds of separate sites with all the licence and server considerations that entails. For example, for product A alone we would have to produce: productA.brand.de
productA.brand.fr
productA.brand.cn
productA.brand.jp
ect ect ect This just would not be sustainable in license/server costs alone across 37 products and 24 countries. However, I saw in a recent presentation at SES London that (auto) geo-targeting is risky, often doesn't work well for SEO and can even be seen as cloaking. I think the above strategy could still work, but perhaps we should avoid the use of auto-geotargetting altogether and hope the search engines alone do their job in getting users to the right content as we optimise the unique content for each country (and if they don't, ensure our desgn, UX and country selectors do the job instead). SEO guru consensus is to use the ccTLD if you own it, but as described above, in the real world that just isn't possible or practical given the company's strategic position. Which leads to the final question- we do own the brand ccTLDs- if they are directed back to the content mirror for the country on the .com, is there any SEO benefit in doing so aside from directing back any link juice associated with the domain)?0