Voice inconsistency across pages is a subconscious trust signal. A home page that addresses the visitor as "you" in a warm, direct tone — and a pricing page that switches to "the user shall" in formal, passive constructions — makes the site feel like it was assembled from parts by different people. Visitors experience this as cognitive dissonance: the brand that felt approachable on the homepage suddenly feels bureaucratic. This is especially common in AI-built sites where each page was generated in a separate prompting session, each session producing slightly different copy characteristics. The inconsistency rarely prevents conversion on its own, but it creates friction at the moment visitors are evaluating trust — exactly when friction is most costly.
Medium because jarring voice inconsistency between pages creates cognitive dissonance at trust-evaluation moments, though it rarely prevents conversion entirely on its own.
Read the home page, pricing page, and about page back to back — not in separate sessions — and note where the register shifts. The most common failure point is the pricing page, which tends to drift toward formal or legal-sounding language.
Fixes for the most common patterns:
Pricing page drift:
"The user shall receive access to..." → "You get access to..."
"The subscription will automatically renew" → "We renew your subscription automatically"
"The user may cancel at any time" → "You can cancel anytime"
"Upon termination of the account" → "If you close your account"
About page drift:
"Our team strives to deliver..." → "We work to deliver..."
"Customers are our first priority" → "You come first"
Decide on 3 voice adjectives (e.g., "direct, warm, confident") and verify each page against them. Update the pricing and about page copy in their respective route files (app/pricing/page.tsx, app/about/page.tsx) or in shared components.
ID: marketing-content-quality.readability-quality.consistent-voice-tone
Severity: medium
What to look for: Count all relevant instances and enumerate each. Read the marketing copy on the home page, pricing page, and about page (or whichever pages exist). Look for inconsistencies in: person (switching between "you/your" and "users" or "customers" without reason), formality (casual home page then formal legal-sounding pricing copy), and brand voice (friendly and conversational in one section, stiff and corporate in another). Flag jarring inconsistencies that a visitor moving through the site would notice.
Pass criteria: Copy across pages uses consistent person (you/we or they/user, not mixed), consistent register (either professional or conversational throughout), and a consistent brand voice character that doesn't switch dramatically between pages.
Fail criteria: The home page uses "you" and casual language, while the pricing page uses "users" and "the subscription will automatically renew" — formal, third-person, passive. Or the hero is warm and personal, but the features page reads like a technical specification. These create cognitive dissonance that reduces trust.
Skip (N/A) when: Only one public-facing page exists (no multi-page comparison possible). Signal: single-route project.
Detail on fail: Describe the specific inconsistency and where it was found. Example: "Home page uses casual second-person ('You finally have a tool...') but pricing page switches to formal third-person ('The user shall receive...')" Keep under 200 chars.
Remediation: Inconsistent voice makes your site feel assembled from different sources rather than built by a coherent team. Visitors notice this subconsciously as a trust signal.
Decide on a voice and write it down as 3 adjectives (e.g., "direct, friendly, expert"). Then audit your copy against those adjectives page by page.
The most common fix: make pricing pages and policy sections less formal. Rewrite "the subscription will be charged" as "we charge your card" and "the user may cancel at any time" as "you can cancel anytime."
Review the configuration in src/ or app/ directory for implementation patterns.