# Crawl a documentation site to clean text: Flask docs

**Use case:** 

Crawls the Flask documentation and returns each page with its URL, title, H1, breadcrumbs, meta description, the clean text without menus and footers, the word count and the link depth. Change the start link to any site, set the depth, or keep only paths that match a pattern.

## Input

```json
{
  "startUrls": [
    "https://flask.palletsprojects.com/en/stable/"
  ],
  "maxDepth": 1,
  "maxPagesPerUrl": 20,
  "maxItems": 20,
  "proxyConfiguration": {
    "useApifyProxy": true
  }
}
```

## Output

```json
{
  "url": {
    "label": "Page URL",
    "format": "string"
  },
  "title": {
    "label": "Title",
    "format": "string"
  },
  "h1": {
    "label": "H1 Heading",
    "format": "string"
  },
  "breadcrumbs": {
    "label": "Breadcrumbs",
    "format": "array"
  },
  "description": {
    "label": "Description",
    "format": "text"
  },
  "textContent": {
    "label": "Text content",
    "format": "string"
  },
  "wordCount": {
    "label": "Word count",
    "format": "number"
  },
  "depth": {
    "label": "Crawl depth",
    "format": "number"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Website Content Crawler: Pages to Clean Text Actor is ready to run with the inputs already set for "Crawl a documentation site to clean text: Flask docs". [Sign up or log in](https://console.apify.com/create-task-from-example/7JlKtdPr2GYwcJSSf) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Crawl a documentation site to clean text: Flask docs" task

The Website Content Crawler: Pages to Clean Text Actor will start running based on the input automatically. You can also change all the input fields, like start urls, max crawl depth, and more, to match your specific use case.

### 3. Receive the "Crawl a documentation site to clean text: Flask docs" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as page url, title, h1 heading, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Crawl a documentation site to clean text: Flask docs" task via API](https://apify.com/v0iddo/website-content-crawler.md).

## About this Actor

This example demonstrates how to use [Website Content Crawler: Pages to Clean Text](https://apify.com/v0iddo/website-content-crawler.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/v0iddo/website-content-crawler.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/v0iddo/website-content-crawler.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).