diff --git a/docs.json b/docs.json
index 7c87e009af..dcf965da15 100644
--- a/docs.json
+++ b/docs.json
@@ -540,7 +540,7 @@
                     "group": "Get Started",
                     "pages": [
                       "weave/agent-integration-quickstart",
-                      "weave/custom-agents-quickstart",
+                      "weave/guides/tracking/trace-agents-otel",
                       "weave/quickstart"
                     ]
                   },
diff --git a/weave.mdx b/weave.mdx
index f3f9e9afa9..743915a42c 100644
--- a/weave.mdx
+++ b/weave.mdx
@@ -26,11 +26,11 @@ Select your workload type and then use the following docs to guide you through t
   </Card>
 
   <Card
-    title="Set up custom agent observability"
+    title="Send OpenTelemetry spans to the Agents view"
     icon="code"
-    href="/weave/custom-agents-quickstart"
+    href="/weave/guides/tracking/trace-agents-otel"
   >
-    Trace a custom multi-turn agent with the Weave SDK to capture sessions, LLM calls, and tool calls as OpenTelemetry spans.
+    Quickly configure your OTel-instrumented agent to send traces to Weave's OTLP endpoint. No Weave SDK installation required.
   </Card>
 
   <Card
diff --git a/weave/guides/tracking/otel.mdx b/weave/guides/tracking/otel.mdx
index 87b1a396a8..7f075946c1 100644
--- a/weave/guides/tracking/otel.mdx
+++ b/weave/guides/tracking/otel.mdx
@@ -4,6 +4,10 @@ description: "Import OpenTelemetry compatible trace data through a dedicated end
 keywords: ["OTLP", "OpenTelemetry Collector", "OpenInference", "OpenLLMetry", "threads"]
 ---
 
+<Warning>
+We recommend using [Weave's new OTel-native workflow](/weave/guides/tracking/trace-agents-otel) to send OTel spans to Weave's new Agents view. Only use this guide if you want to send raw OTLP trace ingestion into Weave's standard Traces view.
+</Warning>
+
 Weave supports import of OpenTelemetry compatible trace data through a dedicated endpoint. This endpoint lets you send OTLP (OpenTelemetry Protocol) formatted trace data directly to your Weave project. Use this integration when you want to instrument your application with the OpenTelemetry standard and have those traces appear alongside your other Weave data, without replacing your existing OTel-based observability pipeline.
 
 This page covers the endpoint details, authentication, end-to-end examples in Python and TypeScript, how to forward traces through an OpenTelemetry Collector, how to organize traces into Weave threads, and the attribute mappings Weave applies to incoming spans.
diff --git a/weave/guides/tracking/trace-agents-otel.mdx b/weave/guides/tracking/trace-agents-otel.mdx
index 49084dc7ff..ead011aa2f 100644
--- a/weave/guides/tracking/trace-agents-otel.mdx
+++ b/weave/guides/tracking/trace-agents-otel.mdx
@@ -4,7 +4,7 @@ description: "Send OTLP trace data from any OpenTelemetry pipeline to the Weave
 keywords: ["OTLP", "OpenTelemetry", "GenAI semantic conventions", "agents endpoint", "no SDK"]
 ---
 
-W&B Weave agent observability is built on [OpenTelemetry (OTel)](https://opentelemetry.io/docs/concepts/). Weave provides a dedicated OTLP endpoint that ingests spans into the **Agents** view. If your agent already emits OTel spans, you can send them to Weave by pointing your existing OTel pipeline at the endpoint without installing the Weave SDK.
+W&B Weave agent observability is built on [OpenTelemetry (OTel)](https://opentelemetry.io/docs/concepts/) and provides a dedicated OTLP endpoint that ingests spans into the **Agents** view. This means that you can quickly redirect your OTel-instrumented application's spans to Weave by swapping your OTel exporter's current endpoint configuration with Weave's endpoint configuration. You do not need to install the Weave SDK to do this.
 
 This page covers how to authenticate with and send spans to the endpoint.