# How to read and understand the prioritized recommendations.

This checklist isn't just a random list of suggestions; it's a prioritized action plan based on your website's specific weaknesses and the potential for the most significant score improvement. Each item in the checklist is designed to be clear and actionable. Here’s how to interpret each part:

<figure><img src="/files/eKipstXhuZ5Q7t4ac9nC" alt=""><figcaption></figcaption></figure>

* **Title:** A concise summary of the task that needs to be done (e.g., "Add Comprehensive Meta Descriptions to Key Pages").
* **Priority (High/Medium/Low):** This is the most important indicator. **High-priority** tasks offer the biggest potential score increase and should be addressed first. Low-priority tasks are still beneficial but have a smaller impact.
* **Potential Points:** This number estimates how many points your overall AI Visibility Score could increase by if you successfully implement this fix. It directly correlates with the task's priority.
* **Description:** Provides clear, detailed steps on what you need to do to implement the fix and why it's important for AI visibility.
* **Difficulty (Easy/Medium/Hard):** This estimates the amount of effort or technical skill required. "Easy" fixes are often quick changes, while "Hard" fixes might involve more significant content or structural work.
* **AI Engines:** Shows which specific AI platforms (like ChatGPT, Gemini, etc.) will benefit most from this particular fix.
* **Time & Results:** Gives you a realistic estimate of how long the task might take to implement and when you can expect to see results after the changes are live.


---

# 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.4.-using-the-instant-fix-checklist/how-to-read-and-understand-the-prioritized-recommendations..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.