Weekly Docs Report

docs.wal.app Analytics

2026-04-09 to 2026-04-15 · Plausible + Kapa · Run 20260416T202350Z

Executive Summary

Kapa Conversations
72
Themes Identified
7
Visitors (7d)
11,795
Solid weekly traffic for a technical docs site, but bounce rate of 82% is high, suggesting many visitors land and leave quickly.
Pageviews (7d)
18,625
Averages ~1.58 pages per visit, slightly below the 30-day average of 1.62, indicating slightly shallower browsing this week.
Bounce Rate (7d)
82%
Significantly higher than the 30-day rate of 67%, suggesting recent traffic is less engaged or more direct-lookup oriented.
Avg Visit Duration (7d)
38 seconds
Very short session time; consistent with users quickly referencing specific docs rather than deep reading.
Views Per Visit (7d)
1.36
Lower than the 30-day average of 1.62, reinforcing that this week's cohort is browsing fewer pages per session.

Summary

docs.wal.app recorded 11,795 visitors and 18,625 pageviews in the week of Apr 9–15, 2026, with an 82% bounce rate indicating high intent-driven, single-page lookups. Across 72 Kapa conversations, 7 distinct themes emerged, dominated by Mainnet onboarding friction, blob ID confusion, and blob enumeration limitations.

Traffic Overview

Over the 7-day period (Apr 9–15, 2026), docs.wal.app attracted 11,795 visitors and 18,625 pageviews with an average bounce rate of 82% and a visit duration of 38 seconds. Traffic has been growing steadily through the week, peaking on Apr 15 with 2,142 visitors. Compared to the prior 7-day window (implied from 14d data: ~16,785 visitors), the recent 7 days show a notable drop, suggesting the first half of the 14-day window was heavier. The 30-day window shows stronger engagement (1.62 views/visit, 67% bounce rate), indicating recent traffic may be less engaged or more intent-driven.

Daily traffic growing through the week

Visitors increased from 1,380–1,880 on Apr 9–11 to 2,016–2,142 by Apr 14–15, a ~55% rise over the week. This upward trend suggests growing awareness or a recent content/product update driving more traffic.

Weekend dip mid-week

Apr 10–11 (Thu–Fri) saw the lowest traffic of the week (1,222 and 1,381 visitors), while Mon Apr 14 and Tue Apr 15 peaked. This weekday-heavy pattern is typical for developer/technical documentation.

Engagement improves over longer windows

Bounce rate drops from 82% (7d) to 78% (14d) to 67% (30d), and views/visit rises from 1.36 to 1.62. Recent traffic is less engaged than the broader cohort, possibly due to a spike of new or one-time visitors this week.

Walrus Sites content is the breakout topic

The /walrus-sites/intro pages (two URL variants combined) are the #2 destination by far, with 100% scroll depth — outperforming even core getting-started docs in engagement quality.

Top 20 Pages

# Page Insight
1 / Homepage leads with 6,683 visitors and 8,674 pageviews, but a very low scroll depth of 10% suggests most users pass through quickly to find specific content.
2 /walrus-sites/intro (+ .html variant) Combined ~4,214 visitors and ~6,084 pageviews — the most-read content page. 100% scroll depth on both URL variants signals high content engagement. Duplicate URLs (with and without .html) may indicate a routing/redirect issue worth fixing.
3 /docs/getting-started 1,191 visitors with 33-second avg time and 15% scroll depth; a key entry point but shallow engagement suggests users may not find what they need immediately.
4 /docs/sites/introduction/components 358 visitors with a strong 43% scroll depth and 20s on page — users are actively reading this content.
5 /docs/operator-guide/storage-nodes/commission-governance Only 107 visitors but 78% bounce rate and 77% scroll depth — niche but highly engaged audience, likely node operators.

Referral Sources

