> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/map.md).

# Firecrawl Map

Blocks for mapping website structure and discovering all links using Firecrawl.

## Firecrawl Map Website

### What it is

Firecrawl maps a website to extract all the links.

### How it works

This block uses Firecrawl's mapping API to discover all links on a website without extracting full content. It quickly scans the site structure and returns a comprehensive list of URLs found.

The block is useful for understanding site architecture before performing targeted scraping or for building site maps. Results include both the raw list of links and structured results with titles and descriptions.

### Inputs

| Input | Description            | Type | Required |
| ----- | ---------------------- | ---- | -------- |
| url   | The website url to map | str  | Yes      |

### Outputs

| Output  | Description                                             | Type                   |
| ------- | ------------------------------------------------------- | ---------------------- |
| error   | Error message if the map failed                         | str                    |
| links   | List of URLs found on the website                       | List\[str]             |
| results | List of search results with url, title, and description | List\[Dict\[str, Any]] |

### Possible use case

**Site Audit**: Map all pages on a website to identify broken links, orphan pages, or SEO issues.

**Crawl Planning**: Discover site structure before deciding which pages to scrape in detail.

**Content Discovery**: Find all blog posts, product pages, or documentation entries on a site.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agpt.co/docs/integrations/block-integrations/map.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.