# Best practices for when and how often to rescan your website.

1. **After Implementing Fixes (The Right Way):** The primary use of the rescan feature is to see the results of your hard work. However, for changes to be effective, they need time to be recognized by search engines.
   * **Follow the "Instant Fix Checklist" Guidance:** Each recommendation in your checklist includes an estimated timeframe for "Results" (e.g., "1-2 weeks"). **It is highly recommended to wait for this suggested period before rescanning.** Rescanning too early may not capture the full impact of your changes.
   * **Workflow:** Implement a batch of fixes -> Wait for the recommended time -> Rescan to see your new score.
2. **After Major Website Changes:** If you've undertaken a significant website overhaul, such as a site redesign, a large content update, or a structural change, a rescan is essential to establish a new performance baseline.
3. **For Marketing Campaigns:** Use Flensh to measure the impact of your marketing efforts.
   * **Before the Campaign:** Run a scan on the campaign's landing page to get a baseline AI Visibility Score. Use the "Instant Fix Checklist" to optimize the page before you launch.
   * **After the Campaign:** Once the campaign has run its course, rescan the page. An increase in score can indicate that the campaign successfully improved the page's authority and relevance in the eyes of AI engines, providing a new metric for campaign ROI.
4. **For Regular Check-ups:** The digital landscape and your competition are constantly evolving. It's a good practice to rescan your key websites on a regular schedule (e.g., quarterly) to stay ahead of new trends and keep your top rankings secure.


---

# 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.7.-rescanning-and-tracking-progress/best-practices-for-when-and-how-often-to-rescan-your-website..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.