fix(seo): redirect orphaned paths and stop linking through redirects

[shawnmuggle]

Fixes the Google Search Console findings for docs.rozo.ai: "Not found (404)" and "Page with redirect".

Root cause

This repo contains directories that appear in zero lines of SUMMARY.md. GitBook publishes only what SUMMARY.md lists, so these files sit in git while returning 404 to crawlers that discovered them through old or external links.

There was also no redirects config in the repo at all — no .gitbook.yaml, netlify.toml or vercel.json — which is precisely why no custom redirect was in effect.

Changes

1. New .gitbook.yaml with five redirects. Every destination was verified to return 200:

404 path	→ destination
/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

Deliberately left as 404, because no meaningful destination exists:

• /blogs — unpublished drafts (en/es/zh)
• /products-1 — a "Coming soon" stub
• /integration/api-doc/api-for-advanced-used — a parent path that never had a page

2. Two internal links fixed in products/intent-based-bridge/intent-based-bridge.md, both of which pointed through a redirect rather than at the canonical URL:

• https://docs.rozo.ai/api-doc → 307 → /integration/api-doc
• https://intents.rozo.ai/ → 308 → /bridge

Not changed, on purpose

All 46 sitemap URLs return 200 with index, follow and correct self-referencing canonicals. The sitemap is auto-generated by GitBook from SUMMARY.md and needs no cleanup.

The remaining "Page with redirect" entries are GitBook's own 307s for pages that were renamed or moved (/contact/contact-us/privacy-policy → /contact/privacy-policy, and similar). That GSC status is informational, not an error — the redirect target is indexed instead. GitBook does not expose a way to force 301.

⚠️ Merge note

This repo is a mirror of GitBook and the sync is bidirectional (see a5154c8 GitBook: Update content). Merging here may not be sufficient — confirm in the GitBook editor that the redirects took effect.

Post-deploy check

for u in reports reward-docs docs rozo-intentpay-techdoc testnet; do
  curl -so /dev/null -w "$u: %{http_code} -> %{redirect_url}\n" "https://docs.rozo.ai/$u"
done

# these must stay 404
for u in blogs products-1; do
  curl -so /dev/null -w "$u: %{http_code}\n" "https://docs.rozo.ai/$u"
done

curl -s https://docs.rozo.ai/sitemap.xml

🤖 Generated with Claude Code