From 02d410250f307d644490d06e522027dfa58acc4a Mon Sep 17 00:00:00 2001 From: Shawn Muggle Date: Sun, 25 Oct 2026 07:13:59 +0800 Subject: [PATCH] chore(seo): drop ineffective rss.xml redirects and document Search Console 404 triage GitBook does not apply redirects to */rss.xml paths: both entries still returned 404 in production on 2026-10-25. Record why templated API paths, rss.xml and stale /_next/static/css assets stay 404 (code spans already render as , no page exposes an RSS feed, assets are old build hashes). Co-Authored-By: Claude Opus 5.5 --- .gitbook.yaml | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/.gitbook.yaml b/.gitbook.yaml index 24d6e16..0cb7301 100644 --- a/.gitbook.yaml +++ b/.gitbook.yaml @@ -16,6 +16,15 @@ ## /blogs, /products-1, /integration/api-doc/api-for-advanced-used, /blog/en ## Templated API paths such as /payments/{paymentId} are not pages; Google ## extracts them from the GitBook/Apidog hydration JSON. Leave them as 404. +## Verified 2026-10-25: every occurrence in the Markdown sources is inside a +## code span, code fence or table code cell, and production renders them as +## , never as . There is nothing to unlink in the source. +## */rss.xml URLs: GitBook serves per-page RSS only for pages with an Updates +## block; this site has none, and no page links an RSS feed. GitBook does not +## apply redirects to rss.xml paths (the two rss.xml entries that used to be +## here still returned 404 on 2026-10-25), so they were removed. Leave as 404. +## /_next/static/css/*: stale hashed build assets from earlier GitBook +## deploys. Leave as 404; never redirect them to a page. redirects: # group 1: unpublished directories @@ -46,6 +55,4 @@ redirects: # group 3: legacy URLs still crawled (2026-10-12 Search Console 404 report) integration/deposit-api: integration/api-doc/deposit-api.md start/intent-based-earn: products/intent-based-bridge/README.md - start/intent-based-earn/rss.xml: products/intent-based-bridge/README.md - start/supported-tokens-and-chains/rss.xml: integration/api-doc/supported-tokens-and-chains.md blog/en/faq: contact/faqs.md