Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.0xarchive.io/llms.txt

Use this file to discover all available pages before exploring further.

Docs GSC Root Fix Plan - 2026-06-01

Local Checkout

  • Repo: mintlify-docs
  • Local checkout: /Users/mitch/Documents/0xArchive/output/repo-worktrees/gsc-root-fix-plans-20260601/docs
  • Branch: codex/gsc-root-fix-plan-20260601-docs
  • Base: origin/main at dec3974
  • Source evidence: /Users/mitch/Documents/0xArchive/docs/ops/gsc-docs-main-site-defect-ledger-2026-06-01.md

Objective

Fix docs-side public-surface maturity issues behind GSC non-indexing, redirect-error, and crawlable route-template defects. The repair is content quality, crawl safety, redirect coverage, and canonical graph cleanup; GSC validation happens afterward.

Non-Goals

  • Do not bulk-request GSC indexing before representative pages are worth indexing.
  • Do not add redirect variants without removing the crawl source when the source is under our control.
  • Do not hide weak pages in navigation while still submitting them as strong public inventory.

Current Source Trace

  • docs.json owns navigation and redirect rules.
  • scripts/check-search-console-readiness.mjs already encodes several GSC-observed legacy redirects.
  • scripts/check-redirects.mjs validates redirect coverage.
  • recommendations/best-market-data-api.mdx is a representative non-indexed recommendation page.
  • data.mdx, schemas.mdx, generated schema pages, and operation pages expose route-template strings such as /openinterest/{symbol}.
  • sitemap.md, llms.txt, and llms-full.txt expose public discovery maps.

Workstream 1 - Recommendation Page Quality Decisions

Needed work:
  1. Audit non-indexed recommendation pages starting with recommendations/best-market-data-api.mdx.
  2. Decide per page: keep and upgrade, merge into a stronger hub, or noindex/remove from prominent discovery until upgraded.
  3. For kept pages, add evidence-rich substance: direct 0xArchive capability evidence, clear buyer-intent answer, comparison criteria, examples, and links from /recommendations, /comparisons, /rest-api, sitemap.md, and llms.txt.
  4. Avoid generated-feeling breadth. A page should earn indexation through a specific use case and named evidence.
Acceptance:
  • npm run check:recommendation-readiness
  • npm run check:ia
  • Representative kept recommendation page has unique evidence and clear internal links.
  • Pages that do not earn indexation are not submitted as important public inventory.

Workstream 2 - Docs Crawl-Safety Pass

Needed work:
  1. Distinguish route templates shown as code from actual markdown links.
  2. Remove or de-link legacy bare templates that can become crawlable paths, especially /openinterest/{symbol}.
  3. Link readers to concrete operation pages such as /schemas/operations/get-open-interest, /schemas/operations/get-hyperliquid-open-interest, or /schemas/operations/get-lighter-open-interest.
  4. Add a validator that fails when known legacy templates appear as markdown links or generated related-links URLs.
Acceptance:
  • Route examples remain visible as code where useful.
  • No crawlable internal link points to /openinterest/{symbol} or encoded variants.
  • Validator covers at least /openinterest/{symbol} and future known GSC-observed template leaks.

Workstream 3 - Redirect Backstops

Needed work:
  1. Keep existing legacy redirects for /docs/compare/tardis and related comparison variants.
  2. Add encoded redirect aliases for GSC-observed encoded template URLs only if Mintlify supports them:
    • /openinterest/%7Bsymbol%7D
    • /openinterest/%7Bsymbol%7D.md
  3. Update both docs.json and validators together.
  4. Do not treat redirects as the primary fix when the crawl source is still under our control.
Acceptance:
  • npm run check:redirects
  • npm run check:search-console-readiness
  • GSC live URL Inspection succeeds for the encoded URL before validation is clicked.

Workstream 4 - Main-Domain Docs Referrer Cleanup

Needed work:
  1. Confirm docs pages do not link back to https://www.0xarchive.io/docs/*.
  2. Coordinate with CMS and frontend plans so docs-domain pages receive internal authority directly instead of through main-domain compatibility redirects.
  3. Keep docs discovery maps on docs-domain URLs.
Acceptance:
  • rg "www\\.0xarchive\\.io/docs|https://0xarchive\\.io/docs|/docs/rest-api" *.mdx **/*.mdx llms.txt llms-full.txt sitemap.md docs.json has only intentional redirect-source or historical-validator matches.
  • GSC referrers for sampled docs pages stop showing fresh main-domain docs sources after frontend/CMS deploys.

Workstream 5 - Post-Deploy GSC Evidence

Needed work:
  1. Inspect one upgraded recommendation page.
  2. Inspect one legacy comparison redirect.
  3. Inspect /openinterest/%7Bsymbol%7D.
  4. Request indexing or validate fix only after live inspection confirms the docs-domain URL and fetch state.
Acceptance:
  • Representative upgraded docs page is fetchable and canonical to docs domain.
  • Legacy redirect paths live-inspect cleanly.
  • GSC validation is started only after representative live checks pass.

Sequencing

  1. Recommendation keep/merge/noindex decisions.
  2. Crawl-safety pass and validator.
  3. Redirect backstop variants where supported.
  4. Docs discovery map updates.
  5. Frontend/CMS canonical cleanup lands.
  6. Deploy docs.
  7. GSC live inspection and validation.

Verification Bundle

  • npm run check:recommendation-readiness
  • npm run check:ia
  • npm run check:redirects
  • npm run check:search-console-readiness
  • npm run validate
  • npm run broken-links
  • Post-deploy: npm run verify:post-deploy or the narrow live checks named above when full post-deploy verification is too expensive.
Last modified on June 1, 2026