diff --git a/modules/develop/pages/manage-topics/cloud-topics.adoc b/modules/develop/pages/manage-topics/cloud-topics.adoc
index 05f2b332ff..86932e2d5c 100644
--- a/modules/develop/pages/manage-topics/cloud-topics.adoc
+++ b/modules/develop/pages/manage-topics/cloud-topics.adoc
@@ -6,6 +6,8 @@
 :learning-objective-2: Create a Cloud Topic using rpk after enabling Cloud Topics on your cluster
 :learning-objective-3: Identify Cloud Topics limitations and configurations that reduce cross-AZ networking costs
 // tag::single-source[]
+ifdef::env-cloud[:producers-page: develop:topics/configure-producers-for-cloud-topics.adoc]
+ifndef::env-cloud[:producers-page: develop:manage-topics/configure-producers-for-cloud-topics.adoc]
 
 ifndef::env-cloud[]
 [NOTE]
@@ -83,6 +85,6 @@ You can make a topic a Cloud Topic only at topic creation time.
 
 In addition to replication, cross-AZ ingress (producer) and egress (consumer) traffic can also contribute substantially to cloud networking costs. When running multi-AZ clusters in general, Redpanda strongly recommends using xref:develop:consume-data/follower-fetching.adoc[Follower Fetching], which allows consumers to avoid crossing network zones. When possible, you can use xref:develop:produce-data/leader-pinning.adoc[leader pinning], which positions a topic's partition leader close to the producers, providing a similar benefit for ingress traffic. These features can add additional savings to the replication cost savings of Cloud Topics.
 
-For client-side tuning guidance, see xref:develop:manage-topics/configure-producers-for-cloud-topics.adoc[Configure producers for Cloud Topics].
+For client-side tuning guidance, see xref:{producers-page}[Configure producers for Cloud Topics].
 
 // end::single-source[]
diff --git a/modules/develop/partials/cloud-topics-overview.adoc b/modules/develop/partials/cloud-topics-overview.adoc
index 2ec20c0c28..490e120265 100644
--- a/modules/develop/partials/cloud-topics-overview.adoc
+++ b/modules/develop/partials/cloud-topics-overview.adoc
@@ -1,7 +1,7 @@
 // tag::intro[]
 Starting in v26.1, Redpanda provides glossterm:Cloud Topic[,Cloud Topics] to support multi-modal streaming workloads in the most cost-effective way possible: as a per-topic configuration running mixed latency workloads. While standard Redpanda
 ifdef::env-cloud[]
-xref:get-started:config-topics.adoc[topics]
+xref:develop:topics/config-topics.adoc[topics]
 endif::[]
 ifndef::env-cloud[]
 xref:develop:manage-topics/config-topics.adoc[topics]