diff --git a/.gitbook.yaml b/.gitbook.yaml new file mode 100644 index 0000000..0880565 --- /dev/null +++ b/.gitbook.yaml @@ -0,0 +1,22 @@ +## GitBook site configuration. +## +## `redirects` exists to clear the "Not found (404)" URLs Google Search Console +## reports for docs.rozo.ai. Those paths are directories that live in this repo +## but are absent from SUMMARY.md, so GitBook never publishes them — yet Google +## discovered them through old links and keeps re-crawling them. +## +## Only paths with a genuine replacement page are redirected. Every destination +## below was verified to return HTTP 200. Deliberately left as 404, because no +## meaningful destination exists: +## /blogs — unpublished drafts (en/es/zh) +## /products-1 — "Coming soon" stub +## /integration/api-doc/api-for-advanced-used — parent path, never had a page +## +## Source and destination are both site-root-relative and omit the leading slash. + +redirects: + reports: contact/contracts-and-audits + reward-docs: products/intent-based-earn + docs: contact/contact-us + rozo-intentpay-techdoc: start/litepaper/rozo-intentpay-techdoc + testnet: tests/testnet diff --git a/products/intent-based-bridge/intent-based-bridge.md b/products/intent-based-bridge/intent-based-bridge.md index 94e72f7..2ddd7b4 100644 --- a/products/intent-based-bridge/intent-based-bridge.md +++ b/products/intent-based-bridge/intent-based-bridge.md @@ -21,9 +21,9 @@ versus Traditional bridges require users to perform two separate actions: author ## **Web UI:** -{% embed url="https://intents.rozo.ai/?utm_source=docs&utm_medium=referral" %} +{% embed url="https://intents.rozo.ai/bridge?utm_source=docs&utm_medium=referral" %} -**API Integration** : [https://docs.rozo.ai/api-doc](https://docs.rozo.ai/api-doc) +**API Integration** : [https://docs.rozo.ai/integration/api-doc](https://docs.rozo.ai/integration/api-doc)

ROZO Intents