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 corporate SEO - menu and preferences
Hi all, for internationalization we have used subfolders structure (e.g. domain.com/us/) and since we have approx 150 countries to cover, then country selector is quite a link-base, especially if pages itself can have even several hundreds of internal links as well. Currently, all links to other countries are set as rel="nofollow" and I'm planning to change them to "follow" to distribute a juice. Do you please have an experience with such internal links voluminous websites and this follow/nofollow settings? Also we are having and issue with other countries outperforming local search. So for example in US, searching for kind of "Brand America" keyword, our UK branch outperforms US. Hreflangs are set in the sitemaps and each branch (country) is set in search console correctly as well. Since there are some issues with sitemaps (e.g. not actual links, or links returning 404), I assume that google is not using these sitemaps therefore hreflang information is lost as well. Am I correct ? thank you in advance, Tom
International SEO | | execom990 -
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 -
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 -
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 -
International Confusion between .com and .com/us
A question regarding International SEO: We are seeing cases for many sites that meet these criteria: -International sites that have www.example.com/ ip redirecting to country site based on ip redirect (ex. www.example.com/ 301 to www.example.com/us -There is a desktop + mobile site (www.example.com + m.example.com) The issue we see is Google shows www.example.com/ in US search results instead of www.example.com/us in search results. Since the .com/ redirects, there is no mobile version, and www.example.com/ also shows up in mobile SERPs instead of m.example.com/us. My questions are: 1. If www.example.com/ is redirecting users and Googlebot, why is Googlebot caching it with the content of www.example.com/us? 2. Why is www.example.com/ showing up in SERPs instead of www.example.com/us? 3. How can we help Google display www.example.com/us and m.example.com/us in SERPs instead of www.example.com/? Thanks!!
International SEO | | FranFerrara0 -
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 -
Duplicated 404 Pages (Travel Industry)
Our website has creating numberous "future pages" with no alt tag or class tag that are showing up as 404 pages, To make matters worst, they are causing duplicate 404 pages because we have different languages. The visitors cant find the 404s but the searchbots can. Would it better to remove or add the links to robot.txt or add nofollow/noindex tag? This is an example. http://www.solmelia.com/nGeneral.LINK_FAQ http://www.solmelia.com/nGeneral.LINK_HOTELESDESTINOS_BODAS http://www.solmelia.com/nGeneral.LINK_CONDICIONES http://www.solmelia.com/nGeneral.LINK_MAPSITE http://www.solmelia.com/nGeneral.LINK_HOTELESDESTINOS_EMPRESA
International SEO | | Melia0 -
International Link Building
Can anyone weigh in on their own efforts to build links into international TLDs? Which tactics have been successful? Which have failed? Have you engaged any agencies to manage this for you and if so, how did they perform and who are they? We have nine ccTLDs plus our .com site to manage so it's a bit overwhelming! Fortunately, we have teams dedicated to managing day-to-day operations of each site. Each team is comprised of managers who speak the targeted language as their first language and have intimate knowledge of the targeted culture. I want to leverage them to help my SEO efforts, but I'm not sure how my advice should be different than what we do for our .com site.
International SEO | | RyanOD0