Connecting Google Services to SEO & AEO Studio

Private Beta Feature

SEO & AEO Studio connects to two Google services, each optional. Connecting Google PageSpeed Insights adds PageSpeed scores to the Technical page, and connecting Google Search Console adds Google Search data to the Search Performance page.

Before connecting either service, you must add your domain. A Google Cloud project administrator can create the credentials: an API key for PageSpeed Insights or an OAuth client for Search Console. Once you have your credentials, you can configure PageSpeed Insights on the Configurations page and Search Console on the Settings page.

Connecting Google PageSpeed Insights

Connecting Google PageSpeed Insights requires an unrestricted API key from a Google Cloud project with the PageSpeed Insights API enabled. To create one, follow Google’s PageSpeed Insights API documentation. If your organization applies Websites application restrictions to this key, you must ensure https://ai.hub.liferay.com/ is explicitly allowed.

Open SEO & AEO Studio.
In the left navigation, click Configurations.
In the Integrations section, click Add Integration → Google PageSpeed Insights.
In the API Key field, enter your team’s API key.
Click Save.

SEO & AEO Studio validates the key with Google. If Google accepts it, the integration appears in the Integrations table.

Important

After you add the key, turn on the Google PageSpeed Insights engine in the Health Scan’s Scope section. Scans collect PageSpeed scores only while the engine is on, and the Technical page shows them after the next scan completes.

If the Studio can’t validate or save the key, one of these messages appears:

Message	Cause and Fix
Unable to connect to Google PageSpeed. Verify the configuration and try again.	Google rejected the key. Check that it’s unrestricted (or that its Websites restriction includes `https://ai.hub.liferay.com/`) and that its project has the PageSpeed Insights API enabled.
Unable to save API key.	The key couldn’t be stored. Save it again.
No domains were found. Add a domain first.	You haven’t added a domain. Add the domain and save the key again.

To change or remove the key, open the integration’s Actions () menu in the Configurations page’s Integrations table.

Connecting Google Search Console

Connecting Google Search Console requires an OAuth client from a Google Cloud project with the Search Console API enabled, and a Google account with access to the Search Console property that matches your domain.

You must configure the following settings in Google Cloud and your Google account before setting up this connection:

Search Console API: The project must have the Google Search Console API enabled, and its OAuth app must include the read-only Search Console scope (https://www.googleapis.com/auth/webmasters.readonly) in its data access.
OAuth App Audience: The OAuth app’s audience must be set to Internal if the account belongs to the project’s Google Workspace organization, or to External with its publishing status set to In production. If you leave an External app in Testing, Google revokes authorization seven days after sign-in.
Property Access: Ensure your Google account has at least Restricted permission on a Search Console property that matches the domain. The Studio looks for a match in this order: a URL-prefix property (https://www.example.com/), a Domain property for the host (www.example.com), then a Domain property for the host without www. (example.com).

To connect the service:

Open SEO & AEO Studio.
In the left navigation, click Settings.
In the Integrations section, click Add Integration → Google Search Console.
Click Copy next to the Authorized Redirect URI.
In Google Cloud, create or update a Web application OAuth client so its authorized redirect URIs include the exact URI you copied. If an administrator manages your project, send them the copied URI and ask for the client’s ID and secret.
Back in SEO & AEO Studio, enter the OAuth client’s ID and secret in the Google Client ID and Google Client Secret fields.
Click Save. A Google sign-in window opens.
Sign in with the account that has permission on the property, and grant the Studio read-only access to your Search Console data and your email address.

Important

If the OAuth app is External and unverified, Google displays an unverified app screen. You must proceed past this screen to grant consent. Closing the window cancels the connection.

If the connection succeeds, the integration appears in the Settings page’s Integrations table. Search Console data appears on the Search Performance page after the next daily fetch. See Data Refresh and Retention.

The Google Search Console page has fields for the Google client ID and client secret, and an Authorized Redirect URI to copy into the Google Cloud OAuth client.

Troubleshooting the Connection

If the connection fails, one of these messages appears:

Message	Cause and Fix
No domains were found. Add a domain first.	You haven’t added a domain. Add the domain.
Allow pop-ups and try again.	Your browser blocked the sign-in window. Enable browser pop-ups for this site.
No Google Search Console property matches this domain’s hostname. Update the domain’s hostname, or enter a Client ID and Secret from a Google account that has a matching property, then try again.	No Search Console property matches the domain. Ensure you sign in with an account that meets the property access requirements.
Google Search Console connection failed. Please verify your configuration and try again.	The connection failed for another reason. Check your client ID and secret, and confirm that the OAuth client in Google Cloud lists the exact Authorized Redirect URI.

If Google displays an error in the sign-in window (such as a redirect URI mismatch), close the window. No error message appears, but the Save button becomes available again. Correct the OAuth client settings in Google Cloud, wait a few minutes for Google to apply the change, then click Save again.

After your initial setup, you sign in to Google again only if you edit the integration or the connection drops. For example, if someone removes the OAuth app’s access from their Google account or Google’s authorization expires, Search Performance data stops updating. The integration’s status changes to UNAVAILABLE, and the Search Performance page displays a warning with a Reconnect button. If the OAuth client’s secret changes, data stops updating without a warning. To restore access, click Reconnect (or edit the integration), enter the current OAuth credentials, and click Save.

Disabling or Removing the Connection

You can edit, disable, or remove the connection using the integration’s Actions () menu in the Settings page’s Integrations table. Because only one Search Console integration is supported at a time, the Google Search Console option under Add Integration is disabled while an integration exists.

These actions control the daily fetch and your fetched data:

Disable: Stops the daily fetch and keeps already fetched data. Available while the integration is active.

Enable: Resumes the daily fetch. Available while the integration is disabled. Saving an edit also enables a disabled integration.

Remove Connection: Revokes the Studio’s access to Search Console and removes the integration. If you connect again, the next daily fetch loads up to 200 days of history.

Note

To stop fetching and keep your existing data, disable the integration.