Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Splitting sitemap based on locale

See original GitHub issue

I was wondering how we would go about splitting the sitemap with locales?

so instead of just a sitemap-index.xml:

sitemap-index.xml (with references to the following languages indexes)
sitemap-nl-index.xml
sitemap-fr-index.xml
…

Issue Analytics

State:
Created 3 years ago
Reactions:4
Comments:8 (2 by maintainers)

Top GitHub Comments

8reactions

iamvishnusankarcommented, Nov 5, 2020

Hi @BramDecuypere , Working on locale based sitemaps are bit tricky. It involves few challenges to tackle before implementing. Some of them are:

Domain based and sub-dir based locale routes.
We can’t expect the translation for every pages, so creating sitemaps for localised contents from default sitemap becomes challenging.
Nextjs doesn’t have any pre-render manifest for i18n routes. …etc

But a generic solution can be implemented to address all these issue. I will be posting a detailed RFC of next major release.

2reactions

paalescommented, Jun 9, 2021

@iamvishnusankar We’re trying to use nextjs with multiple domains as mentioned here: https://nextjs.org/docs/advanced-features/i18n-routing#getting-started

I’m not totally sure if this issue would solve it, but would be nice if next-sitemap could parse the domains section and everything would ‘just work’.

Maybe we can already get something up and running, but I can’t figure it out. Any ideas?