Please note, that I can't report a bug with cmty.app, because there is no version to select in the sitemap module, but this field is required.

Can you give more details?

• Nuxt.js version
• node.js version
• OS + version
• command used to generate the sitemap (yarn generate or yarn build && yarn start)

Do you confirm that your sitemap config is empty?

Then, can you removed or disabled the other modules and retry?

To fix your issue quickly, you may use the following workaround:

```js
{
sitemap: {
filter ({ routes }) {
return routes.map(route => route.url = route.url.replace("/_nuxt", ""))
}
}
}

@AlexBa Ok, I reproduce when the sitemap: {}configuration object is missing.

@AlexBa for now the better way to fix your issue is to explicitly set the hostname option in your nuxt.config.js file:

{
  sitemap: {
    hostname: "https://alexanderbarton.de"
  }
}

I will check to improve your use case.

@NicoPennec This code seems to work:

{
  sitemap: {
    hostname: "https://alexanderbarton.de"
  }
}

But this code doesn't work (I have tried it before):

{
  sitemap: {
    filter ({ routes }) {
      return routes.map(route => route.url = route.url.replace("/_nuxt", ""))
    }
  }
}

The commands, I tried, were: nuxt and nuxt generate

I just want to provide you some missing info. Maybe it can be helpful for later:

• Node version: 11.7.0
• Nuxt version: 2.4.5
• OS version: maxOS 10.14.4

Thank you for your help!

Thanks for your answer with all details, but as explain before your last post, I found the issue.

It should be fixed since the release v1.1.0, see CHANGELOG

Please update your @nuxtjs/sitemap dependency to the latest release, remove your config `sitemap: { … } as before, and retry to generate the sitemap.

It's working now with v1.1.0. Thank you again!

I experienced this issue when installing the module, adding to the end of my modules: [] without any further configuration.

When looking at the sitemap on my local machine, it was fine; but when deployed it contained /_nuxt/ for each route.

In my case it was actually worse, as I was using a CDN as a publicpath, so the path actually pointed to a _nuxt route on my CDN endpoint.

I was also using i18n with several languages.

Can confirm that adding a sitemap: { hostname: "https://cmpct.io" } fixed the issue as described in this issue.

I was on version 2.0.1

@tommcclean I need more details to reproduce the issue

• Can you share your nuxt.config.js?
• Do you have a custom build: { publicPath: "..." } on production in your nuxt.config.js?
• Which mode did you use? (Universal / SPA / Generate)
• How did you deploy your nuxt project?