Reclaim broken backlinks (part 2): 32 more 301 redirects#2821
Conversation
Follow-up to the initial broken-backlink PR. Adds 32 more 301 redirects for docs.tigera.io/calico paths surfaced by the full tigera.io subdomain backlink export that the first pass (24 redirects) didn't cover. Each broken URL maps 1:1 to the most relevant live page; where a feature was removed, it points to the nearest relevant page or section landing (never the homepage). Ordered by referring-domain rating. SEO broken-backlink audit (Laura Ferguson, 2026-07). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Pull request overview
Adds additional Netlify redirect rules to recover broken inbound links to docs.tigera.io Calico (and one Calico Enterprise) pages, supporting the ongoing SEO backlink-reclamation effort.
Changes:
- Add 32 new
301redirect mappings instatic/_redirects, grouped and annotated by referring domain rating (DR). - Redirect removed/renamed legacy paths (including
master/and olderen/*HTML pages) to the closest current equivalents.
| # DR 83 | ||
| /calico/latest/security/kubernetes-nodes /calico/latest/network-policy/hosts/kubernetes-nodes 301 | ||
| # DR 79 | ||
| /calico/latest/en/latest/understanding.html /calico/latest/about/ 301 |
There was a problem hiding this comment.
Fixed in dc85ad9 — changed the destination to /calico/latest/about (no trailing slash) to match the file convention (lines 25, 27, 101, 113, 122).
| /calico/latest/latest/getting-started/kubernetes/requirements /calico/latest/getting-started/kubernetes/requirements 301 | ||
| /calico/latest/latest/getting-started/kubernetes/installation/hosted/kubeadm/ /calico/latest/getting-started/kubernetes/self-managed-onprem/onpremises 301 | ||
| /calico/latest/latest/getting-started/kubernetes/installation/hosted/ /calico/latest/getting-started/ 301 | ||
| /calico/latest/master/introduction/ /calico/latest/about/ 301 |
There was a problem hiding this comment.
Fixed in dc85ad9 — changed the destination to /calico/latest/about (no trailing slash) to match the file convention (lines 25, 27, 101, 113, 122).
| /calico/latest/latest/getting-started/bare-metal/bare-metal /calico/latest/getting-started/bare-metal/ 301 | ||
| /calico/latest/security/service-policy /calico/latest/network-policy/policy-rules/service-policy 301 | ||
| /calico/latest/security/app-layer-policy /calico/latest/network-policy/istio/app-layer-policy 301 | ||
| /calico/latest/master /calico/latest/about/ 301 |
There was a problem hiding this comment.
Fixed in dc85ad9 — changed the destination to /calico/latest/about (no trailing slash) to match the file convention (lines 25, 27, 101, 113, 122).
Match the file's established convention for the Calico About landing page destination, avoiding inconsistent canonicalization. Per Copilot review. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

What
Follow-up to the first broken-backlink PR (which merged as 24 redirects). Adds 32 more
301redirects tostatic/_redirectsfordocs.tigera.io/calico*(and onedocs.tigera.io/calico-enterprise*) URLs surfaced by the full tigera.io subdomain backlink export that the first pass didn't cover. Each broken URL maps 1:1 to the most relevant live page, ordered by referring-domain rating.Why
SEO audit request from Laura Ferguson (Corporate Marketing, 2026-07): "Reclaim high-authority broken backlinks with 301 redirects." The full subdomain export contains 653
docs.tigera.iobacklink rows → 56 unique broken paths; 24 landed in the first PR, these are the remaining 32. (www.tigera.iorows are out of scope — already addressed per Laura.)Verification
200on the live site.404today.frompaths, no shadowing wildcard; all rules well-formed (from to 301).upstream/main(post first-PR merge); diff is exactly these 32 rules.Judgment calls to review
Where a feature/page was removed and has no direct successor, the redirect points to the nearest relevant page or section landing (never the homepage):
security/(bare) →/network-policy/.../installation/hosted*,.../installation/,master/getting-started/docker/installation/manual→/getting-started/(kubeadm variant →self-managed-onprem/onpremises)en/latest/*.html,en/1.4.0/datapath.html,master,master/introduction/→/about/or/reference/architecture/data-pathapp-layer-policyvariants →/network-policy/istio/app-layer-policyReviewers/product may want more precise destinations for these.
🤖 Generated with Claude Code