Source Type Insight
Direct / None Organic Dominates with 11,181 visitors (95% of traffic). Very low bounce rate context aside, this suggests most users bookmark or type the URL directly — typical for returning technical users.
docs.wal.app Organic 339 visitors referred from internal self-links, indicating in-doc navigation tracked as referrals. 47% bounce rate and 60s duration suggest engaged internal browsing.
Google Organic 203 visitors with a high 77% bounce rate but 53s duration — organic search users land on specific pages, read briefly, and leave.
chatgpt.com AI / Chatbot 10 visitors referred from ChatGPT with a strong 161s average visit duration and 40% bounce rate — AI-referred users are notably more engaged and spend more time reading.
docs.sui.io Organic Only 2 visitors but a remarkable 1,049s (17+ min) average visit duration, suggesting deep cross-referencing between Sui and Walrus docs.
walrus.site Organic 12 visitors with 528s average duration — extremely high engagement, likely developers actively building on Walrus Sites who need detailed reference.

chatgpt.com

10 visitors from ChatGPT averaged 161 seconds on-site with a 40% bounce rate, making them the most engaged external referral cohort by a wide margin. This suggests AI assistants are actively routing developers to Walrus docs for authoritative answers.

Top Referrer URLs

Exact referring URL or domain and the number of visits driven from each. Direct (no referrer) is excluded.

Referrer Visitors Pageviews
docs.wal.app 320 655
google.com 203 382
wal.app 38 151
walrus.xyz 19 50
walrus.site 12 72
chatgpt.com 8 18
docs.wal.app/docs/getting-started 5 9
t.co 4 4
duckduckgo.com 4 4
docs.wal.app/docs/sites/introduction/components 3 5
docs.sui.io 2 47
t.co/vRc3qvc8dk 2 2
android-app://com.slack 2 2
sui.io 2 2
github.com/MystenLabs/walrus 2 2
docs.wal.app/docs/operator-guide 2 2
android-app://com.twitter.android 2 2
docs.wal.app/docs/examples/checkpoint-data 2 13
github.com/MystenLabs/Walrus-Onboarding/blob/main/14-Use-cases/contents/02-walrus-sites.md 2 10
docs.wal.app/docs/http-api/quilt-http-apis 2 3
docs.wal.app/docs/sites/getting-started/installing-the-site-builder 1 3
docs.wal.app/docs/large-uploads 1 1
docs.wal.app/blog/01_announcing_walrus 1 2
docs.wal.app/docs/walrus-client 1 1
docs.wal.app/operator-guide/upload-relay.html 1 4

Page ↔ Kapa Theme Correlations

High-traffic pages mapped to the Kapa themes they correspond to.

Page Related Kapa Theme Insight
/docs/getting-started Mainnet Setup, CLI Configuration & Key Security Low 15% scroll depth suggests onboarding content fails to answer first-time Mainnet setup questions.
/walrus-sites/intro Storing Data and Blob IDs (CLI, HTTP, SDK) 100% scroll depth confirms high engagement aligned with frequent blob storage how-to questions.
/ Blob Access & ID Confusion (Blob ID vs Sui Object ID) 10% scroll depth on homepage suggests users pass through without finding blob ID reference content.
/docs/sites/introduction/components Quilt Feature Usage and Constraints 43% scroll depth shows active reading where Quilt constraints and comparisons are most needed.
/docs/operator-guide/storage-nodes/commission-governance Epoch Timing and Storage Costs 77% scroll depth from node operators correlates with epoch and cost calculation questions.

Notable Takeaways

ChatGPT referrals convert at 4x the engagement of organic search

ChatGPT-referred users: 161s avg duration, 40% bounce rate vs. Google-referred: 53s, 77% bounce rate

AI-referred developers arrive with a specific technical question and trust the docs to answer it, making chatbot-optimized content unusually high-leverage.

Mainnet onboarding is the single largest Kapa pain point this week

13 Kapa conversations on Mainnet setup — the highest evidence count of any theme

First-time Mainnet users are not finding key security and configuration guidance in existing docs, creating real risk of key exposure.

Walrus Sites intro drastically outperforms core Getting Started in engagement quality

/walrus-sites/intro: 100% scroll depth across ~4,214 visitors vs. /docs/getting-started: 15% scroll depth across 1,191 visitors

