We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using both multi sitemaps and i18n, it will be useful to still have a separate sitemap for each language.
nitro.config.js:
sitemap: { sitemaps: { shirts: { sources: ['/api/sitemap/shirts'] } } }
/api/sitemap/shirts:
export default defineSitemapEventHandler(async () => { return [{ loc: `/shirts/white`, _i18nTransform: true }]; });
This will generate /__sitemap__/shirts.xml which contains pages in all languages.
/__sitemap__/shirts.xml
/__sitemap__/shirts/en.xml /__sitemap__/shirts/es.xml ...
No response
Thank you :pr
The text was updated successfully, but these errors were encountered:
Google does not support nesting multiple index sitemaps within each other so this is not something I will implement, sorry.
Sorry, something went wrong.
Oh right, sorry about that. What about /__sitemap__/shirts-en.xml?
/__sitemap__/shirts-en.xml
It's possible but it's unlikely I'll attempt this any time soon as there's quite a bit of complixity involved in supporting this.
No branches or pull requests
🆒 Your use case
When using both multi sitemaps and i18n, it will be useful to still have a separate sitemap for each language.
nitro.config.js:
/api/sitemap/shirts:
This will generate
/__sitemap__/shirts.xml
which contains pages in all languages.🆕 The solution you'd like
🔍 Alternatives you've considered
No response
ℹ️ Additional info
Thank you :pr
The text was updated successfully, but these errors were encountered: