This repository was archived by the owner on Sep 9, 2026. It is now read-only.
seo: publish privacy at /privacy so the sitemap stops advertising a redirect - #17
Merged
Merged
Conversation
…edirect jekyll-sitemap emits page.url, which was /privacy.html. Cloudflare Pages serves clean URLs, so that address 308s to /privacy — the sitemap was pointing crawlers at a redirect while the canonical already pointed at the destination. The estate SEO sweep flags exactly that. `permalink: /privacy` moves page.url onto the URL that answers 200. The built file is still privacy.html, so Pages' own /privacy.html -> /privacy redirect is untouched and the old address keeps working; nothing needs a _redirects entry. This matches the intent already recorded in _config.yml, where the /install/ landing page is kept out of the sitemap to avoid "Page with redirect" in Search Console. Verified with a production Jekyll build: _site/privacy.html unchanged, sitemap now lists https://gsamanager.org/privacy, canonical agrees. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0119vXMJC7FKdDTYJkLVLusg
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
jekyll-sitemapemitspage.url, which was/privacy.html. Cloudflare Pages serves clean URLs, so that address 308s to/privacy— the sitemap was pointing crawlers at a redirect whilecanonical_urlalready pointed at the destination.permalink: /privacymovespage.urlonto the URL that answers 200.The built file does not change
Worth stating, because it's what makes this safe:
permalink: /privacywith no trailing slash still writesprivacy.html. Pages' own/privacy.html → /privacyredirect is untouched and the old address keeps working, so no_redirectsentry is needed. (I added one first, then removed it after the build showed the filename was unchanged.)This matches the intent already recorded in
_config.yml, where/install/is kept out of the sitemap to avoid "Page with redirect" in Search Console.Verification
Production Jekyll build:
🤖 Generated with Claude Code
https://claude.ai/code/session_0119vXMJC7FKdDTYJkLVLusg