> For the complete documentation index, see [llms.txt](https://gitbook.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.com/docs/guides/editing-and-publishing-documentation/find-and-replace-or-make-batch-changes-across-your-gitbook-docs-with-git-sync.md).

# Updating docs in bulk with GitBook Agent

Find, replace, and update content across your GitBook docs with GitBook Agent

{% hint style="warning" %}

#### GitBook now supports find & replace through GitBook Agent

Head to [GitBook Agent](/docs/gitbook-agent/overview.md) to learn more about using GitBook Agent to edit pages in bulk.
{% endhint %}

GitBook Agent can find and replace content across your documentation. It can also make broader, targeted updates in a change request.

Use GitBook Agent for routine bulk edits. It keeps changes together for review before you merge them.

### Start a bulk update

To make a bulk update:

1. In your space, click the GitBook Agent icon next to **Edit**.
2. Describe the change, the pages it affects, and any exclusions.
3. Click **Start change request**.
4. In **Changes**, review every proposed edit.
5. Merge the change request when the updates are correct.

### Write a focused prompt

If you want to make targeted changes to your documentation — such as a ‘find and replace’ process for an outdated or incorrect term — you can use a focused prompt. 

Be sure to include these details in your prompt:

* The text or content you want to change.
* The replacement or intended outcome.
* Any pages to include and content to exclude.

Here’s an simple example prompt you could copy and customize:

{% prompt description="Find an replace content" %}

```markdown
Find all instances of “Gitbook” and replace them with “GitBook.” Ignore code blocks and URLs. Tell me how many replacements you make.
```

{% endprompt %}

For larger changes, it’s a good idea to also state the goal and constraints. If there are pages pages that define the correct wording or structure, reference them in the prompt to point the Agent in the right direction.

### Review bulk edits

GitBook Agent will make the updates in a change request. Be sure to review the change request and the diff before merging.

Pay particular attention to the following:

* Each replacement has the intended meaning.
* Links, formatting, and page structure remain correct.
* The change request excludes content outside the requested scope.

### FAQ

<details>

<summary>Can I still use Git Sync for bulk updates?</summary>

Yes. Git Sync creates a bidirectional connection with a GitHub or GitLab repository. Use it when your documentation follows a docs-as-code or CI/CD workflow, or you want to use a different AI agent (e.g. ChatGPT, Codex, Claude etc) to make changes to your documentation.

Create a branch, commit the changes, open a pull or merge request, and merge after review.

</details>

<details>

<summary>Can GitBook Agent exclude some matches?</summary>

Yes. Name the pages to include and content to exclude. For example, tell GitBook Agent to ignore code blocks, URLs, or a specific page.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://gitbook.com/docs/guides/editing-and-publishing-documentation/find-and-replace-or-make-batch-changes-across-your-gitbook-docs-with-git-sync.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.