Google Search Console

Ownership and availability#

You retain ownership of the Search Console property. Obelo manages OAuth and stores encrypted refresh credentials server-side.

Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.

Before you connect#

• A Google account with verified owner or full-user access to the property
• The property should represent the same site configured in Obelo
• An Obelo workspace owner or admin must authorize Google access

Connect an existing account#

1. Open the provider in Settings → Integrations for the intended website.
2. Authorize Obelo with the Google account that can access the property
3. Choose the verified Search Console property from the returned list
4. Start the first sync and wait for stored search-performance data

If you need a new resource#

1. Add the website in Search Console as a Domain or URL-prefix property
2. Complete Google's DNS, file, tag, or Analytics verification
3. Confirm the property appears in Search Console before returning

Permissions to check#

• Obelo requests read-only Search Console access
• Property verification and user permissions are managed in Google, not Obelo

Verify and troubleshoot#

Once verification is complete, return and reload the property list.

Google returned no verified Search Console properties. Add or verify the site, or switch to a Google account with property access, then check again.

Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.

Disconnect or change access#

Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.