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

# Google Docs

Bring your Google Docs into Frase to teach it your brand or optimize existing drafts, then send briefs back to Docs for review.

## Connect Google Docs

{% stepper %}
{% step %}

### Open Settings

Go to **Settings → Integrations**, find Google Docs, and click **Connect**.
{% endstep %}

{% step %}

### Connect your account

Choose your Google account and click **Allow**.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**You can connect more than one account.** Disconnecting an account from *Integrations* removes it everywhere Frase used it.
{% endhint %}

## Using Google Docs in Frase

### Teach Frase your brand&#x20;

{% stepper %}
{% step %}

#### Open [**Brand Hub**](/feature-reference/brand-hub.md)&#x20;

Find it in the left sidebar. You should see a starting point from your onboarding's site crawl.&#x20;
{% endstep %}

{% step %}

#### Import your docs

* **Reference docs or terminology:** click **Import from Notion / Docs**, choose **Google Docs**, and pick the document.
* **Brand voice:** click **New Profile**, open the *Import* tab, choose **Google Docs**, and pick your voice guide.
  {% endstep %}

{% step %}

#### Finish the import

Set the site scope if needed, using universal docs across domains if you have them.&#x20;
{% endstep %}
{% endstepper %}

{% hint style="success" %}
Frase uses these docs to keep its writing on-brand and accurate. You can also add a Google Doc as a *Smart Source* when you [create content](https://docs.frase.io/using-frase/content-creation).
{% endhint %}

### Optimize a draft&#x20;

{% stepper %}
{% step %}

#### Import from Google Docs

Go to **Create → Content** and click **New Content.** Select **Optimize Existing**, then choose ***Google Docs.***
{% endstep %}

{% step %}

#### Pick the document&#x20;

You can link it to a site in Frase if you'd like.
{% endstep %}

{% step %}

#### Complete the import

Adjust the optimization settings and click **Import and Optimize**. Frase pulls in the full document so you can improve it with briefs, SERP insights, and AI tools.
{% endstep %}

{% step %}

#### Optimize the document

[Optimize your article](/core-workflows/optimize-existing-content.md) for SEO, GEO, and EEAT signals, so its ready to perform when it goes live.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**You can also push briefs back to Google Docs.** If you prefer to write or review content outside of our Editor, open a brief and click **Export** to bring it into a new or existing doc.
{% endhint %}


---

# 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://docs.frase.io/integrations/connectors/google-docs.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.
