Executive Summary
Summary
Over Apr 9–15 2026, docs.wal.app received 11,795 visitors and 18,625 pageviews with an 82% bounce rate, signaling high lookup-intent traffic. Kapa logged 67 conversations across 7 distinct themes, with blob lifecycle, access/indexing, and mainnet setup as the top pain points.
Traffic Overview
Over the 7-day period (Apr 9–15, 2026), docs.wal.app attracted 11,795 visitors and 18,625 pageviews with a high bounce rate of 82% and a short average visit duration of 38 seconds. Traffic grew steadily through the week, peaking on Apr 15 with 2,142 visitors. The vast majority of traffic (94%) arrived directly, with Google and internal self-referrals being the next largest sources. Content interest centers heavily on the homepage and Walrus Sites introduction pages.
Weekly traffic acceleration
Daily visitors grew from 1,222 on Apr 10 (weekend low) to 2,142 on Apr 15, a 75% increase across the week. Weekday traffic (Mon–Fri) consistently outpaces weekends, peaking mid-to-late week.
Engagement degradation vs. 30-day baseline
The 7-day bounce rate (82%) is notably worse than the 30-day rate (67%), and views/visit dropped from 1.62 to 1.36, suggesting the recent cohort of visitors is less engaged or exploring less content.
Walrus Sites content dominates interest
The /walrus-sites/intro pages (with and without .html extension) together rival the homepage in traffic and show near-perfect scroll depth (100%), making Walrus Sites the clearest area of user interest.
AI-driven referrals emerging
ChatGPT is sending a small but highly engaged audience (161s avg duration) to the docs. This channel is worth monitoring as AI assistants increasingly cite technical documentation.
Top 20 Pages
| # | Page | Insight |
|---|---|---|
| 1 | / | By far the most visited page with 6,683 visitors and 8,674 pageviews. Low time-on-page (10s) and 46% scroll depth suggest it primarily serves as a navigation hub. |
| 2 | /walrus-sites/intro (+ .html variant) | Combined ~4,200 visitors and ~6,080 pageviews — the most-read content page. High scroll depth (100%) indicates strong reader engagement with Walrus Sites intro content. |
| 3 | /docs/getting-started | 1,191 visitors with 33% scroll depth and short time (15s), suggesting users skim it quickly; may benefit from clearer quick-start guidance. |
| 4 | /docs/sites/introduction/components | 358 visitors with 43% scroll depth and 20s avg time. Solid secondary interest in Walrus Sites component details after the intro. |
| 5 | /docs/operator-guide/storage-nodes/commission-governance | High bounce rate (78%) but 77% scroll depth among 107 visitors — those who stay read thoroughly; niche but dedicated audience of node operators. |
Referral Sources
| Source | Type | Insight |
|---|---|---|
| Direct / None | Organic | Dominates with 11,181 visitors (94.8% of total). High bounce rate (83%) and short duration (36s) suggest many are bookmarked or linked users with specific lookup intent. |
| docs.wal.app (self-referral) | Organic | 339 visitors coming from internal pages, indicating some multi-page navigation is occurring within the docs site itself. |
| Organic | 203 visitors with a relatively low bounce rate (77%) and longer duration (53s) — organic search users are more engaged than average. | |
| wal.app | Organic | 38 visitors referred from the main Walrus app, with a 102s average duration — the highest engagement of any source, suggesting motivated users following docs links from the product. |
| chatgpt.com | AI / Chatbot | 10 visitors referred from ChatGPT, indicating AI assistants are beginning to surface Walrus docs as a reference. Visit duration (161s) is very high, suggesting these users read deeply. |
| docs.sui.io | Organic | Only 2 visitors but 1,049s average duration — extremely high engagement. Sui ecosystem cross-referrals are rare but result in very invested readers. |
chatgpt.com
10 visitors with 161s average session duration — the highest engagement of any referral source, suggesting ChatGPT users arrive with specific technical questions and read deeply.
Top Referrer URLs
Exact referring URL or domain and the number of visits driven from each. Direct (no referrer) is excluded.
Page ↔ Kapa Theme Correlations
High-traffic pages mapped to the Kapa themes they correspond to.
| Page | Related Kapa Theme | Insight |
|---|---|---|
| /walrus-sites/intro | Walrus Sites Deployment and Architecture | High scroll depth (100%) shows strong intent but SDK vs CLI confusion persists in Kapa. |
| /docs/getting-started | Mainnet Setup, CLI Configuration, and Tooling | 33% scroll depth suggests users bail early, matching Kapa's mainnet setup friction signals. |
| / | Blob Access, Retrieval, and Indexing | 10s time-on-page indicates users can't find blob ID guidance quickly from the homepage. |
| /docs/sites/introduction/components | Walrus Sites Deployment and Architecture | Secondary Walrus Sites traffic confirms developer interest beyond the intro page. |
| /docs/operator-guide/storage-nodes/commission-governance | Epoch Duration and Timing | Dedicated node-operator readers align with epoch timing questions seen in Kapa. |
Notable Takeaways
Blob access confusion is the single largest Kapa pain point
17 Kapa conversations on blob access and indexing — the highest evidence count of any themeBlob ID vs Sui object ID ambiguity is generating more support load than any other topic, yet no dedicated explainer page exists.
ChatGPT referrals dwarf all other chatbot channels but remain tiny
10 ChatGPT-referred visitors averaging 161 seconds — 4x the site average of 38 secondsAI-referred users are the most deeply engaged cohort, signaling that improving doc quality will compound as AI citation grows.
Weekly bounce rate is 15 points worse than the 30-day baseline
82% bounce rate (7d) vs 67% bounce rate (30d)Recent visitor cohorts are materially less engaged, possibly from new traffic sources that haven't found the right content.
Walrus Sites intro rivals the homepage in raw traffic
~6,080 pageviews for /walrus-sites/intro vs 8,674 for the homepageWalrus Sites is the dominant content interest yet deployment architecture questions still rank 6th in Kapa volume.
Developer Pain Point Themes
This week's 67 Walrus Q&A conversations reveal recurring friction around blob lifecycle management, indexing limitations, and mainnet setup. Token operations, CLI tooling, and epoch concepts also generated significant confusion across users.
Blob Access, Retrieval, and Indexing
Blob vs object ID confusion creates direct blockers for developers trying to retrieve stored data.
Blob Lifecycle Management (Storage, Expiry, Extension, Deletion)
Missing end-to-end lifecycle guidance forces repeated support escalations across store, extend, and burn workflows.
Mainnet Setup, CLI Configuration, and Tooling
First-time mainnet friction prevents developers from completing even basic setup without external help.
Epoch Duration and Timing
Epoch confusion leads to miscalculated storage renewals and unexpected blob expiry in production.
Walrus Sites Deployment and Architecture
TypeScript SDK vs site-builder CLI boundary confusion stalls Walrus Sites deployments early.
Token Management and Coin Operations (WAL/SUI)
Token operation gaps block users from funding storage or completing WAL/SUI exchanges independently.
Recommended Actions
Publish a Blob ID vs Sui Object ID explainer with indexing limitations
Add a dedicated reference page clarifying blob IDs, object IDs, and enumeration constraints.
17 Kapa conversations make this the highest-volume unaddressed topic this week.
Create an end-to-end blob lifecycle guide
Single page covering store, extend, expire, burn, and re-upload with code examples.
15 Kapa conversations span every lifecycle stage, indicating no unified reference exists.
Build a mainnet quickstart with version compatibility table and CLI troubleshooting
Rewrite or replace /docs/getting-started with a mainnet-first flow and version matrix.
33% scroll depth and 14 Kapa conversations confirm users abandon setup guidance early.
Add an epoch reference card for Testnet and Mainnet
Inline reference card on epoch page listing durations, end-time queries, and Sui vs Walrus differences.
7 Kapa conversations repeat the same epoch timing questions that a reference card would resolve instantly.
Document blob SDK vs site-builder CLI integration boundary
Add an architecture diagram and integration guide to the Walrus Sites section.
High Walrus Sites traffic (6,080 pageviews) paired with deployment confusion creates outsized doc debt.
Improve CLI error messages for mainnet configuration and key import failures
Add actionable error text to CLI paths covering config file location, version mismatch, and key import steps.
14 Kapa conversations cite CLI setup friction that better diagnostics would resolve at the tool layer.
Build a homepage navigation improvement with quick-links to top-question pages
Add prominent quick-link cards on the homepage for blob lifecycle, mainnet setup, and epoch reference.
82% weekly bounce rate and 10s homepage time-on-page indicate users fail to find content quickly.