# Best practices for adding and managing a large portfolio of websites.

A systematic approach is key to managing multiple client websites efficiently.

* **Establish a Clear Naming Convention:** This is the most critical practice for staying organized. When adding a new website, use the **"Website Name (Optional)"** field to assign a consistent, identifiable name.
  * **Best Practice:** Use a format like \[Client Name] - \[Website] (e.g., "Acme Corp - Main Site" or "Innovate Ltd - Blog"). This makes searching and identifying clients on the dashboard effortless.
* **Schedule Your Scans Systematically:** Instead of scanning randomly, set a recurring schedule. A great workflow is to rescan all client websites at the beginning of each month. This provides you with fresh data right before your monthly reporting cycle.
* **Prepare Information in Advance:** When onboarding a new batch of clients, have their URLs and chosen custom names ready in a separate document. This allows you to add them to your Flensh dashboard in a quick, streamlined session.
* **Choose the Right Plan:** Ensure your subscription plan (e.g., Agency) has enough website slots and monthly rescans to accommodate your entire client portfolio. You can check your current limits under Account Settings > Usage.


---

# 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/for-agencies-and-power-users/3.1.-bulk-website-management/best-practices-for-adding-and-managing-a-large-portfolio-of-websites..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.