With the Internationalization module enabled, the sitemap.xml will end up being forwarded to www.example.com/en/sitemap.xml when called via www.example.com/sitemap.xml. It no longer appears inside the root folder.
Google sitemap validation reports this as a problem.

Google and Yahoo validation links seem to work fine, though.

Comments

daniel_h’s picture

Status: Active » Closed (duplicate)

Sorry, duplicate to: "Generate sitemap for each i18n language" (http://drupal.org/node/182442)

darren oh’s picture

Status: Closed (duplicate) » Postponed (maintainer needs more info)

I can't reproduce this. Please provide information about your system.

darren oh’s picture

Status: Postponed (maintainer needs more info) » Closed (duplicate)
daniel_h’s picture

No need for more information.

You already fixed it.

Version 1.3. Tested with i18n module active. sitemap.xml is no longer at /xx/sitemap.xml, but appears as www.example.com/sitemap.xml as it should.

Reopened only to give feedback.

Thank you

daniel_h’s picture

Status: Closed (duplicate) » Postponed

I might add, though, that I was surprised to find that 'Additional's added as "en/foo/bar" store as "en/foo/bar" but appear as "foo/bar" in the sitemap file (the languagepath is removed).

Easy to work around using URL alias. (I have one '/willkommen' redirecting to '/de/' frontpage and one '/welcome' redirecting to '/en/' frontpage. There is no frontpage without /countrycode/ on my site. Visitors accessing 'www.example.com' are redirected to their specific language frontpage. E.g.: 'www.example.com/en/welcome'.
'/willkommen' and '/welcome' are 'Additionals' in the sitemap.xml file.)
This was an unexpected effect, though. Depends on site design.

Removing the language path from sitemaps (current situation) might even be the better solution.

One effect might occur, if I may stress this point to the limit:
Spider enters sitemap and starts with
www.example.com/willkommen
www.example.com/welcome
(no language paths in the sitemap.xml)
It finds all links to be of the form '/en/foo/bar' and '/de/foo/bar' respectively (all of them with language path). Their content is in German or English respectively.
Both might lead back to '/en/welcome' and '/de/willkommen'. This is minimal duplicate content.

Relevant notes:

  • There is no 'right' way to handle multi-language sites in sitemaps. I googled the hell out of it for weeks.
  • Duplicate content and /languagepath/ might be an issue for the Internationalization project. Not for the Sitemap module.
  • My opinion is, that the current situation is 'by design' or 'makes no real difference even if fixed'.
    Just wanted to show up the effect of this.

    darren oh’s picture

    Status: Postponed » Fixed

    Fixed additional links in CVS commit 89293.

    darren oh’s picture

    Title: Generates www.example.com/en/sitemap.xml » Additional links page shows language prefix
    Version: 5.x-1.2 » 5.x-1.3
    daniel_h’s picture

    Thank you.

    Anonymous’s picture

    Status: Fixed » Closed (fixed)

    Automatically closed -- issue fixed for two weeks with no activity.