Getting Started with the Optimize and Google Docs Integration

Thanks to Positional’s recently released Google Docs integration, you can now access Optimize, our content optimization toolset, within Google Docs.

First, you’ll want to generate a Positional API key. Head to Integrations within Positional and click on Create API Key (you’ll use this key in a later step):

Next, you’ll need to install our app from Google’s Workspace Marketplace:

Click on Admin Install if you are an administrator and you would like to install the app for all or some users in your organization. You can install apps for users even when you don't allow users to install apps themselves.

Click on Individual Install if you’d like to install an app for your account only.

After installing Positional, open a new Google Doc, go to Extensions, and select Positional > Optimize from the list of options:

You’ll see our Optimize editor appear on the right-hand side of your Google Docs document.

Next, copy and paste the Positional API key that you generated into the Optimize window.

After entering the API key, you’re good to go. You can now generate Optimize reports directly from the Optimize editor, within Google Docs.

You may notice that scoring and suggestions are slower to load and update when you’re using Optimize within Google Docs than when you’re using it inside Positional. This is normal, and unfortunately, given Google's requirements, there isn’t much we can do to improve performance.

If you have questions about using Optimize, our Knowledge Base has a training video and additional documentation.

Google Docs Integration FAQs:

Can two users share the same API key?

Yes.

If I make updates in Google Docs, will those updates be carried into the Positional editor?

No.

Can I access other tools via Google Docs, such as AutoDetect or Internals?

Not yet. However, integration with Google Docs is coming for these tools very soon.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.