A recent project: 13 broken pages. 4 competing voices. Orphaned CTAs pointing to features that didn’t exist. A navigation structure that contradicted the information architecture. A brand that said “credibly neutral” while the website said “please use our product.” This is what a comprehensive voice audit looked like for a Web3 protocol.
The structural problem
Protocol brands seem to have a structural problem that product brands don’t. A product can describe itself in terms of features and benefits — what it does and why you should use it. A protocol can’t. A protocol is infrastructure. It doesn’t have users in the product sense. It has participants, builders, node operators, researchers, and communities that may or may not share the same understanding of what the protocol is for.
The result is a brand that accumulates voices. The research team writes for academics. The developer relations team writes for builders. The marketing team writes for potential users. The legal team writes for regulators. Each voice is internally coherent. Together they’re incoherent — and the website, which is the only place all these voices converge, becomes a museum of contradictions.
The audit method
The audit covers every public-facing page. Not a sample. Not the pages that were recently updated. Every page, including the ones nobody remembers exist. The method is three passes.
First pass: inventory. What pages exist. What each page says it does. What links point where. Which CTAs are live, which are orphaned, which point to features that have been renamed or removed. This pass produces the map of what the brand actually is, as opposed to what anyone thinks it is.
Second pass: voice analysis. Who wrote each page. What register they wrote in. Whether the tone matches the adjacent pages. Whether the vocabulary is consistent — does the brand call the same thing by three different names in three different sections? It usually does.
Third pass: structural critique. The information architecture. The navigation model. The hierarchy of messages. Whether the site tells a coherent story when read in order, or whether it’s a collection of independent pages that happen to share a domain name.
What the audit found
27 issues across four categories: voice inconsistency, structural contradiction, orphaned content, and missing context. The voice inconsistencies might have been the most damaging — not because any individual page was poorly written, but because the aggregate effect was a brand that seemed to not know what it was. A page describing the protocol as “credibly neutral infrastructure” sat next to a page describing it as “a platform for building private applications.” Both are true. Together they’re confusing.
The structural contradictions were subtler. The navigation hierarchy implied a product with features. The content described a protocol with primitives. The CTAs assumed the reader was a user. The content assumed the reader was a builder. The site was having two conversations at once and neither was landing.
A redesign principle
The audit became a redesign. Not of the visual identity — of the voice. One voice, three registers: explain the protocol (for the curious), build on the protocol (for developers), and participate in the protocol (for the community). Same vocabulary across all three. Same structural patterns. Different depth.
The principle underneath: a protocol brand might need to sound like the protocol works. If the protocol is minimalist, the brand should be minimalist. If the protocol is neutral, the brand shouldn’t advocate. If the protocol values privacy, the brand shouldn’t track. The brand isn’t a description of the protocol. It might need to be evidence of it.