Executive Summary
Summary
docs.wal.app received 12,036 visitors and 19,569 pageviews April 10–16, 2026, with the homepage and Walrus Sites intro pages driving the majority of traffic. The Kapa chatbot handled 229 conversations across 6 identified themes, with blob storage operations and spam/off-topic queries accounting for the largest share of volume.
Traffic Overview
docs.wal.app saw 12,036 visitors and 19,569 pageviews over the past 7 days (Apr 10–16), with a steady day-over-day growth trend. Traffic is heavily direct, with modest contributions from Google, internal Walrus properties, and ChatGPT. The homepage and Walrus Sites intro pages dominate traffic. Bounce rate is high at 81%, suggesting most visitors are looking for quick answers rather than deep exploration.
Strong intra-week visitor growth
Daily visitors nearly doubled from 1,222 on Apr 10 to 2,129 on Apr 16, while bounce rate dropped from 88% to 78%. This suggests either an organic growth event (announcement, listing) or improved traffic quality toward the end of the week.
Recent 7d engagement below 30d baseline
The 7d bounce rate (81%) and views/visit (1.4) are worse than the 30d averages (68%, 1.61), indicating the prior ~3 weeks had higher-quality or more exploratory traffic — worth investigating what drove that earlier engagement.
Walrus Sites intro content is a key engagement driver
The /walrus-sites/intro pages collectively drive the second-highest traffic with near-100% scroll depth, indicating strong developer interest in Walrus Sites as a product.
AI agent referrals are small but high-value
ChatGPT sends only 12 visitors but they average 329s on site — the highest visit duration of any tracked source except walrus.site. As AI assistants increasingly surface docs, this channel may grow.
Operator content has a niche but dedicated audience
Pages under /docs/operator-guide, especially commission-governance and storage-node-setup, show disproportionately high scroll depth and time-on-page relative to visitor count, indicating a small but deeply engaged operator community.
Top 20 Pages
| # | Page | Insight |
|---|---|---|
| 1 | / | 6,964 visitors and 9,202 pageviews — by far the most visited page. Low 11% time-on-page and 46% scroll depth suggest it primarily serves as a navigation hub. |
| 2 | /walrus-sites/intro (+ .html variant) | Combined ~4,137 visitors and ~6,103 pageviews. High scroll depth (~100%) indicates strong content engagement. The duplicate .html and clean URL versions suggest legacy URL handling. |
| 3 | /docs/getting-started | 1,249 visitors with 33% scroll depth and 17% time-on-page — a key entry point for new users but moderate engagement suggests some drop-off before completion. |
| 4 | /docs/sites/introduction/components | 421 visitors with 41% scroll depth. A secondary but meaningful destination for developers exploring Walrus Sites architecture. |
| 5 | /docs/operator-guide/storage-nodes/commission-governance | 115 visitors with a notably high 76% time-on-page and 77% scroll depth — operator-focused content that attracts a smaller but highly engaged audience. |
| 6 | /walrus-sites/tutorial (+ .html variant) | Combined 46 visitors with 100% scroll depth — small audience but extremely high engagement, indicating tutorial content is highly valuable to those who find it. |
| 7 | /docs/system-overview/red-stuff | 34 visitors but 51% time-on-page and 65% scroll depth — technical deep-dive content attracting engaged readers despite low volume. |
| 8 | /docs/tusky-migration-guide | 28 visitors — notable as a migration guide, likely driven by a specific product event or announcement related to Tusky. |
Referral Sources
| Source | Type | Insight |
|---|---|---|
| Direct / None | Organic | 11,419 visitors (95% of total) — dominant traffic source. Suggests most users arrive via bookmarks, direct URL entry, or untracked links (e.g., Discord, Telegram, newsletters). |
| docs.wal.app | Organic | 346 visitors referred from within the same domain — internal navigation tracked as referral, with low 47% bounce rate indicating engaged returning users. |
| Organic | 203 visitors with a high 76% bounce rate and 38s duration. Organic search traffic is modest, suggesting limited SEO visibility or narrow keyword targeting. | |
| wal.app | Organic | 38 visitors from the main Walrus app with only 60% bounce rate and 92s visit duration — highest quality traffic source in terms of engagement. |
| walrus.xyz | Organic | 21 visitors with 71% bounce rate and 33s duration — likely the main marketing site driving some developer traffic. |
| chatgpt.com | AI / Chatbot | 12 visitors referred from ChatGPT with a very long average visit duration of 329s and 38% bounce rate — AI-referred users are highly engaged, spending significantly more time than average. |
| walrus.site | Organic | 12 visitors with an extraordinary 588s average visit duration — small but extremely engaged cohort, possibly developers testing Walrus Sites who then consult docs. |
| Organic | 10 visitors with 80% bounce rate and 61s duration. Social traffic is minimal, suggesting limited viral or promotional activity on X/Twitter this week. |
chatgpt.com
12 visitors referred from ChatGPT averaged 329 seconds on site—the highest engagement of any external referral source—suggesting AI-surfaced docs satisfy deep research intent.
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 | 324 | 650 |
| google.com | 203 | 358 |
| wal.app | 38 | 126 |
| walrus.xyz | 21 | 52 |
| walrus.site | 12 | 128 |
| chatgpt.com | 10 | 38 |
| docs.wal.app/docs/getting-started | 7 | 11 |
| t.co | 6 | 8 |
| duckduckgo.com | 4 | 4 |
| docs.wal.app/docs/sites/introduction/components | 3 | 5 |
| sui.io | 2 | 2 |
| t.co/vRc3qvc8dk | 2 | 2 |
| sites.wal.app | 2 | 6 |
| bing.com | 2 | 4 |
| github.com/MystenLabs/walrus | 2 | 2 |
| docs.wal.app/docs/operator-guide | 2 | 2 |
| android-app://com.twitter.android | 2 | 2 |
| docs.wal.app/blog/01_announcing_walrus | 2 | 11 |
| 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 |
| android-app://com.slack | 2 | 2 |
| docs.wal.app/operator-guide/upload-relay.html | 1 | 4 |
| docs.wal.app/docs/sites/getting-started/installing-the-site-builder | 1 | 3 |
| docs.wal.app/docs/system-overview/red-stuff | 1 | 21 |
| docs.wal.app/docs/walrus-client | 1 | 1 |
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 Configuration | High traffic and 100% scroll depth align with 38 chatbot questions on Sites deployment. |
| /docs/getting-started | Storing and Retrieving Blobs | 1,249 visitors with only 33% scroll depth suggests the page leaves key storage steps incomplete. |
| /docs/sites/introduction/components | Walrus Sites Deployment and Configuration | 421 visitors exploring Sites architecture mirrors chatbot confusion about site configuration options. |
| /docs/operator-guide/storage-nodes/commission-governance | Configuration, Setup, and Network Information | 76% time-on-page signals operators need clearer network constants and governance reference content. |
| /walrus-sites/tutorial | Walrus Sites Deployment and Configuration | 100% scroll depth on tutorial content confirms step-by-step deployment guides are highly valued. |
| /docs/system-overview/red-stuff | Storing and Retrieving Blobs | 65% scroll depth on erasure-coding deep-dive correlates with chatbot questions about blob internals. |
| /docs/tusky-migration-guide | Storing and Retrieving Blobs | Migration guide visits suggest users moving from Tusky need clearer blob re-upload instructions. |
| / | Configuration, Setup, and Network Information | High homepage bounce rate suggests users cannot quickly find network config or getting-started links. |
Notable Takeaways
Spam consumes nearly a quarter of chatbot capacity
55 of 229 Kapa conversations (24%) were spam or fully off-topic queriesUnfiltered bot traffic is diluting signal quality and wasting assistant compute that could serve real developer questions.
Getting-started page loses most readers before completion
33% scroll depth on /docs/getting-started despite 1,249 weekly visitorsThe majority of new users abandon the primary onboarding page mid-way, indicating a critical content gap or pacing problem early in the guide.
ChatGPT referrals convert at extraordinary engagement depth
329-second average visit duration from 12 ChatGPT-referred visitors vs. 40-second site averageAI-referred users are 8x more engaged than average, making docs quality increasingly important as AI surfaces become a primary discovery channel.
Walrus Sites intro drives disproportionate engagement relative to volume
~4,137 visitors with ~100% scroll depth on /walrus-sites/intro vs. 81% overall site bounce rateWalrus Sites is the single stickiest entry point in the docs, suggesting it should anchor cross-linking and onboarding flows.
Developer Pain Point Themes
Walrus users this week primarily asked about blob storage operations, Walrus Sites deployment, and storage costs, with a significant volume of off-topic and spam queries. Key recurring friction points include getting started with storage APIs and understanding pricing and token mechanics.
Storing and Retrieving Blobs
Blob storage is the core developer action; repeated confusion blocks adoption across all user segments.
Show 76 conversations
Off-topic and Spam Queries
Spam load degrades chatbot signal quality and inflates support cost without yielding useful feedback.
Show 55 conversations
Walrus Sites Deployment and Configuration
Sites deployment is a top growth surface; friction here blocks the highest-traffic content category from converting.
Show 39 conversations
Storage Costs, Epochs, and Token Management
Cost uncertainty prevents developers from committing to Walrus for production use cases.
Show 16 conversations
Configuration, Setup, and Network Information
Missing or scattered network constants force repeated chatbot lookups, slowing integration velocity.
Show 19 conversations
WAL Token, Staking, and Ecosystem
Staking and token mechanic confusion creates governance participation barriers and support overhead.
Show 18 conversations
Recommended Actions
Rewrite Getting-Started page with progressive disclosure and completion checkpoints
Restructure /docs/getting-started into clearly delimited steps with inline code snippets for CLI, HTTP API, and TypeScript SDK.
1,249 weekly visitors abandon at 33% scroll depth, making this the highest-volume drop-off point in the funnel.
Publish a unified Network Constants reference page
Create a single page listing all mainnet and testnet object IDs, package IDs, epoch durations, aggregator URLs, and publisher endpoints.
26 Kapa conversations this week asked for specific config values that are currently scattered across multiple pages.
Add a Storage Cost FAQ with concrete worked examples and cost calculator link
Add a prominent FAQ section to /docs/getting-started and /docs/system-overview covering WAL vs SUI split, epoch duration, encoded-size calculation, and a link to costcalculator.wal.app.
36 Kapa conversations this week involved cost and epoch confusion; no single reference page currently consolidates this.
Create a consolidated Walrus Sites deployment guide with testnet and mainnet examples
Merge Sites deploy, update, site-builder CLI commands, package IDs, and framework-specific static-export notes into one structured guide.
38 chatbot conversations on Sites deployment and 4,137 high-scroll visitors to /walrus-sites/intro show demand exceeds current doc depth.
Publish a WAL token and staking quick-reference card
Create a concise reference covering WAL utility, staking flow, unstaking delay, slashing status, and airdrop eligibility criteria in one page.
21 Kapa conversations this week spanned staking, slashing, and airdrop questions that currently have no single canonical answer page.
Implement chatbot input filtering to reject clearly off-topic and spam queries
Add a lightweight pre-classification layer to the Kapa assistant that deflects explicit spam patterns before they consume inference.
55 of 229 conversations this week were spam, consuming 24% of chatbot capacity with zero developer value.
Build an interactive cost estimator embedded in the docs
Embed a lightweight cost calculator widget directly in the storage costs documentation page accepting blob size, epoch count, and network selection.
36 chatbot conversations on pricing show users want immediate cost answers without leaving the docs to visit an external tool.