Keep the status page out of search: allow the crawl, send noindex #272
No reviewers
Labels
No labels
area:docs
area:identity
area:ops
area:plugin
area:server
channel:community
channel:direct
channel:owned
channel:press
channel:social
e2ee-constrained
gate:at-ga
gate:pre-ga
marketing
parity
relay:absent
relay:planned
relay:requested
relay:supported
risk:additive
risk:contract
risk:none
usability
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
Nectenda/nectenda!272
Loading…
Reference in a new issue
No description provided.
Delete branch "worktree-nec-237-status-noindex"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Task: NEC-237
Search Console reported status.nectenda.com as "Indexed, though blocked by robots.txt". Uptime Kuma answers
robots.txtwithDisallow: /, and every nectenda.com footer links to the status page. Google indexed the bare URL from those links without fetching the page, so it never saw a noindex.deploy/ops/Caddyfile, status host only:/robots.txtitself withAllow: /.X-Robots-Tag: noindex.Checked by running the block in a local Caddy against a stub upstream whose own robots.txt is
Disallow./and/api/xreach the stub with the header, and/robots.txtreturns Caddy'sAllow: /.Merging does not deploy it. The ops Caddyfile reaches the host only at provisioning, so after merging it has to be copied to
/srv/ops/Caddyfileby hand and Caddy reloaded.Changelog
NONE
🤖 Generated with Claude Code
https://claude.ai/code/session_01StURdiv33xnMfE2XRyg8Lt