Weekly Docs Report

docs.wal.app Analytics

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

Executive Summary

Kapa Conversations
64
Themes Identified
7
Visitors (7d)
11,795
The 7-day visitor count represents roughly 41% of the 30-day total (59,735), suggesting traffic has accelerated or surged recently compared to the prior weeks.
Pageviews (7d)
18,625
At 1.36 views per visit on average, most sessions are single-page. The 30-day average of 1.62 suggests deeper engagement over a longer window, indicating some returning users explore more.
Bounce Rate (7d)
82%
Notably higher than the 30-day rate of 67%, indicating recent traffic may be less engaged or more targeted — possibly from link shares or AI referrals sending users to specific pages.
Avg Visit Duration (7d)
38 seconds
Very short session duration consistent with documentation lookup behavior — users likely come with a specific question and leave once answered.
Views per Visit (30d)
1.62
Slightly better engagement over 30 days vs 7 days (1.36), suggesting that regular or returning users browse more pages per session.

Summary

docs.wal.app recorded 11,795 unique visitors and 18,625 pageviews from Apr 9–15, with traffic accelerating 75% over the week. Analysis of 64 Kapa Q&A conversations reveals 7 distinct themes, dominated by mainnet onboarding friction, blob lifecycle confusion, and global blob enumeration gaps. Immediate documentation priorities center on mainnet onboarding, blob lifecycle consolidation, and RPC pruning warnings.

Priority 1

Create a dedicated mainnet onboarding guide covering CLI setup, publisher requirements, and all write methods.

Priority 2

Publish a consolidated blob lifecycle reference covering store, extend, expire, burn, and re-upload.

Priority 3

Document global blob enumeration limitations and add RPC pruning warnings with alternative provider options.

Priority 4

Add an explicit explainer distinguishing Blob ID from Sui Object ID with bidirectional lookup examples.

Traffic Overview

docs.wal.app saw 11,795 unique visitors and 18,625 pageviews over the last 7 days (Apr 9–15). Traffic grew steadily through the week, peaking on Apr 15 with 2,142 visitors. The vast majority of traffic arrives directly, with a high bounce rate of 82% suggesting many users land, find what they need quickly, and leave. Engagement metrics are modest but consistent.

Accelerating daily traffic through the week

Daily visitors grew from 1,222 on Apr 10 (lowest point) to 2,142 on Apr 15 (highest), a 75% increase over 5 days. This consistent upward trend may reflect a product announcement, community push, or content being shared.

Bounce rate improving over longer windows

Bounce rate drops from 82% (7d) to 78% (14d) to 67% (30d), suggesting older traffic cohorts are more engaged. Recent spikes may be bringing in lower-quality or more casual traffic.

Walrus Sites content is a breakout interest area

The /walrus-sites/intro pages collectively rank #2 in pageviews with 100% scroll depth — indicating strong, sustained reader interest in the Sites feature beyond just the getting-started flow.

AI agent referrals emerging with high quality

ChatGPT referrals, while small in volume (10 visitors), show the highest engagement duration (161s) and low bounce rate (40%), suggesting AI-referred users arrive with context and intent — a trend worth monitoring as AI web agents grow.

Top 20 Pages

# Page Insight
1 / Homepage dominates with 6,683 visitors and 8,674 pageviews. Low bounce rate of 10% and 46% scroll depth suggest it serves as a strong navigation hub.
2 /walrus-sites/intro (and .html variant) Combined ~4,214 visitors and ~6,084 pageviews, making Walrus Sites intro the most-read content page. 100% scroll depth indicates users read it fully — high interest in the Sites feature.
3 /docs/getting-started 1,191 visitors with a low 15% bounce rate and strong 33% scroll depth — a key onboarding page with solid engagement.
4 /docs/sites/introduction/components 358 visitors with 20% bounce rate and 43% scroll depth, showing solid engagement with the technical components of Walrus Sites.
5 /docs/operator-guide/storage-nodes/commission-governance 107 visitors but a high 78% bounce rate and 77% scroll depth — users who land here are likely operators with a specific governance question; they read deeply but don't explore further.

Referral Sources