Developers find Walrus Sites content more actionable than the primary onboarding page, signaling a structural gap in getting-started content.

Blob enumeration is a high-frequency dead end with no documented workaround

9 Kapa conversations hit the same programmatic blob listing wall without a node

Absence of documented alternatives forces repeated support escalations for a known platform limitation.

Developer Pain Point Themes

This week's Walrus questions centered on storage fundamentals, blob/object ID confusion, and CLI/mainnet onboarding challenges across 72 conversations. Recurring pain points include epoch timing, quilt usage, and token management workflows.

#1 13 conversations high priority

Mainnet Setup, CLI Configuration & Key Security

Users accidentally share private keys in chat, posing immediate security risk to real funds.

#2 11 conversations high priority

Storing Data and Blob IDs (CLI, HTTP, SDK)

Inability to reliably retrieve blob IDs across interfaces blocks core developer workflows.

#3 10 conversations high priority

Blob Access & ID Confusion (Blob ID vs Sui Object ID)

ID confusion causes silent retrieval failures that are hard to debug without clear reference material.

#4 9 conversations medium priority

Enumerating All Global Blobs

No documented workaround forces repeated support escalations for a known platform limitation.

#5 7 conversations medium priority

Epoch Timing and Storage Costs

Unpredictable cost and timing estimates block testnet-to-mainnet migration decisions.

#6 7 conversations medium priority

Quilt Feature Usage and Constraints

Undocumented per-blob size limits cause silent failures for developers adopting Quilt.

Recommended Actions

high Documentation

Publish a Mainnet Onboarding Security Guide with Key Handling Warnings

New consolidated guide covering CLI config, private key import, and explicit key-sharing warnings.

13 Kapa conversations this week included accidental key sharing, indicating active security risk.

↑ Reduces key exposure incidents and cuts repeat Mainnet setup questions in Kapa.
high Documentation

Create a Unified 'Store Your First Blob' Quickstart with CLI, HTTP, and SDK Examples

Single page with copy-paste examples for all three storage interfaces and blob ID retrieval steps.

11 Kapa conversations span all three interfaces; no single reference page covers them together.

↑ Deflects the highest-volume Kapa theme and improves getting-started scroll depth.
high Documentation

Add a Blob ID vs. Sui Object ID Reference Guide with Lookup Examples

Dedicated reference section explaining the distinction with concrete lookup commands for each ID type.

10 conversations this week traced failures to ID confusion; no dedicated disambiguation page exists.

↑ Reduces retrieval-failure support load and improves developer confidence in blob access workflows.
medium Documentation

Document Global Blob Enumeration Limitations and Archive RPC Alternatives

New section covering why global listing is restricted and which RPC alternatives exist for known use cases.

9 Kapa conversations this week hit this wall with no documented path forward.

↑ Eliminates a recurring dead-end escalation and sets accurate developer expectations.
medium Documentation

Add Quilt vs. Standard Storage Comparison Table with Explicit Per-Blob Size Limits

Update the Quilt overview page with a feature comparison table and hard size-limit callouts.

7 Kapa conversations this week revealed Quilt constraints are entirely undiscovered until failure.

↑ Reduces silent Quilt failures and helps developers choose the right storage primitive upfront.
medium Tooling

Fix Duplicate URL Routing for /walrus-sites/intro and /walrus-sites/intro.html

Implement canonical redirect so both URL variants resolve to one canonical page.

Both URL variants appear separately in top-page analytics, splitting engagement signals and risking SEO dilution.

↑ Consolidates pageview attribution and removes routing ambiguity for the highest-engagement content page.
low Developer Experience

Build a Live Epoch Status and Cost Calculator Widget for the Docs

New interactive widget surfacing current epoch number, duration, and estimated storage cost on testnet and mainnet.

7 Kapa conversations ask epoch and cost questions that static docs cannot answer in real time.

↑ Eliminates a class of repetitive lookup questions and accelerates testnet-to-mainnet planning.