Add 5 custom canonical tags based on SEO agency recs (#11727)

* Add 5 custom canonical tags based on SEO agency recs * Fix incorrect tag change --------- Co-authored-by: Alex Krawiec <alex.krawiec@R7J1Y747QQ.local>
getsentry · Nov 7, 2024 · a3f8187 · a3f8187
1 parent 7381fc9
commit a3f8187
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 0 deletions.
diff --git a/docs/platforms/javascript/common/configuration/integrations/console.mdx b/docs/platforms/javascript/common/configuration/integrations/console.mdx
@@ -1,6 +1,7 @@
 ---
 title: Console
 description: "Capture console logs as breadcrumbs. (default)"
+customCanonicalTag: "/platforms/javascript/guides/express/configuration/integrations/console/"
 supported:
   - javascript.node
   - javascript.aws-lambda

diff --git a/docs/platforms/javascript/common/configuration/integrations/nodefetch.mdx b/docs/platforms/javascript/common/configuration/integrations/nodefetch.mdx
@@ -1,6 +1,7 @@
 ---
 title: NodeFetch
 description: "Capture spans & breadcrumbs for node fetch requests. (default)"
+customCanonicalTag: "/platforms/javascript/guides/nuxt/configuration/integrations/nodefetch/"
 supported:
   - javascript.node
   - javascript.aws-lambda

diff --git a/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx b/docs/platforms/javascript/common/data-management/sensitive-data/index.mdx
@@ -1,6 +1,7 @@
 ---
 title: "Scrubbing Sensitive Data"
 description: "Learn about filtering or scrubbing sensitive data within the SDK, so that data is not sent with the event. You can also configure server-side scrubbing to ensure the data is not stored."
+customCanonicalTag: "/platforms/javascript/guides/koa/data-management/sensitive-data/"
 sidebar_order: 100
 keywords:
   - pii

diff --git a/docs/platforms/javascript/common/sourcemaps/uploading/rollup.mdx b/docs/platforms/javascript/common/sourcemaps/uploading/rollup.mdx
@@ -2,6 +2,7 @@
 title: Rollup
 description: "Upload your source maps with the Sentry Rollup Plugin."
 sidebar_order: 5
+customCanonicalTag: "/platforms/javascript/guides/koa/sourcemaps/uploading/rollup/"
 ---
 
 <Note>

diff --git a/...orms/native/common/tracing/trace-propagation/dealing-with-cors-issues/index.mdx b/...orms/native/common/tracing/trace-propagation/dealing-with-cors-issues/index.mdx
@@ -1,6 +1,7 @@
 ---
 title: Dealing with CORS Issues
 sidebar_order: 80
+customCanonicalTag: "/platforms/javascript/guides/wasm/tracing/trace-propagation/dealing-with-cors-issues/"
 ---
 
 If your frontend and backend are hosted on different domains (for example, your frontend is on `https://example.com` and your backend is on `https://api.example.com`), and the frontend does XHR/fetch requests to your backend, you'll need to configure your backend [CORS](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Access-Control-Allow-Headers) headers to ensure requests aren't blocked.