Skip to content

feat(sitemap): use udata generated sitemap - #1176

Open
maudetes wants to merge 6 commits into
mainfrom
feat/use-udata-sitemap
Open

feat(sitemap): use udata generated sitemap#1176
maudetes wants to merge 6 commits into
mainfrom
feat/use-udata-sitemap

Conversation

@maudetes

@maudetes maudetes commented Jul 30, 2026

Copy link
Copy Markdown
Contributor

Following opendatateam/udata#3830

Both udata and cdata sitemaps index will be exposed in robots.txt.

Comment thread tests/sitemap.spec.ts Outdated
expect(locCount).toBe(3)
})

test('omits the external sitemap URL when NUXT_SITEMAP_INDEX_URL is not set', async ({ page }) => {

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think it's worth adding a step to test it explicitly in CI?

@maudetes
maudetes requested a review from ThibaudDauce July 30, 2026 12:38
@ThibaudDauce

Copy link
Copy Markdown
Contributor

Claude is not sure it's allowed to reference an index inside an index, but it may be better to just reference two sitemaps in our robots.txt (in infra)

Something like:

Sitemap: {{ udata__cdata_base_url }}/sitemap_index.xml
Sitemap: {{ udata__sitemap_index_url }}

@maudetes

Copy link
Copy Markdown
Contributor Author

Claude is not sure it's allowed to reference an index inside an index, but it may be better to just reference two sitemaps in our robots.txt (in infra)

Hmm, indeed when looking it up again, I find contradictory information on nested sitemaps 😓

Let's go for the robots approach, I liked the single entry point but it's not worth the trouble.

I've removed any reference to udata sitemap in 8113fe8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants