> ## 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.

# Auto-detect

> Auto-detect scans a page, finds repeated lists, fields, and pagination, and generates a starting workflow you can review and adjust.

Auto-detect scans a web page, identifies repeated data patterns, and generates a starting extraction workflow — including data fields and pagination logic. It sits between [templates](https://www.octoparse.com/docs/en/templates/overview.md) (fastest, but limited to supported sites) and the [no-code builder](https://www.octoparse.com/docs/en/desktop/no-code-builder.md) (full manual control) in terms of effort and flexibility.

## When to use Auto-detect

Use Auto-detect when:

* The page has repeated items such as products, listings, reviews, or search results
* You want a quick starting workflow
* You are not sure which elements to select manually
* You want Octoparse to suggest fields and pagination logic
* You want to quickly preview what data can be extracted from a target website before committing to a full configuration
* You plan to review and adjust the generated workflow afterward

Auto-detect is a starting point, not a guarantee that every field or action will be correct.

## How Auto-detect works

Auto-detect analyzes the page DOM structure and visual layout, finds repeated data regions, and generates extraction rules automatically.

**1. Open the target page**

Start from the page that contains the data you want to extract.

**2. Run Auto-detect**

Octoparse scans the page, detects repeated data regions, and generates extraction fields. It also attempts to identify pagination or next-page buttons so the task can move through multiple result pages automatically.

**3. Review detected fields**

Check whether the suggested fields match the data you need.

**4. Confirm page navigation**

Review pagination, scrolling, or next-page actions. Auto-detect may identify a next-page button or infinite scroll pattern — verify that it works correctly before running at scale.

**5. Test the task**

Run a sample and verify the output before scaling the extraction.

## What to review after detection

After Auto-detect generates a workflow, check:

| Area | What to verify | How to fix |
| - | - | - |
| Fields | Are the correct values captured? | Re-select the element or adjust the XPath in the Data Preview panel |
| Field names | Are column names clear and meaningful? | Rename fields before export |
| Pagination | Does the task move to the next page correctly? | Manually set the next-page button or scroll action |
| Detail pages | Does the workflow open item details when needed? | Add a click action to enter detail pages |
| Duplicates | Are repeated or unwanted elements included? | Delete unwanted fields or rows in the Data Preview panel |
| Missing values | Are some rows missing important fields? | Add fields manually in the Data Preview panel |

## Known limitations

Auto-detect works best on pages with clear, repeated data structures. It may produce incomplete or inaccurate results in certain situations:

| Situation | What may happen |
| - | - |
| Non-standard or irregular page layout | Fields may be misidentified or missing |
| JavaScript-rendered dynamic content | Data that loads after the initial page render may not be detected |
| Sites with strong anti-bot protection | Auto-detect may fail to load or parse the page |
| Complex nested structures | The detected list may include incorrect or duplicate elements |
| Wrong field captured | The system may pick up promotional text instead of the actual value (e.g. a discount label instead of the real price) |

A common runtime error after Auto-detect is **"\[Loop Item] failed to find current loop item, exiting loop now"**, which usually means the generated XPath no longer matches the actual page elements. Re-running Auto-detect or manually adjusting the selector in the no-code builder typically resolves this.

## When manual editing is needed

Manual adjustments may be needed when:

* The page layout is irregular
* Important fields are outside the detected list
* The website loads content dynamically
* Pagination is not detected correctly
* The page requires login, filters, popups, or user interaction
* You need to extract data from detail pages

Use the no-code builder to refine the generated workflow.

If the workflow is generally correct and only its extraction fields need adjustment, use [AI Field Fixer](https://www.octoparse.com/docs/en/desktop/field-fixer.md) to describe the desired result in natural language and review the proposed change before applying it.

> [!WARNING]
>
> Do not assume Auto-detect output is production-ready. Always review fields, run a sample, and check the exported data.

## Related pages

> [card] [Templates](https://www.octoparse.com/docs/en/templates/overview.md)
>
> Start with a prebuilt workflow for common websites.

> [card] [No-code builder](https://www.octoparse.com/docs/en/desktop/no-code-builder.md)
>
> Adjust or build workflows manually after Auto-detect.

> [card] [AI Field Fixer](https://www.octoparse.com/docs/en/desktop/field-fixer.md)
>
> Review and adjust Auto-detected fields with natural language.

> [card] [Refine data](https://www.octoparse.com/docs/en/desktop/refine-data.md)
>
> Clean and reformat extracted fields before export.


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