> ## 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.

# Project Overview

> Orient yourself in a Project, then open the evidence behind each change.

**Overview** is the starting point for one Project. It brings recent measurements and work needing attention into one place. Use it to decide where to investigate; open the relevant product area before deciding what caused a change.

## Find your way around

In your Project's **Visibility** navigation:

* **Overview** summarizes the Project.
* **Analytics** opens Share of Voice, Mentions, Citations, and Competitors.
* **Prompts** opens Performance and Library.
* **Analysis History** shows completed Analyses and their reports.

**Content Studio** and **Technical Audit** are separate places to plan content work and investigate Website findings.

## A useful first review

<Steps>
  <Step title="Choose a Project">
    Open the Project whose Brand and Market you want to review. Check the Project name before interpreting its measurements.
  </Step>

  <Step title="Read the current summary">
    Note the latest AI Visibility and Share of Voice alongside the available history. Treat a single Analysis as a snapshot.
  </Step>

  <Step title="Open the underlying evidence">
    Use **Mentions** to inspect text appearances, **Citations** to inspect source links, and **Prompts → Performance** to see which Prompts produced the results.
  </Step>

  <Step title="Choose a next action">
    Open a Content Opportunity in **Content Studio** or a Finding in **Technical Audit**. Check its evidence, affected scope, and status before assigning work.
  </Step>
</Steps>

## Compare like with like

A change in the active Prompt Library, AI Platforms, or available response captures can change the measurement scope. When a number moves, compare the Analyses in **Analysis History** and inspect the underlying responses before attributing the movement to a recent edit.

For a Technical Audit fix, run a new **Audit Run** and compare the Finding there. An Analysis measures AI responses; a Technical Audit checks the Website.

## Next steps

<CardGroup cols={2}>
  <Card title="Understand the measurements" icon="ruler" href="/metrics/overview">
    Read what each Metric counts and how to compare it.
  </Card>

  <Card title="Review Technical Audit" icon="list-check" href="/features/geo-audit">
    Investigate Findings and check a deployed fix.
  </Card>

  <Card title="Work on a content gap" icon="lightbulb" href="/features/content-gaps">
    Move from evidence to a Content Brief and Article.
  </Card>

  <Card title="Ask Sira" icon="sparkles" href="/how-to/work-with-sira">
    Give Sira a specific Project question and review its evidence.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.