AI Visibility Audit | Vitally

Dimension	Combined	Platform Delta
All Queries	50%	Perplexity +5 percentage points

By Persona
Chief Revenue Officer	48.1%	ChatGPT +4 percentage points
Director of CS Operations	36.7%	Perplexity +7 percentage points
Customer Success Team Lead	64.5%	Perplexity +10 percentage points
Head of Customer Success	46.7%	Perplexity +10 percentage points
VP of Customer Success	53.1%	Perplexity +3 percentage points

By Buying Job
Artifact Creation	16.7%	ChatGPT +8 percentage points
Comparison	65.6%	Perplexity +6 percentage points
Consensus Creation	23.1%	Perplexity +15 percentage points
Problem Identification	15.4%	Perplexity +8 percentage points
Requirements Building	60%	Perplexity +13 percentage points
Shortlisting	88%	Perplexity +4 percentage points
Solution Exploration	37.5%	Perplexity +6 percentage points
Validation	41.7%	Even

Dimension	ChatGPT	Perplexity
All Queries	37.3%	42.7%

By Persona
Chief Revenue Officer	40.7%	37%
Director of CS Operations	23.3%	30%
Customer Success Team Lead	48.4%	58.1%
Head of Customer Success	33.3%	43.3%
VP of Customer Success	40.6%	43.8%

By Buying Job
Artifact Creation	16.7%	8.3%
Comparison	56.2%	62.5%
Consensus Creation	7.7%	23.1%
Problem Identification	7.7%	15.4%
Requirements Building	40%	53.3%
Shortlisting	72%	76%
Solution Exploration	18.8%	25%
Validation	29.2%	29.2%

ID	Query	Persona	Stage	Winner
⚑ Competitor Wins — 34 queries where a named competitor captures the buyer
vit_036	"What AI capabilities actually matter when evaluating CS platforms — account summaries, meeting prep, or risk alerts?"	VP of Customer Success	Requirements Building	Planhat
vit_038	"Evaluation criteria for CS platforms focused on expansion revenue — what features help identify upsell-ready accounts?"	Head of Customer Success	Requirements Building	Gainsight
vit_066	"customer success tools that integrate with Amplitude or Mixpanel for real-time feature adoption tracking"	Director of CS Operations	Shortlisting	Custify
vit_071	"How does Gainsight compare to Totango for CS workflow automation at a 300-person company?"	VP of Customer Success	Comparison	Gainsight
vit_072	"ChurnZero vs Planhat — which integrates better with Salesforce and product analytics tools?"	Director of CS Operations	Comparison	Planhat
vit_073	"Gainsight vs Planhat for customer success — pros and cons for a mid-market SaaS company"	Head of Customer Success	Comparison	Planhat
vit_075	"ChurnZero vs Totango for tracking customer product usage and predicting churn risk"	Customer Success Team Lead	Comparison	ChurnZero
vit_087	"Planhat vs Catalyst for data integration — which handles complex multi-tool tech stacks better?"	Director of CS Operations	Comparison	Planhat
vit_088	"Gainsight vs ChurnZero playbook automation — which is easier for a small CS team to manage without a dedicated admin?"	Head of Customer Success	Comparison	ChurnZero
vit_089	"Compare Gainsight and Totango reporting dashboards — which is better for C-suite visibility into NRR and churn?"	Chief Revenue Officer	Comparison	Gainsight

ID	Query	Persona	Buying Job	Winner	Vitally Position
vit_001	"How do you know which customers are about to churn before it's too late?"	VP of Customer Success	Problem Identification	No Vendor Mentioned	Mentioned In List
vit_014	"Build vs. buy for customer success — when should a SaaS company invest in a dedicated CS platform instead of building on top of Salesforce?"	Director of CS Operations	Solution Exploration	No Clear Winner	Mentioned In List
vit_015	"What's the difference between a dedicated customer success platform and just using Salesforce with add-ons for CS workflows?"	VP of Customer Success	Solution Exploration	No Clear Winner	Mentioned In List
vit_016	"How do customer health scoring models work in practice — what data do they need to be accurate?"	Customer Success Team Lead	Solution Exploration	No Vendor Mentioned	Mentioned In List
vit_020	"How is AI being used in customer success platforms today — account summaries, next-best-action, or something else?"	Customer Success Team Lead	Solution Exploration	No Vendor Mentioned	Mentioned In List
vit_023	"We've been running CS out of spreadsheets and Salesforce — at what point does a dedicated CS platform make sense?"	Head of Customer Success	Solution Exploration	No Vendor Mentioned	Mentioned In List
vit_028	"What integrations matter most for a CS platform at a product-led SaaS company using Segment and Intercom?"	Customer Success Team Lead	Solution Exploration	No Clear Winner	Mentioned In List
vit_030	"Key requirements for evaluating customer success platforms at a 200-person B2B SaaS company using Salesforce"	Director of CS Operations	Requirements Building	No Clear Winner	Mentioned In List
vit_031	"What questions should I ask CS platform vendors about their health scoring methodology and data requirements?"	VP of Customer Success	Requirements Building	No Vendor Mentioned	Mentioned In List
vit_032	"Must-have vs. nice-to-have features for a CS platform focused on automating onboarding, renewals, and risk escalations"	Customer Success Team Lead	Requirements Building	No Clear Winner	Mentioned In List

ID	Query	Persona	Buying Job	Winner	Vitally Position
vit_033	"What reporting capabilities should a customer success platform have for executive visibility into NRR and churn trends?"	Chief Revenue Officer	Requirements Building	No Clear Winner	Brief Mention
vit_035	"Requirements checklist for customer success platforms that integrate with Segment, Mixpanel, and Salesforce"	Director of CS Operations	Requirements Building	No Vendor Mentioned	Mentioned In List
vit_037	"We need a CS platform that collects NPS and triggers follow-ups automatically — what should be on our requirements list?"	Customer Success Team Lead	Requirements Building	No Clear Winner	Mentioned In List
vit_040	"What Customer Segmentation & Lifecycle Management and automation features should a CS platform have to manage 1,000+ accounts with a team of 8 CSMs?"	Director of CS Operations	Requirements Building	Custify	Mentioned In List
vit_042	"We're replacing our homegrown health scoring with a CS platform — what capabilities should we prioritize?"	Head of Customer Success	Requirements Building	No Clear Winner	Mentioned In List
vit_045	"Best customer success platforms for mid-market SaaS companies that need real-time churn prediction"	VP of Customer Success	Shortlisting	Gainsight	Mentioned In List
vit_047	"We don't have clean NRR reporting today — which CS platforms have the best executive dashboards for retention metrics?"	Chief Revenue Officer	Shortlisting	Gainsight	Mentioned In List
vit_049	"Customer success platforms with the best Salesforce and HubSpot integrations for mid-market companies"	Head of Customer Success	Shortlisting	Gainsight	Mentioned In List
vit_050	"Which CS platforms have AI features that actually help CSMs manage larger books of business?"	VP of Customer Success	Shortlisting	Gainsight	Mentioned In List
vit_052	"Top customer success platforms for B2B SaaS focused on driving net revenue retention and expansion pipeline"	Chief Revenue Officer	Shortlisting	Gainsight	Mentioned In List
vit_053	"CS platforms that let you run different automated playbooks for different customer segments and tiers"	Customer Success Team Lead	Shortlisting	Gainsight	Strong 2nd
vit_054	"looking for CS platform alternatives that are faster to set up than our current tool — mid-market SaaS, 300 employees"	Head of Customer Success	Shortlisting	No Clear Winner	Mentioned In List
vit_055	"Customer success tools with built-in team collaboration and shared account notes instead of separate Slack channels"	VP of Customer Success	Shortlisting	No Clear Winner	Mentioned In List
vit_056	"customer success platforms that handle complex account hierarchies and custom objects well for larger companies"	Director of CS Operations	Shortlisting	Gainsight	Mentioned In List
vit_057	"Best CS platforms for giving leadership real-time visibility into customer health across the entire book of business"	Chief Revenue Officer	Shortlisting	No Clear Winner	Mentioned In List
vit_058	"Which customer success platforms have built-in NPS surveys with automated follow-up actions based on scores?"	Customer Success Team Lead	Shortlisting	Totango	Mentioned In List
vit_059	"switching from spreadsheet-based renewal tracking — best CS platforms for managing renewals and spotting upsell signals"	Head of Customer Success	Shortlisting	Velaris	Mentioned In List
vit_060	"Top CS platforms besides Gainsight for mid-market teams that need strong workflow automation without the enterprise complexity"	VP of Customer Success	Shortlisting	No Clear Winner	Brief Mention
vit_062	"Which CS platforms work best for scaling customer success at a fast-growing SaaS without doubling the team?"	Chief Revenue Officer	Shortlisting	No Clear Winner	Strong 2nd
vit_063	"we need a better customer health scoring system than what we built internally — which CS platforms are best for predicting churn?"	Customer Success Team Lead	Shortlisting	Gainsight	Brief Mention
vit_064	"Best AI-powered customer success platforms for mid-market B2B SaaS companies"	Head of Customer Success	Shortlisting	No Clear Winner	Mentioned In List
vit_067	"Which customer success platforms have the strongest onboarding project management for fast time-to-value?"	Chief Revenue Officer	Shortlisting	No Clear Winner	Mentioned In List
vit_068	"looking for a CS platform where all customer notes and context live in one place instead of scattered across Slack and Google Docs"	Customer Success Team Lead	Shortlisting	Gainsight	Mentioned In List
vit_069	"customer success platforms for companies with 2,000+ accounts that need custom fields, advanced permissions, and API access"	Head of Customer Success	Shortlisting	Gainsight	Mentioned In List
vit_070	"Gainsight vs ChurnZero — which has better customer health scoring for mid-market SaaS?"	Customer Success Team Lead	Comparison	Gainsight	Mentioned In List
vit_074	"Totango vs Catalyst — which gives better executive visibility into retention and expansion metrics?"	Chief Revenue Officer	Comparison	Totango	Mentioned In List
vit_079	"How do smaller CS platforms compare to Gainsight for managing renewals and identifying expansion opportunities?"	Chief Revenue Officer	Comparison	No Clear Winner	Mentioned In List
vit_080	"Which customer success platforms have AI features that actually compete with Gainsight's AI capabilities?"	Customer Success Team Lead	Comparison	Gainsight	Mentioned In List
vit_081	"Which CS platforms have better customer onboarding management than ChurnZero for mid-market SaaS?"	VP of Customer Success	Comparison	No Clear Winner	Mentioned In List
vit_083	"Vitally vs Catalyst — which is better for a growing mid-market CS team focused on retention?"	Head of Customer Success	Comparison	No Clear Winner	Mentioned In List
vit_084	"Is Gainsight worth the $50K+ price tag for a mid-market company or are there better options at a lower price point?"	Chief Revenue Officer	Comparison	Custify	Mentioned In List
vit_090	"We're on Catalyst and not getting the product usage insights we need — how do other CS platforms handle this better?"	Customer Success Team Lead	Comparison	No Clear Winner	Mentioned In List
vit_091	"Best alternatives to Planhat for renewal management and identifying expansion opportunities at a mid-market SaaS"	VP of Customer Success	Comparison	ChurnZero	Mentioned In List
vit_097	"How do AI features compare across Gainsight, ChurnZero, and other top CS platforms in 2026?"	Director of CS Operations	Comparison	ChurnZero	Mentioned In List
vit_098	"Planhat vs ChurnZero health scoring — which does a better job predicting churn for B2B SaaS customers?"	Head of Customer Success	Comparison	No Clear Winner	Brief Mention
vit_099	"We're evaluating Catalyst alternatives after the Totango merger — what's better for expansion revenue tracking?"	Chief Revenue Officer	Comparison	No Clear Winner	Mentioned In List
vit_100	"Switching from Totango — which CS platforms have better workflow automation for small teams?"	Customer Success Team Lead	Comparison	Totango	Strong 2nd
vit_107	"Catalyst customer success platform reviews — what are the biggest complaints after the Totango merger?"	Customer Success Team Lead	Validation	No Clear Winner	Mentioned In List
vit_112	"ChurnZero UI complaints — is the interface really as hard to navigate as the reviews say?"	Customer Success Team Lead	Validation	ChurnZero	Brief Mention
vit_113	"Vitally reviews from customer success leaders — what are the honest pros and cons?"	VP of Customer Success	Validation	No Clear Winner	Strong 2nd
vit_115	"Planhat renewal management weaknesses — what do customers actually complain about?"	Chief Revenue Officer	Validation	Planhat	Brief Mention
vit_117	"Problems with Totango's customer Customer Segmentation & Lifecycle Management for mid-market SaaS — does it scale or get clunky?"	Customer Success Team Lead	Validation	Totango	Mentioned In List
vit_118	"Can mid-market customer success platforms handle 3,000+ accounts without performance issues and slowdowns?"	VP of Customer Success	Validation	No Clear Winner	Mentioned In List
vit_120	"Which CS platforms' built-in NPS surveys actually get good response rates from customers?"	Chief Revenue Officer	Validation	No Clear Winner	Mentioned In List
vit_123	"What are the biggest implementation risks with Totango for a 200-person SaaS company with a small CS ops team?"	VP of Customer Success	Validation	No Clear Winner	Mentioned In List
vit_124	"How good are CS platform analytics for board-level presentations — do any of them produce reports executives actually read?"	Head of Customer Success	Validation	No Clear Winner	Strong 2nd
vit_128	"Case studies of mid-market SaaS companies that improved NRR after implementing a CS platform"	Head of Customer Success	Consensus Creation	No Clear Winner	Strong 2nd
vit_129	"Typical payback period for customer success platforms like Gainsight, ChurnZero, or Vitally"	Chief Revenue Officer	Consensus Creation	No Clear Winner	Brief Mention
vit_144	"Create a Comparison matrix of Gainsight, ChurnZero, Totango, and Planhat for Customer Segmentation & Lifecycle Management, digital-touch automation, and scalability"	VP of Customer Success	Artifact Creation	Velaris	Mentioned In List
vit_150	"Create a vendor evaluation scorecard for customer success platforms with criteria weighted for a mid-market company preparing to scale"	Head of Customer Success	Artifact Creation	Gainsight	Mentioned In List

Company	Mentions	Share
Gainsight	94	17.7%
ChurnZero	87	16.4%
Vitally	75	14.1%
Totango	71	13.4%
Planhat	65	12.2%
Custify	41	7.7%
Velaris	39	7.3%
Catalyst	31	5.8%
ClientSuccess	26	4.9%
SmartKarrot	3	0.6%

Section 5

Prioritized Action Plan

Three layers of recommendations ranked by commercial impact and implementation speed.

