> ## Documentation Index > Fetch the complete documentation index at: https://docs.videntic.com/llms.txt > Use this file to discover all available pages before exploring further. # Review your first Analysis > Use your first results as a baseline and investigate the evidence behind them. After you finish [Project setup](/getting-started/quickstart), Videntic starts the initial measurement process. You arrive at **Project Overview** while work may still be running. This guide begins when an Analysis has completed; **Analysis History** shows its status. ## 1. Confirm the measurement scope Open **Prompts → Library**. Check that active Prompts reflect the questions your customers ask in the Project's Market. Remove irrelevant questions and correct wording before you build a long-term trend. Note the tracked Competitors, because changing that set changes the Share of Voice comparison. **Best practice:** keep a small stable set of core Prompts across Analyses. Add new questions when your business changes, and interpret the resulting trend with that scope change in mind. ## 2. Read AI Visibility In **Project Overview**, start with **AI Visibility** and its time window. It describes how often your Brand appears in planned AI response opportunities. It is a baseline for this Prompt set and Market, not a rank for the whole web. If the value is lower than expected, open **Dashboard → Analytics → Mentions**. Under **Mentions by Prompt**, expand a relevant Prompt and select a Mention to read the recorded AI Response. If there is no Mention to open, check the Prompt set and Analysis History before treating the absence as a content problem. A zero can reflect no accepted Brand Mentions in the planned opportunities; low response Coverage or a narrow Prompt set changes how useful that result is. ## 3. Compare Brands and sources Open **Dashboard → Analytics → Share of Voice** with the **Mentions** share basis selected to compare your Brand with tracked Competitors in Mentioning Responses. Select a cell in **Share of Voice by engine** to inspect the answers behind it. Then review **Mentions** and **Citations** separately. In **Citations Explorer**, **By prompt** opens the question's source links and recorded answer; **By page** starts from a cited URL. A Brand Mention does not require a source link, and a Citation is not the same as a Mention. See [Share of Voice](/metrics/share-of-voice). Look for repeated patterns across Prompts and AI Platforms before prioritizing work. One response is an example, not a trend. ## 4. Review Website findings separately Open **Technical Audit** for the Website's latest Audit Run and its scope. Focus on findings that apply to pages you control and can verify. The Audit Run has its own timing and score; it does not update automatically just because an Analysis completed. When you make a fix, publish it first, then start or wait for a new Audit Run to check whether the finding remains. Compare runs with the same Audit Scope and methodology where possible. ## 5. Choose one next action Pick a supported change with clear evidence: refine an irrelevant Prompt, correct a tracked Competitor, investigate a repeated content gap, or fix a confirmed Technical Audit issue. Record the date and scope of the change. Read later results as observations rather than guaranteed effects. ## Related Finish Project setup before reading results. Understand each measurement and its denominator. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.