Templates are prebuilt Octoparse tasks for common websites and data collection scenarios. They help you start faster by providing a ready-made workflow, field structure, and extraction setup. Use a template when you want to collect data from a supported website without building the task from scratch.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.
What templates include
A template may include:- Target website logic
- Predefined fields
- Pagination or list extraction settings
- Detail page extraction logic
- Built-in workflow actions
- Export-ready data structure
When to use a template
Templates are useful when:| Use case | Why templates help |
|---|---|
| You need data from a common website | The extraction workflow may already be configured |
| You want a faster setup path | You can start from a prebuilt task instead of selecting every field manually |
| The data structure is standard | Templates often provide common fields such as title, price, URL, rating, or contact information |
| You want to test feasibility quickly | Running a template helps confirm whether the website can be collected with minimal setup |
Template workflow
Configure required inputs
Some templates require URLs, keywords, categories, locations, or other parameters.
When to customize instead
A template may not be enough if:- The website page structure has changed
- You need fields the template does not include
- The website requires a special login or interaction flow
- You need custom cleanup or derived fields
- You want to combine multiple extraction paths
Templates are a starting point. Always test output quality before using template results in production workflows.
Related pages
Auto-detect
Generate a starting workflow from a page automatically.
No-code builder
Build or customize extraction workflows visually.