[TL;DR] 80 priority recommendations (plus 12 near-rebuild optimizations) targeting 142 queries where Vitally is currently invisible. 5 L1 technical fixes + 2 verification checks, 67 content optimizations (L2), 6 new content initiatives (L3).

142 recommendations execute in strict L1-first sequence: infrastructure fixes unblock Comparison page discovery and content freshness signaling before any new content goes live, then 67 L2 page remediations deepen existing pages, then 68 L3 new content pieces fill the six structural gaps driving early-funnel invisibility and zero decision-maker wins.

Layer 1

Fix Crawl Infrastructure

5 fixes + 2 checks · Engineering · Days

Layer 2

Deepen Existing Pages

67 recommendations · Content Team · Weeks

Layer 3

Build Missing Content

6 NIOs · Content Strategy · Months

Reading the priority numbers: Recommendations are ranked 1–80 across all three layers by commercial impact × implementation speed. Within each layer, items appear in priority order. Gaps in the sequence (e.g., L1 shows 1, 2, then 12) mean higher-priority items belong to a different layer.

Layer 1 Technical Fixes

Configuration and infrastructure changes. Owner: Engineering / DevOps. Timeline: Days to weeks.

Priority	Finding	Impact	Timeline
#1	Broken Pages Linked from Site Navigation	High	< 1 day
Issue: Two URLs linked from the site footer navigation return 404 errors: the 'Why Vitally' competitive hub page at /customer-success-platforms and the 'vs. CRM' Comparison page at /customer-success-platforms/vitally-vs-crm. These are publicly indexed URLs that AI crawlers will encounter and fail to process. Fix: Either restore the /customer-success-platforms hub page and /customer-success-platforms/vitally-vs-crm Comparison page, or update footer navigation links to point to live URLs. If these pages were intentionally removed, implement 301 redirects to the most relevant live page (e.g., redirect the hub to /product/features or the homepage).
#49	Competitor Comparison Pages Lack Visible Publication Dates	Medium	< 1 day
Issue: All 5 competitor Comparison pages (vs. Gainsight, ChurnZero, Totango, Planhat, Catalyst) display no visible publication or last-updated date. The only temporal references are G2 badge descriptions mentioning 'Summer 2025'. Combined with the sitemap's missing lastmod timestamps, AI crawlers have no signal for when this Comparison content was created or last verified. Fix: Add a visible 'Last updated: [date]' element to each Comparison page and commit to updating these pages quarterly. Also add lastmod to these URLs in sitemap.xml. When Comparison data is reviewed and confirmed still accurate, update the visible date even if the content hasn't changed substantially.
#50	Multiple H1 Tags on Most Commercial Pages	Medium	1-2 weeks
Issue: The majority of product, feature, and Comparison pages use multiple H1 tags — ranging from 4 to 14 H1 elements per page. For example, the CSM solution page has 14 H1 tags, Comparison pages average 8 H1 tags, and product pillar pages (Productivity, AI, Visibility) each have 6-7 H1 tags. Only the individual feature pages (NPS, Surveys, Note-Taking, Automation) and case study pages maintain a single H1. Fix: Restructure pages to use a single H1 for the primary page topic, demoting secondary sections to H2. The feature pages (health-scores, NPS, surveys, automation) and case study pages already follow this pattern and can serve as templates. Focus first on the 5 competitor Comparison pages and 4 solution pages, as these are the highest-value pages for AI citation.
#51	Schema Markup Cannot Be Verified — Manual Check Recommended	Medium	1-3 days
Issue: Our analysis method returns rendered page content as markdown text, which does not include JSON-LD schema markup, meta descriptions, or Open Graph tags. We cannot determine whether appropriate schema types (Product, FAQPage, Article, Organization) are present on any page. Fix: Audit schema markup using Google's Rich Results Test or Schema.org validator on key page types: (1) Feature pages with FAQ sections — verify FAQPage schema, (2) Product pages — verify Product or SoftwareApplication schema, (3) Case study pages — verify Article schema, (4) Homepage — verify Organization schema. Prioritize the 5 Comparison pages and 7 feature pages.
#52	Sitemap Lacks lastmod Timestamps on All 1,000+ URLs	Medium	1-3 days
Issue: The sitemap.xml at https://www.vitally.io/sitemap.xml contains over 1,000 URLs but none include lastmod, changefreq, or priority attributes. Every entry contains only the <loc> element. Fix: Add accurate lastmod timestamps to all sitemap entries, particularly for competitor Comparison pages, product pages, and recent blog posts. Ensure lastmod reflects actual content changes, not automated regeneration timestamps. Most CMS platforms (Webflow, WordPress) can be configured to output lastmod automatically.

Verification Checks

Items requiring manual review before determining if action is needed.

Priority	Finding	Impact	Timeline
#75	Client-Side Rendering Status Cannot Be Verified	Low	< 1 day
Issue: Our analysis method cannot detect whether pages rely on client-side rendering (CSR) frameworks like React, Angular, or Vue that may block AI crawlers from accessing content. All pages returned substantive text content through our fetch method, suggesting server-side rendering is likely in place, but this cannot be confirmed without inspecting raw HTML source and testing with JavaScript disabled. Fix: Verify rendering method by loading key pages with JavaScript disabled in the browser. If any pages show minimal content without JavaScript, implement server-side rendering or pre-rendering for those pages. Focus verification on product and feature pages.
#76	Meta Descriptions and OG Tags Cannot Be Verified — Manual Check Recommended	Low	< 1 day
Issue: Meta descriptions and Open Graph tags are not visible in rendered markdown output. We cannot verify whether commercial pages have unique, keyword-optimized meta descriptions or proper OG tags for social sharing and AI context. Fix: Verify meta descriptions and OG tags using browser developer tools or a tool like Screaming Frog. Ensure each commercial page has a unique meta description (150-160 characters) that includes the primary topic and Vitally's name. Check that OG title, description, and image are set for all product, feature, and Comparison pages.

Click any row to expand full issue/fix detail.

Layer 2 Existing Content Optimization

Existing pages that need restructuring or deepening. Owner: Content Team. Timeline: Weeks.

Add CS platform ROI and payback period section to /features/reporting for CRO consensus queries

Priority 2

Currently: partialThe /features/reporting page is entirely feature-description content — no business case language, no ROI framing, no financial outcomes. The CRO persona cannot build an investment justification from the current page.

The /features/reporting page has zero content on ROI, payback periods, or retention impact benchmarks — a CRO building a business case for CS platform investment cannot extract any financial justification from this page Vitally wins 0% of CRO consensus-creation queries because no page provides the business-case evidence these queries require — the reporting page is the highest-traffic candidate for this content

Queries affected: vit_126

Add CS platform TCO framework section to /features/reporting for CRO artifact-creation queries

Priority 3

Currently: partialThe /features/reporting page is feature-description content only — no pricing guidance, no implementation cost framing, no training investment, no 3-year cost framing. AI systems cannot generate a Vitally-referencing TCO model because the inputs are not present on any Vitally page.

Vitally has no page anywhere on the site that provides TCO inputs for a CS platform evaluation — AI systems generating TCO models for this query type cannot reference Vitally because no cost framework content exists The Artifact Creation buying job for the CRO persona is Vitally's lowest-win-rate combination — the absence of TCO content is a direct contributor to the 0% CRO win rate

Queries affected: vit_142

Create an AI capability Comparison matrix artifact on /product/ai for vendor evaluation artifact queries

Priority 5

Currently: partialThe /product/ai page is single-vendor only — no competitor data, no multi-vendor Comparison table, no artifact-ready content. AI generating a vendor evaluation matrix for this query type cannot cite Vitally as a source because no comparative data exists.

AI systems building a 'CS platform AI feature matrix' artifact cannot reference Vitally — the /product/ai page has no competitor data and no structured table format that AI can extract for a vendor evaluation matrix This is Artifact Creation buying job — the moment buyers build the Comparison document they share with their team. Being excluded from this artifact means Vitally doesn't advance to the next stage of evaluation

Queries affected: vit_149

Create an onboarding playbook template artifact section on /features/project-management for artifact-creation queries

Priority 6

Currently: partialThe /features/project-management page has no template or artifact content — no sample playbook phases, no task examples, no milestone definitions. AI generating an onboarding playbook template cannot reference Vitally because no template structure exists on any Vitally page.

Vitally has no onboarding playbook template on any page — AI systems generating onboarding playbook artifacts cannot reference Vitally as the source, because the template content does not exist Artifact_creation buying job for a VP-level persona is the highest-value citation opportunity for the /features/project-management page — being excluded means Vitally does not appear in the evaluation documents buyers share with their leadership

Queries affected: vit_148

Add Gainsight reporting limitations section and Comparison table to /features/reporting for competitor-Validation queries

Priority 9

Currently: partialThe /features/reporting page has no competitor-comparative content and no reference to G2 review data or specific Gainsight reporting limitations — the buyer researching a competitor's weaknesses cannot find a Vitally-positioned answer.

The /features/reporting page has no section addressing the top Gainsight reporting criticisms sourced from G2: rigid out-of-box dashboards with limited customization, data refresh lag making real-time decisions difficult, and custom report setup requiring admin support Without a dated Comparison section, AI platforms (especially ChatGPT) reach for Gainsight-published content when answering Validation queries about Gainsight's reporting limitations

Queries affected: vit_110

Add onboarding standardization and retention benchmark section to /features/project-management for consensus-creation queries

Priority 10

Currently: partialThe /features/project-management page is entirely feature-description content — no retention benchmarks, no TTV improvement data, no business outcome evidence. This is a complete content-type gap for the Consensus Creation buying job.

The /features/project-management page has zero business outcome content — no retention benchmarks, no TTV improvement data, no named customer outcomes. A CS Team Lead building an internal business case cannot extract any shareable evidence from this page Consensus_creation queries require data that leaders can share upward — without benchmark content, Vitally is structurally excluded from all consensus-creation citations for the onboarding feature area

Queries affected: vit_132

Near-rebuild: /features/health-scores cannot answer CFO business case queries — inform NIO 001 blueprint

Priority 12

Currently: partialNo business case, ROI calculator, payback period estimate, or CFO-oriented financial justification exists anywhere on Vitally's site — this content category is entirely absent.

The /features/health-scores page describes a product feature and contains no financial justification content — it cannot answer 'what is the business case for reducing churn through health scoring?' The /solution/cs-leader page covers CS leader positioning but also lacks CFO-level financial framing with cost-of-churn benchmarks, platform investment ranges, and payback period estimates

Queries affected: vit_127

Near-rebuild: /features/health-scores requires churn reduction benchmark content for Consensus Creation queries

Priority 13

Currently: partialPage has no benchmark data, industry statistics, or named customer metrics for churn reduction following health scoring implementation. Buyers cannot use this page to form expectations about ROI.

The /features/health-scores page contains no quantified outcome data — no customer churn reduction percentages, no industry benchmarks, no before/after comparisons — making it impossible for AI platforms to cite Vitally when a buyer asks what churn reduction to expect The page has no segment-specific data (what churn reduction does a 200-person mid-market SaaS typically see?), which is the specific framing buyers use at solution exploration stage

Queries affected: vit_025

Near-rebuild: /features/health-scores requires new Comparison matrix for Artifact Creation queries

Priority 14

Currently: partialNo Comparison matrix or structured competitor feature data exists on the health scores page or anywhere on Vitally's site for health scoring capabilities.

The /features/health-scores page contains no competitor capability data — buyers building evaluation matrices cannot find Gainsight, Planhat, or ChurnZero health scoring specifications to compare against Vitally The page has no downloadable or copy-pasteable Comparison table format that serves Artifact Creation buyers

Queries affected: vit_141

Near-rebuild: /integrations requires multi-vendor Comparison scorecard artifact — inform NIO 006 blueprint

Priority 15

Currently: partialNo vendor Comparison scorecard or multi-competitor evaluation matrix exists on Vitally's site covering integration, automation, and ease of use.

The /integrations page lists Vitally's integration capabilities but contains no competitor data — buyers building Comparison scorecards for Gainsight, ChurnZero, and Totango cannot find Vitally's position in their scorecard from this page No downloadable or web-accessible Comparison scorecard template exists on Vitally's site for the integration + automation + ease-of-use evaluation dimensions

Queries affected: vit_140

Near-rebuild: NRR improvement case studies require new content — inform NIO 001 blueprint

Priority 16

Currently: partialNo NRR improvement case studies or quantified retention outcome data exists on automation-related pages. The separate /case-study/ section has some data but is not structured for the 'mid-market SaaS NRR improvement' query.

The /features/automation page contains no NRR improvement metrics — buyers asking for proof that workflow automation improves retention cannot find quantified evidence The case study section is disconnected from the feature pages — NRR outcome data buried in case study subpages is not extractable by AI platforms responding to automation-outcome queries

Queries affected: vit_128

Add 'Gainsight vs ChurnZero playbook automation for small CS teams' section to /customer-success-platforms/vitally-vs-Gainsight

Priority 18

Currently: partialNo three-way Comparison content covering Gainsight, ChurnZero, and Vitally for the 'admin-light playbook automation' use case exists anywhere on Vitally's site.

The /vitally-vs-Gainsight page does not address the 'small CS team without a dedicated admin' use case — the specific buyer context in this query The page lacks a 'ChurnZero vs Gainsight vs Vitally for admin-light playbook automation' three-way Comparison that would intercept buyers comparing the two competitors

Queries affected: vit_088

Add 'Gainsight vs Totango and where Vitally fits' section to /customer-success-platforms/vitally-vs-Gainsight

Priority 19

Currently: partialThe vitally-vs-Gainsight and vitally-vs-Totango Comparison pages cover Vitally against each competitor but do not address the Gainsight-vs-Totango Comparison that buyers are asking — Vitally is never entered into the conversation.

The /vitally-vs-Gainsight page covers Vitally vs Gainsight but does not address the Gainsight vs Totango Comparison question — a buyer deciding between these two never encounters Vitally through this page The /vitally-vs-Gainsight page lacks a 'considering Totango as well?' section that intercepts buyers who have both Gainsight and Totango on their shortlist and introduces Vitally as a third option

Queries affected: vit_071

Add 'switching from Totango for better automation' competitive content to /customer-success-platforms/vitally-vs-Totango

Priority 20

Currently: partialThe vitally-vs-Totango page covers general positioning but does not make a specific, evidence-backed case that Vitally's automation outperforms Totango's for small CS teams — the exact claim the buyer is searching for.

The /vitally-vs-Totango page does not include a head-to-head automation capability Comparison — buyers switching from Totango cannot find specific evidence that Vitally's automation is superior for small teams The page lacks customer testimonials from teams that specifically switched from Totango to Vitally for automation reasons

Queries affected: vit_100

Add 'top CS platforms besides Gainsight for workflow automation' positioning to /features/automation

Priority 21

Currently: partialPage describes automation features but does not explicitly position Vitally as the mid-market alternative to Gainsight for workflow automation — the specific framing buyers use when they've already decided against Gainsight.

The /features/automation page does not include a 'Gainsight alternative for workflow automation' positioning section — buyers who have pre-rejected Gainsight for cost or complexity reasons cannot find Vitally as the recommended next option The page lacks a mid-market framing: automation capability descriptions do not specify that they are designed for 50-500 person CS teams without a dedicated admin

Queries affected: vit_060

Add AI evaluation criteria section to /product/ai for requirements-building queries

Priority 22

Currently: partialThe /product/ai page describes what Vitally's AI does but provides no evaluation framework — what AI capabilities are must-have, what differentiates platforms, and what is overhyped. Buyers building requirements documents cannot derive their criteria from the current page.

The /product/ai page is a feature marketing page, not an evaluation guide — it tells buyers what Vitally AI does but not what they should require from any CS platform AI or how to distinguish strong AI implementations from weak ones The Requirements Building buying job specifically needs checklist or tiered-criteria format that AI platforms can extract for RFP-style responses — the current page has no such structure

Queries affected: vit_036

Add AI time-savings benchmark section to /product/ai for consensus-creation queries

Priority 23

Currently: partialThe /product/ai page has no time-savings benchmarks or productivity outcome data. AI platforms answering 'how much time do AI-powered CS tools save per CSM per week' default to Gainsight because Gainsight publishes specific time-savings claims — Vitally cannot win this query without equivalent content.

The /product/ai page has no productivity benchmark content — 'how much time does AI actually save per CSM per week' cannot be answered from this page, making Vitally invisible for consensus-creation queries that require shareable evidence Gainsight wins this query specifically because it publishes time-savings claims with named customer examples — Vitally's absence from this content category is a direct cause of consensus-stage losses

Queries affected: vit_133

Add CS leader social proof section to /features/health-scores for Validation queries

Priority 24

Currently: partialPage contains no customer testimonials, G2 review excerpts, or honest pros/cons framing that would serve a buyer doing Validation research on Vitally specifically.

The /features/health-scores page has no customer voice content — no testimonials, G2 excerpts, or case study references from CS leaders who use Vitally's health scoring The page does not acknowledge any limitations or trade-offs in Vitally's health scoring approach, which reduces its credibility for buyers doing honest Validation research

Queries affected: vit_113

Add CS platform implementation timeline Comparison section to /features/project-management for competitor-Validation queries

Priority 25

Currently: partialThe /features/project-management page has no content on implementation timelines — neither Vitally's own timeline nor competitor Comparison data. Buyers at Validation stage researching competitor implementation burden are receptive to alternative vendor information.

The /features/project-management page has no implementation timeline content — buyers researching ChurnZero's implementation burden cannot find Vitally as an alternative, because Vitally has not published its own implementation timeline on any page Validation-stage competitor queries are interception opportunities: buyers who encounter friction in their ChurnZero research are receptive to discovering Vitally as a faster-to-implement alternative

Queries affected: vit_108

Add Catalyst implementation Comparison and mid-market framing to implementation section on /features/project-management

Priority 26

Currently: partialSame structural gap as l2_059 — no implementation content on the page. This entry adds the Catalyst Comparison row to the implementation table and adds mid-market-specific implementation framing that l2_059 does not cover.

Catalyst's implementation experience is not addressed on any Vitally page — buyers researching Catalyst implementation smoothness for mid-market teams cannot find Vitally as a Comparison point Mid-market-specific implementation framing is absent — 'no dedicated CS ops admin required' is Vitally's key mid-market implementation differentiator but is not stated anywhere

Queries affected: vit_119

Add ChurnZero Salesforce integration limitation content to /integration/salesforce

Priority 27

Currently: partialThe /integration/salesforce page describes Vitally's Salesforce integration capabilities but does not reference ChurnZero's known Salesforce sync reliability issues, which is the specific Validation research this buyer is conducting.

The /integration/salesforce page does not reference ChurnZero's documented Salesforce sync issues — buyers researching integration reliability by competitor are not finding Vitally as the reliable alternative The page lacks data sync reliability specifications — sync frequency, error handling, and what happens when Salesforce records conflict with Vitally data

Queries affected: vit_103

Add Gainsight competitive positioning for churn prediction to /features/health-scores

Priority 28

Currently: partialPage does not include competitive Comparison against Gainsight for churn prediction, real-time signal processing, or mid-market suitability — the specific factors buyers weigh at Shortlisting.

The /features/health-scores page contains no Comparison against Gainsight's health scoring — buyers specifically comparing mid-market churn prediction options cannot find Vitally's positioning from this page The page does not specify whether health scoring is real-time or batch-processed — this is a direct Shortlisting criterion that buyers explicitly ask about

Queries affected: vit_045

Add Gainsight competitive positioning to /integrations for Salesforce+HubSpot Shortlisting

Priority 29

Currently: partialThe /integrations page lists integrations without competitive positioning against Gainsight's integration capabilities — Gainsight's brand dominance on integration queries is not being challenged.

The /integrations page does not include a 'Vitally vs Gainsight for Salesforce and HubSpot integration' Comparison — the specific competitive question buyers at Shortlisting stage are asking The /integration/salesforce and /integration/hubspot pages describe what Vitally's integrations do but do not compare integration depth, sync frequency, or bidirectional capability against Gainsight

Queries affected: vit_049

Add NPS + automated follow-up requirements checklist to /features/nps for requirements-building queries

Priority 30

Currently: partialThe /features/nps page is a feature marketing page, not an evaluation guide — it tells buyers what Vitally does but not what they should require from any CS platform NPS module. The Requirements Building buying job needs a checklist format the current page does not provide.

The /features/nps page does not provide the requirements checklist format that buyers at the Requirements Building stage need — AI cannot extract structured NPS evaluation criteria from the current feature-description content No differentiation between mandatory NPS requirements and advanced capabilities — buyers building a requirements document need this tiering to prioritize their vendor evaluation

Queries affected: vit_037

Add NPS automation retention impact section to /features/nps for leadership consensus-creation queries

Priority 31

Currently: partialThe /features/nps page describes NPS automation features but has no retention-outcome evidence, no case study connecting NPS automation to churn reduction, and no leadership-ready business case framing. This is a complete content-type gap for the Consensus Creation buying job.

The /features/nps page has no retention-outcome content — 'how automated NPS follow-up workflows improve retention' cannot be answered from this page with Vitally as the recommended platform No named customer example connecting NPS automation to churn reduction — the Consensus Creation buying job specifically requires shareable, attributable evidence, which feature descriptions cannot satisfy

Queries affected: vit_136

Add NRR and retention board reporting framing to /features/reporting

Priority 32

Currently: partialPage describes reporting features generally but does not address the specific CRO use case of building NRR and retention dashboards for board presentations.

The /features/reporting page does not describe how Vitally calculates and displays NRR — the specific metric CROs need for board reporting The page lacks a 'board reporting' use case section showing the executive dashboard views that a CRO would present to the board

Queries affected: vit_003

Add NRR tracking Comparison vs spreadsheets section to /features/reporting

Priority 33

Currently: partialPage does not address the specific limitations of spreadsheet-based NRR tracking or the advantages of platform-based analytics for CRO decision-making.

The /features/reporting page does not explain what a CS platform's NRR tracking provides that spreadsheets cannot — the specific decision buyers are evaluating at Solution Exploration stage The page lacks a 'before and after' Comparison showing a team's NRR reporting workflow in spreadsheets vs in Vitally

Queries affected: vit_019

Add Planhat health scoring Comparison section to /features/health-scores

Priority 34

Currently: partialPage has no Planhat-specific Comparison content. The vitally-vs-Planhat Comparison page exists but does not address health scoring specifically or answer 'does Planhat's health scoring actually predict churn?'

The /features/health-scores page does not reference Planhat or position Vitally's health scoring methodology against Planhat's approach — buyers evaluating both cannot use this page for Comparison The page lacks G2 review evidence about health scoring accuracy — a key Validation-stage concern that Planhat's pages address more directly

Queries affected: vit_105

Add actionable NPS problem-framing section to /features/nps for early-funnel NPS frustration queries

Priority 35

Currently: partialThe /features/nps page skips the problem-identification step — it assumes buyers already know they need a CS platform NPS tool and jumps to feature promotion. Buyers researching 'how to make NPS actionable' do not find a Vitally-sourced answer to the category-level problem.

The /features/nps page opens with feature descriptions ('send NPS surveys from Vitally') rather than validating the buyer's frustration: 'NPS scores sit in a spreadsheet and no one acts on them' No specific mechanism explaining why NPS data goes unused — the buyer at Problem Identification stage needs to understand the root cause (lack of automated workflow routing) before they can evaluate a solution

Queries affected: vit_012

Add dedicated CS platform vs Salesforce positioning section to /features/automation

Priority 36

Currently: partialPage describes Vitally's automation capabilities but does not frame them against the 'just use Salesforce workflows' alternative that many CS teams default to.

The /features/automation page does not address the 'Salesforce vs dedicated CS platform' decision — the most common alternative buyers are evaluating, particularly for automation workflows The page has no content on the specific automation gaps in Salesforce for CS workflows (no health scoring triggers, no CS-specific playbook templates, no customer lifecycle automation native to the CRM)

Queries affected: vit_015

Add executive and board-ready reporting section to /features/reporting for leadership Validation queries

Priority 37

Currently: partialThe /features/reporting page describes report types and dashboard features but does not demonstrate what board-ready output looks like or how Vitally's reports are used by executives — the buyer cannot visualize the end artifact.

The /features/reporting page describes reporting features in product language ('build dashboards', 'export data') without showing what the executive-facing output looks like — no named metrics, no export format descriptions, no executive use case No case study reference connecting Vitally's reporting to a board presentation outcome — ChatGPT has no citable named example to cite for executive reporting queries

Queries affected: vit_124

Add executive dashboard competitive positioning to /features/reporting for Shortlisting

Priority 38

Currently: partialPage describes Vitally's reporting features without competitive positioning against Gainsight for executive dashboard quality — the specific evaluation Gainsight is winning.

The /features/reporting page has no competitive positioning against Gainsight for executive dashboard quality — buyers Shortlisting for 'best executive dashboards for retention metrics' cannot find Vitally's position relative to Gainsight The page lacks a screenshot or description of Vitally's executive retention dashboard showing the specific metrics CROs care about

Queries affected: vit_047

Add executive reporting requirements framework to /features/reporting

Priority 39

Currently: partialPage describes reporting features without organizing them as answers to executive reporting requirements — CROs building requirements lists cannot use this page as a requirements document.

The /features/reporting page is not structured as a requirements answer document — CROs cannot find which Vitally features address each of their executive reporting requirements The page lacks a 'requirements for executive CS reporting' checklist with Vitally's coverage of each requirement clearly marked

Queries affected: vit_033

Add leadership portfolio visibility framing to /features/health-scores

Priority 40

Currently: partialPage is framed for CSM-level health monitoring, not leadership-level portfolio views. Does not address how leaders see health trends across all accounts simultaneously.

The /features/health-scores page does not show or describe the leadership portfolio view — how a CRO or VP CS sees all account health scores across the entire book of business in a single dashboard The page has no 'escalation to leadership' workflow description — how at-risk accounts surface automatically to leadership without requiring manual reporting

Queries affected: vit_057

Add mid-market AI positioning section to /product/ai for segment-specific Shortlisting

Priority 41

Currently: partialThe /product/ai page has no segment-specific positioning — 'mid-market B2B SaaS' is not named on the page, and the contrast with enterprise AI platforms (Gainsight, requiring dedicated admin configuration) is absent. AI platforms Shortlisting by segment cannot identify Vitally as the mid-market AI option.

The /product/ai page does not target mid-market B2B SaaS as the audience — 'mid-market' is not named, and the page describes AI features that apply equally to any company size, making it non-competitive for segment-specific Shortlisting queries No contrast with Gainsight's admin-heavy AI configuration — buyers evaluating 'best AI-powered CS platforms for mid-market' need a reason to prefer Vitally over Gainsight beyond feature parity

Queries affected: vit_064

Add onboarding module evaluation checklist to /features/project-management for requirements-building queries

Priority 42

Currently: partialThe /features/project-management page is a feature marketing page, not an evaluation guide — it tells buyers what Vitally does but not what they should require from any CS platform onboarding module at scale. The Requirements Building buying job needs a checklist format that this page does not provide.

The /features/project-management page does not provide the requirements checklist format that buyers at the Requirements Building stage need — AI platforms cannot extract structured evaluation criteria from the current feature-description content Volume-specific guidance ('at 100+ new customers per quarter') is absent — buyers managing high-volume onboarding need criteria specific to their scale, not generic feature lists

Queries affected: vit_034

Add problem-framing section to /features/project-management for onboarding standardization early-funnel queries

Priority 43

Currently: partialThe /features/project-management page skips the foundational problem-identification step — it assumes the buyer already wants project management and jumps to feature promotion. Buyers researching whether and how CS platforms solve the consistency problem do not find a Vitally-sourced answer.

The /features/project-management page opens with feature descriptions ('manage tasks, milestones, and playbooks') rather than validating the buyer's problem: 'onboarding quality varies by CSM and I cannot scale without fixing this' No data point on the cost of inconsistent onboarding — the buyer at Problem Identification stage needs a reason to believe CS platform project management solves this, not a feature list

Queries affected: vit_006

Add problem-Validation section to /product/ai for early-funnel AI-scaling queries

Priority 44

Currently: partialThe /product/ai page skips the foundational problem-identification step — it assumes the buyer already knows AI can solve the scaling problem and goes straight to Vitally's feature set. Buyers who haven't made this conclusion yet do not find Vitally cited for this query.

The /product/ai page opens with Vitally AI feature descriptions rather than validating the category-level problem: 'can AI help CS teams manage more accounts without burning out?' — a buyer at Problem Identification stage who hasn't concluded AI is the solution cannot extract a direct answer No specific capacity ratio or benchmark on the page — AI platforms have no citable number to anchor the 'how many more accounts' answer

Queries affected: vit_010

Add vendor evaluation questions section to /features/health-scores

Priority 45

Currently: partialPage describes the product but is not structured as an RFP-response or vendor evaluation document — does not address the 5-7 key questions buyers ask when evaluating health scoring capabilities.

The /features/health-scores page is structured as a product showcase, not as an answer to vendor evaluation questions — buyers building a requirements list cannot find Vitally's position on key questions (configurable weighting? ML vs rule-based? integration with Salesforce health fields?) The page lacks a FAQ or evaluation criteria section that would make it citable for requirements-building queries

Queries affected: vit_031

Add volume-specific Shortlisting positioning to /features/project-management for high-volume onboarding shortlist queries

Priority 46

Currently: partialThe /features/project-management page describes Vitally's onboarding features generically — 50+ customers/quarter is not mentioned, and no competitive positioning names Vitally as a top option for high-volume onboarding. AI platforms Shortlisting by volume cannot identify Vitally.

The /features/project-management page does not name the volume tier ('50+ new customers per quarter') that defines this buyer's Shortlisting context — AI cannot match Vitally to volume-specific Shortlisting queries without this explicit qualifier No competitive positioning statement naming Vitally against alternatives for high-volume onboarding — buyers Shortlisting need a reason to include Vitally over Totango or Catalyst

Queries affected: vit_051

Reframe /features/health-scores to open with early churn detection buyer question

Priority 47

Currently: partialPage describes health score configuration but does not frame the early-warning use case with buyer-language urgency. No first-person pain framing ('by the time you see the churn, it's too late') and no data on how early Vitally's signals detect risk vs manual monitoring.

The /features/health-scores page opens with product feature framing ('configure your health score') rather than buyer pain framing — an AI responding to 'how do I know which customers are about to churn' cannot extract a direct answer from this page The /features/health-scores page lacks any data on lead time: how many days before a churn event does Vitally's health scoring surface a risk signal? This is the specific evidence buyers at problem identification stage need to evaluate a solution

Queries affected: vit_001

Reframe /product/ai hero around CSM capacity outcome for Shortlisting queries

Priority 48

Currently: partialThe /product/ai page describes AI features in isolation — the CSM capacity expansion outcome ('manage 40–60% more accounts') is implicit but never stated as the primary value claim. Buyers Shortlisting on 'AI that helps CSMs manage more accounts' cannot extract a Vitally answer from the current page.

The /product/ai page buries the capacity outcome — the primary claim ('Vitally AI lets CSMs manage significantly more accounts without sacrificing relationship quality') is not stated in the hero, above the fold, or in any H2 heading that AI platforms would extract for Shortlisting queries No specific capacity ratio is stated on the page — AI Shortlisting responses require a quantifiable claim to justify including Vitally as 'one of the platforms that helps CSMs manage larger books'

Queries affected: vit_050

Near-rebuild: /features/automation cannot deliver evaluation criteria artifact — inform NIO 004 blueprint

Priority 53

Currently: partialNo evaluation criteria framework exists for the automation + onboarding + renewals combination. The existing feature pages describe capabilities but are not structured as evaluation documents.

The /features/automation page is a product showcase, not an evaluation framework — it cannot serve a buyer who is writing evaluation criteria for a vendor selection process No page on Vitally's site presents a buyer-facing evaluation criteria template for the automation, onboarding, and renewal management combination

Queries affected: vit_143

Add 'CS platform vs Salesforce build' decision framework to /integrations

Priority 55

Currently: partialNo build-vs-buy decision framework exists on Vitally's site. The /integration/salesforce page covers Salesforce integration but does not address when a dedicated CS platform replaces Salesforce-native CS workflows.

The /integrations page does not address the 'build on Salesforce vs buy a dedicated CS platform' decision — the most common architectural decision CS teams face before entering the CS platform evaluation process The /integration/salesforce page positions Vitally as a Salesforce integration but does not explain what Vitally provides that Salesforce + add-ons cannot replicate

Queries affected: vit_014

Add 'better than internal health scoring' positioning to /features/health-scores

Priority 56

Currently: partialPage does not address the specific pain of teams who have already tried building health scoring internally — what they typically miss (automation, real-time alerts, playbook triggers) and why a dedicated CS platform solves it.

The /features/health-scores page has no content addressing why purpose-built CS platform health scoring outperforms homegrown solutions — buyers who built internally need to understand the specific gaps they are filling The page does not cite any G2 reviews or third-party social proof that validates Vitally's health scoring accuracy or predictive power

Queries affected: vit_063

Add 'building health scoring from spreadsheets' buyer framing to /features/health-scores

Priority 57

Currently: partialPage describes health score setup but does not explain what data inputs are required, which signals matter most for churn prediction, or why spreadsheet-based scoring fails at scale.

The /features/health-scores page does not explain what data a health score needs to be predictive — buyers migrating from spreadsheets need a concrete list of inputs (product usage events, CRM data, support tickets, NPS scores) to evaluate whether Vitally can ingest their data The /features/health-scores page has no section addressing why spreadsheet-based health scoring breaks at scale — this is the buyer's current state and the page should acknowledge and address it

Queries affected: vit_011

Add 'how health scoring models work in practice' methodology section to /features/health-scores

Priority 58

Currently: partialPage demonstrates the product UI for health scoring but lacks a methodology explanation: how signals are weighted, whether scoring is rule-based or ML-based, and how scoring thresholds are calibrated.

The /features/health-scores page does not explain Vitally's health score methodology — whether signals are weighted manually, automatically, or via ML — leaving buyers unable to evaluate prediction accuracy The page has no section on how scoring thresholds (red/yellow/green) are calibrated to a specific customer base, which is the key practical question buyers ask at Solution Exploration stage

Queries affected: vit_016

Add 'migrating from homegrown health scoring' framing to /features/health-scores

Priority 59

Currently: partialPage does not acknowledge or address the buyer's current state (homegrown scoring), what capability gaps homegrown scoring leaves, or how migration to Vitally works.

The /features/health-scores page assumes the buyer has no current health scoring solution — it does not address the specific evaluation concerns of teams migrating from a homegrown system (data migration, scoring parity, transition period) The page provides no migration path or implementation timeline information, which is the primary concern of buyers who have already built internal scoring systems

Queries affected: vit_042

Add 'when a CS platform makes sense' inflection-point framing to /features/automation

Priority 60

Currently: partialPage describes Vitally's automation capabilities but provides no inflection-point guidance — company size, account volume, or CSM-to-account ratio at which a dedicated CS platform begins to deliver ROI over spreadsheet/CRM workflows.

The /features/automation page does not address the 'is it time to move to a CS platform?' question — buyers at this stage need a concrete threshold (e.g., '50+ accounts per CSM,' '5+ person CS team') to self-qualify The page lacks a 'signs you've outgrown your current setup' section that validates the buyer's current pain and frames the decision timing

Queries affected: vit_023

Add ChurnZero UI Comparison to /customer-success-platforms/vitally-vs-ChurnZero

Priority 61

Currently: partialThe vitally-vs-ChurnZero page lacks any UX complexity Comparison or reference to ChurnZero's known G2 review complaints about navigation difficulty.

The /vitally-vs-ChurnZero page does not reference ChurnZero's widely documented G2 review complaints about UI complexity and navigation difficulty — missing the specific Validation concern buyers have The page has no interface complexity Comparison showing Vitally's onboarding time vs ChurnZero's learning curve for CSMs

Queries affected: vit_112

Add HubSpot+Segment+Zendesk integration requirements content to /integrations

Priority 62

Currently: partialIndividual integration pages exist for HubSpot and Salesforce but not for Segment or Zendesk. No page explains how Vitally handles the HubSpot + Segment + Zendesk combination that product-led SaaS companies commonly use.

The /integrations page does not explain how Vitally ingests and combines data from HubSpot (CRM), Segment (product analytics), and Zendesk (support) into a unified customer profile — the specific multi-tool architecture this buyer is evaluating No dedicated /integration/zendesk or /integration/segment landing pages exist — buyers cannot verify these specific integrations the same way they can verify Salesforce or HubSpot

Queries affected: vit_043

Add Planhat Salesforce bidirectional sync reliability Comparison to /integration/salesforce

Priority 63

Currently: partialPage does not specify Vitally's bidirectional sync capabilities or contrast them against Planhat — the specific Comparison this buyer is making at Validation stage.

The /integration/salesforce page does not explicitly describe bidirectional sync capability — the buyer specifically wants to know if data flows both ways between Vitally and Salesforce No Planhat sync reliability Comparison exists on any Vitally page — buyers comparing Planhat and Vitally on Salesforce integration cannot find Vitally's position

Queries affected: vit_122

Add Totango Salesforce/HubSpot sync reliability Comparison to /integration/salesforce

Priority 64

Currently: partialThe /integration/salesforce page describes Vitally's integration but does not reference Totango's sync reliability issues that buyers are researching at Validation stage.

The /integration/salesforce page does not address Totango's documented Salesforce/HubSpot sync reliability problems — buyers researching Totango alternatives for integration reliability cannot find Vitally as the answer The page lacks a 'switching from Totango for integration reliability' framing that would intercept buyers who have already identified Totango's sync issues

Queries affected: vit_109

Add Totango automation limitation competitive content to /customer-success-platforms/vitally-vs-Totango

Priority 65

Currently: partialThe vitally-vs-Totango page covers high-level positioning but does not cite G2 review evidence of Totango's specific automation limitations, which is the content type buyers are looking for at Validation stage.

The /vitally-vs-Totango page does not reference G2 review data on Totango's specific automation limitations — the page makes comparative claims without citing the third-party evidence buyers use at Validation stage The page does not address the specific automation struggles teams experience post-implementation with Totango (typically: complex trigger configuration, limited native integrations, admin-heavy playbook management)

Queries affected: vit_104

Add Totango implementation risk Comparison to /customer-success-platforms/vitally-vs-Totango

Priority 66

Currently: partialThe vitally-vs-Totango page lacks implementation risk content — no mention of Totango's data migration complexity, admin requirements, or implementation timeline vs Vitally.

The /vitally-vs-Totango page does not address Totango's documented implementation risks for companies without a dedicated CS ops team — the specific buyer context in this query The page lacks a Vitally implementation process description that would give buyers confidence in a lower-risk alternative

Queries affected: vit_123

Add built-in vs standalone NPS Comparison framework to /features/nps for solution-exploration queries

Priority 67

Currently: partialThe /features/nps page is single-vendor content — it does not address the 'built-in vs standalone' decision the buyer is actively making. Without a Comparison framework, AI platforms cannot cite Vitally when answering this solution-exploration Comparison question.

The /features/nps page does not address the 'built-in CS platform NPS vs standalone NPS tool' decision — a buyer comparing these approaches cannot use this page to understand where Vitally fits in the decision landscape Named alternatives (Delighted, Typeform, Qualtrics) are not mentioned — ChatGPT requires named alternatives in Comparison content to treat the Comparison as authoritative

Queries affected: vit_024

Add buyer-pain framing for CRM manual work to /features/automation

Priority 68

Currently: partialPage describes automation features (playbooks, triggers, sequences) but does not address the specific pain of manual CRM record updates that consume CSM time, nor how Vitally's automation eliminates this overhead.

The /features/automation page leads with product capability descriptions rather than the buyer pain — CSMs spending 60-70% of their time on admin tasks rather than customer interaction The page does not specify which CRM update tasks Vitally automates (contact updates, activity logging, health score pushes, renewal date tracking) — the specific information a frustrated CSM needs to evaluate fit

Queries affected: vit_013

Add buyer-pain framing for fragmented customer data to /integrations

Priority 69

Currently: partialThe /integrations page is an integration directory without buyer problem framing — it lists available integrations but does not address why fragmented customer data is a problem or how Vitally's integrations solve it.

The /integrations page opens with a list of available integrations rather than framing the buyer pain — a CS ops manager who needs to consolidate five tools cannot quickly determine from this page whether Vitally solves their specific data fragmentation problem The page does not explain what a unified customer data view looks like after integrations are connected — the outcome state buyers are trying to reach

Queries affected: vit_002

Add implementation speed positioning to /features/automation and vitally-vs Comparison pages

Priority 70

Currently: partialImplementation speed and time-to-value are not prominently featured on any Vitally page — a key competitive advantage vs Gainsight that is not being communicated.

The /features/automation page does not include implementation timeline data — buyers looking for faster alternatives to Gainsight or their current tool need a specific time-to-value claim (e.g., 'first automated playbook running in 2 weeks') The page does not contrast Vitally's implementation speed against Gainsight's (known for 3-6 month implementations) — the most relevant competitive differentiator for this query type

Queries affected: vit_054

Add must-have vs nice-to-have evaluation framework to /features/automation

Priority 71

Currently: partialPage lists automation features comprehensively but provides no framework for prioritizing them, which is what Requirements Building buyers need.

The /features/automation page lists every automation capability without distinguishing which are foundational vs advanced — buyers building requirements lists cannot determine what to prioritize from this page The page does not frame automation features by use case (onboarding automation vs renewal automation vs risk escalation automation) — Requirements Building buyers organize their evaluation by use case, not feature category

Queries affected: vit_032

Add requirements framing for 200-person SaaS to /integrations page

Priority 72

Currently: partialPage lists integrations without framing integration requirements by company profile — a 200-person SaaS using Salesforce has specific integration requirements that are not addressed.

The /integrations page presents integrations as an undifferentiated catalog — buyers at Requirements Building stage cannot determine which integrations are critical for a 200-person SaaS running Salesforce vs other profiles The page lacks a 'recommended integration stack for [company profile]' section that helps buyers build their integration requirements checklist

Queries affected: vit_030

Add two-approach onboarding framework section to /features/project-management for solution-exploration queries

Priority 73

Currently: partialThe /features/project-management page describes Vitally's milestone approach without framing it within the buyer's decision: 'project management style with milestones vs automated playbook sequences.' Without a Comparison framework, AI platforms cannot cite Vitally when answering this solution-exploration Comparison question.

The /features/project-management page does not frame Vitally's approach within the broader 'milestone vs playbook' solution landscape — a buyer comparing approaches cannot use this page to understand where Vitally fits in the decision Solution_exploration queries require a Comparison framework, not a single-vendor feature description — Vitally misses citation opportunities by not addressing the 'which approach' question

Queries affected: vit_022

Restructure /product/ai into an AI use-case taxonomy for solution-exploration queries

Priority 74

Currently: partialThe /product/ai page mentions AI use cases (account summaries, risk alerts, meeting prep, automated drafting) but does not organize them into the taxonomy format buyers and AI platforms use to extract structured answers. Feature descriptions are isolated rather than categorized.

The /product/ai page does not provide the category taxonomy a buyer uses to evaluate AI in CS — 'account summaries, next-best-action, risk alerts, automated communications' need to be organized as distinct use-case categories with H3 headings, not scattered across marketing copy Without a taxonomy structure, AI platforms cannot extract a clean answer to 'how is AI being used in CS platforms today' — Vitally is not cited because the page doesn't mirror the solution-exploration framing

Queries affected: vit_020

Add NPS response rate evidence section to /features/nps for CRO Validation queries

Priority 77

Currently: partialThe /features/nps page describes NPS feature capabilities without any response rate data or delivery mechanism specifics. A CRO validating whether built-in NPS actually works cannot find a credible answer on any Vitally page — this is the precise content gap causing the 0% CRO win rate for NPS queries.

The /features/nps page has no response rate data — 'which CS platforms' NPS surveys actually get good response rates' cannot be answered with Vitally as the recommended platform because no response rate evidence exists on the page No description of the delivery mechanism (in-app vs email, trigger logic, survey frequency management) that explains how Vitally achieves its response rates — the mechanism is as important as the number for CRO Validation

Queries affected: vit_120

Add Vitally AI vs Gainsight AI Comparison section to /product/ai for direct AI Comparison queries

Priority 78

Currently: partialThe /product/ai page has no competitor-comparative content for AI capabilities — no mention of Gainsight's AI, no feature-level Comparison, no differentiation claims. AI platforms generating a Gainsight AI alternatives response have no Vitally-sourced comparative data to include.

Without a 'Vitally AI vs Gainsight AI' section, AI platforms answering 'which platforms compete with Gainsight's AI' cannot include Vitally — there is no Vitally-sourced Comparison content to cite The /product/ai page's only Gainsight reference is a link to the Comparison page — a buyer researching AI capabilities specifically needs the Comparison on the AI product page, not a redirect

Queries affected: vit_080

Add multi-vendor AI capability matrix to /product/ai for multi-platform Comparison queries

Priority 79

Currently: partialThe /product/ai page is entirely single-vendor — Vitally's AI features only, no competitor context, no multi-platform Comparison. AI systems building a multi-platform AI Comparison matrix for 2026 cannot reference Vitally because no comparative data exists on the page.

Vitally has no multi-vendor AI Comparison content — AI platforms generating a '2026 AI feature Comparison across CS platforms' cannot include Vitally because there is no Vitally-sourced data for the Comparison matrix Without a dated section ('Updated Q1 2026'), the /product/ai page also loses to ChatGPT's recency bias even for queries where Vitally's features are competitive

Queries affected: vit_097

Reframe /features/project-management around time-to-value outcome for CRO Shortlisting queries

Priority 80

Currently: partialThe /features/project-management page uses feature language ('manage tasks', 'track milestones') rather than outcome language ('reduce time-to-value by X weeks'). A CRO evaluating 'strongest onboarding project management for fast TTV' cannot find a business outcome claim from Vitally.

The /features/project-management page's value proposition is framed in product language, not the business outcome language (time-to-value, first-year retention impact) that CRO Shortlisting queries require No specific TTV improvement metric exists on the page — CRO Shortlisting queries for 'fastest TTV' need a citable outcome claim, not feature descriptions

Queries affected: vit_067

Layer 3 Narrative Intelligence Opportunities

Net new content addressing visibility and positioning gaps. Owner: Content Strategy. Timeline: Months.

NIO #1: Expansion Revenue Intelligence: The Content Void Costing Vitally the CRO

Gap Type: Structural Gap — Vitally achieves 0% wins across all 7 visible Renewal & Expansion Management queries (0/7 visible queries won) despite 53.8% visibility (7/13 total queries). No dedicated content hub exists for expansion revenue identification, upsell signal methodology, or NRR benchmarking — the commercial vocabulary CROs use at budget decision time.

Critical

Expansion revenue is the commercial language of the CRO and VP CS — the executives who hold veto power over platform selection. Vitally appears in 53.9% (7/13) of Renewal & Expansion Management queries but wins 0% of those appearances, while Gainsight, ChurnZero, and Velaris claim the recommendation. The structural absence is a content hub that frames Vitally around 'how do we grow NRR' rather than 'how do we manage CS.' Winning 5 of these 13 queries adds coverage across every buying stage from problem identification through artifact creation — the full funnel for a CRO-driven deal. Gainsight and ChurnZero win by publishing ROI calculators, payback benchmarks, and upsell signal frameworks; Vitally can publish original data from its customer base to claim this space without product changes.

Show query cluster, blueprint & platform acuity

Query Cluster

IDs: vit_038, vit_008, vit_021, vit_052, vit_059, vit_079, vit_091, vit_099, vit_115, vit_125, vit_129, vit_138, vit_147

“Evaluation criteria for CS platforms focused on expansion revenue — what features help identify upsell-ready accounts?”

“How do B2B SaaS companies systematically identify which accounts are ready for upsell?”

“Switching from spreadsheet-based renewal tracking — best CS platforms for managing renewals and spotting upsell signals”

“Build an ROI calculator template for a customer success platform based on churn reduction, expansion revenue, and CSM productivity gains”

Blueprint

On-Domain: Create /product/expansion or /features/renewals as a dedicated expansion intelligence hub page, positioning Vitally around NRR growth rather than churn prevention — include upsell signal examples, account health-to-expansion triggers, and CRM-connected opportunity tracking
On-Domain: Publish an original 'CS Platform ROI and Payback Period' benchmark page using anonymized Vitally customer data, with segment-specific data for 100-500 employee SaaS companies — directly wins vit_147 and vit_129
On-Domain: Create /resources/expansion-revenue-guide covering how to build a systematic upsell identification process in a CS platform, with Vitally methodology woven throughout — wins vit_038 and vit_008
On-Domain: Add an 'Expansion Revenue' outcomes section to /solution/cs-leader and /solution/csm pages with quantified NRR improvement from named Vitally case studies
Off-Domain: Commission or co-author a 'State of Expansion Revenue in B2B SaaS' benchmark report with a third-party CS community partner — original cited research is the content type ChatGPT consistently cites in Consensus Creation responses
Off-Domain: Pursue G2 Momentum Grid and Capterra listings in 'Revenue Intelligence' and 'Customer Revenue Optimization' categories to build third-party authority on expansion-related queries
Off-Domain: Secure placements in Customer Success Collective and SaaStr content specifically addressing upsell signal identification methodology with Vitally framing

Platform Acuity

ChatGPT (high): ChatGPT citations favor third-party authoritative sources for ROI and benchmark claims. An original benchmark report with verifiable methodology gives ChatGPT the citable source needed to include Vitally in Consensus Creation and Artifact Creation responses. Perplexity (high): Perplexity rewards freshness signals and self-contained structured passages. A dedicated expansion hub with lastmod timestamps (currently missing site-wide per sitemap_missing_lastmod finding) and scannable data tables would make Vitally's expansion content highly extractable.

NIO #2: Product Usage & Adoption Tracking: PLG-Era Integration Blindspot

Gap Type: Content Type Deficit — Vitally's Product Usage & Adoption Tracking feature shows 27.3% visibility (3/11 queries) and 0% wins (0/3 visible). No dedicated integration landing pages exist for Amplitude, Mixpanel, or Segment — the analytics tools that product-led SaaS teams rely on — making Vitally uncitable when buyers search for CS platforms that connect to their analytics stack.

High

Product-led SaaS companies evaluate CS platforms primarily on how well they ingest product usage data from Amplitude, Mixpanel, and Segment alongside CRM data. Vitally's /integrations page lists connections but provides no dedicated landing pages for these analytics tools — the exact content format AI platforms need to cite Vitally. Custify wins vit_066 ('customer success tools that integrate with Amplitude or Mixpanel for real-time feature adoption tracking') by default because it has named integration pages; Vitally cannot be cited when its integration depth is undetectable from page structure. This gap directly affects the Director of CS Operations — the technical evaluator who vetoes platforms that cannot ingest the existing data stack.

Show query cluster, blueprint & platform acuity

Query Cluster

IDs: vit_066, vit_075, vit_005, vit_018, vit_028, vit_035, vit_048, vit_116, vit_131, vit_146

“customer success tools that integrate with Amplitude or Mixpanel for real-time feature adoption tracking”

“How do B2B SaaS teams catch drops in product usage before they lose the customer?”

“How do customer success platforms pull in product usage data and combine it with CRM and support tickets?”

“Best CS tools for product-led SaaS that need to track feature adoption and usage drop-offs”

Blueprint

On-Domain: Create /integration/amplitude, /integration/mixpanel, and /integration/segment dedicated landing pages — each page should explain what data Vitally pulls, how it combines with health scoring, and what CS actions it enables (not just that the integration exists)
On-Domain: Add a 'Product-Led SaaS' use case page at /solution/product-led that frames Vitally for companies using Amplitude/Mixpanel/Segment stacks, explaining how usage drop detection triggers CS playbooks
On-Domain: Expand /features/product-usage (or create this page) with specific examples of usage signals that trigger churn alerts, including data on how Vitally customers use feature adoption data to identify at-risk accounts
On-Domain: Create a 'CS Platform Integration Requirements Checklist' resource for PLG teams listing Vitally's integrations by data type (product analytics, CRM, support, billing) — directly wins vit_146 and vit_035
Off-Domain: Pursue co-marketing content with Amplitude, Mixpanel, and Segment partner programs — integration partner blog posts are cited by both ChatGPT and Perplexity as authoritative source material for integration capability queries
Off-Domain: Contribute to ProductLed.com and Openview content with thought leadership on how CS platforms should ingest product analytics data — builds domain authority for PLG-era integration queries

Platform Acuity

ChatGPT (high): ChatGPT needs named, structured pages it can cite. When a buyer asks which CS platforms integrate with Amplitude, ChatGPT searches for pages explicitly named /integration/amplitude — a generic integrations index page is too broad to cite confidently for a specific integration query. Perplexity (high): Perplexity rewards self-contained integration specification pages with structured data. A page stating specific data fields Vitally syncs from Amplitude in real time is more extractable than a generic integrations index page.

NIO #3: Enterprise Scale & Compliance Positioning: The Anti-Gainsight Vacuum

Gap Type: Structural Gap — Vitally's Enterprise Scalability & Advanced Customization feature shows 45.5% visibility (5/11 queries) and 0% wins (0/5 visible). Of 14 L3 queries, 8 carry 'missing' coverage status — Vitally has no content on complex account hierarchies, SOC 2/GDPR compliance, custom objects, or Gainsight pricing comparisons. When a mid-market CRO asks whether Gainsight's $50K+ price tag is justified, Vitally is absent from the response.

Critical

The highest-value commercial moment in the CS platform category is when a mid-market CRO asks 'Is Gainsight worth $50K or is there a better option at our scale?' — query vit_084, won by Custify while Vitally is absent. These 14 queries share a common buyer need: enterprise-grade capability evidence without enterprise complexity or pricing. Vitally lacks any content on handling 2,000+ account hierarchies, SOC 2 Type II compliance, custom objects, API access depth, or Gainsight cost-of-ownership comparisons — the exact vocabulary buyers use when they want Gainsight's capabilities without Gainsight's cost. Every one of these 14 queries currently routes buyers to Gainsight, Totango, or Custify rather than positioning Vitally as the rational mid-market alternative.

Show query cluster, blueprint & platform acuity

Query Cluster

IDs: vit_102, vit_106, vit_111, vit_027, vit_039, vit_056, vit_069, vit_084, vit_092, vit_118, vit_134, vit_150, vit_139, vit_145

“Is Gainsight worth the $50K+ price tag for a mid-market company or are there better options at a lower price point?”

“Hidden costs of Gainsight that mid-market companies don't expect — implementation, training, and ongoing fees”

“customer success platforms for companies with 2,000+ accounts that need custom fields, advanced permissions, and API access”

“What security and compliance requirements should a mid-market company include when evaluating customer success platforms — SOC 2, GDPR?”

Blueprint

On-Domain: Create /enterprise or /customers/scale page documenting Vitally's capabilities for 500-5,000+ account deployments: custom objects, advanced permissions, multi-product account hierarchies, and API rate limits — include named customer logos at this scale
On-Domain: Create /security or /trust page with SOC 2 Type II compliance status, GDPR DPA availability, SSO/SAML support, data residency options, and downloadable security questionnaire — directly wins vit_039 and vit_145
On-Domain: Publish a 'Gainsight vs Vitally: Total Cost of Ownership' Comparison page breaking down Gainsight's implementation costs, admin overhead, and contract structure vs Vitally's pricing model — directly wins vit_084, vit_106, and vit_111
On-Domain: Create a downloadable RFP template for CS platform evaluation at mid-market SaaS companies, formatted to showcase Vitally's advantages in the scoring criteria — directly wins vit_139 and vit_150
Off-Domain: Submit Vitally to security review platforms (SecurityPal, Whistic, OneTrust) and link the Trust Center to the /security page — ChatGPT uses these as corroborating signals when answering compliance queries
Off-Domain: Pursue Gartner Peer Insights and Forrester Wave coverage in the mid-market CS platform segment to build analyst citation authority for enterprise-scale positioning

Platform Acuity

ChatGPT (medium): ChatGPT requires verified third-party signals for security and compliance claims. A Trust Center linked from the /security page plus G2 reviews mentioning SOC 2 compliance gives ChatGPT the corroborating sources needed to cite Vitally in compliance-related queries. Perplexity (high): Perplexity will extract structured compliance specification tables directly from on-domain pages. A /security page with a scannable compliance checklist (SOC 2: Yes, GDPR DPA: Yes, SSO: Yes) is highly receptive to Perplexity extraction and would directly win vit_039 and vit_145.

NIO #4: Digital-Touch & Segmentation: Invisible for Scale-Without-Headcount Buyers

Gap Type: Content Type Deficit — Vitally's Customer Segmentation & Lifecycle Management feature shows 63.6% visibility (7/11 queries) but only 28.6% wins (2/7 visible queries). Of 9 L3 queries, 6 carry 'missing' coverage status — no content exists on tiered playbook management, digital-touch CS methodology, or managing 1,000+ accounts with a small team. Gainsight and Custify win these queries by publishing digital-touch CS frameworks that Vitally has not created.

High

The scaling question — how to grow from 5 to 15 CSMs and manage 5x the accounts without proportional headcount growth — is among the most commercially urgent problems mid-market CS leaders face. Vitally's Customer Segmentation & Lifecycle Management and automation capabilities directly address this, but no content exists that frames this use case in the vocabulary buyers search for: 'digital-touch,' 'tiered playbooks,' '1,000+ account management.' Gainsight wins vit_053 and Custify wins vit_040 despite Vitally's competitive feature strength. The root cause is a missing content type — buyers need blog content, use case pages, and methodology guides for scale-without-headcount queries, but Vitally only has product feature pages for this topic.

Show query cluster, blueprint & platform acuity

Query Cluster

IDs: vit_007, vit_017, vit_029, vit_040, vit_053, vit_062, vit_117, vit_130, vit_144

“What approaches work for scaling customer success without hiring more CSMs?”

“Digital-touch vs. high-touch customer success — what's the right balance for a mid-market SaaS with 500+ accounts?”

“How do mid-market CS teams segment their customer base to run different playbooks for different tiers?”

“CS platforms that let you run different automated playbooks for different customer segments and tiers”

Blueprint

On-Domain: Create /features/Customer Segmentation & Lifecycle Management or expand /product/productivity with a dedicated 'Customer Segmentation and Tiered Playbooks' section explaining how Vitally segments accounts by health, ARR, and lifecycle stage, and routes each tier to a different automated playbook
On-Domain: Publish a 'Digital-Touch CS at Scale' guide at /resources/digital-touch-cs defining high-touch vs digital-touch models, providing recommended account-per-CSM ratios by company stage, and showing how Vitally's automation bridges the gap — directly wins vit_007 and vit_017
On-Domain: Create a /solution/scale use case page targeting CS leaders at 200-1,000 employee SaaS companies, with customer examples showing account growth without proportional headcount increases
On-Domain: Create a Comparison matrix of Customer Segmentation & Lifecycle Management capabilities across Gainsight, ChurnZero, Totango, Planhat, and Vitally — directly wins vit_144
Off-Domain: Contribute to Customer Success Collective, CS Insider, and Pavilion CS community with bylined content on building a tiered CS model with automation — these sources are cited in AI responses for digital-touch methodology queries
Off-Domain: Commission G2 case study content with 2-3 Vitally customers who specifically grew from high-touch to digital-touch models on Vitally's platform

Platform Acuity

ChatGPT (medium): ChatGPT answers digital-touch CS queries by drawing from CS practitioner content and vendor guides. A Vitally-authored digital-touch guide needs third-party citations or customer data points to rank over Gainsight's established content in this methodology space. Perplexity (high): Perplexity strongly favors freshly dated, structured methodology content. A /resources/digital-touch-cs page with clean heading hierarchy and a lastmod timestamp extracts cleanly for definitional and how-to queries in this cluster.

NIO #5: Team Knowledge Continuity: CSM Turnover Risk Content Gap

Gap Type: Content Type Deficit — Vitally's Team Collaboration & Shared Docs feature shows 37.5% visibility (3/8 queries) and 33.3% wins (1/3 visible). All 7 L3 queries carry 'thin' coverage status — collaboration features exist but are described as product capabilities rather than as a solution to the specific buyer pain of CSM turnover creating irreversible customer knowledge loss.

Medium

When a CS team lead or Director of CS Ops asks 'how do we prevent losing all customer context when a CSM leaves?' they are describing a pain with direct revenue consequences: account risk during transitions, slower ramp for replacement CSMs, and customer trust erosion. Vitally's notes and collaboration features directly address this, but existing /features/ pages describe what the features do rather than why a company without them bleeds revenue during CSM turnover. The 7 queries in this cluster span the full buying journey, suggesting buyers are actively searching for this solution — Vitally simply is not in the frame when they find it. ChurnZero wins vit_121 by framing collaboration features around the knowledge retention use case specifically.

Show query cluster, blueprint & platform acuity

Query Cluster

IDs: vit_009, vit_026, vit_041, vit_055, vit_068, vit_121, vit_137

“How do you prevent losing all customer context when a CSM leaves the company?”

“We're using Notion for CS account notes but it doesn't connect to anything — how do CS platforms handle shared knowledge?”

“What team collaboration features should a CS platform have to prevent critical customer context from living in individual CSMs' heads?”

“looking for a CS platform where all customer notes and context live in one place instead of scattered across Slack and Google Docs”

Blueprint

On-Domain: Reframe the collaboration/notes feature page to lead with the CSM turnover use case: include a specific section on account handoff workflows and how Vitally ensures continuity when a CSM departs — adds the buyer-language framing without rebuilding the page
On-Domain: Create a 'CSM Offboarding Playbook' resource at /resources/csm-offboarding outlining how CS teams use Vitally to capture account context before a CSM departs — directly wins vit_009 and vit_137
On-Domain: Add a 'Shared Knowledge' use case section to /solution/operations that quantifies the cost of knowledge silos and shows Vitally's solution with a customer example
Off-Domain: Publish bylined content on LinkedIn and Customer Success Collective on 'the hidden cost of CSM turnover and how to protect customer relationships' — references Vitally as the infrastructure solution
Off-Domain: Seek G2 reviews specifically mentioning knowledge retention and account handoff features to build social proof for this query cluster

Platform Acuity

ChatGPT (medium): ChatGPT answers knowledge management queries by citing vendor-neutral guides and then naming specific platform solutions. A Vitally-authored CSM knowledge continuity guide needs to rank for the generic question before ChatGPT will cite it in vendor-specific responses. Perplexity (high): Perplexity extracts self-contained answers well. A page with a clear H2 'How Vitally prevents customer knowledge loss when CSMs leave' followed by a structured workflow description extracts directly as an answer to the Problem Identification queries in this cluster.

NIO #6: Comparison Content Architecture: Losing Deals Vitally Was Never Invited To

Gap Type: Content Type Deficit — 15 high-intent Comparison and Shortlisting queries route to L3 because Vitally's pages use product/feature content types where Comparison buying_job queries require Comparison-format content. 6 queries ask about competitor-vs-competitor matchups where Vitally has no page or presence at all. Comparison is the highest-visibility buying job at 65.6% (21/32 queries) — these 15 losses directly compound an already weak conversion rate at the most commercially critical stage.

Critical

Comparison is the highest-intent buying job — buyers who ask Comparison questions have a shortlist and are choosing. Vitally's 5 existing competitor Comparison pages cover Vitally-vs-[competitor] matchups but fail to intercept two adjacent query types: competitor-vs-competitor queries where buyers are choosing between Gainsight and Planhat (Vitally never enters the frame), and feature-level Comparison queries where Vitally's feature pages lack Comparison-table structure that AI platforms need to extract and cite Vitally as an answer. The routing engine's affinity override — 'Comparison buying_job requires Comparison page types, found feature/product' — is the technical signal for this structural deficit. Fixing the Comparison content architecture protects the highest-intent buying stage and is the highest-leverage single investment in this audit.

Show query cluster, blueprint & platform acuity

Query Cluster

IDs: vit_070, vit_072, vit_073, vit_074, vit_081, vit_083, vit_087, vit_089, vit_090, vit_093, vit_094, vit_098, vit_101, vit_107, vit_058

“Gainsight vs ChurnZero — which has better customer health scoring for mid-market SaaS?”

“ChurnZero vs Planhat — which integrates better with Salesforce and product analytics tools?”

“Gainsight vs Planhat for customer success — pros and cons for a mid-market SaaS company”

“Compare Gainsight, ChurnZero, and Totango for a mid-market B2B SaaS company — which is the best fit?”

Blueprint

On-Domain: Create /customer-success-platforms/vitally-vs-Catalyst Comparison page — Vitally's Comparison hub has no Catalyst page despite Catalyst being a primary competitor after the Totango merger; vit_083 is a direct named match for this page
On-Domain: Add 'Where Vitally fits when you're deciding between [Competitor A] and [Competitor B]' sections to each existing Comparison page, structured as a third-column Comparison table — directly addresses the 7 competitor-vs-competitor queries (vit_072, vit_073, vit_087, vit_089, vit_093, vit_094, vit_101)
On-Domain: Add feature Comparison tables to /features/health-scores, /features/reporting, and /integration/salesforce — structured as 'How Vitally compares to [Competitor] on [Feature]' with G2-sourced data points — provides Comparison-format content without new pages for vit_070, vit_098, vit_074, vit_101
On-Domain: Create /resources/cs-platform-Comparison as a hub page with feature matrices across all primary competitors — captures vit_094 and multi-competitor Comparison queries
On-Domain: Restore /customer-success-platforms hub page (currently returning 404 per broken_navigation_links L1 finding) — prerequisite for Comparison content to be discoverable through hierarchical crawling
Off-Domain: Publish Comparison-format content on G2 Vitally profile, Capterra sponsored listings, and Software Advice — AI platforms cite these third-party Comparison sources for vendor evaluation queries at higher rates than vendor-owned Comparison pages
Off-Domain: Pitch CS analyst coverage (SoftwareReviews, TrustRadius) specifically for three-way comparisons including Vitally alongside Gainsight and ChurnZero

Platform Acuity

ChatGPT (high): ChatGPT cites named Comparison pages directly for vendor evaluation queries. The broken /customer-success-platforms hub (L1 finding: broken_navigation_links) prevents ChatGPT from discovering the Comparison section through hierarchical crawling — restoring the hub page is the prerequisite for Comparison content to be discoverable. Perplexity (high): Perplexity extracts Comparison tables directly from pages. Existing Comparison pages lack visible publication dates (L1 finding: comparison_pages_undated) and carry 8+ H1 tags (L1 finding: multiple_h1_tags) — both structural issues reduce Perplexity extractability. Fixing those two L1 issues would immediately improve Perplexity performance for this cluster without any new content creation.

Unified Priority Ranking

All recommendations across all three layers, ranked by commercial impact × implementation speed.

1
Broken Pages Linked from Site Navigation
Two URLs linked from the site footer navigation return 404 errors: the 'Why Vitally' competitive hub page at /customer-success-platforms and the 'vs. CRM' Comparison page at /customer-success-platforms/vitally-vs-crm. These are publicly indexed URLs that AI crawlers will encounter and fail to process.
Technical Fix · Engineering · 2 URLs linked from footer navigation across all pages site-wide
2
Add CS platform ROI and payback period section to /features/reporting for CRO consensus queries
The /features/reporting page has zero content on ROI, payback periods, or retention impact benchmarks — a CRO building a business case for CS platform investment cannot extract any financial justification from this page
Content Optimization → New Content · Content · 1 queries, personas: Chief Revenue Officer
3
Add CS platform TCO framework section to /features/reporting for CRO artifact-creation queries
Vitally has no page anywhere on the site that provides TCO inputs for a CS platform evaluation — AI systems generating TCO models for this query type cannot reference Vitally because no cost framework content exists
Content Optimization → New Content · Content · 1 queries, personas: Chief Revenue Officer
4
Comparison Content Architecture: Losing Deals Vitally Was Never Invited To
15 high-intent Comparison and Shortlisting queries route to L3 because Vitally's pages use product/feature content types where Comparison buying_job queries require Comparison-format content. 6 queries ask about competitor-vs-competitor matchups where Vitally has no page or presence at all. Comparison is the highest-visibility buying job at 65.6% (21/32 queries) — these 15 losses directly compound an already weak conversion rate at the most commercially critical stage.
New Content · Content · 15 queries affecting personas: Director of CS Operations, Customer Success Team Lead, Head of Customer Success, Chief Revenue Officer, VP of Customer Success
5
Create an AI capability Comparison matrix artifact on /product/ai for vendor evaluation artifact queries
AI systems building a 'CS platform AI feature matrix' artifact cannot reference Vitally — the /product/ai page has no competitor data and no structured table format that AI can extract for a vendor evaluation matrix
Content Optimization → New Content · Content · 1 queries, personas: Customer Success Team Lead
6
Create an onboarding playbook template artifact section on /features/project-management for artifact-creation queries
Vitally has no onboarding playbook template on any page — AI systems generating onboarding playbook artifacts cannot reference Vitally as the source, because the template content does not exist
Content Optimization → New Content · Content · 1 queries, personas: VP of Customer Success
7
Enterprise Scale & Compliance Positioning: The Anti-Gainsight Vacuum
Vitally's Enterprise Scalability & Advanced Customization feature shows 45.5% visibility (5/11 queries) and 0% wins (0/5 visible). Of 14 L3 queries, 8 carry 'missing' coverage status — Vitally has no content on complex account hierarchies, SOC 2/GDPR compliance, custom objects, or Gainsight pricing comparisons. When a mid-market CRO asks whether Gainsight's $50K+ price tag is justified, Vitally is absent from the response.
New Content · Content · 14 queries affecting personas: Chief Revenue Officer, Director of CS Operations, Head of Customer Success, VP of Customer Success
8
Expansion Revenue Intelligence: The Content Void Costing Vitally the CRO
Vitally achieves 0% wins across all 7 visible Renewal & Expansion Management queries (0/7 visible queries won) despite 53.8% visibility (7/13 total queries). No dedicated content hub exists for expansion revenue identification, upsell signal methodology, or NRR benchmarking — the commercial vocabulary CROs use at budget decision time.
New Content · Content · 13 queries affecting personas: Chief Revenue Officer, Head of Customer Success, VP of Customer Success, Director of CS Operations
9
Add Gainsight reporting limitations section and Comparison table to /features/reporting for competitor-Validation queries
The /features/reporting page has no section addressing the top Gainsight reporting criticisms sourced from G2: rigid out-of-box dashboards with limited customization, data refresh lag making real-time decisions difficult, and custom report setup requiring admin support
Content Optimization → New Content · Content · 1 queries, personas: Head of Customer Success
10
Add onboarding standardization and retention benchmark section to /features/project-management for consensus-creation queries
The /features/project-management page has zero business outcome content — no retention benchmarks, no TTV improvement data, no named customer outcomes. A CS Team Lead building an internal business case cannot extract any shareable evidence from this page
Content Optimization → New Content · Content · 1 queries, personas: Customer Success Team Lead
11
Digital-Touch & Segmentation: Invisible for Scale-Without-Headcount Buyers
Vitally's Customer Segmentation & Lifecycle Management feature shows 63.6% visibility (7/11 queries) but only 28.6% wins (2/7 visible queries). Of 9 L3 queries, 6 carry 'missing' coverage status — no content exists on tiered playbook management, digital-touch CS methodology, or managing 1,000+ accounts with a small team. Gainsight and Custify win these queries by publishing digital-touch CS frameworks that Vitally has not created.
New Content · Content · 9 queries affecting personas: Director of CS Operations, Customer Success Team Lead, VP of Customer Success, Chief Revenue Officer
12
Near-rebuild: /features/health-scores cannot answer CFO business case queries — inform NIO 001 blueprint
The /features/health-scores page describes a product feature and contains no financial justification content — it cannot answer 'what is the business case for reducing churn through health scoring?'
Content Optimization → New Content · Content · 1 queries, personas: VP of Customer Success
13
Near-rebuild: /features/health-scores requires churn reduction benchmark content for Consensus Creation queries
The /features/health-scores page contains no quantified outcome data — no customer churn reduction percentages, no industry benchmarks, no before/after comparisons — making it impossible for AI platforms to cite Vitally when a buyer asks what churn reduction to expect
Content Optimization → New Content · Content · 1 queries, personas: Chief Revenue Officer
14
Near-rebuild: /features/health-scores requires new Comparison matrix for Artifact Creation queries
The /features/health-scores page contains no competitor capability data — buyers building evaluation matrices cannot find Gainsight, Planhat, or ChurnZero health scoring specifications to compare against Vitally
Content Optimization → New Content · Content · 1 queries, personas: Head of Customer Success
15
Near-rebuild: /integrations requires multi-vendor Comparison scorecard artifact — inform NIO 006 blueprint
The /integrations page lists Vitally's integration capabilities but contains no competitor data — buyers building Comparison scorecards for Gainsight, ChurnZero, and Totango cannot find Vitally's position in their scorecard from this page
Content Optimization → New Content · Content · 1 queries, personas: Director of CS Operations
16
Near-rebuild: NRR improvement case studies require new content — inform NIO 001 blueprint
The /features/automation page contains no NRR improvement metrics — buyers asking for proof that workflow automation improves retention cannot find quantified evidence
Content Optimization → New Content · Content · 1 queries, personas: Head of Customer Success
17
Product Usage & Adoption Tracking: PLG-Era Integration Blindspot
Vitally's Product Usage & Adoption Tracking feature shows 27.3% visibility (3/11 queries) and 0% wins (0/3 visible). No dedicated integration landing pages exist for Amplitude, Mixpanel, or Segment — the analytics tools that product-led SaaS teams rely on — making Vitally uncitable when buyers search for CS platforms that connect to their analytics stack.
New Content · Content · 10 queries affecting personas: Director of CS Operations, Customer Success Team Lead, Head of Customer Success, VP of Customer Success
18
Add 'Gainsight vs ChurnZero playbook automation for small CS teams' section to /customer-success-platforms/vitally-vs-Gainsight
The /vitally-vs-Gainsight page does not address the 'small CS team without a dedicated admin' use case — the specific buyer context in this query
Content Optimization · Content · 1 queries, personas: Head of Customer Success
19
Add 'Gainsight vs Totango and where Vitally fits' section to /customer-success-platforms/vitally-vs-Gainsight
The /vitally-vs-Gainsight page covers Vitally vs Gainsight but does not address the Gainsight vs Totango Comparison question — a buyer deciding between these two never encounters Vitally through this page
Content Optimization · Content · 1 queries, personas: VP of Customer Success
20
Add 'switching from Totango for better automation' competitive content to /customer-success-platforms/vitally-vs-Totango
The /vitally-vs-Totango page does not include a head-to-head automation capability Comparison — buyers switching from Totango cannot find specific evidence that Vitally's automation is superior for small teams
Content Optimization · Content · 1 queries, personas: Customer Success Team Lead
21
Add 'top CS platforms besides Gainsight for workflow automation' positioning to /features/automation
The /features/automation page does not include a 'Gainsight alternative for workflow automation' positioning section — buyers who have pre-rejected Gainsight for cost or complexity reasons cannot find Vitally as the recommended next option
Content Optimization · Content · 1 queries, personas: VP of Customer Success
22
Add AI evaluation criteria section to /product/ai for requirements-building queries
The /product/ai page is a feature marketing page, not an evaluation guide — it tells buyers what Vitally AI does but not what they should require from any CS platform AI or how to distinguish strong AI implementations from weak ones
Content Optimization · Content · 1 queries, personas: VP of Customer Success
23
Add AI time-savings benchmark section to /product/ai for consensus-creation queries
The /product/ai page has no productivity benchmark content — 'how much time does AI actually save per CSM per week' cannot be answered from this page, making Vitally invisible for consensus-creation queries that require shareable evidence
Content Optimization · Content · 1 queries, personas: Head of Customer Success
24
Add CS leader social proof section to /features/health-scores for Validation queries
The /features/health-scores page has no customer voice content — no testimonials, G2 excerpts, or case study references from CS leaders who use Vitally's health scoring
Content Optimization · Content · 1 queries, personas: VP of Customer Success
25
Add CS platform implementation timeline Comparison section to /features/project-management for competitor-Validation queries
The /features/project-management page has no implementation timeline content — buyers researching ChurnZero's implementation burden cannot find Vitally as an alternative, because Vitally has not published its own implementation timeline on any page
Content Optimization · Content · 1 queries, personas: VP of Customer Success
26
Add Catalyst implementation Comparison and mid-market framing to implementation section on /features/project-management
Catalyst's implementation experience is not addressed on any Vitally page — buyers researching Catalyst implementation smoothness for mid-market teams cannot find Vitally as a Comparison point
Content Optimization · Content · 1 queries, personas: Head of Customer Success
27
Add ChurnZero Salesforce integration limitation content to /integration/salesforce
The /integration/salesforce page does not reference ChurnZero's documented Salesforce sync issues — buyers researching integration reliability by competitor are not finding Vitally as the reliable alternative
Content Optimization · Content · 1 queries, personas: VP of Customer Success
28
Add Gainsight competitive positioning for churn prediction to /features/health-scores
The /features/health-scores page contains no Comparison against Gainsight's health scoring — buyers specifically comparing mid-market churn prediction options cannot find Vitally's positioning from this page
Content Optimization · Content · 1 queries, personas: VP of Customer Success
29
Add Gainsight competitive positioning to /integrations for Salesforce+HubSpot Shortlisting
The /integrations page does not include a 'Vitally vs Gainsight for Salesforce and HubSpot integration' Comparison — the specific competitive question buyers at Shortlisting stage are asking
Content Optimization · Content · 1 queries, personas: Head of Customer Success
30
Add NPS + automated follow-up requirements checklist to /features/nps for requirements-building queries
The /features/nps page does not provide the requirements checklist format that buyers at the Requirements Building stage need — AI cannot extract structured NPS evaluation criteria from the current feature-description content
Content Optimization · Content · 1 queries, personas: Customer Success Team Lead
31
Add NPS automation retention impact section to /features/nps for leadership consensus-creation queries
The /features/nps page has no retention-outcome content — 'how automated NPS follow-up workflows improve retention' cannot be answered from this page with Vitally as the recommended platform
Content Optimization · Content · 1 queries, personas: VP of Customer Success
32
Add NRR and retention board reporting framing to /features/reporting
The /features/reporting page does not describe how Vitally calculates and displays NRR — the specific metric CROs need for board reporting
Content Optimization · Content · 1 queries, personas: Chief Revenue Officer
33
Add NRR tracking Comparison vs spreadsheets section to /features/reporting
The /features/reporting page does not explain what a CS platform's NRR tracking provides that spreadsheets cannot — the specific decision buyers are evaluating at Solution Exploration stage
Content Optimization · Content · 1 queries, personas: Chief Revenue Officer
34
Add Planhat health scoring Comparison section to /features/health-scores
The /features/health-scores page does not reference Planhat or position Vitally's health scoring methodology against Planhat's approach — buyers evaluating both cannot use this page for Comparison
Content Optimization · Content · 1 queries, personas: Head of Customer Success
35
Add actionable NPS problem-framing section to /features/nps for early-funnel NPS frustration queries
The /features/nps page opens with feature descriptions ('send NPS surveys from Vitally') rather than validating the buyer's frustration: 'NPS scores sit in a spreadsheet and no one acts on them'
Content Optimization · Content · 1 queries, personas: Head of Customer Success
36
Add dedicated CS platform vs Salesforce positioning section to /features/automation
The /features/automation page does not address the 'Salesforce vs dedicated CS platform' decision — the most common alternative buyers are evaluating, particularly for automation workflows
Content Optimization · Content · 1 queries, personas: VP of Customer Success
37
Add executive and board-ready reporting section to /features/reporting for leadership Validation queries
The /features/reporting page describes reporting features in product language ('build dashboards', 'export data') without showing what the executive-facing output looks like — no named metrics, no export format descriptions, no executive use case
Content Optimization · Content · 1 queries, personas: Head of Customer Success
38
Add executive dashboard competitive positioning to /features/reporting for Shortlisting
The /features/reporting page has no competitive positioning against Gainsight for executive dashboard quality — buyers Shortlisting for 'best executive dashboards for retention metrics' cannot find Vitally's position relative to Gainsight
Content Optimization · Content · 1 queries, personas: Chief Revenue Officer
39
Add executive reporting requirements framework to /features/reporting
The /features/reporting page is not structured as a requirements answer document — CROs cannot find which Vitally features address each of their executive reporting requirements
Content Optimization · Content · 1 queries, personas: Chief Revenue Officer
40
Add leadership portfolio visibility framing to /features/health-scores
The /features/health-scores page does not show or describe the leadership portfolio view — how a CRO or VP CS sees all account health scores across the entire book of business in a single dashboard
Content Optimization · Content · 1 queries, personas: Chief Revenue Officer
41
Add mid-market AI positioning section to /product/ai for segment-specific Shortlisting
The /product/ai page does not target mid-market B2B SaaS as the audience — 'mid-market' is not named, and the page describes AI features that apply equally to any company size, making it non-competitive for segment-specific Shortlisting queries
Content Optimization · Content · 1 queries, personas: Head of Customer Success
42
Add onboarding module evaluation checklist to /features/project-management for requirements-building queries
The /features/project-management page does not provide the requirements checklist format that buyers at the Requirements Building stage need — AI platforms cannot extract structured evaluation criteria from the current feature-description content
Content Optimization · Content · 1 queries, personas: Head of Customer Success
43
Add problem-framing section to /features/project-management for onboarding standardization early-funnel queries
The /features/project-management page opens with feature descriptions ('manage tasks, milestones, and playbooks') rather than validating the buyer's problem: 'onboarding quality varies by CSM and I cannot scale without fixing this'
Content Optimization · Content · 1 queries, personas: VP of Customer Success
44
Add problem-Validation section to /product/ai for early-funnel AI-scaling queries
The /product/ai page opens with Vitally AI feature descriptions rather than validating the category-level problem: 'can AI help CS teams manage more accounts without burning out?' — a buyer at Problem Identification stage who hasn't concluded AI is the solution cannot extract a direct answer
Content Optimization · Content · 1 queries, personas: VP of Customer Success
45
Add vendor evaluation questions section to /features/health-scores
The /features/health-scores page is structured as a product showcase, not as an answer to vendor evaluation questions — buyers building a requirements list cannot find Vitally's position on key questions (configurable weighting? ML vs rule-based? integration with Salesforce health fields?)
Content Optimization · Content · 1 queries, personas: VP of Customer Success
46
Add volume-specific Shortlisting positioning to /features/project-management for high-volume onboarding shortlist queries
The /features/project-management page does not name the volume tier ('50+ new customers per quarter') that defines this buyer's Shortlisting context — AI cannot match Vitally to volume-specific Shortlisting queries without this explicit qualifier
Content Optimization · Content · 1 queries, personas: Director of CS Operations
47
Reframe /features/health-scores to open with early churn detection buyer question
The /features/health-scores page opens with product feature framing ('configure your health score') rather than buyer pain framing — an AI responding to 'how do I know which customers are about to churn' cannot extract a direct answer from this page
Content Optimization · Content · 1 queries, personas: VP of Customer Success
48
Reframe /product/ai hero around CSM capacity outcome for Shortlisting queries
The /product/ai page buries the capacity outcome — the primary claim ('Vitally AI lets CSMs manage significantly more accounts without sacrificing relationship quality') is not stated in the hero, above the fold, or in any H2 heading that AI platforms would extract for Shortlisting queries
Content Optimization · Content · 1 queries, personas: VP of Customer Success
49
Competitor Comparison Pages Lack Visible Publication Dates
All 5 competitor Comparison pages (vs. Gainsight, ChurnZero, Totango, Planhat, Catalyst) display no visible publication or last-updated date. The only temporal references are G2 badge descriptions mentioning 'Summer 2025'. Combined with the sitemap's missing lastmod timestamps, AI crawlers have no signal for when this Comparison content was created or last verified.
Technical Fix · Content · 5 competitor Comparison pages (vs. Gainsight, ChurnZero, Totango, Planhat, Catalyst)
50
Multiple H1 Tags on Most Commercial Pages
The majority of product, feature, and Comparison pages use multiple H1 tags — ranging from 4 to 14 H1 elements per page. For example, the CSM solution page has 14 H1 tags, Comparison pages average 8 H1 tags, and product pillar pages (Productivity, AI, Visibility) each have 6-7 H1 tags. Only the individual feature pages (NPS, Surveys, Note-Taking, Automation) and case study pages maintain a single H1.
Technical Fix · Engineering · Approximately 20 of 35 commercial pages, including all Comparison pages, product pillar pages, and solution pages
51
Schema Markup Cannot Be Verified — Manual Check Recommended
Our analysis method returns rendered page content as markdown text, which does not include JSON-LD schema markup, meta descriptions, or Open Graph tags. We cannot determine whether appropriate schema types (Product, FAQPage, Article, Organization) are present on any page.
Technical Fix · Engineering · All 35 analyzed pages — verification needed
52
Sitemap Lacks lastmod Timestamps on All 1,000+ URLs
The sitemap.xml at https://www.vitally.io/sitemap.xml contains over 1,000 URLs but none include lastmod, changefreq, or priority attributes. Every entry contains only the <loc> element.
Technical Fix · Engineering · All 1,000+ URLs in sitemap.xml
53
Near-rebuild: /features/automation cannot deliver evaluation criteria artifact — inform NIO 004 blueprint
The /features/automation page is a product showcase, not an evaluation framework — it cannot serve a buyer who is writing evaluation criteria for a vendor selection process
Content Optimization → New Content · Content · 1 queries, personas: Customer Success Team Lead
54
Team Knowledge Continuity: CSM Turnover Risk Content Gap
Vitally's Team Collaboration & Shared Docs feature shows 37.5% visibility (3/8 queries) and 33.3% wins (1/3 visible). All 7 L3 queries carry 'thin' coverage status — collaboration features exist but are described as product capabilities rather than as a solution to the specific buyer pain of CSM turnover creating irreversible customer knowledge loss.
New Content · Content · 7 queries affecting personas: Customer Success Team Lead, Director of CS Operations, VP of Customer Success
55
Add 'CS platform vs Salesforce build' decision framework to /integrations
The /integrations page does not address the 'build on Salesforce vs buy a dedicated CS platform' decision — the most common architectural decision CS teams face before entering the CS platform evaluation process
Content Optimization · Content · 1 queries, personas: Director of CS Operations
56
Add 'better than internal health scoring' positioning to /features/health-scores
The /features/health-scores page has no content addressing why purpose-built CS platform health scoring outperforms homegrown solutions — buyers who built internally need to understand the specific gaps they are filling
Content Optimization · Content · 1 queries, personas: Customer Success Team Lead
57
Add 'building health scoring from spreadsheets' buyer framing to /features/health-scores
The /features/health-scores page does not explain what data a health score needs to be predictive — buyers migrating from spreadsheets need a concrete list of inputs (product usage events, CRM data, support tickets, NPS scores) to evaluate whether Vitally can ingest their data
Content Optimization · Content · 1 queries, personas: Director of CS Operations
58
Add 'how health scoring models work in practice' methodology section to /features/health-scores
The /features/health-scores page does not explain Vitally's health score methodology — whether signals are weighted manually, automatically, or via ML — leaving buyers unable to evaluate prediction accuracy
Content Optimization · Content · 1 queries, personas: Customer Success Team Lead
59
Add 'migrating from homegrown health scoring' framing to /features/health-scores
The /features/health-scores page assumes the buyer has no current health scoring solution — it does not address the specific evaluation concerns of teams migrating from a homegrown system (data migration, scoring parity, transition period)
Content Optimization · Content · 1 queries, personas: Head of Customer Success
60
Add 'when a CS platform makes sense' inflection-point framing to /features/automation
The /features/automation page does not address the 'is it time to move to a CS platform?' question — buyers at this stage need a concrete threshold (e.g., '50+ accounts per CSM,' '5+ person CS team') to self-qualify
Content Optimization · Content · 1 queries, personas: Head of Customer Success
61
Add ChurnZero UI Comparison to /customer-success-platforms/vitally-vs-ChurnZero
The /vitally-vs-ChurnZero page does not reference ChurnZero's widely documented G2 review complaints about UI complexity and navigation difficulty — missing the specific Validation concern buyers have
Content Optimization · Content · 1 queries, personas: Customer Success Team Lead
62
Add HubSpot+Segment+Zendesk integration requirements content to /integrations
The /integrations page does not explain how Vitally ingests and combines data from HubSpot (CRM), Segment (product analytics), and Zendesk (support) into a unified customer profile — the specific multi-tool architecture this buyer is evaluating
Content Optimization · Content · 1 queries, personas: Director of CS Operations
63
Add Planhat Salesforce bidirectional sync reliability Comparison to /integration/salesforce
The /integration/salesforce page does not explicitly describe bidirectional sync capability — the buyer specifically wants to know if data flows both ways between Vitally and Salesforce
Content Optimization · Content · 1 queries, personas: Director of CS Operations
64
Add Totango Salesforce/HubSpot sync reliability Comparison to /integration/salesforce
The /integration/salesforce page does not address Totango's documented Salesforce/HubSpot sync reliability problems — buyers researching Totango alternatives for integration reliability cannot find Vitally as the answer
Content Optimization · Content · 1 queries, personas: Director of CS Operations
65
Add Totango automation limitation competitive content to /customer-success-platforms/vitally-vs-Totango
The /vitally-vs-Totango page does not reference G2 review data on Totango's specific automation limitations — the page makes comparative claims without citing the third-party evidence buyers use at Validation stage
Content Optimization · Content · 1 queries, personas: Director of CS Operations
66
Add Totango implementation risk Comparison to /customer-success-platforms/vitally-vs-Totango
The /vitally-vs-Totango page does not address Totango's documented implementation risks for companies without a dedicated CS ops team — the specific buyer context in this query
Content Optimization · Content · 1 queries, personas: VP of Customer Success
67
Add built-in vs standalone NPS Comparison framework to /features/nps for solution-exploration queries
The /features/nps page does not address the 'built-in CS platform NPS vs standalone NPS tool' decision — a buyer comparing these approaches cannot use this page to understand where Vitally fits in the decision landscape
Content Optimization · Content · 1 queries, personas: Customer Success Team Lead
68
Add buyer-pain framing for CRM manual work to /features/automation
The /features/automation page leads with product capability descriptions rather than the buyer pain — CSMs spending 60-70% of their time on admin tasks rather than customer interaction
Content Optimization · Content · 1 queries, personas: Customer Success Team Lead
69
Add buyer-pain framing for fragmented customer data to /integrations
The /integrations page opens with a list of available integrations rather than framing the buyer pain — a CS ops manager who needs to consolidate five tools cannot quickly determine from this page whether Vitally solves their specific data fragmentation problem
Content Optimization · Content · 1 queries, personas: Director of CS Operations
70
Add implementation speed positioning to /features/automation and vitally-vs Comparison pages
The /features/automation page does not include implementation timeline data — buyers looking for faster alternatives to Gainsight or their current tool need a specific time-to-value claim (e.g., 'first automated playbook running in 2 weeks')
Content Optimization · Content · 1 queries, personas: Head of Customer Success
71
Add must-have vs nice-to-have evaluation framework to /features/automation
The /features/automation page lists every automation capability without distinguishing which are foundational vs advanced — buyers building requirements lists cannot determine what to prioritize from this page
Content Optimization · Content · 1 queries, personas: Customer Success Team Lead
72
Add requirements framing for 200-person SaaS to /integrations page
The /integrations page presents integrations as an undifferentiated catalog — buyers at Requirements Building stage cannot determine which integrations are critical for a 200-person SaaS running Salesforce vs other profiles
Content Optimization · Content · 1 queries, personas: Director of CS Operations
73
Add two-approach onboarding framework section to /features/project-management for solution-exploration queries
The /features/project-management page does not frame Vitally's approach within the broader 'milestone vs playbook' solution landscape — a buyer comparing approaches cannot use this page to understand where Vitally fits in the decision
Content Optimization · Content · 1 queries, personas: Director of CS Operations
74
Restructure /product/ai into an AI use-case taxonomy for solution-exploration queries
The /product/ai page does not provide the category taxonomy a buyer uses to evaluate AI in CS — 'account summaries, next-best-action, risk alerts, automated communications' need to be organized as distinct use-case categories with H3 headings, not scattered across marketing copy
Content Optimization · Content · 1 queries, personas: Customer Success Team Lead
75
Client-Side Rendering Status Cannot Be Verified
Our analysis method cannot detect whether pages rely on client-side rendering (CSR) frameworks like React, Angular, or Vue that may block AI crawlers from accessing content. All pages returned substantive text content through our fetch method, suggesting server-side rendering is likely in place, but this cannot be confirmed without inspecting raw HTML source and testing with JavaScript disabled.
Technical Fix · Engineering · All pages — verification needed, but likely not an issue based on observed content rendering
76
Meta Descriptions and OG Tags Cannot Be Verified — Manual Check Recommended
Meta descriptions and Open Graph tags are not visible in rendered markdown output. We cannot verify whether commercial pages have unique, keyword-optimized meta descriptions or proper OG tags for social sharing and AI context.
Technical Fix · Marketing · All 35 analyzed pages — verification needed
77
Add NPS response rate evidence section to /features/nps for CRO Validation queries
The /features/nps page has no response rate data — 'which CS platforms' NPS surveys actually get good response rates' cannot be answered with Vitally as the recommended platform because no response rate evidence exists on the page
Content Optimization · Content · 1 queries, personas: Chief Revenue Officer
78
Add Vitally AI vs Gainsight AI Comparison section to /product/ai for direct AI Comparison queries
Without a 'Vitally AI vs Gainsight AI' section, AI platforms answering 'which platforms compete with Gainsight's AI' cannot include Vitally — there is no Vitally-sourced Comparison content to cite
Content Optimization · Content · 1 queries, personas: Customer Success Team Lead
79
Add multi-vendor AI capability matrix to /product/ai for multi-platform Comparison queries
Vitally has no multi-vendor AI Comparison content — AI platforms generating a '2026 AI feature Comparison across CS platforms' cannot include Vitally because there is no Vitally-sourced data for the Comparison matrix
Content Optimization · Content · 1 queries, personas: Director of CS Operations
80
Reframe /features/project-management around time-to-value outcome for CRO Shortlisting queries
The /features/project-management page's value proposition is framed in product language, not the business outcome language (time-to-value, first-year retention impact) that CRO Shortlisting queries require
Content Optimization · Content · 1 queries, personas: Chief Revenue Officer

Workstream Mapping

All three workstreams can start this week.

Engineering / DevOps

Layer 1 — Technical Fixes

Timeline: Days to 2 weeks

Broken Pages Linked from Site Navigation
Sitemap Lacks lastmod Timestamps on All 1,000+ URLs
Multiple H1 Tags on Most Commercial Pages
Competitor Comparison Pages Lack Visible Publication Dates

Content Team

Layer 2 — Content Optimization

Timeline: 2–6 weeks

Reframe /features/health-scores to open with early churn…
Add 'building health scoring from spreadsheets' buyer…
Add 'how health scoring models work in practice'…
Near-rebuild: /features/health-scores requires churn…

Content Strategy

Layer 3 — NIOs + Off-Domain

Timeline: 1–3 months

Create /product/expansion or /features/renewals as a…
Create /integration/amplitude, /integration/mixpanel, and…
Create /enterprise or /customers/scale page documenting…
Create /features/Customer Segmentation & Lifecycle Management or expand…
Reframe the collaboration/notes feature page to lead with…

[Synthesis] The 142 recommendations execute in L1-first sequence regardless of commercial priority ranking, because two L1 fixes specifically unblock downstream content: restoring the broken /customer-success-platforms hub enables AI crawler discovery of all 5 Comparison pages, and adding sitemap lastmod timestamps signals freshness for all 68 new L3 pieces as they publish. L2 remediations deepen 67 existing pages — the majority targeting practitioner-to-decision-maker content reframes on health scoring, workflow automation, reporting, and CRM integration pages. L3 new content fills six structural gaps: expansion revenue intelligence (13 queries), enterprise scalability (14 queries), Comparison content architecture (15 queries), product usage tracking (10 queries), digital-touch Customer Segmentation & Lifecycle Management (9 queries), and team knowledge continuity (7 queries).

TL;DR

Visibility

Win Rate

Share of Voice (SOV)

Buying Jobs

NIO

L1 / L2 / L3

Citation

Invisible Query

Platform Visibility

Visibility by Buying Job

Visibility & Win Rate by Persona

Visibility by Feature Focus

Visibility by Pain Point

Invisibility Gaps — 75 Queries Where Vitally Doesn’t Appear

Positioning Gaps — 60 Queries Where Vitally Appears But Loses

Share of Voice

Head-to-Head Records

Invisible Query Winners

Top Cited Domains (citation instances)

Vitally URL Citations by Page

Competitor URL Citations

Third-Party Citation Gaps

Layer 1 Technical Fixes

Verification Checks

Layer 2 Existing Content Optimization

Add CS platform ROI and payback period section to /features/reporting for CRO consensus queries

Add CS platform TCO framework section to /features/reporting for CRO artifact-creation queries

Create an AI capability Comparison matrix artifact on /product/ai for vendor evaluation artifact queries

Create an onboarding playbook template artifact section on /features/project-management for artifact-creation queries

Add Gainsight reporting limitations section and Comparison table to /features/reporting for competitor-Validation queries

Add onboarding standardization and retention benchmark section to /features/project-management for consensus-creation queries

Near-rebuild: /features/health-scores cannot answer CFO business case queries — inform NIO 001 blueprint

Near-rebuild: /features/health-scores requires churn reduction benchmark content for Consensus Creation queries

Near-rebuild: /features/health-scores requires new Comparison matrix for Artifact Creation queries

Near-rebuild: /integrations requires multi-vendor Comparison scorecard artifact — inform NIO 006 blueprint

Near-rebuild: NRR improvement case studies require new content — inform NIO 001 blueprint

Add 'Gainsight vs ChurnZero playbook automation for small CS teams' section to /customer-success-platforms/vitally-vs-Gainsight

Add 'Gainsight vs Totango and where Vitally fits' section to /customer-success-platforms/vitally-vs-Gainsight

Add 'switching from Totango for better automation' competitive content to /customer-success-platforms/vitally-vs-Totango

Add 'top CS platforms besides Gainsight for workflow automation' positioning to /features/automation

Add AI evaluation criteria section to /product/ai for requirements-building queries

Add AI time-savings benchmark section to /product/ai for consensus-creation queries

Add CS leader social proof section to /features/health-scores for Validation queries

Add CS platform implementation timeline Comparison section to /features/project-management for competitor-Validation queries

Add Catalyst implementation Comparison and mid-market framing to implementation section on /features/project-management

Add ChurnZero Salesforce integration limitation content to /integration/salesforce

Add Gainsight competitive positioning for churn prediction to /features/health-scores

Add Gainsight competitive positioning to /integrations for Salesforce+HubSpot Shortlisting

Add NPS + automated follow-up requirements checklist to /features/nps for requirements-building queries

Add NPS automation retention impact section to /features/nps for leadership consensus-creation queries

Add NRR and retention board reporting framing to /features/reporting

Add NRR tracking Comparison vs spreadsheets section to /features/reporting

Add Planhat health scoring Comparison section to /features/health-scores

Add actionable NPS problem-framing section to /features/nps for early-funnel NPS frustration queries

Add dedicated CS platform vs Salesforce positioning section to /features/automation

Add executive and board-ready reporting section to /features/reporting for leadership Validation queries

Add executive dashboard competitive positioning to /features/reporting for Shortlisting

Add executive reporting requirements framework to /features/reporting

Add leadership portfolio visibility framing to /features/health-scores

Add mid-market AI positioning section to /product/ai for segment-specific Shortlisting

Add onboarding module evaluation checklist to /features/project-management for requirements-building queries

Add problem-framing section to /features/project-management for onboarding standardization early-funnel queries

Add problem-Validation section to /product/ai for early-funnel AI-scaling queries

Add vendor evaluation questions section to /features/health-scores

Add volume-specific Shortlisting positioning to /features/project-management for high-volume onboarding shortlist queries

Reframe /features/health-scores to open with early churn detection buyer question

Reframe /product/ai hero around CSM capacity outcome for Shortlisting queries

Near-rebuild: /features/automation cannot deliver evaluation criteria artifact — inform NIO 004 blueprint

Add 'CS platform vs Salesforce build' decision framework to /integrations

Add 'better than internal health scoring' positioning to /features/health-scores

Add 'building health scoring from spreadsheets' buyer framing to /features/health-scores

Add 'how health scoring models work in practice' methodology section to /features/health-scores

Add 'migrating from homegrown health scoring' framing to /features/health-scores

Add 'when a CS platform makes sense' inflection-point framing to /features/automation

Add ChurnZero UI Comparison to /customer-success-platforms/vitally-vs-ChurnZero

Add HubSpot+Segment+Zendesk integration requirements content to /integrations

Add Planhat Salesforce bidirectional sync reliability Comparison to /integration/salesforce

Add Totango Salesforce/HubSpot sync reliability Comparison to /integration/salesforce

Add Totango automation limitation competitive content to /customer-success-platforms/vitally-vs-Totango