diff --git a/__tests__/crawler.test.js b/__tests__/crawler.test.js
index 222db64e33..322a163bb9 100644
--- a/__tests__/crawler.test.js
+++ b/__tests__/crawler.test.js
@@ -52,6 +52,9 @@ test('Crawl the docs and execute tests', async () => {
     /^https:\/\/v1-(15|16|17|18)\.docs\.kubernetes\.io\/docs\/reference\/generated\/kubernetes-api\/v1\.(15|16|17|18)/i,
     /^https:\/\/github\.com\/projectcalico\/calico\/tree\/master\/[\w/.-]+\.md$/i,
     /^https:\/\/www\.linkedin\.com\/company\/tigera\/?$/,
+    // LinkedIn returns 999 to datacenter crawlers; the company page is fine in a browser. Same
+    // treatment as the tigera page above. Linked from the "about" / product-editions pages.
+    /^https:\/\/www\.linkedin\.com\/company\/project-calico\/?$/,
     /^https:\/\/installer\.calicocloud\.io\/manifests\/.+\/manifests/,
     'http://etcd.co',
     'https://www.tigera.io/project-calico/community',
@@ -70,6 +73,10 @@ test('Crawl the docs and execute tests', async () => {
     `https://installer.calicocloud.io/charts`,
     `https://docs.tigera.io/calico/charts`,
     'https://downloads.tigera.io/ee/charts',
+    // The DatastoreMigration CRD manifest is referenced by the CRD migration page but is not yet
+    // published to downloads.tigera.io for any released version; it ships once the publish step
+    // (calico-private master) is cut into a release. Live then; tracked in DOCS-2995.
+    /^https:\/\/downloads\.tigera\.io\/ee\/[\w.-]+\/manifests\/migration\.projectcalico\.org_datastoremigrations\.yaml$/,
     'https://Q4GSZWRKBA-dsn.algolia.net',
     'http://backend.stars:6379/status',
     'http://client.client:9000/status',
diff --git a/calico-enterprise_versioned_docs/version-3.23-2/operations/crd-migration.mdx b/calico-enterprise_versioned_docs/version-3.23-2/operations/crd-migration.mdx
index 74bf1638e6..391dea7f8c 100644
--- a/calico-enterprise_versioned_docs/version-3.23-2/operations/crd-migration.mdx
+++ b/calico-enterprise_versioned_docs/version-3.23-2/operations/crd-migration.mdx
@@ -51,7 +51,7 @@ The locked window is typically short (seconds to a few minutes depending on clus
 
 ## Before you begin
 
-- $[prodname] v3.32+ (or the release that includes the migration controller)
+- $[prodname] v3.23+ (or the release that includes the migration controller)
 - Cluster is currently running in API server mode (the aggregated API server is deployed)
 - **If using GitOps (ArgoCD, Flux):** pause sync before starting the migration. These tools may interfere with the API group switchover. You'll update your manifests to use `projectcalico.org/v3` after migration completes.
 
@@ -64,13 +64,13 @@ The locked window is typically short (seconds to a few minutes depending on clus
    Apply the v3 CRD manifests from the $[prodname] release. While the aggregated API service is active, Kubernetes ignores these CRDs, so this is safe to do ahead of time.
 
    ```bash
-   kubectl apply -f $[manifestsUrl]/manifests/v3_projectcalico_org.yaml
+   kubectl apply -f $[filesUrl]/manifests/v3_projectcalico_org.yaml
    ```
 
 2. **Install the DatastoreMigration CRD.**
 
    ```bash
-   kubectl apply -f $[manifestsUrl]/manifests/migration.projectcalico.org_datastoremigrations.yaml
+   kubectl apply -f $[filesUrl]/manifests/migration.projectcalico.org_datastoremigrations.yaml
    ```
 
 3. **Create the DatastoreMigration CR.**