Source Type Insight
Direct / None Organic Overwhelmingly dominant at 11,181 visitors (95% of all traffic). High bounce rate (83%) and short duration (36s) suggest users arrive via bookmarks, direct links, or dark social sharing.
docs.wal.app Organic 339 self-referrals likely from internal navigation or redirects between doc versions. Lower bounce rate (47%) and longer duration (60s) indicate more engaged browsing sessions.
Google Organic 203 visitors with a notably low 77% bounce rate and 53s duration — organic search users are among the more engaged cohorts, suggesting good SEO relevance.
chatgpt.com AI / Chatbot 10 visitors referred from ChatGPT with 40% bounce rate and 161s average duration — the longest engagement of any referral source. AI-referred users explore deeply, likely following up on AI-generated answers.
docs.sui.io Organic Only 2 visitors but an extraordinary 1,049s average duration (17+ minutes) — highly engaged cross-ecosystem readers likely researching Walrus in the context of Sui development.
walrus.site Organic 12 visitors with 528s average duration and 0% bounce rate — small but extremely engaged segment, likely developers using Walrus Sites who follow links from live sites.
Twitter Organic 8 visitors with 100% bounce rate and 0s duration — social media traffic is completely unengaged, likely accidental clicks or link previews.

chatgpt.com

10 visitors with 161s avg duration and 40% bounce rate — AI-referred users arrive with context and explore deeply.

Page ↔ Kapa Theme Correlations

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

Page Related Kapa Theme Insight
/ Mainnet Onboarding (CLI setup, publisher requirements, write methods) Homepage is the primary entry point for new users hitting mainnet onboarding confusion.
/walrus-sites/intro Blob Storage & Lifecycle (store, extend, expire, delete) High scroll depth on Sites intro correlates with lifecycle questions about blobs backing site deployments.
/docs/getting-started Mainnet Onboarding (CLI setup, publisher requirements, write methods) Low bounce rate suggests users linger here struggling with CLI and key setup steps.
/docs/sites/introduction/components Quilt Batch Storage Feature Components page engagement aligns with quilt mechanics questions about multi-blob site storage.
/docs/operator-guide/storage-nodes/commission-governance Storage Node Setup and Expected Errors High bounce with deep scroll matches operators landing here for specific commission command answers.

Notable Takeaways

Mainnet onboarding is the single largest friction point

15 of 64 Kapa conversations (23%) focused on mainnet CLI setup, publisher requirements, and write methods.

No dedicated mainnet onboarding guide exists, forcing users to piece together information from multiple pages.

Action → Create a single mainnet onboarding guide consolidating CLI init, key import, publisher requirements, and write methods.

Global blob enumeration gap is causing repeated support load

11 of 64 Kapa conversations cited inability to list certified blobs and silent failures from RPC event pruning.

The absence of documented workarounds and archive node requirements is causing repeated developer confusion.

Action → Add a pruning warning and archive node guidance to the blob enumeration section of the docs.

Blob lifecycle questions represent a consolidated documentation gap

12 of 64 Kapa conversations asked about store, extend, expire, burn, or re-upload steps across separate pages.

Users cannot find a single authoritative lifecycle reference, leading to repeated fragmented questions.

Action → Consolidate all blob lifecycle steps into one reference page with a visual lifecycle diagram.

ChatGPT referrals show highest engagement quality despite low volume

10 ChatGPT-referred visitors averaged 161 seconds on-site with a 40% bounce rate, the best of any referral source.

AI-referred users arrive with specific intent and explore more deeply, signaling a growing high-value traffic segment.

Action → Ensure key docs pages have structured, scannable content optimized for AI citation and deep linking.

Blob ID vs Sui Object ID confusion causes retrieval errors

8 of 64 Kapa conversations involved users conflating Sui object IDs with Walrus blob IDs during retrieval.

No single page explicitly differentiates the two ID types with lookup examples, causing repeated errors.

Action → Add a dedicated explainer with bidirectional lookup code examples to the blob reference documentation.

Developer Pain Point Themes

This week's 64 Walrus Q&A conversations reveal strong user confusion around blob/object ID distinctions, quilt mechanics, epoch timing, and mainnet onboarding. Node operators and indexer builders also repeatedly hit documentation gaps around expected errors and global blob enumeration.

