2026-04-09 to 2026-04-15 · run 20260416T144633Z
docs.sui.io received 5,051 unique visitors and 15,408 pageviews for Apr 9–15, 2026, with moderate engagement (64% bounce rate, 184s avg session). Across 105 Kapa conversations, 7 distinct themes emerged, dominated by GraphQL/gRPC migration challenges, transaction fetching bugs, and Move basics. The getting-started funnel and API reference pages drive the bulk of traffic, aligning closely with top developer pain points.
Evidence: 19 of 105 Kapa conversations (18%) focused on GraphQL/gRPC migration, the single largest theme.
Interpretation: Deprecated JSON-RPC endpoints and missing migration examples are creating significant friction for developers upgrading their integrations.
Action: Publish a JSON-RPC-to-GraphQL/gRPC mapping guide with working code samples as the top documentation priority.
Evidence: 181 visitors landed on /guides/developer/transactions/ptbs/prog-txn-blocks with a 66% bounce rate and only 29 scroll depth.
Interpretation: Content or structure on the PTB page is failing to retain readers, wasting high-intent inbound traffic.
Action: Audit and restructure the PTB page with clearer examples and improved content hierarchy to reduce bounce rate.
Evidence: 14 Kapa conversations involved gas extraction, balance calculation, or in/out direction logic errors in transaction history tools.
Interpretation: Absence of an official reference implementation forces developers to build buggy custom solutions independently.
Action: Publish an official TypeScript/Python transaction-fetching reference covering gas, balance tracking, and direction detection.
Evidence: ChatGPT sent 48 visitors (72% bounce, 112s session); Claude sent 8 visitors (50% bounce, 395s session).
Interpretation: AI-referred traffic is emerging but ChatGPT users show low engagement, suggesting docs may not satisfy AI-driven query intent.
Action: Ensure high-traffic pages have clear, scannable answers to common questions to better serve AI-referred visitors.
Evidence: 9 Kapa conversations covered Move fundamentals and publish errors; hello-world page has a 44% bounce rate with 229 visitors.
Interpretation: New developers lack a consolidated Move reference, causing repeated questions and onboarding dropoff.
Action: Create a beginner Move reference consolidating primitives, object model basics, and a publish-error troubleshooting section.
Why it matters: This is the highest-volume theme, blocking developers migrating off deprecated JSON-RPC endpoints.
Recommended doc action: Publish a JSON-RPC-to-GraphQL/gRPC method-mapping guide with complete, runnable code samples.
Why it matters: Developers building transaction history tools are producing buggy implementations due to missing official patterns.
Recommended doc action: Publish an official Python/TypeScript transaction-fetching reference with gas, balance, and direction examples.
Why it matters: New developer onboarding is undermined by scattered Move fundamentals and undocumented publish errors.
Recommended doc action: Create a consolidated beginner Move reference page including a publish troubleshooting section.
Why it matters: Active PAS exploration combined with address normalization confusion signals an emerging documentation gap.
Recommended doc action: Publish a PAS getting-started guide and clarify normalizeStructTag vs normalizeSuiAddress in SDK reference docs.
Why it matters: Auth flow errors in Seal and zkLogin are blocking developers with no troubleshooting path available in docs.
Recommended doc action: Add troubleshooting sections to Seal and zkLogin docs covering session keys, signPersonalMessage, and JWK rotation.
Why it matters: BalanceManager setup confusion is a recurring blocker for DeFi developers integrating DeepBook V3.
Recommended doc action: Create a step-by-step DeepBook V3 quickstart covering BalanceManager creation, funding, and order placement.
Why it matters: Incorrect cursor usage causes silent data errors in developer applications relying on paginated queries.
Recommended doc action: Add a dedicated pagination guide showing correct endCursor/after usage with concrete GraphQL query examples.
Scope: Create a method-mapping reference with runnable GraphQL and gRPC code samples for all major JSON-RPC endpoints.
Why now: 19 Kapa conversations this week confirm this is the single largest active developer blocker.
Expected impact: Reduces repeat migration questions and unblocks developers upgrading from deprecated JSON-RPC endpoints.
Scope: Produce a Python/TypeScript reference covering gas extraction, balance calculation, and in/out direction detection.
Why now: 14 Kapa conversations this week show developers building buggy custom implementations without official guidance.
Expected impact: Eliminates a class of compounding transaction-history bugs across the developer community.
Scope: Audit /guides/developer/transactions/ptbs/prog-txn-blocks for content gaps and restructure with clearer examples.
Why now: 66% bounce rate and 29 scroll depth on 181 weekly visitors signals urgent content failure.
Expected impact: Retains more high-intent developers and reduces transaction-related Kapa questions.
Scope: Write a single-page Move fundamentals reference covering primitives, object model, and common publish errors.
Why now: 9 Kapa conversations and onboarding funnel dropoff at hello-world confirm a persistent beginner documentation gap.
Expected impact: Reduces repetitive Move basics questions and improves onboarding completion rates.
Scope: Write a dedicated pagination guide showing correct pageInfo.endCursor usage for Sui GraphQL queries.
Why now: 4 Kapa conversations show developers misusing transaction digests as cursors, causing silent data errors.
Expected impact: Prevents a common class of incorrect pagination implementations in developer applications.
Scope: Produce a step-by-step guide covering BalanceManager creation, funding, payWithDeep, and limit order placement.
Why now: deepbook.tech refers 89 highly engaged visitors and 4 Kapa conversations confirm setup confusion persists.
Expected impact: Reduces DeepBook integration friction and supports the active DeFi developer segment.
Scope: Add troubleshooting content to Seal and zkLogin docs covering 403 errors, session keys, and JWK rotation.
Why now: 5 Kapa conversations show developers hitting auth blockers with no in-docs resolution path.
Expected impact: Reduces escalated auth-related questions and unblocks developers integrating Seal and zkLogin.
Scope: Write a PAS introduction guide and clarify normalizeStructTag vs normalizeSuiAddress in SDK reference documentation.
Why now: 8 Kapa conversations show active PAS exploration paired with address normalization confusion causing integration errors.
Expected impact: Supports emerging PAS adopters and eliminates a recurring SDK formatting confusion point.
Plausible and Kapa raw JSON were fetched and analyzed automatically before this report was rendered.