Merge pull request #186 from flashcatcloud/codex/mintlify-seo

docs: optimize Mintlify SEO and canonical URLs

Author: GraceWalk

README.md

@@ -3,7 +3,7 @@
 English | [中文](https://github.com/flashcatcloud/flashduty-docs/blob/main/README_zh.md)
 
 [![Mintlify](https://img.shields.io/badge/Built_with-Mintlify-8B5CF6?style=flat-square)](https://mintlify.com/)
-[![Docs](https://img.shields.io/badge/Live-docs.flashcat.cloud-blue?style=flat-square)](https://docs.flashcat.cloud)
+[![Docs](https://img.shields.io/badge/Live-docs.flashduty.com-blue?style=flat-square)](https://docs.flashduty.com)
 [![License: MIT](https://img.shields.io/badge/License-MIT-green?style=flat-square)](LICENSE)
 
 Official documentation for [Flashduty](https://flashcat.cloud/), bilingual (Chinese & English), built with [Mintlify](https://mintlify.com/). Covers On-call incident management, RUM real user monitoring, and Monitors alert rules — **390+** pages in total.
@@ -131,7 +131,7 @@ Full glossary: [`glossary.md`](glossary.md)
 
 | Resource | Link |
 |----------|------|
-| Flashduty Docs | [docs.flashcat.cloud](https://docs.flashcat.cloud) |
+| Flashduty Docs | [docs.flashduty.com](https://docs.flashduty.com) |
 | Flashduty Console | [console.flashcat.cloud](https://console.flashcat.cloud/) |
 | Flashduty Website | [flashcat.cloud](https://flashcat.cloud/) |
 | MCP Server | [flashduty-mcp-server](https://github.com/flashcatcloud/flashduty-mcp-server) |

README_zh.md

@@ -3,7 +3,7 @@
 [English](https://github.com/flashcatcloud/flashduty-docs/blob/main/README.md) | 中文
 
 [![Mintlify](https://img.shields.io/badge/Built_with-Mintlify-8B5CF6?style=flat-square)](https://mintlify.com/)
-[![Docs](https://img.shields.io/badge/Live-docs.flashcat.cloud-blue?style=flat-square)](https://docs.flashcat.cloud)
+[![Docs](https://img.shields.io/badge/Live-docs.flashduty.com-blue?style=flat-square)](https://docs.flashduty.com)
 [![License: MIT](https://img.shields.io/badge/License-MIT-green?style=flat-square)](LICENSE)
 
 [Flashduty](https://flashcat.cloud/) 官方文档站，中英双语，基于 [Mintlify](https://mintlify.com/) 构建。覆盖 On-call 故障管理、RUM 真实用户监控、Monitors 告警规则三大产品模块，共 **390+** 页文档。
@@ -131,7 +131,7 @@ flashduty-docs/
 
 | 资源 | 链接 |
 |------|------|
-| Flashduty 文档站 | [docs.flashcat.cloud](https://docs.flashcat.cloud) |
+| Flashduty 文档站 | [docs.flashduty.com](https://docs.flashduty.com) |
 | Flashduty 控制台 | [console.flashcat.cloud](https://console.flashcat.cloud/) |
 | Flashduty 官网 | [flashcat.cloud](https://flashcat.cloud/) |
 | MCP Server | [flashduty-mcp-server](https://github.com/flashcatcloud/flashduty-mcp-server) |

api-reference/openapi.legacy.zh.json

@@ -12690,7 +12690,7 @@
                   },
                   "include_events": {
                     "type": "boolean",
-                    "description": "是否包含原始事件数据，了解[告警降噪](https://docs.flashcat.cloud/zh/flashduty/what-is-noise-reduction#%E5%9F%BA%E6%9C%AC%E6%A6%82%E5%BF%B5)"
+                    "description": "是否包含原始事件数据，了解[告警降噪](https://docs.flashduty.com/zh/flashduty/what-is-noise-reduction#%E5%9F%BA%E6%9C%AC%E6%A6%82%E5%BF%B5)"
                   },
                   "is_active": {
                     "type": [
@@ -28766,7 +28766,7 @@
           },
           "title_rule": {
             "type": "string",
-            "description": "告警标题生成规则，具体请[参考规则](https://docs.flashcat.cloud/zh/flashduty/customize-incident-attrs)"
+            "description": "告警标题生成规则，具体请[参考规则](https://docs.flashduty.com/zh/flashduty/customize-incident-attrs)"
           },
           "description": {
             "type": "string",
@@ -30678,7 +30678,7 @@
             "title": "新的告警标题",
             "minLength": 1,
             "maxLength": 512,
-            "description": "支持通过变量生成，参考[定制故障标题](https://docs.flashcat.cloud/zh/flashduty/customize-incident-attrs)"
+            "description": "支持通过变量生成，参考[定制故障标题](https://docs.flashduty.com/zh/flashduty/customize-incident-attrs)"
           }
         },
         "required": [
@@ -30691,7 +30691,7 @@
           "description": {
             "type": "string",
             "title": "新的告警描述",
-            "description": "支持通过变量生成，参考[定制故障描述](https://docs.flashcat.cloud/zh/flashduty/customize-incident-attrs)",
+            "description": "支持通过变量生成，参考[定制故障描述](https://docs.flashduty.com/zh/flashduty/customize-incident-attrs)",
             "minLength": 1,
             "maxLength": 2048
           }
@@ -30706,7 +30706,7 @@
           "severity": {
             "type": "string",
             "title": "新的严重程度",
-            "description": "支持通过变量生成，参考[定制故障描述](https://docs.flashcat.cloud/zh/flashduty/customize-incident-attrs)",
+            "description": "支持通过变量生成，参考[定制故障描述](https://docs.flashduty.com/zh/flashduty/customize-incident-attrs)",
             "enum": [
               "Critical",
               "Warning",
@@ -33283,4 +33283,4 @@
     }
   ],
   "security": []
-}
+}

docs.json

@@ -1,5 +1,6 @@
 {
   "$schema": "https://mintlify.com/docs.json",
+  "description": "Flashduty 官方文档，涵盖 On-call 告警响应、Monitors 监控、RUM 与 AI SRE 的配置指南、集成方式和 API 参考。",
   "theme": "mint",
   "name": "Flashduty Docs",
   "favicon": "/logo/saas-favicon.png",
@@ -15,7 +16,17 @@
   },
   "seo": {
     "metatags": {
-      "canonical": "https://docs.flashcat.cloud"
+      "canonical": "https://docs.flashduty.com"
+    },
+    "organization": {
+      "id": "https://flashduty.com/#organization",
+      "name": "Flashduty",
+      "legalName": "北京快猫星云科技有限公司",
+      "url": "https://flashduty.com/",
+      "logo": "https://docs.flashduty.com/logo/saas-logo.svg",
+      "sameAs": [
+        "https://github.com/flashcatcloud"
+      ]
     }
   },
   "redirects": [

en/ai-sre/init.mdx

@@ -18,7 +18,7 @@ Type `/init` in the input box of any AI SRE session, and the agent switches into
 `/init` is the **starting point** for the knowledge base. AI SRE's diagnostic quality depends directly on how much real knowledge it can read about your systems: the more complete and accurate your [Knowledge](/en/ai-sre/knowledge) base is, the faster and more reliably the agent pinpoints root causes. `/init` is the guided flow that builds that knowledge from zero — and once it's built, every session loads it automatically.
 
 <Note>
-`/init` will **never** write or install anything without your consent. Before anything lands at each phase, it lists exactly "which files will be created/updated," and only acts after you confirm them one by one. Credentials (tokens, passwords, AK/SK) are never echoed back in plain text in the conversation — only recorded as `<recorded (length=N)>`. See [Safety & consent](#safety--consent).
+`/init` will **never** write or install anything without your consent. Before anything lands at each phase, it lists exactly "which files will be created/updated," and only acts after you confirm them one by one. Credentials (tokens, passwords, AK/SK) are never echoed back in plain text in the conversation — only recorded as `<recorded (length=N)>`. See [Safety and consent](#safety-and-consent).
 </Note>
 
 ## When to use /init vs. plain natural language
@@ -98,7 +98,7 @@ Type `/init` in the input box of any AI SRE session, and the agent switches into
   </Accordion>
 </AccordionGroup>
 
-## Safety & consent
+## Safety and consent
 
 ---
 

en/compliance/user-agreement.mdx

@@ -1,6 +1,6 @@
 ---
 title: "User Agreement"
-description: "Learn about the Flashduty Terms of Service from Beijing Flashcat Cloud Technology Co.,Ltd."
+description: "Review the legal terms governing user registration, account management, and use of Flashduty services."
 ---
 
 Last Updated: 2022-12-24
@@ -365,4 +365,4 @@ When the following circumstances occur, the Flashcat Cloud service system may no
 
 13.2 This Agreement takes effect after you click "Agree to Agreement and Submit" (specific wording detailed on the registration page) on the Flashcat Cloud platform, and unless otherwise agreed by both parties, this Agreement will remain valid during your use of Flashcat Cloud services.
 
-13.3 The effectiveness, interpretation, modification, execution, and dispute resolution of this Agreement are governed by the laws of the People's Republic of China. Any disputes arising from or related to this Agreement shall be submitted to the People's Court of Haidian District, Beijing for adjudication.
+13.3 The effectiveness, interpretation, modification, execution, and dispute resolution of this Agreement are governed by the laws of the People's Republic of China. Any disputes arising from or related to this Agreement shall be submitted to the People's Court of Haidian District, Beijing for adjudication.

en/developer/go-sdk.mdx

@@ -1,5 +1,5 @@
 ---
-title: Go SDK
+title: Flashduty Go SDK
 sidebarTitle: Go SDK
 description: "go-flashduty is the official open-source Go SDK for Flashduty — a typed, strictly 1:1 wrapper over the Open API currently covering all 288 API operations across 32 services."
 keywords: ["Go SDK", "go-flashduty", "Open API", "Golang", "client"]

en/monitors/faq/faq.mdx

@@ -1,5 +1,6 @@
 ---
-title: "FAQ"
+title: "Flashduty Monitors FAQ"
+sidebarTitle: "FAQ"
 description: "Monitors frequently asked questions"
 ---
 

en/monitors/quickstart/quickstart.mdx

@@ -1,5 +1,6 @@
 ---
-title: "Getting Started"
+title: "Flashduty Monitors Getting Started"
+sidebarTitle: "Getting Started"
 description: "Monitors quick start guide to help you get started with alerting"
 ---
 

en/on-call/channel/escalation-rule.mdx

@@ -75,7 +75,7 @@ Determines how users are reached.
     - **Group Bots**: Supports Feishu/Lark, Dingtalk, WeCom, Telegram, Zoom, and other Webhook bots. Telegram requires configuring a Webhook notification address and Chat IDs, Zoom requires configuring a Webhook address and Verify Token, and supports enabling @ mention functionality. See [Notification Channel Configuration](/en/on-call/configuration/notifications)
 
     <Note>
-    **Don't use any of the above IM platforms?** You can select any bot type and set the webhook URL to your own server endpoint (the system does not validate domains), then implement the corresponding message protocol on your server. See [FAQ](/en/on-call/quickstart/faq#i-dont-use-feishudingtalkwecomtelegram--how-can-i-receive-bot-notifications).
+    **Don't use any of the above IM platforms?** You can select any bot type and set the webhook URL to your own server endpoint (the system does not validate domains), then implement the corresponding message protocol on your server. See [FAQ](/en/on-call/quickstart/faq#custom-bot-notifications).
     </Note>
   </Tab>
 </Tabs>