> ## Documentation Index
> Fetch the complete documentation index at: https://docs.aeolo.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Rewrite articles from a Drive folder

> Import Google Docs and review one draft per original.

Use a Drive folder to rewrite an existing collection of articles. Each imported original gets its own writing job and draft. The Drive source folder and your website path are independent settings.

## Import the originals

1. Select the correct brand and open **Content import** in Aeolo.
2. Connect the Google account that can read the shared documents.
3. Open the folder containing the Google Docs in the file picker and select the documents to import. Grant access to the actual files when prompted; folder access alone may not grant the app access to its contents.
4. Check the imported folder, titles and full original text before starting.

Files are grouped by their direct parent folder. Selecting a parent does not recursively import all nested folders. This workflow imports Google Docs; see [Drive and data sources](/cli/drive-data-sources) for other source reads.

The imported text is a saved snapshot. Editing the Google Doc later does not silently replace the original used by an existing writing job. Inspect the saved original before commissioning a rewrite.

## Prepare a batch in Aeolo chat

Finish uploading first, then ask the dashboard agent:

```text theme={null}
Prepare a rewrite batch for the imported folder "Approved articles".
Use only its originals, one writing job per original.
Preserve facts, conditions, exceptions, questions and evidence.
Show the folder and total count before starting. Save drafts only.
```

The agent resolves the imported folder and prepares a fixed list of originals. Select the intended folder if names are ambiguous. Preparation does not start generation or consume writing credits.

Review the folder, count and paid draft-generation scope, then explicitly tell the agent to start that batch. If the folder changed since preparation, prepare again and confirm the new scope.

## After confirmation

The server registers a durable batch and returns its job ID. Workers create or reuse one writing job for each original in the snapshot. Closing the chat does not discard the registered batch.

This starts an immediate batch, not a recurring or future calendar schedule. Later uploads are not silently added. Automatic translation and publication are disabled for this workflow.

Ask for the status of that batch ID. Registration is not completion: inspect individual writing-job results and failures. Existing jobs, including failed ones, are not duplicated by repeating the same request. Investigate failed items before requesting recovery.

## Review before publishing

The rewrite aims to preserve original information while improving answer structure, specific headings, evidence placement and question coverage. Retain conditions and exceptions; correct outdated claims only with evidence. Missing facts and unresolved claims need review. A completed job is not editorial approval.

Compare the draft with its saved original:

* Are facts, numbers, dates, requirements and exceptions retained or explicitly corrected?
* Do the original questions still receive answers?
* Do citations support the exact claims next to them?
* Are new claims supported and brand recommendations appropriate?

Results remain drafts. Publication requires separate approval and a destination; specialist review may also be needed. Better structure alone does not prove higher AI-search visibility. Measure that after approved publication.

## Troubleshooting

| Symptom | Next step |
| - | - |
| Empty folder in the Google picker | Check the account, sharing permissions and direct folder; select the Docs themselves to grant access |
| Wrong batch count | Finish importing, inspect the saved folder, then prepare again |
| Suspected duplicate request | Look up original batch/job IDs before starting another operation |
| Failed or incomplete draft | Read per-article results and review findings; do not treat it as approved |

Prepare the destination with the [subfolder connection guide](/guides/subfolder-connection).


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