SEO pass: rename edot-* URL slugs to match 9.5 product rebrand

[alexandra5000]

Context

The 9.5 GA rebrand renamed display names (EDOT Collector → Elastic Agent, EDOT Cloud Forwarder → Elastic Cloud Forwarder, EDOT → Elastic OpenTelemetry) but intentionally kept URL paths unchanged to avoid breaking inbound links during the 9.5 release window. This issue tracks the follow-up SEO pass to align the public URLs with the new product names.

Related: elastic/docs-content-internal#1242

Scope

elastic/elastic-agent

Current path	New path	Notes
docs/reference/edot-collector/ (37 files)	docs/reference/otel-collector/	Largest tree; also has a single existing redirect entry in docs/redirects.yml

elastic/opentelemetry

Current path	New path	Notes
docs/reference/edot-cloud-forwarder/	docs/reference/elastic-cloud-forwarder/	(4 files)
docs/reference/compatibility/edot-vs-upstream.md	docs/reference/compatibility/elastic-vs-upstream-otel.md	Single file
docs/reference/_snippets/edot-collector-auth.md	docs/reference/_snippets/otel-collector-auth.md	Snippet, not a public URL

elastic/docs-content

Current path	New path	Notes
troubleshoot/ingest/opentelemetry/edot-collector/ (10 files)	troubleshoot/ingest/opentelemetry/otel-collector/
solutions/observability/logs/stream-any-log-file-using-edot-collector.md	solutions/observability/logs/stream-any-log-file-using-elastic-agent.md
solutions/_snippets/edot-reference-arch.md	solutions/_snippets/otel-reference-arch.md	Snippet
solutions/observability/get-started/opentelemetry/_snippets/edot-collector-auth.md	solutions/observability/get-started/opentelemetry/_snippets/otel-collector-auth.md	Snippet
solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-elastic-distributions-of-opentelemetry-edot.md	solutions/observability/get-started/quickstart-unified-kubernetes-observability-with-opentelemetry.md	Long filename with edot at the end

Note: The edot-* product IDs used in applies_to frontmatter (edot_collector, edot_cf_aws, etc.) are machine identifiers inside docs-builder and are not part of this rename — only public-facing URL path segments change.

What makes this complex

1. The opentelemetry redirects.yml is already a redirect hub

opentelemetry/docs/redirects.yml currently holds:

• ~60 entries redirecting old reference/edot-collector/* paths → elastic-agent://reference/edot-collector/*
• Several entries redirecting reference/edot-collector/troubleshooting/* → docs-content://troubleshoot/ingest/opentelemetry/edot-collector/*

Renaming the target paths means updating all these redirect targets at the same time, or they will point at non-existent pages.

2. Cross-repo links (repo:// format)

Across docs-content and opentelemetry there are ~25 unique cross-repo links of the form elastic-agent://reference/edot-collector/* and ~9 of the form opentelemetry://reference/edot-*. Every one must be updated to the new path.

3. Hard-coded elastic.co/docs/ URLs

~11 pages in docs-content embed hard-coded https://www.elastic.co/docs/...edot-collector... URLs rather than repo:// cross-links. These bypass the redirect system entirely and must be updated by hand.

4. GitHub raw URLs pointing to deploy/helm/edot-collector/

Multiple pages link to GitHub raw content at paths like:

https://raw.githubusercontent.com/elastic/elastic-agent/refs/tags/v9.x.y/deploy/helm/edot-collector/kube-stack/values.yaml

These point at the actual repo directory structure (not docs paths). Whether the Helm chart directory itself gets renamed is a separate decision that would cascade here.

5. TOC/nav files

Four TOC files across three repos reference edot-* paths by filename (not just product ID):

• elastic-agent/docs/docset.yml — toc: reference/edot-collector
• opentelemetry/docs/reference/toc.yml — toc: edot-cloud-forwarder
• docs-content/solutions/toc.yml — 4 entries
• docs-content/troubleshoot/toc.yml — 24 entries

🤖 Generated with Claude Code

[github-actions]

Elastic Docs AI Menu

Check one box to run an AI workflow for this issue.

• Triage (docs-triage). Status: not started.
• Size the work (docs-size). Status: not started.
• Scope the docs work (docs-issue-scope). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

[alexandra5000]

PRs (merge in order):

1. docs: rename reference/edot-collector slug to reference/otel-collector (Phase 4) elastic-agent#16022 — rename reference/edot-collector/ → reference/otel-collector/
2. docs: rename edot-cloud-forwarder, edot-vs-upstream, and edot-collector-auth slugs (Phase 4) opentelemetry#654 — rename edot-cloud-forwarder/, edot-vs-upstream.md, edot-collector-auth.md; update ~60 redirect targets
3. docs: rename edot-collector, quickstart, and stream-any-log-file slugs (Phase 4) #7807 — rename troubleshoot tree, two solution pages, two snippets; update ~25 cross-links and 28 toc entries

2 and 3 can merge simultaneously after 1.

[alexandra5000]

Merge plan

The build failures on the PRs in this issue are expected and the plan to resolve them is below.

Root cause: The global nav config in elastic/docs-builder still maps reference/edot-collector for elastic-agent. The NavigationPrefixChecker validates every page in a PR's link index against that nav, so every new otel-collector/* page fails. A phantom in the nav suppresses this until the nav entry is swapped.

Merge order:

1. nav: add phantom for elastic-agent otel-collector slug rename docs-builder#3795 (draft) — adds a phantom for elastic-agent://reference/otel-collector; once merged, elastic-agent #16022 CI goes green
2. docs: rename reference/edot-collector slug to reference/otel-collector (Phase 4) elastic-agent#16022 — rename reference/edot-collector/ → reference/otel-collector/; can merge independently after step 1
3. nav: swap elastic-agent nav entry edot-collector → otel-collector, remove phantom docs-builder#3799 (follow-up PR) — swap nav entry edot-collector → otel-collector, remove phantom; must merge immediately after step 2 to restore live nav
4. docs: rename edot-cloud-forwarder, edot-vs-upstream, and edot-collector-auth slugs (Phase 4) opentelemetry#654 and docs: rename edot-collector, quickstart, and stream-any-log-file slugs (Phase 4) #7807 — can merge simultaneously after step 2; their redirect-target validation errors resolve once elastic-agent publishes the new otel-collector link index