seo: unify docs.decdn.org Organization with the main site's @id

[yigitdot]

Background

PR #192 added a seo.organization block to docs/docs.json so docs.decdn.org emits Organization structured data. It sets name / url / logo / sameAs, but not a stable @id.

The main site declares its Organization with a stable @id of https://decdn.org/#organization (ORG_ID in lib/links.ts — export const ORG_ID = \${SITE_URL}#organization`; referenced from every schema's publisher/provider` in app/layout.tsx).

Problem

Because the docs seo.organization omits id, Mintlify emits a separate Organization node scoped to docs.decdn.org. Search engines may treat docs.decdn.org and decdn.org as two different organizations rather than one entity.

Proposal

Mintlify's docs.json schema exposes seo.organization.id (a URI). Setting it to the main site's canonical id consolidates the two into a single entity:

```json
"organization": {
"id": "https://decdn.org/#organization",
"name": "deCDN",
"url": "https://decdn.org",
"logo": "https://docs.decdn.org/logo/logomark-light.png",
"sameAs": ["https://github.com/decdn", "https://x.com/decdn_", "https://www.linkedin.com/company/decdn"]
}
```

Low-risk, one-line change. Deferred from PR #192 for a later look.

Verify after deploy

Run a docs.decdn.org page through Google's Rich Results test and confirm the Organization @id matches the main site's.

[github-actions]

🎯 Agentic Issue Triage

Type: SEO enhancement — structured data consolidation
Risk: Very low (one-line config change in docs/docs.json)
Scope: docs/ only (Mintlify pipeline, independent of pnpm build)

This is a straightforward follow-up to PR #192. Without seo.organization.id, Mintlify emits a separate Organization node for docs.decdn.org, potentially fragmenting the entity graph that search engines use to build knowledge panels. Setting it to the canonical `(decdn.org/redacted) merges the two nodes.

Implementation

In docs/docs.json, update the seo.organization block to include id:

"organization": {
  "id": "(decdn.org/redacted),
  "name": "deCDN",
  "url": "(decdn.org/redacted)",
  "logo": "(docs.decdn.org/redacted),
  "sameAs": ["https://github.com/decdn", "(x.com/redacted), "(www.linkedin.com/redacted)
}

ORG_ID is exported from lib/links.ts as `${SITE_URL}#organization` → (decdn.org/redacted) This is a static string so hard-coding it in docs/docs.json` is safe.

After editing, run pnpm exec prettier --write docs/docs.json (required by the docs workflow).

Verification

After Mintlify Cloud redeploys:

1. Open any docs.decdn.org page in [Google's Rich Results Test]((search.google.com/redacted)
2. Confirm the detected Organization node has `@id: "(decdn.org/redacted)
3. Confirm it matches the main site's node (run decdn.org through the same tool).

Context & related issues

• PR feat(seo): add social preview image to docs.decdn.org #192 — added seo.organization to docs/docs.json (deferred id field)
• Issue Expand Organization.sameAs once more social accounts exist #27 — expanding Organization.sameAs once more accounts exist (the sameAs array here should stay in sync)
• lib/links.ts — ORG_ID definition; app/layout.tsx — main site's Organization schema

Generated by Agentic Triage for #193 · ◷

_{Add this agentic workflow to your repo}

To install this agentic workflow, run

gh aw add githubnext/agentics/workflows/issue-triage.md@c7d030cd6d4607b90d9ac3ffc8b24aff4f251632