Nuxt: fix sitemap missing handbook, ebooks, whitepapers, and integrations pages#5351
Merged
Conversation
✅ Deploy Preview for flowforge-website ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
ZJvandeWeg
approved these changes
Jul 22, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Description
sitemap.xmlwas only listing 1 URL (/resources/publications) in production, everything native to Nuxt (handbook, ebooks, whitepapers, integrations) was missing.handbook,ebooks, andwhitepaperscontent collections into@nuxtjs/sitemap's native@nuxt/contentv3 integration (defineSitemapSchema()incontent.config.ts), instead of relying on static-route auto-discovery, which can't see dynamic routes.integrations(not a content collection — built from the npm/GitHub catalogue at request time).sitemap-legacy.xmland merged it intositemap.xmlon every request. Instead, declare both sitemaps separately inrobots.txt:sitemap.xmlfor Nuxt-native pages,sitemap-legacy.xml(served as-is fromnuxt/public/) for whatever's still on 11ty.useHeadrobots meta tag inpages/[...slug].vuethat raced against@nuxtjs/robots's own computed meta/header for the same pages — nowrouteRulesis the single source of truth./termsfrom a hardcoded.vuepage tonuxt/content/terms.md, matching the existingprivacy-policy.mdpattern (both now render through the samepages/[...slug].vuecatch-all).Verified locally
sitemap.xml: 241 URLs (174 handbook + 60 integrations + 4 whitepapers + 2 ebooks + 1 publications), nonoindexleaks.sitemap-legacy.xml: confirmed reachable and correctly proxied to 11ty in dev; will be served as a static file fromnuxt/public/in production (11ty build step runs before the Nuxt build)./termsand/privacy-policy: both returnnoindex, nofolloweven when simulating production (?mockProductionEnv=1).Related Issue(s)
Checklist