> ## Documentation Index
> Fetch the complete documentation index at: https://www.octoparse.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Who is it for?

> Octoparse is built for people and teams who need structured web data but don't want to build and maintain scrapers from scratch themselves.

Octoparse is built for teams that need structured web data but do not want every extraction workflow to become an engineering project.

It is especially useful when the data is available on websites, changes regularly, and needs to be collected repeatedly for research, operations, sales, pricing, or reporting workflows.

## Common users

> [card] Analysts and researchers
>
> Collect market data, public datasets, directory listings, product information, and competitor signals for analysis.

> [card] Growth and sales teams
>
> Build lead lists, enrich prospect data, monitor business directories, and collect public company information.

> [card] E-commerce teams
>
> Monitor product listings, prices, reviews, inventory signals, and marketplace content across multiple sites.

> [card] Operations teams
>
> Automate recurring data collection and export results to spreadsheets, databases, or shared destinations.

## When Octoparse is a good fit

Octoparse is a good fit when:

* The data is visible or accessible on a website
* The website requires browser interaction, such as clicking, scrolling, pagination, or login
* The data needs to be collected repeatedly
* The task can be defined as a repeatable workflow
* Non-developers need to build or maintain the extraction process
* The output needs to be exported to files, sheets, databases, or other systems

Octoparse is often used when teams need flexibility: the target websites may not offer APIs, the page structure may vary, or the workflow needs to be adjusted without waiting for engineering resources.

## When another approach may be better

Octoparse is not always the right tool. Consider another approach when:

| Situation | Better approach |
| - | - |
| The website provides a complete and stable official API | Use the official API directly |
| The workflow requires heavy custom logic or application-specific code | Build a custom integration |
| The target data is not permitted to be collected | Do not scrape it |
| The data needs complex analysis or visualization | Use Octoparse for collection, then process the data in analytics tools |

> [!WARNING]
>
> Always make sure your data collection follows the target website's terms, applicable laws, and internal compliance requirements.

## Teams

On the Enterprise plan, your organization gets one admin account, plus agent accounts for your team members. The admin account allocates the account's cloud and anti-blocking resources to agent accounts and can see their cloud tasks. Agent accounts see only their own tasks. See [Enterprise](https://www.octoparse.com/docs/en/account.md#enterprise-admin-and-agent-accounts).

## Related pages

> [card] [How it works](https://www.octoparse.com/docs/en/what-is-octoparse.md#how-it-works)
>
> See the basic build, run, and export workflow.

> [card] [Core concepts](https://www.octoparse.com/docs/en/core-concepts.md)
>
> Learn the main terms used across Octoparse.


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