feat(seo): custom page sitemap via fetchCustomPages#380
Merged
Conversation
Rewrites sitemap-weaverse.xml.ts to use the new SDK method instead of calling the auth-gated content API directly. Adds XML escaping, <lastmod> from publishedAt, and proper priority/changeFrequency. Registers route and injects into sitemap index.
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
1 participant
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.
Summary
sitemap-weaverse.xml.tsto useweaverse.fetchCustomPages()SDK method instead of directly calling the auth-gated content API<lastmod>frompublishedAttimestamproutes.tsand inject into sitemap index insitemap.tsDepends on
fetchCustomPagesmethod)Test plan
/sitemap-weaverse.xmlreturns valid XML with custom pages/sitemap.xmlincludes the weaverse sitemap reference<lastmod>dates are present and correctly formatted