# How is the score calculated? (A high-level, transparent explanation).

Your score is not an arbitrary number; it's the result of a multi-step, data-driven analysis that happens in real-time when you run a scan. Here’s a simplified breakdown of how Flensh calculates it:

1. **Multi-Engine Analysis:** Flensh evaluates your website's performance across five major AI platforms (ChatGPT, Claude, Perplexity, Gemini, and Bing Chat). It assesses how well your content aligns with the unique ranking preferences of each engine.
2. **Content and Authority Assessment:** The system analyzes your site's content for key Generative Engine Optimization (GEO) factors, including:
   * **Answer Quality:** How well your content directly and clearly answers questions.
   * **Source Authority:** Signals of expertise, trust, and credibility.
   * **Content Structure:** The use of proper headings, lists, and structured data that AI can easily parse.
3. **Real-Time Competitive Research:** Flensh identifies the top-performing competitors in your specific niche and analyzes their content strategies and AI visibility.
4. **Weighted Average Calculation:** Your final AI Visibility Score is a weighted average of your performance across all the individual AI engines, benchmarked against your competitors. This provides a holistic and realistic measure of your position in the market.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://flensh.gitbook.io/flensh-docs/core-features-in-detail/2.2.-understanding-your-ai-visibility-score/how-is-the-score-calculated-a-high-level-transparent-explanation-..md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.