Access blocked: Authorization Error
Error 400: invalid_request

or

Access blocked: This app’s request is invalid
Error 400: redirect_uri_mismatch

The Authorized redirect URI was not configured or not entered correctly.

Go to your Google Cloud Console project, APIs & Services > Credentials and select the OAuth 2.0 Client ID that was created for this site connection. Make sure that the URL that is shown after the text “The redirect URI for your Google Cloud Console OAuth 2.0 client configuration should be: …” in your WordPress admin (on the Google Search Console Connection page) is listed there under Authorized redirect URIs in Google Cloud Console.

It should match exactly, including http or https and www or non-www.

Failed to refresh Google access token (HTTP 401): Unauthorized

or

OAuth token exchange failed: Unauthorized

There was a mismatch between your Cloud Console Client ID and Client Secret or the Client Secret encryption/decryption went wrong. This can happen when the WordPress Salts were changed by you or by a security plugin.

If you saved your credentials after the initial creation in Google Cloud Console, then carefully copy/paste them both into the form fields again and hit Save Settings. Then try connecting again.

If the problem persists, or if you did not save your Client Secret somewhere, then you will have to create new credentials. Go to your Google Cloud Console project, APIs & Services > Credentials and select the OAuth 2.0 Client ID that was created for this site connection. Hit + Add secret to create a new Client Secret. You may disable and delete the old client secret for safety.

Access blocked: … has not completed the Google verification process
Error 403: access_denied

or

Access blocked: Project can only be used within its organization
Error 403: org_internal

In both cases, you are trying to finish the connection with another account than the one with which the Cloud project was created. This is possible but needs a little more tweaking and attention.

Go to the Google Cloud console, select the project and go to API & Services > OAuth Consent Screen and choose Audience.

• If the User type is set to Internal here, then Make external and choose In production.
• If the Publishing status is Testing here, then Publish app and Confirm.

Workspace users have the option to keep the app Internal if the account that will finish the site connection is a member of the same organization.

Google API Error (HTTP 403): Google Search Console API has not been used in project … before or it is disabled

In your Cloud Console, with the correct Project selected, Go to API & Services > Library, search for Google Search Console API and Enable it. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.

Google API Error (HTTP 403): User does not have sufficient permission for site…

Go to Google Search Console, log in, go to the Settings > Users and rights under the relevant Property. Make sure the user that signed in during the Google Cloud Console authorization process is listed there and is either (Verified) Owner or has Full rights.

If you are not sure which user was used to finalize the connection, you can disconnect and reconnect your site, using an account that is listed with enough rights. Go to your WordPress admin Settings > Google News and click the button Disconnect from Google Search Console on the right. Then after the page reloads, click the button Connect and then follow the last step

The requested URL was not found on this server. That’s all we know.

You are trying to connect with an OAuth Client ID that does not exist (anymore) on Google Cloud Console. Verify your credentials and maybe create new ones and configure them in the plugin settings again.

To return to the Stage I and II descriptions in your admin, remove the faulty Client ID and save settings. You’ll then be able to follow the steps again. Make sure to copy/paste the complete Client ID and Client secret.

You either finalized (stage iii) the connection with an account that does not have sufficient rights to access the site property in Google Search Console, or the property is not fully set up in your Google Search Console.

Go to Google Search Console and select your site property. If it’s not yet configured or property ownership is not yet verified, complete the steps as given there to finish the property setup. Then, make sure the connected user account has full access to the property. Go to the property Settings > Users and rights. The user account that you wish to use for the site connection should have at least Full rights.

If you wish to change the user account that is used for the site connection, go in your WordPress admin to Settings > XML Sitemap. Use the Disconnect button to release the current connection. The Google Cloud projet settings will not be deleted and can be used to reconnect to Search Console with another account.

When fetching sitemap data for the first time, the plugin tries to find a matching domain property in Google Search Console. Something went wrong trying to determine the correct domain from the WordPress site/home URL.

If this happens, please contact us.

When the access token is about to expire, the plugin tries to get a fresh one using the refresh token that was obtained during the site connection. Something in this proces has gone wrong.

Refresh your page and if the error remains, you’ll need to Disconnect and reconnect your site to obtain a new refresh and access tokens.

Go to Google Search Console and select your site property. If it’s not yet configured or property ownership is not yet verified, complete the steps as given there to finish the property setup. Then, make sure the connected user account has full access to the property. Go to the property Settings > Users and rights. The user account that you wish to use for the site connection should have at least Full rights.