#1 15 conversations high priority

Mainnet Onboarding (CLI setup, publisher requirements, write methods)

It is the top Kapa theme and directly blocks developers from successfully using Walrus on mainnet.

Action → Create a dedicated mainnet onboarding guide covering CLI, keys, publishers, and write methods.
#2 12 conversations high priority

Blob Storage & Lifecycle (store, extend, expire, delete)

Fragmented lifecycle docs force users to ask repeated questions across multiple conversation threads.

Action → Publish one consolidated lifecycle reference page with all stages and re-upload guidance.
#3 11 conversations high priority

Global Blob Enumeration and Sui RPC Event Pruning

Silent RPC pruning failures are blocking indexer builders with no documented mitigation path.

Action → Document archive node requirement and add a pruning warning with alternative RPC provider examples.
#4 8 conversations medium priority

Blob ID & Sui Object ID Distinction

ID conflation causes retrieval errors and erodes developer trust in the storage model.

Action → Add a clear explainer with bidirectional lookup examples to the blob reference page.
#5 7 conversations medium priority

Quilt Batch Storage Feature

Missing consolidated Quilt docs leave users unsure of size limits and correct API usage.

Action → Create a dedicated Quilt FAQ with size limits, per-blob constraints, and API code examples.
#6 6 conversations medium priority

Storage Node Setup and Expected Errors

Undocumented 403 metrics errors and commission commands cause unnecessary operator anxiety during setup.

Action → Add an 'Expected Errors' callout section to the storage node setup page.
#7 5 conversations low priority

Epoch Timing and Duration

Epoch confusion leads to incorrect storage cost estimates and missed expiry deadlines.

Action → Add an epoch reference table with current durations and a link to a live status page.

Recommended Actions

high Documentation

Create a dedicated mainnet onboarding guide

New standalone page covering CLI init, key import, publisher requirements, and all write methods.

15 conversations this week confirm it is the top friction point blocking new mainnet users.

↑ Reduces repeat mainnet onboarding questions and shortens time-to-first-successful-write for new users.
high Documentation

Publish a consolidated blob lifecycle reference page

Single page covering store, extend, expire, burn, and re-upload with a lifecycle diagram.

12 conversations this week asked about disconnected lifecycle steps across multiple pages.

↑ Eliminates the most common category of fragmented lifecycle questions in Kapa.
high Documentation

Document global blob enumeration and RPC pruning limitations

Add archive node requirement, pruning warning, and alternative RPC provider list to enumeration docs.

11 conversations reveal indexer builders are silently failing with no documented workaround.

↑ Unblocks indexer and analytics builders and reduces high-effort support conversations.
medium Documentation

Add Blob ID vs Sui Object ID explainer with lookup examples

New explainer section on the blob reference page with bidirectional lookup code examples.

8 conversations this week show ID conflation is causing repeated retrieval errors.

↑ Reduces ID-confusion support load and prevents a common class of developer retrieval errors.
medium Documentation

Create a dedicated Quilt FAQ page

New FAQ page covering size limits, per-blob constraints, API usage, and comparison to standard blobs.

7 conversations this week asked about Quilt mechanics with no single reference to point to.

↑ Provides a canonical reference for Quilt users and reduces repetitive API usage questions.
low Documentation

Add epoch reference table with live status link

Epoch duration table distinguishing Walrus vs Sui epochs, with a link to a live epoch status page.

5 conversations this week asked about epoch timing, end dates, and cross-chain distinctions.

↑ Reduces epoch-timing confusion and helps users calculate storage costs and expiry dates accurately.
medium Developer Experience

Add Expected Errors section to storage node setup page

Highlighted callout block on the storage node setup page covering 403 metrics error and commission commands.

6 operator conversations this week were caused by undocumented but normal setup errors.

↑ Reduces operator anxiety during setup and decreases node-setup support volume.
medium Developer Experience

Optimize high-traffic pages for AI citation and deep linking

Audit homepage, getting-started, and Walrus Sites intro pages for structured, scannable headings and anchors.

ChatGPT referrals show 161s avg session duration, signaling a growing AI-referred high-intent audience.

↑ Improves discoverability via AI agents and increases engagement quality for AI-referred users.