You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
Automatic sitemap generation based on Sanity documents with a defined slug value. Sitemap is available to crawlers at /sitemap.xml and the full url is included in a generated robots.txt.
We are assuming that all documents containing the field slug should be included in the sitemap. If this assumption is wrong, the GROQ query can be adjusted to for example only include specific document types (like blog and page).
Added environment value NEXT_PUBLIC_URL for development and production, as this is required to provide fully qualitifed URLs in the sitemap.
Checklist
Please ensure that you’ve completed the following checkpoints before submitting your pull request:
Documentation: Relevant documentation has been added or updated (if applicable).
Image support in the Next.js sitemap generator was recently added in a canary release (https://github.com/vercel/next.js/releases/tag/v15.0.0-canary.107). So unless it's a top priority we might want to wait for that to be available. We could test if our images are already available to search engines (e.g. not using JavaScript to load), which would reduce the need to include them in the sitemap.
Image support in the Next.js sitemap generator was recently added in a canary release (https://github.com/vercel/next.js/releases/tag/v15.0.0-canary.107). So unless it's a top priority we might want to wait for that to be available. We could test if our images are already available to search engines (e.g. not using JavaScript to load), which would reduce the need to include them in the sitemap.
could also be that most of our images are for illustrations only, and that images for say news and costumer cases are more important. But yeah, I agree. Let's hold images until we've got more of the project defined.
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.
mathiazom
force-pushed
the
feat/v3-automatic-sitemap
branch
from
Further explanation is found here: #578
Automatic sitemap generation based on Sanity documents with a defined
slugvalue. Sitemap is available to crawlers at/sitemap.xmland the full url is included in a generatedrobots.txt.We are assuming that all documents containing the field
slugshould be included in the sitemap. If this assumption is wrong, the GROQ query can be adjusted to for example only include specific document types (like blog and page).Added environment value
NEXT_PUBLIC_URLfor development and production, as this is required to provide fully qualitifed URLs in the sitemap.Checklist
Please ensure that you’ve completed the following checkpoints before submitting your pull request: