Practical workflows for monitoring, analysis, reporting, APIs, citations, competitors, prompts, and model comparisons.
Each use case owns one operational job. The pages show the evidence to retain, the metric to use, and the interpretation risk to control.
Competitor Monitoring is useful when it preserves the question and answer evidence behind every metric, so teams tracking which alternatives enter AI-generated shortlists can distinguish an observation from an assumption.
Open the playbookCitation Tracking is useful when it preserves the question and answer evidence behind every metric, so SEO, content, and communications teams reviewing answer sources can distinguish an observation from an assumption.
Open the playbookBrand Monitoring is useful when it preserves the question and answer evidence behind every metric, so brand and growth teams measuring AI answer presence can distinguish an observation from an assumption.
Open the playbookSentiment Analysis is useful when it preserves the question and answer evidence behind every metric, so brand, communications, and product marketing teams can distinguish an observation from an assumption.
Open the playbookGap Analysis is useful when it preserves the question and answer evidence behind every metric, so growth teams deciding what to fix after an AI visibility audit can distinguish an observation from an assumption.
Open the playbookVisibility Reporting is useful when it preserves the question and answer evidence behind every metric, so teams turning answer evidence into a recurring operating report can distinguish an observation from an assumption.
Open the playbookModel Comparison is useful when it preserves the question and answer evidence behind every metric, so teams comparing how different AI systems answer the same commercial questions can distinguish an observation from an assumption.
Open the playbookPrompt Monitoring is useful when it preserves the question and answer evidence behind every metric, so teams running a stable portfolio of commercial AI questions can distinguish an observation from an assumption.
Open the playbookAI Search Monitoring is useful when it preserves the question and answer evidence behind every metric, so teams watching commercial discovery answers over time can distinguish an observation from an assumption.
Open the playbookExecutive Reporting is useful when it preserves the question and answer evidence behind every metric, so leaders who need a decision-ready view of AI recommendation risk can distinguish an observation from an assumption.
Open the playbookAgency Reporting is useful when it preserves the question and answer evidence behind every metric, so agencies producing comparable evidence for multiple clients can distinguish an observation from an assumption.
Open the playbookAI Visibility API is useful when it preserves the question and answer evidence behind every metric, so product and data teams integrating AI visibility evidence into internal systems can distinguish an observation from an assumption.
Open the playbookUse the methodology and audit template to define scope, record answers, review exceptions, and plan a comparable retest.
Analytics preferences
RecoProof uses optional Google Analytics to understand acquisition, product activation, and purchases. Advertising storage and personalization remain disabled. Rejecting analytics does not affect the product.