What problem does this feature solve?

Currently, if I want to use the @nuxtjs/router I'm left with a blank sitemap which doesn't take into account the custom routes I added manually in my router.js file as per @nuxtjs/router documentation. This would eliminate redundancy of definition of routes

What does the proposed changes look like?

Instead of using the result of createRoutes from nuxt, the manual router.js code could be parsed and used.

Version

2.0.1

Reproduction link

https://codesandbox.io/s/epic-chatterjee-pnzlr

Steps to reproduce

use image with a caption in a route

What is expected ?

<url>
  <loc>https://examplee.com/</loc>
  <changefreq>weekly</changefreq>
  <priority>0.8</priority>
  <image:image>
    <image:loc>https://example.com/some-image.png</image:loc>
    <image:caption>normal string</image:caption>
  </image:image>
</url>

What is actually happening?

<url>
  <loc>https://examplee.com/</loc>
  <changefreq>weekly</changefreq>
  <priority>0.8</priority>
  <image:image>
    <image:loc>https://example.com/some-image.png</image:loc>
    <image:caption><![CDATA[normal string]]></image:caption>
  </image:image>
</url>

Additional comments?

And i don't know why my sandbox does not even generate the xml file properly anyway.
I tried setting "cdata" to false in sitemap options defaults but it didn't help.
I have tested the route example in the sandbox on my local environment and it got wrapped in cdata

I'm not sure whats causing it but even if there's a character somewhere in the file that needs to be escaped, It shouldn't wrap everything in CDATA.
example:

<url>
  <loc>https://examplee.com/</loc>
  <changefreq>weekly</changefreq>
  <priority>0.8</priority>
  <image:image>
    <image:loc>https://example.com/someimage.png</image:loc>
    <image:caption><![CDATA[normal string]]></image:caption>
  </image:image>
</url>

What problem does this feature solve?

Hello! 👋🏼

Proposition : Automatically generate adequate sitemap with the concept rel-alternate-hreflang proposed by Google itself when using nuxt-i18n paths feature.

Why : Multilingual website cannot benefit from this plugin's automatic sitemap generation at the moment without heavy modifications/custom code. It would greatly help newcomers that doesn't know how to code this properly AND devs who do not know SEO's current best practices towards multilingual websites.

Source : Tell Google about localized versions of your page[https://support.google.com/webmasters/answer/189077?hl=en]

I am sure this can be implemented easily. nuxt-i18n is already supporting this rel-alternate-hreflang concept with link tags in the head.

What does the proposed changes look like?

Exemple

// contact.vue
nuxtI18n: {
    paths: {
        en: '/contact-us',
        fr: '/contactez-nous',
    },
},

Would generate

// generated sitemap.xml
<url>
    <loc>https://example.ca/en/contact-us/</loc>
    <xhtml:link rel="alternate" hreflang="fr-ca" href="https://example.ca/fr/contactez-nous/" />
    <xhtml:link rel="alternate" hreflang="en-ca" href="https://example.ca/en/contact-us/" />
    <changefreq>monthly</changefreq>
    <priority>1.0</priority>
</url>

Root page x-default when all locales are prefixed
Bonus point if you could support for the newest x-default value on root when i18n's option strategy = prefix

// generated sitemap.xml
<url>
    <loc>https://example.ca/</loc>
    <xhtml:link rel="alternate" hreflang="fr-ca" href="https://example.ca/fr/" />
    <xhtml:link rel="alternate" hreflang="en-ca" href="https://example.ca/en/" />
    <xhtml:link rel="alternate" hreflang="x-default" href="https://example.ca/" />
    <changefreq>monthly</changefreq>
    <priority>1.0</priority>
</url>

What problem does this feature solve?

If defined the router base in nuxt.config.js file, the links in the sitemap file did not consider that.
router: {
base: '/something/'
}

What does the proposed changes look like?

When creating the links in the sitemap file, It would be nice that consider the router base to make the real link.

Hey. There was an incomprehensible situation when using the @ nuxtjs / sitemap package.
When generating a system map file, the static paths were displayed incorrectly (without a domain name). Wrong old women: https://about/, https://contact/, https://news/, https://test/.Tell me how to solve the problem. Thank.

Hey. There was an incomprehensible situation when using the @ nuxtjs / sitemap package.
When generating a system map file, the static paths were displayed incorrectly (without a domain name). Wrong old women: https://about/, https://contact/, https://news/, https://test/.Tell me how to solve the problem. Thank.

What problem does this feature solve?

I have a website running on https on heroku, so https request via CNAME goes to herou and website is hosted there.
What am I experiencing now is that isHTTPS(req) function on production is returning false for these kind of requests, probably because of current hosting architecture.

I wanted to raise a PR with an option for forced https links in sitemap to avoid such issues and such situations.

What does the proposed changes look like?

Option in sitemaps module like forceHTTPS, which then creates all links with https reagrdless of request type and so on.

Version

2.0

Reproduction link

https://postwoman.io/sitemap.xml

Steps to reproduce

1. Build nuxt application in Travis CI
2. Deploy the application
3. Find the /sitemap.xml generated
4. Routes are relative to CI build job and not actual routes

What is expected ?

Routes should be relative to base path and not relative to build environment.

What is actually happening?

Instead of base path, build environment is considered as the root and /pages/routes are set relative to build enironment

Hi!
Does the cached sitemap gets invalidated every time my website is rebuild with nuxt generate?
If yes, what would be the recommended value for the cacheTime property? Disabling it with the value 0 or setting to a long period?

And thanks for this useful module!

Hey you can delete this if needed. It worked when I deployed the entire nuxt project to my host. Thank you though!

Hey I'm having difficulties with getting the actual sitemap page to display on my live website. It works just fine using run && build.

Any help much appreciated! I've tried both sitemap configs.

nuxt.config.js

modules:["@nuxtjs/sitemap"],

sitemap: {
hostname: "https://silentauctionvacations.com",
path: "/sitemap.xml",
exclude: ["/admin/**"]
}

OR

sitemap: {
exclude: ["/admin/**"]
}

Have this settings for sitemap:

  sitemap: {
    routes: [
      "/",
      "/en"
    ],
    path: '/sitemap.xml',
  },

in dev mode and in production mode (npm start) can see /sitemap.xml, but when deploy have this error:

Nuxt.js Internal Server Error

Sitemap files are limited to 50K URLs each.

1. Does this package support sitemap creation for sites with large (hundreds of thousands) of URLs?
2. How can I pass data from the database into this sitemap module? Is there an example of how to do this?

What problem does this feature solve?

Sitemap with Rtag can speed up search engine crawling. Baidu search engine can respond to sitemap updates more quickly. refer:https://ziyuan.baidu.com/college/articleinfo?id=456

What does the proposed changes look like?

options:{
Etag:true
}

What problem does this feature solve?

Hello to everybody,
does anyone have a solution to solve sitemap generation for a large number of pages? I generate articles from wordpress rest api and I need to split the sitemap into more files.

There is a solution in the sitemap.js documentation but I don't know how to use it in nuxt.js
https://github.com/ekalinin/sitemap.js#building-just-the-sitemap-index-file

Thanks for any advice.

I have a project where i generate a sitemap based on the current domain, to do this is need the hostname in the routes function to send it to an api which returns all info needed for my dynamic routes.
Is there any way to get the hostname/current domain in the routes function?

What problem does this feature solve?

We can already add a trailing slash to our own defined routes, but there is no way (AFAIK) yet to add it to generated/static routes.

e.g.
/about -> /about/ (while there is a pages/about.vue)