NEW: Added sitemap_suffix_included to better work with Cloudflare Pages and search engines #89
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.
When hosting a Sphinx project on Cloudflare Pages with default suffix
.html
, a very annoying fact is that the Cloudflare platform generates 301 responses to remove the suffix.Search engines (especially Google) dislike such redirection and refuse to index such pages, and that makes the generated sitemap less useful for SEO.
Thus, this pull request proposes a new setting
sitemap_suffix_included
to control whether.html
should be written tositemap.xml
. The default value is set toTrue
to keep current behavior. WhenFalse
is set, the generatedsitemap.xml
works well with Cloudflare and SEO.